<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-v6ops-rfc6146-bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-rfc6146-bis-13">
   <front>
      <title>Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers</title>
      <author initials="M." surname="Bagnulo" fullname="Marcelo Bagnulo">
         <organization>UC3M</organization>
      </author>
      <author initials="P." surname="Matthews" fullname="Philip Matthews">
         </author>
      <author initials="J. P." surname="Martinez" fullname="Jordi Palet Martinez">
         <organization>The IPv6 Company</organization>
      </author>
      <date month="August" day="6" year="2026" />
      <abstract>
	 <t>   This document specifies a stateful NAT64 translation, which allows
   IPv6-Only clients to contact IPv4 servers using unicast UDP, TCP, or
   ICMP.  One or more public IPv4 addresses assigned to a stateful NAT64
   translator are shared among several IPv6-Only clients.  Stateful
   NAT64 translation also supports IPv4-initiated communications to a
   subset of the IPv6 hosts through statically configured bindings in
   the stateful NAT64 translator.  When the stateful NAT64 translation
   is used in conjunction with DNS64, no changes are required in either
   the IPv6 client or the IPv4 server.

   This document obsoletes RFC 6146.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-v6ops-rfc6146-bis-13" />
   
</reference>
