@techreport{ietf-v6ops-nat64-wkp-1918-06,
    number =    {draft-ietf-v6ops-nat64-wkp-1918-06},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-wkp-1918/06/},
    author =    {Warren Kumari and Jen Linkova},
    title =     {{Using the Well-Known IPv6 Prefix to Represent Non-Global IPv4 Addresses}},
    pagetotal = 11,
    year =      2026,
    month =     aug,
    day =       4,
    abstract =  {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 ("Restrictions on the Use of the Well-Known Prefix") to allow packets in which an address is composed of the Well-Known Prefix and specific non-globally reachable IPv4 addresses to be translated.},
}