IPv6 transition mechanism: Difference between revisions

Content deleted Content added
m NAT64: no sentence
Rescuing 15 sources and tagging 0 as dead.) #IABot (v2.0.9.5
Line 49:
 
;Implementations
* [[Unbound_(DNS_server)|Unbound]] dns server via the dns64 module <ref>{{cite web |url=https://github.com/NLnetLabs/unbound/blob/master/doc/README.DNS64 |title=README.DNS64|website=[[GitHub]]|access-date=2024-04-07|archive-date=2024-04-07|archive-url=https://web.archive.org/web/20240407205104/https://github.com/NLnetLabs/unbound/blob/master/doc/README.DNS64|url-status=live}}</ref>
* [[OpenWrt]] via unbound opkg packages.
 
Line 61:
 
==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.
Line 67:
;Implementations
* [[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 - IPv6 Single Stack |url=https://lists.ausnog.net/pipermail/ausnog/2020-February/043869.html |access-date=June 12, 2023 |archive-date=June 12, 2023 |archive-url=https://web.archive.org/web/20230612051408/https://lists.ausnog.net/pipermail/ausnog/2020-February/043869.html |url-status=live }}</ref>
*[[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>
* [[Windows 11]] (23H2) 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 <ref>{{cite web |access-date=March 7, 2024 |url=https://techcommunity.microsoft.com/t5/networking-blog/windows-11-plans-to-expand-clat-support/ba-p/4078173 |title=Windows 11 Plans to Expand CLAT Support |website=[[Microsoft]] Networking Blog |archive-date=March 8, 2024 |archive-url=https://web.archive.org/web/20240308105450/https://techcommunity.microsoft.com/t5/networking-blog/windows-11-plans-to-expand-clat-support/ba-p/4078173 |url-status=live }}</ref>
 
* [[macOS]] starts to have native CLAT support in Ventura, released in 2022.<ref>{{cite web |title=Twitter
|access-date=27 June 2022|url=https://twitter.com/Oskar456/status/1541509105898164225}}</ref>
* [[iOS]] has a native CLAT implementation since version 12.0, released in 2018.<ref>{{cite web |title=[v6ops] iOS12 IPv6-only
|access-date=5 November 2018|url=https://www.ietf.org/mail-archive/web/v6ops/current/msg30153.html}}</ref> Additionally, Apple requires all apps submitted to the [[App Store (iOS)|App Store]] to work on IPv6 networks.<ref>{{cite web|last1=van Beijnum|first1=Iljitsch|title=Apple to iOS devs: IPv6-only cell service is coming soon, get your apps ready|url=https://arstechnica.com/apple/2015/06/apple-to-ios-devs-ipv6-only-cell-service-is-coming-soon-get-your-apps-ready/|website=Ars Technica|access-date=2 July 2016|date=2015-06-16|archive-date=2016-06-28|archive-url=https://web.archive.org/web/20160628114602/http://arstechnica.com/apple/2015/06/apple-to-ios-devs-ipv6-only-cell-service-is-coming-soon-get-your-apps-ready/|url-status=live}}</ref>
* clatd is a CLAT implementation for [[Linux]].<ref>{{Cite web |last=Anderson |first=Tore |date=May 20, 2019 |title=clatd |url=https://github.com/toreanderson/clatd |access-date=January 15, 2023 |website=[[GitHub]] |archive-date=December 17, 2022 |archive-url=https://web.archive.org/web/20221217201141/https://github.com/toreanderson/clatd |url-status=live }}</ref>
* [[OpenWRT]] linux OS for routers has optional support for clat via the 464xlat package <ref>{{cite web| title=OpenWrt Wiki package: 464xlat|url=https://openwrt.org/packages/pkgdata/464xlat|website=OpenWrt|access-date=1 April 2024}}</ref>
 
* [[FreeBSD]] has implemented NAT64 CLAT since Release 12.1.<ref>{{Cite web |last=Baoi |first=Danilo G. |date=June 19, 2021 |title=FreeBSD 12.1-RELEASE Release Notes |url=https://www.freebsd.org/releases/12.1R/relnotes/ |website=FreeBSD |access-date=January 15, 2023 |archive-date=January 15, 2023 |archive-url=https://web.archive.org/web/20230115224443/https://www.freebsd.org/releases/12.1R/relnotes/ |url-status=live }}</ref>
 
==Dual-Stack Lite (DS-Lite)==
Line 93:
''V4-via-v6'' routing 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.
 
V4-via-v6 is defined for the [[Border Gateway Protocol]] (BGP)<ref>{{Cite IETF|title=Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop|rfc=5549|last1=Le Faucheur|first1=François|last2=Rosen|first2=Eric|date=May 2009}}</ref> and the [[Babel (protocol)|Babel routing protocol]].<ref>{{Cite IETF|rfc=9229|title=Pv4 Routes with an IPv6 Next Hop in the Babel Routing Protocol|last1=Chroboczek|first1=Juliusz|date=May 2022}}</ref> It has been implemented the [[Bird Internet routing daemon]]<ref>{{Cite web |last=Rammhold |first=Andreas |date=December 15, 2020 |title=[RFC] Babel: Add v4viav6 Support |url=https://bird.network.cz/pipermail/bird-users/2020-December/015082.html |access-date=2023-01-15 |website=BIRD Internet Routing Daemon |archive-date=2022-12-29 |archive-url=https://web.archive.org/web/20221229084844/https://bird.network.cz/pipermail/bird-users/2020-December/015082.html |url-status=live }}</ref> and in [[Babel (protocol)#Implementations|''babeld'']].<ref>{{Cite web |last=Chroboczek |first=Juliusz |date=May 5, 2022 |title=[Babel-users] ANNOUNCE: babeld-1.12 |url=https://alioth-lists.debian.net/pipermail/babel-users/2022-May/003963.html |access-date=2023-01-15 |website=Debian Alioth Lists |archive-date=2022-12-29 |archive-url=https://web.archive.org/web/20221229084813/https://alioth-lists.debian.net/pipermail/babel-users/2022-May/003963.html |url-status=live }}</ref>
 
==MAP==
[[Mapping of Address and Port]] (MAP) is a [[Cisco]] [[IPv6 transition]] proposal which combines [[A+P]] port address translation with tunneling of the IPv4 packets over an ISP provider's internal [[IPv6]] network.<ref>{{cite web|url=https://ripe65.ripe.net/presentations/91-townsley-map-ripe65-ams-sept-24-2012.pdf|title=Mapping Address + Port|author=Mark Townsley|publisher=Cisco|date=September 24, 2012|access-date=2012-09-25|archive-date=2022-12-29|archive-url=https://web.archive.org/web/20221229084809/https://ripe65.ripe.net/presentations/91-townsley-map-ripe65-ams-sept-24-2012.pdf|url-status=live}}</ref> MAP-T{{Ref RFC|7599}} and MAP-E{{Ref RFC|7597}} entered standards track in July 2015, and Sky Italia has deployed MAP-T in its internet services as early as year 2021.<ref>{{cite web |last1=Patterson |first1=Richard |title=IPv6-Only with MAP-T |url=https://www.ripe.net/participate/meetings/open-house/presentations/richard-patterson-sky-italia-and-map-t |website=RIPE NCC Open House |date=May 2021 |access-date=1 August 2023 |archive-date=21 February 2023 |archive-url=https://web.archive.org/web/20230221111150/https://www.ripe.net/participate/meetings/open-house/presentations/richard-patterson-sky-italia-and-map-t |url-status=live }}</ref>
 
==Draft proposals==