Following Ipv6 addressed are not being allowed by the IoTDM as valid address. "Fadf:ddd0::/32","::/1","FE80::1" etc.

CIDR suffixed, or with special character (: etc are not being recognized a valid ipv6 address by IoTDM.

Steps to recreate -

1) when i am trying to set the following value of ACP:
"pv":{"acr":[{"acor" : ["admin"],"acop":35,"acco":[{"acip":{"ipv6":["Fadf:ddd0::/32","::/1","FE80::1","2001:db8:0:0:0:ff00:42:8329"]}}]},

{"acor" : ["admin"],"acop":35}

]},"pvs":{"acr":[{"acor" : ["admin"],"acop":7,"acco":[{"acip":{"ipv6":["::/1","2001:db8:0:0:0:ff00:42:8329"]}}]},

{"acor" : ["admin"],"acop":9}

]}

2) I am seeing following error message.
Cannot update this resource [400] :

{"error":"PRIVILEGES(ipv6) : Fadf:ddd0::/32 is not a valid Ipv6 address."}

Actual behavior -
IoTDM is not allowing to set the CIDR suffixed ipv6 address (or subnet ip) for the element "accessControlContext/accessControlIpAddresses/ipv6Addresses"
under ACP resource.

Expected behavior -

As per spec TS-0004: "accessControlContext/accessControlIpAddresses/ipv6Addresses" is the list of type - m2m:ipv6

Table (Table 6.3.3-1) m2m:ipv6
IPv6 address string with optional CIDR suffix ::/0, Fadf:ddd0::/32, abcd:ffff:abb0:aaaa::/64

We need to correct this behavior and allow supporting of subnet (CIDR based suffixed) based IPv6 address while creating ACP resource with IPv6 address.