…3 . Introduction As part of the transition to IPv6, NAT64 [ RFC6146 ] and DNS64 RFC6147 ] technologies will be utilized by some access networks to provide IPv4 connectivity for IPv6-only nodes [ RFC6144 ]. DNS64 utilizes IPv6 address synthesis to create local IPv6 addresses for p…

…aL3h75K0EHgKpJloYLg8/ 3734328 2247411 [DNSOP] Re: (Concluded) RE: Moving DNS64 (RFC6147) to Internet Standard [DNSOP] Re: (Concluded) RE: Moving DNS64 (RFC6147) to Internet Standard jordi.palet@consulintel.es 2026-04-24 dnsop /arch/msg/dnsop/PxMtWzSO4Xdz0fRFZi-ZPPNnRGQ/ 3734327 2…

…ffect the responses it gets to its queries. For example, in the case of DNS64 [ RFC6147 ], the choice could affect whether IPv6/IPv4 translation will work at all. The HTTPS channel used by this specification establishes secure two- party communication between the DoH client and t…

… an IPv6-only agent is in a network that utilizes NAT64 [ RFC6146 ] and DNS64 [ RFC6147 ] technologies, it may also gather IPv4 server- reflexive and/or relayed candidates from IPv4-only STUN or TURN servers. IPv6-only agents SHOULD also utilize IPv6 prefix discovery [ RFC7050 ] …

… an IPv6-only agent is in a network that utilizes NAT64 [ RFC6146 ] and DNS64 [ RFC6147 ] technologies, it may also gather IPv4 server- reflexive and/or relayed candidates from IPv4-only STUN or TURN servers. IPv6-only agents SHOULD also utilize IPv6 prefix discovery [ RFC7050 ] …

…onses to AAAA queries for names that only have an A record ( Section 5.1.7 of [ RFC6147 ). SVCB-aware DNS64 resolvers SHOULD apply the same synthesis logic when resolving AAAA records for the TargetName for inclusion in the Additional section (Step 2 in Section 4.2 ) and MAY omit…

…ransparent to client devices. The combined use of NAT64 [ RFC6146 ] and DNS64 [ RFC6147 ] is a popular solution that is being deployed and requires changes in client devices. One possible way to handle these networks is for the client device networking stack to implement 464XLAT …

…onses to AAAA queries for names that only have an A record ( Section 5.1.7 of [ RFC6147 ). SVCB-aware DNS64 resolvers SHOULD apply the same synthesis logic when resolving AAAA records for the TargetName for inclusion as Additionals (Step 2 in Section 4.2 ), and MAY omit the Addit…

…onses to AAAA queries for names that only have an A record ( Section 5.1.7 of [ RFC6147 ). SVCB-aware DNS64 resolvers SHOULD apply the same synthesis logic when resolving AAAA records for the TargetName for inclusion as Additionals (Step 2 in Section 4.2 ), and MAY omit the Addit…

… For example: A. As part of the transition to IPv6, NAT64 [ RFC6146 ] and DNS64 RFC6147 ] technologies will be utilized by some access networks to provide IPv4 connectivity for IPv6-only nodes RFC6144 ]. B. Note that SAVI raises a number of important privacy considerations that a…