IPv6 transition mechanism: Difference between revisions

Content deleted Content added
V4-via-v6 routing: missing word
fix typo
 
(2 intermediate revisions by 2 users not shown)
Line 17:
==6rd==
{{Main|IPv6 rapid deployment}}
6rd was developed by [[Rémi Després]].<ref>{{Cite IETF|rfc=5569}}</ref><ref>{{Cite web |title=IETF RFC 5569 - IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) |url=https://www.researchgate.net/publication/262571770_IETF_RFC_5569_-_IPv6_Rapid_Deployment_on_IPv4_Infrastructures_6rd262571770}}</ref> It is a mechanism to facilitate rapid deployment of the IPv6 service across [[IPv4]] infrastructures of Internet service providers ([[Internet service provider|ISP]]s). It uses stateless address mappings between [[IPv4]] and [[IPv6]] addresses, and transmits [[IPv6]] packets across automatic tunnels that follow the same optimized routes between customer nodes as [[IPv4]] packets.<ref>{{Cite web |title=IPv6 Rapid Deployment |url=https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/configuration/xe-16-10/ir-xe-16-10-book/ip6-6rd-tunls-xe.pdf}}</ref>
 
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) – Protocol Specification |rfc=5969 |last1=Troan |first1=O. |date=August 2010 }}</ref>
Line 79:
|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 |last1=Anderson |first1=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>
* [[Network Manager]] (WIP)<ref>{{Cite web |last1=StrodlrStrodl|first1=Mary|date=Jan 12, 2025 |title=Add support for CLAT using a BPF program|url=https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2107 |access-date=February 6, 2025 |website=[[GitLab]]|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>
Line 125:
*[https://downloads.isc.org/isc/aftr/ Address Family Transition Router (AFTR)], a DS-Lite implementation
*[https://code.google.com/p/fabfi/wiki/niit niit] Linux Kernel device that allow transmission of IPv4 unicast traffic through an IPv6 network
*[http://www.ivi2.org/IVI/ IVI] {{Webarchive|url=https://web.archive.org/web/20150319154837/http://www.ivi2.org/IVI/ |date=2015-03-19 }} IPv4/IPv6 packet translation implementation as a Linux kernel(2.6 only) patch
*[[Microsoft Forefront Unified Access Gateway]], a reverse proxy and VPN solution that implements DNS64 and NAT64
*[[BIND]], Berkeley Internet Name Domain DNS server, implements DNS64 since version 9.8