…ETF publishes an RFC that catalogs special-purpose address blocks. Currently, [ RFC5735 ] catalogs all IPv4 special- purpose address blocks and [ RFC5156 ] catalogs all IPv6 special- purpose address blocks. [ RFC5736 ] assigns an IPv4 address block (192.0.0.0/24) to IANA and inst…

…IETF publishes an RFC that catalogs special-purpose address blocks. Currently, [RFC5735] catalogs all IPv4 special- purpose address blocks and [RFC5156] catalogs all IPv6 special- purpose address blocks. [RFC5736] assigns an IPv4 address block (192.0.0.0/24) to IANA and instructs…

…ETF publishes an RFC that catalogs special-purpose address blocks. Currently, [ RFC5735 ] catalogs all IPv4 special- purpose address blocks and [ RFC5156 ] catalogs all IPv6 special- purpose address blocks. [ RFC5736 ] assigns an IPv4 address block (192.0.0.0/24) to IANA and inst…

…s 192.0.2.33 is part of the subnet 192.0.2.0/24 reserved for documentation in [ RFC5735 ]. The representation of IPv6 addresses is compatible with [ RFC5952 ]. 3 . Deployment Guidelines 3.1 . Restrictions on the Use of the Well-Known Prefix The Well-Known Prefix MUST NOT be used …

…ture, as described in Section 3 . 2 . IANA IPv4 Special Purpose Address Block [ RFC5735 ] records the assignment of an IPv4 address prefix to IANA for IETF protocol assignments. 192.0.0.0/24 - This block is reserved for IETF protocol assignments. This address allocation to IANA i…

…s 192.0.2.33 is part of the subnet 192.0.2.0/24 reserved for documentation in [ RFC5735 ]. The representation of IPv6 addresses is compatible with [ RFC5952 ]. . Deployment Guidelines 3.1 . Restrictions on the Use of the Well-Known Prefix The Well-Known Prefix MUST NOT be used to…

… and Routing Parameter Area Domain ("arpa")", BCP 52 RFC 3172 , September 2001. RFC5735 ] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses", RFC 5735 , January 2010. RFC6144 ] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for IPv4/IPv6 Translation", RFC 6144 , April 201…

…for AAAA record synthesis. This allows handling of special use IPv4 addresses [ RFC5735 ]. DNS messages contain several sections. The portion of a DNS message that is altered by DNS64 is the answer section, which is discussed below in Section 5.1 . The resulting synthetic answer …

…for AAAA record synthesis. This allows handling of special use IPv4 addresses [ RFC5735 ]. DNS messages contain several sections. The portion of a DNS message that is altered by DNS64 is the answer section, which is discussed below in Section 5.1 . The resulting synthetic answer …

…tching the document if the IP address is within the loopback range defined by [ RFC5735 ] or any other implementation-specific internal IP address. 4.2.1 Client Metadata This section is based on [ ClientIDMetadataDocument ], and is included here for convenience, but the normative…

…l IPv4 addresses, such as those defined in [RFC1918] or listed in Section 3 of [RFC5735]. Address translators MUST NOT translate packets in which an address is composed of the Well-Known Prefix and a non- global IPv4 address; they MUST drop these packets. It should say: The parag…

…l IPv4 addresses, such as those defined in [RFC1918] or listed in Section 3 of [RFC5735]. Address translators MUST NOT translate packets in which an address is composed of the Well-Known Prefix and a non- global IPv4 address; they MUST drop these packets. It should say: The parag…