Content deleted Content added
No edit summary Tags: Reverted Mobile edit Mobile web edit |
m Reverted 3 edits by 2804:1B3:6080:8FA6:4933:EFD4:C5A3:B310 (talk) to last revision by Rodw |
||
Line 63:
Unlike 6over4 (an older similar protocol using IPv4 multicast), ISATAP uses IPv4 as a virtual nonbroadcast multiple-access network (NBMA) data link layer, so that it does not require the underlying IPv4 network infrastructure to support multicast.
==464XLAT==
464XLAT (RFC 6877) allows clients on IPv6-only networks to access IPv4-only Internet services.<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>
Line 91:
'''Lightweight [[4over6]]''' extends DS-Lite by moving the NAT functionality from the ISP side to the CPE, eliminating the need to implement carrier-grade NAT.{{Ref RFC|7596}} This is accomplished by allocating a port range for a shared IPv4 address to each CPE. Moving the NAT functionality to the CPE allows the ISP to reduce the amount of state tracked for each subscriber, which improves the scalability of the translation infrastructure.
==V4-via-v6 routing==
''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.
Line 97:
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 deployment|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>
| |||