IPv6 rapid deployment

Short description: Internet transition mechanism

6rd IPv6 transition mechanisms

Standards Track

* 4in6
* Lightweight 4over6
* 6in4
* 6over4
* DS-Lite
* 6rd
* 6to4
* ISATAP
* NAT64 / DNS64
* Teredo
* SIIT
* MAP

Experimental

* TSP
* 4rd

Informational

* Tunnel broker
* IVI
* TRT
* 464XLAT
* Public 4over6

Drafts

* AYIYA
* dIVI

Deprecated

* NAT-PT
* NAPT-PT

* v
* t
* e

6rd is a mechanism to facilitate IPv6 rapid deployment across IPv4 infrastructures of Internet service providers (ISPs).

The protocol is derived from 6to4, a preexisting mechanism to transfer IPv6 packets over the IPv4 network, with the significant change that it operates entirely within the end-user's ISP network, thus avoiding the major architectural problems inherent in the design of 6to4. The name 6rd is a reference to both the rapid deployments of IPv6 it enables, and, informally, the initials (RD) of its inventor, Rémi Després.

A description of 6rd principles and their first application by the ISP Free is published in RFC 5569,[1] The 6rd specification prepared for standardization in the IETF is available as RFC 5969.[2]

## Contents

* 1 History
* 2 Comparison to 6to4
* 3 Address space consumption
* 4 Current usage
* 5 See also
* 6 References
* 7 External links

## History

In November 2007, Rémi Després[3] — who was one of the creators of the Transpac data network in France in the 1970s — proposed to Free, the second largest ISP in France, to use the 6rd mechanism he had invented to rapidly deploy IPv6. While Free had until then no short-term plan to offer IPv6 service, Rani Assaf, the CTO of Free, immediately decided to implement the solution. Five weeks later,[4] with due marketing approval and operational validation, the press release[5] announcing that IPv6 was available to Free's customers was issued.

The first draft describing the 6rd mechanism and Free's deployment was submitted to IETF on 9 February 2008.[6] After improvements, it was published on 24 January 2010 as informational RFC 5569.[1]

In March 2010, a Working Group of the IETF approved that its latest draft on 6rd should become, after some more modifications, a standards-track RFC. In August 2010, the standards-track RFC 5969[2] was published. In October 2010 Comcast made 6rd software for home gateway devices available via open source for free.[7]

## Comparison to 6to4

6to4 works by relaying traffic between native IPv6 and IPv4 using relay servers which advertise common IPv4 and IPv6 prefixes to networks they are prepared to provide relay services for, but there is no guarantee that all native IPv6 hosts have a working route toward such a relay. Because of this, a 6to4 host is not guaranteed to be reachable by all native IPv6 hosts. Even when a relay is available, it is often operated by a third party who has no obligation to maintain a good quality of service as traffic grows. 6rd changes this model by making each ISP use one of its own IPv6 prefixes instead of the special 2002::/16 prefix standardized for 6to4,[8] so a provider is guaranteed that its 6rd hosts will be reachable from all native IPv6 hosts that can reach their IPv6 network. Because the relay is fully under the ISP's control, it keeps full responsibility for the quality of service for its customers.

Because 6rd relays can only be used by a limited set of hosts that are all under the control of the same administrative entity, it also reduces the scope for traffic anonymization attacks such as those possible with 6to4.[2]

## Address space consumption

The simplest 6rd deployment, which uses 32 bits of IPv6 address space to map the entire IPv4 address space, consumes more address space than typical with IPv6 natively supported in all ISP routers. This can be mitigated by omitting redundant parts of the IPv4 address space, and in some cases by deploying multiple 6rd domains.[1][2]

The default allocation of IPv6 space by a regional Internet registry (RIR) is a 32-bit prefix. Since it takes 32 bits to map an IPv4 address with 6rd, this implies that an ISP would only be able to allocate 64-bit IPv6 prefixes to its customers if it were to use entire IPv4 addresses. 6rd, however, allows any redundant part of an IPv4 address to be discarded: For example, if the IPv4 addresses that an ISP issues to its customers all share the same first eighteen bits, a 6rd prefix only need include the remaining fourteen bits. Without this flexibility, Free originally assigned 64-bit IPv6 prefixes to its customers but was able to assign them shorter prefixes once it obtained a larger allocation of IPv6 space (a 26-bit prefix) from the RIPE NCC.

## Current usage

This section needs to be updated. Please update this article to reflect recent events or newly available information. (February 2017)

|

* Free has used 6rd since December 2007.[5] In 2008, a report from Google on its visibility of IPv6 use[9] showed France as having the second highest IPv6 penetration in the world, with 95% of its IPv6 being with "native" IPv6 addresses, almost all from Free.
* Comcast announced in January 2010 a trial using 6rd in the second quarter of 2010.[10] They began that 6RD trial on June 30, 2010, which was expected to ramp up to several hundred users in July 2010.[11] But 6rd is not anticipated to be Comcast's primary IPv6 strategy.[12] Comcast has tested 2 different home gateways with 6rd, one of which they have made available via open source.[13] In addition, they have published 6rd configuration instructions for any user on their network that wishes to use their 6rd border relays.[14] Comcast planned to deactivate their 6rd service on June 30, 2011, in anticipation of their wider deployment of native dual stack.[15]
* Charter has announced the planned deployment of 6rd across their network in 2012.[16] They host a public 6rd border relay for their subscribers.
* The Linux kernel added support for 6rd in version 2.6.33.[17]
* The Japanese company SoftBank have announced that they will begin rolling out IPv6 using 6rd.[18]
* Swisscom is rolling out 6RD in 2011.[19] Starting 2022, Swisscom passed to a full dual stack approach.[20]
* The Japanese company SAKURA Internet (ja) began its 6rd trial in March 2011.[21]
* Canadian ISP Videotron has deployed 6rd in beta on June 8, 2011, for customers using a 6rd-ready router.[22]
* In December 2011, Dutch ISP Telfort announced it was starting an IPv6 pre-pilot based on 6rd, inviting customers to participate. As of January 2013, 6rd is open as opt-in to all Telfort fixed line (ADSL and VDSL) customers. The "opt-in" means the customer has to enable 6RD in the Telfort Zyxel modem to get IPv6 connectivity. However this pilot has since been discontinued as parent company KPN shut down the Telfort subsidiary in 2019.
* CenturyLink has supported 6rd since April 2012 including a list of compatible modems.[23]
* In January 2013, Dutch ISP ZeelandNet announced it was starting an IPv6 pre-pilot based on 6rd, inviting customers to participate. After the trial they expect to have a native/dual-stack solution on their EuroDOCSIS consumer network and business fiber network.[24]
* As of June 12, 2013, Dutch ISP OnsBrabantNet supports 6rd on their network.[25]
* In October 2013, Norwegian ISP Altibox announced that they offer IPv6 to 70,000 customers based on 6rd.[26] All customers who bypass the ISP's "home central" were able to use 6rd in March 2013, though it was only announced on a technician's Twitter account.[27]
* In November 2014, Sonic.net made 6rd available for subscribers with compatible equipment to choose to enable it.[28]
* Telia Company is using 6rd.[29]
* Tweak, a Dutch fiber ISP, is using 6rd.[30]
* Alaska Communications, a telecommunications corporation headquartered in Alaska, provides experimental support for 6rd to subscribers.[31]

## See also

* IPv6 deployment

## References

1. ↑ 1.0 1.1 1.2 Despres, Remi (January 2010), IPv6 Rapid Deployment on IPv4 Infrastructures (6rd), IETF, doi:10.17487/RFC5569, RFC 5569, https://tools.ietf.org/html/rfc5569, retrieved 2025-02-16
2. ↑ 2.0 2.1 2.2 2.3 Townsley, Mark; Troan, Ole (August 2010), IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification, IETF, doi:10.17487/RFC5969, RFC 5969, https://tools.ietf.org/html/rfc5969, retrieved 2025-02-16
3. ↑ "Les visionnaires" (in fr). http://www.01net.com/editorial/320349/les-visionnaires/.
4. ↑ "IPv6 @ Free". http://ripe58.ripe.net/content/presentations/ipv6-free.pdf.
5. ↑ 5.0 5.1 "Free déploie l'IPv6" (in fr). http://www.iliad.fr/presse/2007/CP_IPv6_121207.pdf.
6. ↑ "IPv6 Rapid Deployment on IPv4 infrastructures (6rd)". Ietf Datatracker. http://tools.ietf.org/html/draft-despres-v6ops-6rd-ipv6-rapid-deployment-00. Initial draft
7. ↑ "Comcast releases open source 6rd software". http://blog.comcast.com/2010/10/comcast-donates-additional-ipv6-open-source-software.html.
8. ↑ "What is 6to4, and how is 6rd an improvement?". http://www.qacafe.com/knowledgebase/testing-6to4-and-6rd-ipv6-islands-with-cdrouter/.
9. ↑ "Global IPv6 Statistics - Measuring the current state of IPv6 for ordinary users, Lorenzo Colitti (Google), RIPE 57 (Dubai, Oct 2008)". http://www.ripe.net/ripe/meetings/ripe-57/presentations/Colitti-Global_IPv6_statistics_-_Measuring_the_current_state_of_IPv6_for_ordinary_users_.7gzD.pdf.
10. ↑ "Comcast sees end of IPv4 tunnel, beginning IPv6 trial". 29 January 2010. https://arstechnica.com/tech-policy/news/2010/01/comcast-running-out-of-ipv4-addresses-beginning-ipv6-trial.ars.
11. ↑ "Comcast IPv6 Information Center". http://www.comcast6.net.
12. ↑ "Google IPv6 Implementors Conference: Comcast IPv6 trials – John Jason Brzozowski, Comcast". https://www.youtube.com/watch?v=lSsbJj4TVPM#t=51m0s.
13. ↑ "Comcast releases open source 6rd software". http://blog.comcast.com/2010/10/comcast-donates-additional-ipv6-open-source-software.html.
14. ↑ "How to configure 6rd for use on the Comcast network". http://www.comcast6.net/6rd-config.php.
15. ↑ "6RD Deactivation Planned". http://www.comcast6.net/.
16. ↑ "IPv6". http://www.charter.net/support/internet/ipv6/.
17. ↑ "ipv6 sit: 6rd (IPv6 Rapid Deployment) Support". http://kernelnewbies.org/Linux_2_6_33#head-5fb916ab0f5afd77ff35436ea17b8d99520a3d33.
18. ↑ "IPv6インターネットサービスの提供について" (in ja). http://www.softbankbb.co.jp/ja/news/press/2010/20100223_01/.
19. ↑ "Swisscom IPv6 sneak preview". http://labs.swisscom.ch/fr/news/ipv6-sneak-preview.
20. ↑ "Introduction DualStack for IPv6 | Swisscom". https://www.swisscom.ch/en/business/wholesale/ueberwholesale/aktuelles/dualstackipv6.html.
21. ↑ "IPv6接続テストサービス「さくらの6rd」（トライアル）提供のお知らせ" (in ja). http://www.sakura.ad.jp/news/archives/20110301-003.news.
22. ↑ "Videotron IPV6 FAQ". http://support.videotron.com/residential/internet/ipv6.
23. ↑ "IPv6 FAQs". Qwest.CenturyLink.com. http://qwest.centurylink.com/internethelp/static-ipv6-q.html.
24. ↑ "ZeelandNet IPv6 Rapid Deployment test". http://www.martijnvandorst.nl/ipv6/testing/. (in Dutch)
25. ↑ "OnsBrabantNet website". June 2013. http://www.onsbrabantnet.nl/IPV6/.
26. ↑ "70.000 kunder får tilbud om IPv6" (in no). http://www.altibox.no/nyheter?p_p_id=62_INSTANCE_fK9b&p_p_lifecycle=0&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_count=1&_62_INSTANCE_fK9b_struts_action=/journal_articles/view&_62_INSTANCE_fK9b_groupId=10327&_62_INSTANCE_fK9b_articleId=7860137&_62_INSTANCE_fK9b_version=1.3.
27. ↑ "Tweet from @finnsen about Altibox' 6rd". https://twitter.com/finnsen/status/315810034779058176.
28. ↑ "Fusion IPv6 Tool". help.sonic.com. 2021-11-13. https://help.sonic.com/hc/en-us/articles/236083487-Fusion-IPv6-Tool.
29. ↑ "Overall IPv6 and v4 protocol support in Finland". http://ipv6-test.com/stats/country/FI.
30. ↑ "Tweak IPv6 wiki page". https://www.tweak.nl/internet/ipv6.html.
31. ↑ "Alaska Communications IPv6 Tunnels". https://6rd.acsalaska.net/6rd/.

* Adeel Ahmed, Salman Asadullah, Deploying IPv6 in Broadband Access Networks, John Wiley and Sons, 2009, ISBN 0-470-19338-7, pp. 195-205

## External links

* IPv4 and IPv6 Transition and Coexistence, 6DEPLOY project, 2011

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/IPv6 rapid deployment. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=IPv6_rapid_deployment&oldid=4226959"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template