[IOTDM-68] Compliance - IoTDM is not allowing CIDR suffixed Ipv6 address for "acco/acip/ipv6" element under ACP resource Created: 06/Mar/17 Updated: 19/Oct/17 |
|
| Status: | Open |
| Project: | iotdm |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Anil Pandey | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 7903 |
| Description |
|
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 (: Steps to recreate - 1) when i am trying to set the following value of ACP: ]},"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. Actual behavior - 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 We need to correct this behavior and allow supporting of subnet (CIDR based suffixed) based IPv6 address while creating ACP resource with IPv6 address. |