…luded in the candidate addresses. o Deprecated IPv4-compatible IPv6 addresses [ RFC4291 ] and IPv6 site- local unicast addresses [ RFC3879 ] MUST NOT be included in the address candidates. o IPv4-mapped IPv6 addresses SHOULD NOT be included in the address candidates unless the ap…

…ss block (0.0.0.0/8) to represent the local (i.e., "this") network. Likewise, [ RFC4291 ] reserves an IPv6 address block (fe80::/10) for link-local unicast addresses. Several issues have been raised with the documentation of some of the special-purpose address blocks in [ RFC6890…

…onform with the IPv6 global unicast address format defined in Section 2.5.4 of [RFC4291] since they do not have a 64-bit Interface ID formatted as described in Section 2.5.1. of [RFC4291]. 3. Routing Considerations ORCHIDs are designed to serve as location independent endpoint- i…

0000:0000:0000:0000 Subnet-Router Anycast [ RFC4291 ] 2008-12-24 0200:5EFF:FE00:0000-0200:5EFF:FE00:5212 Reserved IPv6 Interface Identifiers corresponding to the IANA Ethernet Block [ RFC4291 ] 0200:5EFF:FE00:5213 Proxy Mobile IPv6 [ RFC6543 ] 0200:5EFF:FE00:5214-0200:5EFF:FEFF:F…

…onform with the IPv6 global unicast address format defined in Section 2.5.4 of [RFC4291] since they do not have a 64-bit Interface ID formatted as described in Section 2.5.1. of [RFC4291] . 3 . Routing and Forwarding Considerations ORCHIDs are designed to serve as location-indepe…

…onform with the IPv6 global unicast address format defined in Section 2.5.4 of [RFC4291] since they do not have a 64-bit Interface ID formatted as described in Section 2.5.1. of [RFC4291] . 3 . Routing and Forwarding Considerations ORCHIDs are designed to serve as location-indepe…

…onform with the IPv6 global unicast address format defined in Section 2.5.4 of [RFC4291] since they do not have a 64-bit Interface ID formatted as described in Section 2.5.1. of [RFC4291] . 3 . Routing Considerations ORCHIDs are designed to serve as location independent endpoint-…

0000:0000:0000:0000 Subnet-Router Anycast [ RFC4291 ] 2008-12-24 0200:5EFF:FE00:0000-0200:5EFF:FE00:5212 Reserved IPv6 Interface Identifiers corresponding to the IANA Ethernet Block [ RFC4291 ] 0200:5EFF:FE00:5213 Proxy Mobile IPv6 [ RFC6543 ] 0200:5EFF:FE00:5214-0200:5EFF:FEFF:F…

…onform with the IPv6 global unicast address format defined in Section 2.5.4 of [RFC4291] since they do not have a 64-bit Interface ID formatted as described in Section 2.5.1. of [RFC4291] . 3 . Routing Considerations ORCHIDs are designed to serve as location independent endpoint-…

…l typically represent IPv4 systems. The IPv6 nodes may use any IPv6 addresses [ RFC4291 ] except in that range. A stateful IP/ICMP translator continuously maintains a dynamic translation table containing bindings between the IPv4 and IPv6 addresses, and likely also the Layer-4 id…

…luded in the candidate addresses. o Deprecated IPv4-compatible IPv6 addresses [ RFC4291 ] and IPv6 site- local unicast addresses [ RFC3879 ] MUST NOT be included in the address candidates. o IPv4-mapped IPv6 addresses SHOULD NOT be included in the address candidates unless the ap…

…l typically represent IPv4 systems. The IPv6 nodes may use any IPv6 addresses [ RFC4291 ] except in that range. A stateful IP/ICMP translator continuously maintains a dynamic translation table containing bindings between the IPv4 and IPv6 addresses, and likely also the Layer-4 id…

…luded in the candidate addresses. o Deprecated IPv4-compatible IPv6 addresses [ RFC4291 ] and IPv6 site- local unicast addresses [ RFC3879 ] MUST NOT be included in the address candidates. o IPv4-mapped IPv6 addresses SHOULD NOT be included in the address candidates unless the ap…

…a list of 8 16-bit unsigned integers , also known as an IPv6 address ’s pieces [RFC4291] Support for <zone_id> is intentionally omitted An opaque host is a non-empty ASCII string that can be used for further processing. An empty host is the empty string. 3.2. Host miscellaneous f…

…nes an extension to the multicast portion of the IPv6 addressing architecture [ RFC4291 ]. The current architecture does not contain any built-in support for dynamic address allocation. The extension allows for use of IIDs to allocate multicast addresses. When a link-local unicas…