Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
IPv6 transition mechanism
open-in-new
<h2 id="stateless-ipicmp-translation">Stateless IP/ICMP Translation</h2> <p>Stateless IP/<a href="/facts/Internet_Control_Message_Protocol/VnrV56J0">ICMP</a> Translation (SIIT) translates between the packet header formats in <a href="/facts/IPv6/d4dg7kIL">IPv6</a> and <a href="/facts/IPv4/bnQ5MEqm">IPv4</a>.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> The SIIT method defines a class of IPv6 addresses called <i>IPv4-translated</i> addresses.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> They have the prefix <i>::ffff:0:0:0/96</i> and may be written as <i>::ffff:0:a.b.c.d</i>, in which the IPv4 formatted address <i>a.b.c.d</i> refers to an <i>IPv6-enabled</i> node. The prefix was chosen to yield a zero-valued <a href="/facts/Checksum/AqxQ0I8g">checksum</a> to avoid changes to the transport protocol header checksum.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> The algorithm can be used in a solution that allows IPv6 hosts that do not have a permanently assigned IPv4 address to communicate with IPv4-only hosts. Address assignment and routing details are not addressed by the specification. SIIT can be viewed as a special case of stateless <a href="/facts/Network_address_translation/nFweFNfN">network address translation</a>. </p><p>The specification is a product of the NGTRANS IETF working group, and was initially drafted in February 2000 by E. Nordmark of <a href="/facts/Sun_Microsystems/VJ9EzEFd">Sun Microsystems</a>.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> It was revised in 2011,<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> and in 2016 its current revision was published.<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a> </p> <h2 id="tunnel-broker">Tunnel broker</h2> <p>A <a href="/facts/Tunnel_broker/Vvw0NSGc">tunnel broker</a> provides IPv6 connectivity by encapsulating IPv6 traffic in IPv4 Internet transit links, typically using <a href="/facts/6in4/yzjhTMwq">6in4</a>. This establishes IPv6 tunnels within the IPv4 Internet. The tunnels may be managed with the <a href="/facts/Tunnel_Setup_Protocol/uLQAx0C6">Tunnel Setup Protocol</a> (TSP)<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a> or <a href="/facts/AYIYA/G3kJxWfm">AYIYA</a>.<a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a> </p> <h2 id="6rd">6rd</h2> <p class="note">Main article: <a href="/facts/IPv6_rapid_deployment/loyVutqb">IPv6 rapid deployment</a></p> <p>6rd was developed by <a href="/facts/R%C3%A9mi_Despr%C3%A9s/szTyWDxc">Rémi Després</a>. It is a mechanism to facilitate rapid deployment of the IPv6 service across <a href="/facts/IPv4/bnQ5MEqm">IPv4</a> infrastructures of Internet service providers (<a href="/facts/Internet_service_provider/dUacAxef">ISPs</a>). It uses stateless address mappings between <a href="/facts/IPv4/bnQ5MEqm">IPv4</a> and <a href="/facts/IPv6/d4dg7kIL">IPv6</a> addresses, and transmits <a href="/facts/IPv6/d4dg7kIL">IPv6</a> packets across automatic tunnels that follow the same optimized routes between customer nodes as <a href="/facts/IPv4/bnQ5MEqm">IPv4</a> packets. </p><p>It was used for an early large deployment of an IPv6 service with native addresses during 2007 (RFC 5569<a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a>). The standard-track specification of the protocol is in RFC 5969.<a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a> </p> <h2 id="transport-relay-translation">Transport Relay Translation</h2> <p>RFC 3142 defines the Transport Relay Translation (TRT) method. TRT acts as an intermediate device between two hosts. The function of the translator is to convert IPV6 into IPV4 addresses and vice versa. TRT accomplishes this translation through IP address mapping and a custom IP address.<a class="footnote-ref" id="fnref:12" href="#fn:12"><sup>12</sup></a> </p><p>The address, for example, if packets are to be transmitted from an IPv6 address (fec0:0:0:1::/64) to an IPV4 address (10.1.1.1) would read as fec0:0:0:1::10.1.1.1. The packets are routed towards the translator firstly through an IPv6/TCP protocol and then from the translator to the IPv4 host through an IPv4/TCP protocol.<a class="footnote-ref" id="fnref:13" href="#fn:13"><sup>13</sup></a> </p><p>TRT employs a similar operation to DNS translation between AAAA and A records known as <i>DNS-ALG</i> as defined in RFC 2694.<a class="footnote-ref" id="fnref:14" href="#fn:14"><sup>14</sup></a> </p> <h2 id="nat64">NAT64</h2> <p class="note">Main article: <a href="/facts/NAT64/ePpAojmB">NAT64</a></p> <p><a href="/facts/NAT64/ePpAojmB">NAT64</a> is a mechanism to allow IPv6 hosts to communicate with IPv4 servers. The NAT64 server is the endpoint for at least one IPv4 address and an IPv6 network segment of 32-bits, e.g., <i>64:ff9b::/96</i>.<a class="footnote-ref" id="fnref:15" href="#fn:15"><sup>15</sup></a> The IPv6 client embeds the IPv4 address with which it wishes to communicate using these bits, and sends its packets to the resulting address. The NAT64 server then creates a <a href="/facts/Network_address_translation/nFweFNfN">NAT</a>-mapping between the IPv6 and the IPv4 address, allowing them to communicate.<a class="footnote-ref" id="fnref:16" href="#fn:16"><sup>16</sup></a> </p> <h2 id="dns64">DNS64</h2> <p>DNS64 describes a <a href="/facts/DNS_server/pUgmBMNW">DNS server</a> that when asked for a domain's <a href="/facts/AAAA_record/CgzuvJXy">AAAA records</a>, but only finds <a href="/facts/A_record/CgzuvJXy">A records</a>, synthesizes the AAAA records from the A records. The first part of the synthesized IPv6 address points to an IPv6/IPv4 translator and the second part embeds the IPv4 address from the A record. The translator in question is usually a NAT64 server. The standard-track specification of DNS64 is in RFC 6147.<a class="footnote-ref" id="fnref:17" href="#fn:17"><sup>17</sup></a> </p><p>There are two noticeable issues with this transition mechanism: </p> <ul><li>It only works for cases where DNS is used to find the remote host address, if IPv4 literals are used the DNS64 server will never be involved.</li> <li>Because the DNS64 server needs to return records not specified by the domain owner, <a href="/facts/DNSSEC/cL9zwhjj">DNSSEC</a> validation against the <a href="/facts/DNSSEC/cL9zwhjj">root</a> will fail in cases where the DNS server doing the translation is not the domain owner's server.</li></ul> # DNS resolver 2606:4700:4700:64 synthesizes AAAA records for # ipv6test.google.com to a NAT64 address: 64:ff9b::<original-ipv4> $ nslookup ipv6test.google.com 2606:4700:4700::64 Non-authoritative answer: ipv6test.google.com canonical name = ipv6test.l.google.com. Name: ipv6test.l.google.com Address: 64:ff9b::8efa:c3e4 Implementations <ul><li><a href="/facts/Unbound_(DNS_server)/0WeDyewu">Unbound</a> dns server via the dns64 module <a class="footnote-ref" id="fnref:18" href="#fn:18"><sup>18</sup></a></li> <li><a href="/facts/OpenWrt/3VYxerTY">OpenWrt</a> via unbound opkg packages.</li></ul> <h2 id="isatap">ISATAP</h2> <p class="note">Main article: <a href="/facts/ISATAP/MTA5JFp5">ISATAP</a></p> <p>ISATAP (Intra-Site Automatic Tunnel Addressing Protocol) is an IPv6 transition mechanism meant to transmit IPv6 packets between dual-stack nodes on top of an IPv4 network. </p><p>Unlike 6over4 (an older similar protocol using IPv4 multicast), ISATAP uses IPv4 as a virtual nonbroadcast multiple-access network (NBMA) data link layer, so that it does not require the underlying IPv4 network infrastructure to support multicast. </p> <h2 id="464xlat">464XLAT</h2> <p>464XLAT (RFC 6877) allows clients on IPv6-only networks to access IPv4-only Internet services.<a class="footnote-ref" id="fnref:19" href="#fn:19"><sup>19</sup></a><a class="footnote-ref" id="fnref:20" href="#fn:20"><sup>20</sup></a> </p><p>The client uses a SIIT translator to convert packets from IPv4 to IPv6. These are then sent to a <a href="/facts/NAT64/ePpAojmB">NAT64</a> translator which translates them from IPv6 back into IPv4 and on to an IPv4-only server. The client translator may be implemented on the client itself or on an intermediate device and is known as the CLAT (Customer-side transLATor). The NAT64 translator, or PLAT (Provider-side transLATor), must be able to reach both the server and the client (through the CLAT). The use of NAT64 limits connections to a client-server model using UDP, TCP, and ICMP. </p> Implementations <ul><li><a href="/facts/T-Mobile_US/tRY9PLtF">T-Mobile US</a> became IPv6-only using 464XLAT.<a class="footnote-ref" id="fnref:21" href="#fn:21"><sup>21</sup></a></li> <li><a href="/facts/Orange_Polska/J37VkLQd">Orange Polska</a> began IPv6-only (CLAT/NAT64/DNS) service in September 2013, migrating all <a href="/facts/ADSL/Y5wsglVy">ADSL</a>, <a href="/facts/VDSL/HXABSD2c">VDSL</a>, and <a href="/facts/Fiber_to_the_x/YaokmYnc">FTTH</a> gateways by January 2015.<a class="footnote-ref" id="fnref:22" href="#fn:22"><sup>22</sup></a></li> <li><a href="/facts/Telstra/tm3J2MTK">Telstra</a> became IPv6-only for mobile services using 464XLAT in February 2020.<a class="footnote-ref" id="fnref:23" href="#fn:23"><sup>23</sup></a></li> <li><a href="/facts/Android_(operating_system)/nNyHb0xz">Android</a> includes a native implementation of CLAT since <a href="/facts/Android_Jelly_Bean/I6cvSzx3">Jelly Bean</a> 4.3, released in 2013.<a class="footnote-ref" id="fnref:24" href="#fn:24"><sup>24</sup></a></li> <li><a href="/facts/Windows_10/be9IHehJ">Windows 10</a> has a native WWAN-only implementation of 464XLAT for desktop and mobile since the <a href="/facts/Windows_10_version_1703/waK3joRl">2017 Creators Update</a>.<a class="footnote-ref" id="fnref:25" href="#fn:25"><sup>25</sup></a></li> <li><a href="/facts/Windows_11/J2ywV8r4">Windows 11</a> (24H2) has the same implementation as Windows 10. A future version will extend CLAT support to other network devices (currently limited to WWAN). The implementation will use RFC 7050 (ipv4only.arpa DNS query), RFC 8781 (PREF64, and RFC 8925 (DHCP Option 108) standard <a class="footnote-ref" id="fnref:26" href="#fn:26"><sup>26</sup></a></li> <li><a href="/facts/MacOS/Y93vVpTm">macOS</a> starts to have native CLAT support in Ventura, released in 2022.<a class="footnote-ref" id="fnref:27" href="#fn:27"><sup>27</sup></a></li> <li><a href="/facts/IOS/mK5cggH5">iOS</a> has a native CLAT implementation since version 12.0, released in 2018.<a class="footnote-ref" id="fnref:28" href="#fn:28"><sup>28</sup></a> Additionally, Apple requires all apps submitted to the <a href="/facts/App_Store_(iOS)/0yqcGqey">App Store</a> to work on IPv6 networks.<a class="footnote-ref" id="fnref:29" href="#fn:29"><sup>29</sup></a></li> <li>clatd is a CLAT implementation for <a href="/facts/Linux/9FvCKSTq">Linux</a>.<a class="footnote-ref" id="fnref:30" href="#fn:30"><sup>30</sup></a></li> <li><a href="/facts/Network_Manager/FgD5xFP5">Network Manager</a> (WIP):<a class="footnote-ref" id="fnref:31" href="#fn:31"><sup>31</sup></a> :</li> <li><a href="/facts/OpenWRT/3VYxerTY">OpenWRT</a> linux OS for routers has optional support for clat via the 464xlat package <a class="footnote-ref" id="fnref:32" href="#fn:32"><sup>32</sup></a></li> <li><a href="/facts/FreeBSD/RKsFTm7F">FreeBSD</a> has implemented NAT64 CLAT since Release 12.1.<a class="footnote-ref" id="fnref:33" href="#fn:33"><sup>33</sup></a></li></ul> <h2 id="dual-stack-lite-ds-lite">Dual-Stack Lite (DS-Lite)</h2> <p class="note">"DS-Lite" redirects here. For the 2006 video game system, see <a href="/facts/Nintendo_DS_Lite/WP4UCDyw">Nintendo DS Lite</a>.</p> <p>Dual-Stack Lite technology does not involve allocating an IPv4 address to <a href="/facts/Customer-premises_equipment/dVGqvkWL">customer-premises equipment</a> (CPE) for providing Internet access.<a class="footnote-ref" id="fnref:34" href="#fn:34"><sup>34</sup></a> The CPE distributes <a href="/facts/Private_network/CqVdg83c">private IPv4 addresses</a> for the LAN clients, according to the networking requirement in the local area network. The CPE <a href="/facts/IP_tunnel/GW7aeJyI">encapsulates</a> IPv4 packets within IPv6 packets. The CPE uses its global IPv6 connection to deliver the packet to the ISP's <a href="/facts/Carrier-grade_NAT/e9QtbwmN">carrier-grade NAT</a> (CGN), which has a global IPv4 address. The original IPv4 packet is recovered and NAT is performed upon the IPv4 packet and is routed to the public IPv4 Internet. The CGN uniquely identifies traffic flows by recording the CPE public IPv6 address, the private IPv4 address, and TCP or UDP port number as a session. </p><p>Lightweight <a href="/facts/4over6/Hy16ER2I">4over6</a> extends DS-Lite by moving the NAT functionality from the ISP side to the CPE, eliminating the need to implement carrier-grade NAT.<a class="footnote-ref" id="fnref:35" href="#fn:35"><sup>35</sup></a> This is accomplished by allocating a port range for a shared IPv4 address to each CPE. Moving the NAT functionality to the CPE allows the ISP to reduce the amount of state tracked for each subscriber, which improves the scalability of the translation infrastructure. </p> <h2 id="v4-via-v6-routing">V4-via-v6 routing</h2> <p><i>V4-via-v6</i> routing<a class="footnote-ref" id="fnref:36" href="#fn:36"><sup>36</sup></a> is a technique where IPv4 addresses are assigned to end hosts only while intermediate routers are only assigned IPv6 addresses. IPv4 routes are propagated as usual, and no packet translation or encapsulation is employed, but use an IPv6 next hop. V4-via-v6 reduces the amount of management required, since the core network only needs to be assigned IPv6 addresses, but still requires that the core network be able to forward IPv4 packets. </p><p>V4-via-v6 is defined for the <a href="/facts/Border_Gateway_Protocol/XfYgBzW3">Border Gateway Protocol</a> (BGP)<a class="footnote-ref" id="fnref:37" href="#fn:37"><sup>37</sup></a> and the <a href="/facts/Babel_(protocol)/yq3GKoP0">Babel routing protocol</a>.<a class="footnote-ref" id="fnref:38" href="#fn:38"><sup>38</sup></a> It has been implemented the <a href="/facts/Bird_Internet_routing_daemon/zuFMMlMf">Bird Internet routing daemon</a><a class="footnote-ref" id="fnref:39" href="#fn:39"><sup>39</sup></a> and in <a href="/facts/Babel_(protocol)/yq3GKoP0"><i>babeld</i></a>.<a class="footnote-ref" id="fnref:40" href="#fn:40"><sup>40</sup></a> </p> <h2 id="map">MAP</h2> <p><a href="/facts/Mapping_of_Address_and_Port/tzz6rB5T">Mapping of Address and Port</a> (MAP) is a <a href="/facts/Cisco/ocDgQt6T">Cisco</a> <a href="/facts/IPv6_deployment/DAGWLDdS">IPv6 transition</a> proposal which combines <a href="/facts/A%2BP/kpk2j9Cl">A+P</a> port address translation with tunneling of the IPv4 packets over an ISP provider's internal <a href="/facts/IPv6/d4dg7kIL">IPv6</a> network.<a class="footnote-ref" id="fnref:41" href="#fn:41"><sup>41</sup></a> MAP-T<a class="footnote-ref" id="fnref:42" href="#fn:42"><sup>42</sup></a> and MAP-E<a class="footnote-ref" id="fnref:43" href="#fn:43"><sup>43</sup></a> entered standards track in July 2015, and Sky Italia has deployed MAP-T in its internet services as early as year 2021.<a class="footnote-ref" id="fnref:44" href="#fn:44"><sup>44</sup></a> </p> <h2 id="draft-proposals">Draft proposals</h2> <p>The following mechanisms are still being discussed or have been abandoned by the IETF: </p> <h3>4rd</h3> <p><a href="/facts/IPv4_Residual_Deployment_(4rd)/Jm7eaBmg">IPv4 Residual Deployment (4rd)</a> is an experimental mechanism<a class="footnote-ref" id="fnref:45" href="#fn:45"><sup>45</sup></a> to facilitate residual deployment of the IPv4 service across <a href="/facts/IPv6/d4dg7kIL">IPv6</a> networks. Like <a href="/facts/6rd/loyVutqb">6rd</a>, it uses stateless address mappings between <a href="/facts/IPv6/d4dg7kIL">IPv6</a> and <a href="/facts/IPv4/bnQ5MEqm">IPv4</a>. It supports an extension of IPv4 addressing based on transport-layer ports. This is a stateless variant of the <a href="/facts/Address_plus_Port/kpk2j9Cl">A+P</a> model. </p> <h2 id="deprecated-mechanisms">Deprecated mechanisms</h2> <p>These mechanisms have been deprecated by the IETF: </p> <h3>NAT-PT</h3> <p><i>Network Address Translation/Protocol Translation</i> (NAT-PT) is defined in RFC 2766, but due to numerous problems, it has been obsoleted by RFC 4966 and deprecated to historic status. It is typically used in conjunction with a <a href="/facts/Domain_Name_System/rfxdWFsj">DNS</a> <a href="/facts/Application-level_gateway/Bdj0UBXG">application-level gateway</a> (DNS-ALG) implementation. </p> <h3>NAPT-PT</h3> <p>While almost identical to NAT-PT, <i>Network Address Port Translation + Protocol Translation</i>, which is also described in RFC 2766, adds translation of the ports as well as the address. This is done primarily to avoid two hosts on one side of the mechanism from using the same exposed port on the other side of the mechanism, which could cause application instability and security flaws. This mechanism has been deprecated by RFC 4966. </p> <h2 id="implementations">Implementations</h2> <ul><li>stone (software), port translator for Windows & Unix-based systems.</li> <li>faithd, BSD-based static TRT implementation by the <a href="/facts/KAME_project/Bsbto2fH">KAME project</a></li> <li><a href="https://github.com/toreanderson/clatd">CLATD</a>, a CLAT / SIIT-DC Edge Relay implementation for Linux</li> <li><a href="https://www.semirocket.science/projects/wrapsix/">WrapSix</a>, a NAT64 implementation for Linux</li> <li><a href="http://www.litech.org/tayga">TAYGA</a>, a stateless NAT64 implementation for Linux</li> <li><a href="https://nicmx.github.io/Jool">Jool</a>, a SIIT and stateful NAT64 implementation for Linux</li> <li><a href="https://web.archive.org/web/20110506035248/http://tomicki.net/naptd.php">naptd</a>, user-level NAT-PT</li> <li><a href="http://ecdysis.viagenie.ca/">Ecdysis</a>, a NAT64 gateway, includes DNS64</li> <li><a href="https://downloads.isc.org/isc/aftr/">Address Family Transition Router (AFTR)</a>, a DS-Lite implementation</li> <li><a href="https://code.google.com/p/fabfi/wiki/niit">niit</a> Linux Kernel device that allow transmission of IPv4 unicast traffic through an IPv6 network</li> <li><a href="http://www.ivi2.org/IVI/">IVI</a> IPv4/IPv6 packet translation implementation as a Linux kernel(2.6 only) patch</li> <li><a href="/facts/Microsoft_Forefront_Unified_Access_Gateway/95UxcbhY">Microsoft Forefront Unified Access Gateway</a>, a reverse proxy and VPN solution that implements DNS64 and NAT64</li> <li><a href="/facts/BIND/Mj5qNIuW">BIND</a>, Berkeley Internet Name Domain DNS server, implements DNS64 since version 9.8</li> <li><a href="/facts/PF_(firewall)/pc1fgj4Y">PF (firewall)</a>, the <a href="/facts/OpenBSD/xmPS9tek">OpenBSD</a> packet filter supports IP version translation since version 5.1, includes NAT64</li></ul> <h2 id="see-also">See also</h2> <ul> <li>Internet portal</li></ul> <ul><li><a href="/facts/Comparison_of_IPv6_support_in_operating_systems/RqDH8Usn">Comparison of IPv6 support in operating systems</a></li> <li><a href="/facts/Softwire_(protocol)/MzIhA5bK">Softwire (protocol)</a></li></ul> <h2 id="external-links">External links</h2> <ul><li><i>IPv6 in Practice</i>, Benedikt Stockebrand (2006), <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 3-540-24524-3</li> <li>RFC <a href="https://datatracker.ietf.org/doc/html/rfc2767">2767</a>, <i>Bump-in-the-Stack</i></li> <li>RFC <a href="https://datatracker.ietf.org/doc/html/rfc3089">3089</a>, <i>Socks-based Gateway</i></li> <li>RFC <a href="https://datatracker.ietf.org/doc/html/rfc3338">3338</a>, <i>Bump-in-the-API</i></li> <li>RFC <a href="https://datatracker.ietf.org/doc/html/rfc6144">6144</a>, <i>Framework for IPv4/IPv6 Translation</i></li> <li>RFC <a href="https://datatracker.ietf.org/doc/html/rfc6219">6219</a>, <i>The China Education and Research Network (CERNET) IVI Translation Design and Deployment for the IPv4/IPv6 Coexistence and Transition</i></li> <li><a href="http://cr.yp.to/djbdns/ipv6mess.html">D. J. Bernstein – The IPv6 mess</a></li> <li><a href="https://web.archive.org/web/20070901003217/http://www.join.uni-muenster.de/Dokumente/Howtos/Howto_TRT.php?lang=en">Christian and Tina Strauf – Transport Relay Translator How To</a></li> <li><a href="/facts/International_Data_Group/WvwTlWHu"><i>Network World</i></a> – <a href="http://www.networkworld.com/community/node/46600">Understanding Dual-Stack Lite</a> <a href="https://web.archive.org/web/20111020091240/http://www.networkworld.com/community/node/46600">Archived</a> 2011-10-20 at the <a href="/facts/Wayback_Machine/nmQ3a6JC">Wayback Machine</a></li> <li><a href="/facts/Institution_of_Electronics_and_Telecommunication_Engineers/StV7328V"><i>IETE Technical Review</i></a> – <a href="https://www.tandfonline.com/doi/abs/10.4103/0256-4602.95384">Assuring Interoperability Between Heterogeneous (IPv4/IPv6) Networks Without using Protocol Translation</a></li> <li><i>KSII Transactions on Internet and Information Systems -</i> <a href="https://www.thefreelibrary.com/Configuring+hosts+to+auto-detect+(IPv6%2C+IPv6-in-IPv4%2C+or+IPv4)+network...-a0269432131">Configuring Hosts to Auto-detect (IPv6, IPv6-in-IPv4, or IPv4) Network Connectivity</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>Partridge, C.; Kastenholz, F. (December 1994). Technical Criteria for Choosing IP The Next Generation (IPng). doi:10.17487/RFC1726. RFC 1726. <a href="https://datatracker.ietf.org/doc/html/rfc1726" target="_blank">https://datatracker.ietf.org/doc/html/rfc1726</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>F. Baker; X. Li; C. Bao; K. Yin (April 2011). Framework for IPv4/IPv6 Translation. Internet Engineering Task Force. doi:10.17487/RFC6144. ISSN 2070-1721. RFC 6144. Informational. <a href="/wiki/Fred_Baker_(IETF_chair)" target="_blank">/wiki/Fred_Baker_(IETF_chair)</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>C. Bao; C. Huitema; M. Bagnulo; M. Boucadair; X. Li (October 2010). IPv6 Addressing of IPv4/IPv6 Translators. Internet Engineering Task Force (IETF). doi:10.17487/RFC6052. ISSN 2070-1721. RFC 6052. Proposed Standard. Updates RFC 4291. <a href="/wiki/Christian_Huitema" target="_blank">/wiki/Christian_Huitema</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>C. Bao; X. Li; F. Baker; T. Anderson; F. Gont (June 2016). Stateless IP/ICMP Translation Algorithm. doi:10.17487/RFC7915. RFC 7915. <a href="/wiki/Fred_Baker_(IETF_chair)" target="_blank">/wiki/Fred_Baker_(IETF_chair)</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>E. Nordmark (February 2000). Stateless IP/ICMP Translation Algorithm (SIIT). Network Working Group. doi:10.17487/RFC2765. RFC 2765. Obsolete. Obsoleted by RFC 6145. <a href="https://datatracker.ietf.org/doc/html/rfc2765" target="_blank">https://datatracker.ietf.org/doc/html/rfc2765</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>X. Li; C. Bao; F. Baker (April 2011). IP/ICMP Translation Algorithm. Internet Engineering Task Force. doi:10.17487/RFC6145. ISSN 2070-1721. RFC 6145. Obsolete. Obsoleted by RFC 7915. Updated by RFC 6791 and 7757. <a href="/wiki/Fred_Baker_(IETF_chair)" target="_blank">/wiki/Fred_Baker_(IETF_chair)</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>C. Bao; X. Li; F. Baker; T. Anderson; F. Gont (June 2016). Stateless IP/ICMP Translation Algorithm. doi:10.17487/RFC7915. RFC 7915. <a href="/wiki/Fred_Baker_(IETF_chair)" target="_blank">/wiki/Fred_Baker_(IETF_chair)</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>M. Blanchet; F. Parent (February 2010). IPv6 Tunnel Broker with the Tunnel Setup Protocol (TSP). doi:10.17487/RFC5572. ISSN 2070-1721. RFC 5572. Experimental. <a href="https://datatracker.ietf.org/doc/html/rfc5572" target="_blank">https://datatracker.ietf.org/doc/html/rfc5572</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>A. Durand; P. Fasano; I. Guardini; D. Lento (January 2001). IPv6 Tunnel Broker. Network Working Group. doi:10.17487/RFC3053. RFC 3053. Informational. <a href="https://datatracker.ietf.org/doc/html/rfc3053" target="_blank">https://datatracker.ietf.org/doc/html/rfc3053</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> <li id="fn:10"><p>Despres, R. (January 2010). IPv6 Rapid Deployment on IPv4 Infrastructures (6rd). doi:10.17487/RFC5569. RFC 5569. <a href="https://datatracker.ietf.org/doc/html/rfc5569" target="_blank">https://datatracker.ietf.org/doc/html/rfc5569</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li> <li id="fn:11"><p>Troan, O. (August 2010). IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) – Protocol Specification. doi:10.17487/RFC5969. RFC 5969. <a href="https://datatracker.ietf.org/doc/html/rfc5969" target="_blank">https://datatracker.ietf.org/doc/html/rfc5969</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li> <li id="fn:12"><p>Hagino, J.; Yamamoto, K. (June 2001). "An IPv6-to-IPv4 Transport Relay Translator". rfc-editor.org. Request for Comments Editor. Retrieved 28 June 2024. <a href="https://www.rfc-editor.org/rfc/rfc3142" target="_blank">https://www.rfc-editor.org/rfc/rfc3142</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></p></li> <li id="fn:13"><p>Shanmugaraja, P. "Design and Implementation of Transport Relay Translator and its security Mitigations". researchgate.net. Research Gate. Retrieved 28 June 2024. <a href="https://www.researchgate.net/publication/290350020" target="_blank">https://www.researchgate.net/publication/290350020</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></p></li> <li id="fn:14"><p>Heffernan, Andy; Tsirtsis, George; Srisuresh, Pyda; Akkiraju, Praveen (September 1999). "DNS extensions to Network Address Translators (DNS_ALG)". rfc-editor.org. Retrieved 28 June 2024. <a href="https://www.rfc-editor.org/rfc/rfc2694" target="_blank">https://www.rfc-editor.org/rfc/rfc2694</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></p></li> <li id="fn:15"><p>C. Bao; C. Huitema; M. Bagnulo; M. Boucadair; X. Li (October 2010). IPv6 Addressing of IPv4/IPv6 Translators. Internet Engineering Task Force (IETF). doi:10.17487/RFC6052. ISSN 2070-1721. RFC 6052. Proposed Standard. Updates RFC 4291. <a href="/wiki/Christian_Huitema" target="_blank">/wiki/Christian_Huitema</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></p></li> <li id="fn:16"><p>M. Bagnulo; P. Matthews; I. van Beijnum (April 2011). Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers. Internet Engineering Task Force. doi:10.17487/RFC6146. ISSN 2070-1721. RFC 6146. Proposed Standard. <a href="https://datatracker.ietf.org/doc/html/rfc6146" target="_blank">https://datatracker.ietf.org/doc/html/rfc6146</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></p></li> <li id="fn:17"><p>Bagnulo, M.; Sullivan, A.; Matthews, P.; van Beijnum, I. (April 2011). DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers. doi:10.17487/RFC6147. RFC 6147. <a href="https://datatracker.ietf.org/doc/html/rfc6147" target="_blank">https://datatracker.ietf.org/doc/html/rfc6147</a> <a href="#fnref:17" class="footnote-back-ref">↩</a></p></li> <li id="fn:18"><p>"README.DNS64". GitHub. Archived from the original on 2024-04-07. Retrieved 2024-04-07. <a href="https://github.com/NLnetLabs/unbound/blob/master/doc/README.DNS64" target="_blank">https://github.com/NLnetLabs/unbound/blob/master/doc/README.DNS64</a> <a href="#fnref:18" class="footnote-back-ref">↩</a></p></li> <li id="fn:19"><p>Žorž, Jan (3 April 2013). "Video: 464XLAT Live Demo at World IPv6 Congress in Paris". Internet Society. Archived from the original on 13 September 2017. Retrieved 5 August 2013. <a href="https://www.internetsociety.org/deploy360/blog/2013/04/video-464xlat-live-demo-at-world-ipv6-congress-in-paris/" target="_blank">https://www.internetsociety.org/deploy360/blog/2013/04/video-464xlat-live-demo-at-world-ipv6-congress-in-paris/</a> <a href="#fnref:19" class="footnote-back-ref">↩</a></p></li> <li id="fn:20"><p>"464XLAT – A Solution for Providing IPv4 Services Over and IPv6-only Network". T-Mobile USA. Archived from the original on 12 November 2020. Retrieved 5 August 2013. <a href="https://web.archive.org/web/20201112031924/https://sites.google.com/site/tmoipv6/464xlat" target="_blank">https://web.archive.org/web/20201112031924/https://sites.google.com/site/tmoipv6/464xlat</a> <a href="#fnref:20" class="footnote-back-ref">↩</a></p></li> <li id="fn:21"><p>"Case Study: T-Mobile US Goes IPv6-only Using 464XLAT". Internet Society. June 13, 2014. Archived from the original on February 4, 2024. Retrieved January 15, 2023. <a href="https://www.internetsociety.org/resources/deploy360/2014/case-study-t-mobile-us-goes-ipv6-only-using-464xlat/" target="_blank">https://www.internetsociety.org/resources/deploy360/2014/case-study-t-mobile-us-goes-ipv6-only-using-464xlat/</a> <a href="#fnref:21" class="footnote-back-ref">↩</a></p></li> <li id="fn:22"><p>Twardowska, Marta (January 6, 2015). "Orange Polska Has Launched a World's First Innovative IPv6 Solution with SoftAtHome". Business Wire. Archived from the original on 2023-01-15. Retrieved 2023-01-15. <a href="https://www.businesswire.com/news/home/20150106005488/en/Orange-Polska-Has-Launched-a-World%E2%80%99s-First-Innovative-IPv6-Solution-with-SoftAtHome" target="_blank">https://www.businesswire.com/news/home/20150106005488/en/Orange-Polska-Has-Launched-a-World%E2%80%99s-First-Innovative-IPv6-Solution-with-SoftAtHome</a> <a href="#fnref:22" class="footnote-back-ref">↩</a></p></li> <li id="fn:23"><p>"Telstra IPv6 Wireless Enablement – IPv6 Single Stack". February 6, 2020. Archived from the original on June 12, 2023. Retrieved June 12, 2023. <a href="https://lists.ausnog.net/pipermail/ausnog/2020-February/043869.html" target="_blank">https://lists.ausnog.net/pipermail/ausnog/2020-February/043869.html</a> <a href="#fnref:23" class="footnote-back-ref">↩</a></p></li> <li id="fn:24"><p>Drown, Dan. "What is Android CLAT?". Dan's Notes. Archived from the original on December 17, 2022. Retrieved January 15, 2023. <a href="https://github.com/toreanderson/clatd" target="_blank">https://github.com/toreanderson/clatd</a> <a href="#fnref:24" class="footnote-back-ref">↩</a></p></li> <li id="fn:25"><p>Havey, Daniel; Balasubramanian, Praveen (February 14, 2019). "Core Network Stack Features in the Creators Update for Windows 10". Microsoft Networking Blog. Archived from the original on February 1, 2023. Retrieved January 15, 2023. <a href="https://techcommunity.microsoft.com/t5/Networking-Blog/Core-Network-Stack-Features-in-the-Creators-Update-for-Windows/ba-p/339676" target="_blank">https://techcommunity.microsoft.com/t5/Networking-Blog/Core-Network-Stack-Features-in-the-Creators-Update-for-Windows/ba-p/339676</a> <a href="#fnref:25" class="footnote-back-ref">↩</a></p></li> <li id="fn:26"><p>"Windows 11 Plans to Expand CLAT Support". Microsoft Networking Blog. Archived from the original on March 8, 2024. Retrieved March 7, 2024. <a href="https://techcommunity.microsoft.com/t5/networking-blog/windows-11-plans-to-expand-clat-support/ba-p/4078173" target="_blank">https://techcommunity.microsoft.com/t5/networking-blog/windows-11-plans-to-expand-clat-support/ba-p/4078173</a> <a href="#fnref:26" class="footnote-back-ref">↩</a></p></li> <li id="fn:27"><p>"Twitter". Retrieved 27 June 2022. <a href="https://twitter.com/Oskar456/status/1541509105898164225" target="_blank">https://twitter.com/Oskar456/status/1541509105898164225</a> <a href="#fnref:27" class="footnote-back-ref">↩</a></p></li> <li id="fn:28"><p>"[v6ops] iOS12 IPv6-only". Retrieved 5 November 2018. <a href="https://www.ietf.org/mail-archive/web/v6ops/current/msg30153.html" target="_blank">https://www.ietf.org/mail-archive/web/v6ops/current/msg30153.html</a> <a href="#fnref:28" class="footnote-back-ref">↩</a></p></li> <li id="fn:29"><p>van Beijnum, Iljitsch (2015-06-16). "Apple to iOS devs: IPv6-only cell service is coming soon, get your apps ready". Ars Technica. Archived from the original on 2016-06-28. Retrieved 2 July 2016. <a href="https://arstechnica.com/apple/2015/06/apple-to-ios-devs-ipv6-only-cell-service-is-coming-soon-get-your-apps-ready/" target="_blank">https://arstechnica.com/apple/2015/06/apple-to-ios-devs-ipv6-only-cell-service-is-coming-soon-get-your-apps-ready/</a> <a href="#fnref:29" class="footnote-back-ref">↩</a></p></li> <li id="fn:30"><p>Anderson, Tore (May 20, 2019). "clatd". GitHub. Archived from the original on December 17, 2022. Retrieved January 15, 2023. <a href="https://github.com/toreanderson/clatd" target="_blank">https://github.com/toreanderson/clatd</a> <a href="#fnref:30" class="footnote-back-ref">↩</a></p></li> <li id="fn:31"><p>Strodlr, Mary (Jan 12, 2025). "Add support for CLAT using a BPF program". GitLab. Retrieved February 6, 2025.{{cite web}}: CS1 maint: url-status (link) <a href="https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2107" target="_blank">https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2107</a> <a href="#fnref:31" class="footnote-back-ref">↩</a></p></li> <li id="fn:32"><p>"OpenWrt Wiki package: 464xlat". OpenWrt. Retrieved 1 April 2024. <a href="https://openwrt.org/packages/pkgdata/464xlat" target="_blank">https://openwrt.org/packages/pkgdata/464xlat</a> <a href="#fnref:32" class="footnote-back-ref">↩</a></p></li> <li id="fn:33"><p>Baoi, Danilo G. (June 19, 2021). "FreeBSD 12.1-RELEASE Release Notes". FreeBSD. Archived from the original on January 15, 2023. Retrieved January 15, 2023. <a href="https://www.freebsd.org/releases/12.1R/relnotes/" target="_blank">https://www.freebsd.org/releases/12.1R/relnotes/</a> <a href="#fnref:33" class="footnote-back-ref">↩</a></p></li> <li id="fn:34"><p>A. Durand; R. Droms; J. Woodyatt; Y. Lee (August 2011). Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion. Internet Engineering Task Force. doi:10.17487/RFC6333. ISSN 2070-1721. RFC 6333. Proposed Standard. <a href="https://datatracker.ietf.org/doc/html/rfc6333" target="_blank">https://datatracker.ietf.org/doc/html/rfc6333</a> <a href="#fnref:34" class="footnote-back-ref">↩</a></p></li> <li id="fn:35"><p>Y. Cui; Q. Sun; M. Boucadair; T. Tsou; Y. Lee; I. Farrer (July 2015). Lightweight 4over6: An Extension to the Dual-Stack Lite Architecture. Internet Engineering Task Force. doi:10.17487/RFC7596. ISSN 2070-1721. RFC 7596. Proposed Standard. <a href="https://datatracker.ietf.org/doc/html/rfc7596" target="_blank">https://datatracker.ietf.org/doc/html/rfc7596</a> <a href="#fnref:35" class="footnote-back-ref">↩</a></p></li> <li id="fn:36"><p>Chroboczek, Juliusz; Kumari, Warren; Høiland-Jørgensen, Toke (Jan 2025). IPv4 routes with an IPv6 next hop. I-D draft-chroboczek-intarea-v4-via-v6-03. <a href="https://datatracker.ietf.org/doc/html/draft-chroboczek-intarea-v4-via-v6-03" target="_blank">https://datatracker.ietf.org/doc/html/draft-chroboczek-intarea-v4-via-v6-03</a> <a href="#fnref:36" class="footnote-back-ref">↩</a></p></li> <li id="fn:37"><p>Le Faucheur, François; Rosen, Eric (May 2009). Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop. doi:10.17487/RFC5549. RFC 5549. <a href="https://datatracker.ietf.org/doc/html/rfc5549" target="_blank">https://datatracker.ietf.org/doc/html/rfc5549</a> <a href="#fnref:37" class="footnote-back-ref">↩</a></p></li> <li id="fn:38"><p>Chroboczek, Juliusz (May 2022). Pv4 Routes with an IPv6 Next Hop in the Babel Routing Protocol. doi:10.17487/RFC9229. RFC 9229. <a href="https://datatracker.ietf.org/doc/html/rfc9229" target="_blank">https://datatracker.ietf.org/doc/html/rfc9229</a> <a href="#fnref:38" class="footnote-back-ref">↩</a></p></li> <li id="fn:39"><p>Rammhold, Andreas (December 15, 2020). "[RFC] Babel: Add v4viav6 Support". BIRD Internet Routing Daemon. Archived from the original on 2022-12-29. Retrieved 2023-01-15. <a href="https://bird.network.cz/pipermail/bird-users/2020-December/015082.html" target="_blank">https://bird.network.cz/pipermail/bird-users/2020-December/015082.html</a> <a href="#fnref:39" class="footnote-back-ref">↩</a></p></li> <li id="fn:40"><p>Chroboczek, Juliusz (May 5, 2022). "[Babel-users] ANNOUNCE: babeld-1.12". Debian Alioth Lists. Archived from the original on 2022-12-29. Retrieved 2023-01-15. <a href="https://alioth-lists.debian.net/pipermail/babel-users/2022-May/003963.html" target="_blank">https://alioth-lists.debian.net/pipermail/babel-users/2022-May/003963.html</a> <a href="#fnref:40" class="footnote-back-ref">↩</a></p></li> <li id="fn:41"><p>Mark Townsley (September 24, 2012). "Mapping Address + Port" (PDF). Cisco. Archived (PDF) from the original on 2022-12-29. Retrieved 2012-09-25. <a href="https://ripe65.ripe.net/presentations/91-townsley-map-ripe65-ams-sept-24-2012.pdf" target="_blank">https://ripe65.ripe.net/presentations/91-townsley-map-ripe65-ams-sept-24-2012.pdf</a> <a href="#fnref:41" class="footnote-back-ref">↩</a></p></li> <li id="fn:42"><p>X. Li; C. Bao; O. Troan; S. Matsushima; T. Murakami (July 2015). W. Dec (ed.). Mapping of Address and Port using Translation (MAP-T). Internet Engineering Task Force. doi:10.17487/RFC7599. ISSN 2070-1721. RFC 7599. Proposed Standard. <a href="https://datatracker.ietf.org/doc/html/rfc7599" target="_blank">https://datatracker.ietf.org/doc/html/rfc7599</a> <a href="#fnref:42" class="footnote-back-ref">↩</a></p></li> <li id="fn:43"><p>W. Dec; X. Li; C. Bao; S. Matsushima; T. Murakami (July 2015). O. Troan; T. Taylor (eds.). Mapping of Address and Port with Encapsulation (MAP-E). Internet Engineering Task Force. doi:10.17487/RFC7597. ISSN 2070-1721. RFC 7597. Proposed Standard. <a href="https://datatracker.ietf.org/doc/html/rfc7597" target="_blank">https://datatracker.ietf.org/doc/html/rfc7597</a> <a href="#fnref:43" class="footnote-back-ref">↩</a></p></li> <li id="fn:44"><p>Patterson, Richard (May 2021). "IPv6-Only with MAP-T". RIPE NCC Open House. Archived from the original on 21 February 2023. Retrieved 1 August 2023. <a href="https://www.ripe.net/participate/meetings/open-house/presentations/richard-patterson-sky-italia-and-map-t" target="_blank">https://www.ripe.net/participate/meetings/open-house/presentations/richard-patterson-sky-italia-and-map-t</a> <a href="#fnref:44" class="footnote-back-ref">↩</a></p></li> <li id="fn:45"><p>R. Despres; R. Penno; Y. Lee; G. Chen; M. Chen (July 2015). S. Jiang (ed.). IPv4 Residual Deployment via IPv6 - A Stateless Solution (4rd). Internet Engineering Task Force. doi:10.17487/RFC7600. ISSN 2070-1721. RFC 7600. Experimental. <a href="https://datatracker.ietf.org/doc/html/rfc7600" target="_blank">https://datatracker.ietf.org/doc/html/rfc7600</a> <a href="#fnref:45" class="footnote-back-ref">↩</a></p></li> </ol>