<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-v6ops-nat64-wkp-1918" target="https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-nat64-wkp-1918-06">
   <front>
      <title>Using the Well-Known IPv6 Prefix to Represent Non-Global IPv4 Addresses</title>
      <author initials="W." surname="Kumari" fullname="Warren Kumari">
         <organization>Google, LLC</organization>
      </author>
      <author initials="J." surname="Linkova" fullname="Jen Linkova">
         <organization>Google, LLC</organization>
      </author>
      <date month="August" day="4" year="2026" />
      <abstract>
	 <t>   This document modifies the requirement introduced in Section 3.1 of
   RFC6052 that IPv4/IPv6 Translators MUST NOT use the Well-Known Prefix
   64:ff9b::/96 to represent non-globally reachable IPv4 addresses, such
   as those defined in RFC1918 or listed in Section 2.2.2 of RFC6890.
   The proposed change enables IPv6-only nodes to reach IPv4-only
   services with specific non-globally reachable addresses by leveraging
   the Well-Known Prefix.

   This document updates Section 3.1 of RFC6052 (&quot;Restrictions on the
   Use of the Well-Known Prefix&quot;) to allow packets in which an address
   is composed of the Well-Known Prefix and specific non-globally
   reachable IPv4 addresses to be translated.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-v6ops-nat64-wkp-1918-06" />
   
</reference>
