Content deleted Content added
→464XLAT: sentence missing final punctuation; random space |
fix typo |
||
| (3 intermediate revisions by 3 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/
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=
* [[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 94:
''V4-via-v6'' routing<ref>{{Cite IETF|title=IPv4 routes with an IPv6 next hop|draft=draft-chroboczek-intarea-v4-via-v6-03|last1=Chroboczek|first1=Juliusz|last2=Kumari|first2=Warren|last3=Høiland-Jørgensen|first3=Toke|date=Jan 2025}}</ref> 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 in 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==
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
| |||