Restrictions on IPv6 addresses configured in the TCP/IP profile

The following IPv6 addresses are not accepted for ipaddr_spec:

  • Link local IP addresses
  • Multicast IP addresses
  • IPv4-mapped IPv6 addresses
  • Addresses with the reserved prefix ::/96
  • Default loopback address (::1)
  • Unspecified address (::)
  • Any address where bit 6 (the universal/local flag - 'U' bit) or bit 7 (the group/individual flag - 'G' bit) of the Interface ID portion is nonzero.
    The Interface ID portion is the lower 64 bits of the address. The Interface ID bit positions are numbered 0 - 63. This is shown in the following code example:
    |               1|1              3|3              4|4              6|
    |0              5|6              1|2              7|8              3|
    +----------------+----------------+----------------+----------------+
    |xxxxxxUGxxxxxxxx|xxxxxxxxxxxxxxxx|xxxxxxxxxxxxxxxx|xxxxxxxxxxxxxxxx|
    +----------------+----------------+----------------+----------------+
  • ISATAP address ( '00005EFE'x in bits 0 - 31 of the Interface ID portion of the address).
  • Reserved Anycast address (Non-multicast format prefix 001 - - 111 and 'FCFFFFFFFFFFFF8'x in bits 0 - 56 of the Interface ID portion of the address. The format prefix is the bit string consisting of the first 3 bits of the address.)
  • A site-local address that has any value other than 0 in bits 10 - 47 of the address. (A site-local address has 1111111011 in bits 0 - 9 of the address.)

    Guideline: Site-local addresses were designed to use private address prefixes that could be used within a site without the need for a global prefix. Until recently, the full negative impacts of site-local addresses in the Internet were not fully understood. Because of problems in the use and deployment of addresses constructed using a site-local prefix, the IETF has deprecated the special treatment given to the site-local prefix. An IPv6 address constructed using a site-local prefix is now being treated as a global unicast address. The site-local prefix might be reassigned for other use by future IETF standards action.

    You should not use site-local unicast addresses. Instead of site-local addresses, you should use global unicast addresses.