…presentation Flexibility of RFC 4291 Examples of flexibility in Section 2.2 of [RFC4291] are described below. 2.1 . Leading Zeros in a 16-Bit Field 'It is not necessary to write the leading zeros in an individual field.' Conversely, it is also not necessary to omit leading zeros.…

…ess block (0.0.0.0/8) to represent the local (i.e., "this") network. Likewise, [RFC4291] reserves an IPv6 address block (fe80::/10) to represent link-scoped unicast addresses. Periodically, the IETF publishes an RFC that catalogs special-purpose address blocks. Currently, [RFC573…

…ss block (0.0.0.0/8) to represent the local (i.e., "this") network. Likewise, [ RFC4291 ] reserves an IPv6 address block (fe80::/10) to represent link-scoped unicast addresses. Periodically, the IETF publishes an RFC that catalogs special-purpose address blocks. Currently, [ RFC5…

…handle both "AAAA" and "A" records, for clients on IPv4-mapped IPv6 addresses [ RFC4291 ]. IPv4 <ip> addresses are only listed in an SPF record using the "ip4" mechanism. Several mechanisms rely on information fetched from the DNS. For these DNS queries, except where noted, if th…

…IID) that typically embeds a hardware address (e.g., an IEEE LAN MAC address) [ RFC4291 ]. Cryptographically Generated Addresses (CGAs) [ RFC3972 ] are yet another method for generating Interface Identifiers; CGAs bind a public signature key to an IPv6 address in the SEcure Neigh…

…ted work in IPv6 that an implementer would be best served to study includes - [ RFC4291 ] ("IP Version 6 Addressing Architecture") - [ RFC4862 ] ("IPv6 Stateless Address Autoconfiguration") - [ RFC4861 ] ("Neighbor Discovery for IP version 6 (IPv6)") Mrugalski, et al. Standards T…

…IID) that typically embeds a hardware address (e.g., an IEEE LAN MAC address) [ RFC4291 ]. Cryptographically Generated Addresses (CGAs) [ RFC3972 ] are yet another method for generating Interface Identifiers; CGAs bind a public signature key to an IPv6 address in the SEcure Neigh…

::1/128 Loopback Address [ RFC4291 ] 2006-02 N/A False False False False True ::/128 Unspecified Address [ RFC4291 ] 2006-02 N/A True False False False True ::ffff:0:0/96 IPv4-mapped Address [ RFC4291 ] 2006-02 N/A False False False False True 64:ff9b::/96 IPv4-IPv6 Translat. [ R…

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…