Content deleted Content added
Queernix1028 (talk | contribs) →Implementations: Jool also implements SIIT |
m fixed dashes using User:Ohconfucius/dashes.js |
||
Line 20:
It was used for an early large deployment of an IPv6 service with native addresses during 2007 (RFC 5569<ref name=RFC5569>{{Cite IETF |title=IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) |rfc=5569 |last1=Despres |first1=R. |date=January 2010 }}</ref>).
The standard-track specification of the protocol is in RFC 5969.<ref name=RFC5969>{{Cite IETF |title=IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)
==Transport Relay Translation==
Line 65:
==464XLAT==
464XLAT (RFC 6877) allows clients on IPv6-only networks to access IPv4-only Internet services, such as Skype.<ref>{{cite news|title=Video: 464XLAT Live Demo at World IPv6 Congress in Paris|date=3 April 2013|newspaper=[[Internet Society]]|url=http://www.internetsociety.org/deploy360/blog/2013/04/video-464xlat-live-demo-at-world-ipv6-congress-in-paris/|last1=Žorž|first1=Jan|access-date=5 August 2013|archive-date=13 September 2017|archive-url=https://web.archive.org/web/20170913134101/http://www.internetsociety.org/deploy360/blog/2013/04/video-464xlat-live-demo-at-world-ipv6-congress-in-paris/|url-status=live}}</ref><ref>{{cite web|title=464XLAT
The client uses a SIIT translator to convert packets from IPv4 to IPv6. These are then sent to a [[NAT64]] 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.
Line 72:
* [[T-Mobile US]] became IPv6-only using 464XLAT.<ref>{{Cite web |date=June 13, 2014 |title=Case Study: T-Mobile US Goes IPv6-only Using 464XLAT |url=https://www.internetsociety.org/resources/deploy360/2014/case-study-t-mobile-us-goes-ipv6-only-using-464xlat/ |url-status=live |archive-url=https://web.archive.org/web/20240204021359/https://www.internetsociety.org/deploy360/2014/case-study-t-mobile-us-goes-ipv6-only-using-464xlat/ |archive-date=February 4, 2024 |access-date=January 15, 2023 |website=[[Internet Society]]}}</ref>
* [[Orange Polska]] began IPv6-only (CLAT/NAT64/DNS) service in September 2013, migrating all [[ADSL]], [[VDSL]], and [[Fiber to the x|FTTH]] gateways by January 2015.<ref>{{Cite web |last=Twardowska |first=Marta |date=January 6, 2015 |title=Orange Polska Has Launched a World's First Innovative IPv6 Solution with SoftAtHome |url=https://www.businesswire.com/news/home/20150106005488/en/Orange-Polska-Has-Launched-a-World%E2%80%99s-First-Innovative-IPv6-Solution-with-SoftAtHome |access-date=2023-01-15 |website=[[Business Wire]] |language=en |archive-date=2023-01-15 |archive-url=https://web.archive.org/web/20230115224447/https://www.businesswire.com/news/home/20150106005488/en/Orange-Polska-Has-Launched-a-World%E2%80%99s-First-Innovative-IPv6-Solution-with-SoftAtHome |url-status=live }}</ref>
* [[Telstra]] became IPv6-only for mobile services using 464XLAT in February 2020. <ref>{{Cite web |date=February 6, 2020 |title=Telstra IPv6 Wireless Enablement
*[[Android (operating system)|Android]] includes a native implementation of CLAT since [[Android Jelly Bean|Jelly Bean]] 4.3, released in 2013.<ref>{{Cite web |last=Drown |first=Dan |title=What is Android CLAT? |url=https://github.com/toreanderson/clatd |access-date=January 15, 2023 |website=Dan's Notes |archive-date=December 17, 2022 |archive-url=https://web.archive.org/web/20221217201141/https://github.com/toreanderson/clatd |url-status=live }}</ref>
* [[Windows 10]] has a native WWAN-only implementation of 464XLAT for desktop and mobile since the [[Windows 10 version 1703|2017 Creators Update]].<ref>{{cite web |last1=Havey |first1=Daniel |last2=Balasubramanian |first2=Praveen |date=February 14, 2019 |title=Core Network Stack Features in the Creators Update for Windows 10 |url=https://techcommunity.microsoft.com/t5/Networking-Blog/Core-Network-Stack-Features-in-the-Creators-Update-for-Windows/ba-p/339676 |access-date=January 15, 2023 |website=[[Microsoft]] Networking Blog |archive-date=February 1, 2023 |archive-url=https://web.archive.org/web/20230201204557/https://techcommunity.microsoft.com/t5/networking-blog/core-network-stack-features-in-the-creators-update-for-windows/ba-p/339676 |url-status=live }}</ref>
Line 148:
* {{IETF RFC|6144|link=no}}, ''Framework for IPv4/IPv6 Translation''
* {{IETF RFC|6219|link=no}}, ''The China Education and Research Network (CERNET) IVI Translation Design and Deployment for the IPv4/IPv6 Coexistence and Transition''
*[http://cr.yp.to/djbdns/ipv6mess.html D. J. Bernstein
*[https://web.archive.org/web/20070901003217/http://www.join.uni-muenster.de/Dokumente/Howtos/Howto_TRT.php?lang=en Christian and Tina Strauf
*[[International Data Group|''Network World'']]
* [[Institution of Electronics and Telecommunication Engineers|''IETE Technical Review'']]
* ''KSII Transactions on Internet and Information Systems -'' [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]
{{IPv6}}
| |||