IPv6 transition mechanism: Difference between revisions

Revision as of 02:30, 20 November 2024

Revision as of 11:02, 29 December 2024

Line 64:

==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 – A Solution for Providing IPv4 Services Over and IPv6-only Network|publisher=[[T-Mobile USA]]|access-date=5 August 2013|url=https://sites.google.com/site/tmoipv6/464xlat|archive-date=12 November 2020|archive-url=https://web.archive.org/web/20201112031924/https://sites.google.com/site/tmoipv6/464xlat|url-status=dead}}</ref>

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.