IPv6 rapid deployment

Last updated
6rd 6rd.svg
6rd

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

Contents

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]

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

See also

Related Research Articles

An Internet Protocol address is a numerical label such as 192.0.2.1 that is assigned to a device connected to a computer network that uses the Internet Protocol for communication. IP addresses serve two main functions: network interface identification, and location addressing.

<span class="mw-page-title-main">Internet Protocol version 4</span> Fourth version of the Internet Protocol

Internet Protocol version 4 (IPv4) is the fourth version of the Internet Protocol (IP). It is one of the core protocols of standards-based internetworking methods in the Internet and other packet-switched networks. IPv4 was the first version deployed for production on SATNET in 1982 and on the ARPANET in January 1983. It is still used to route most Internet traffic today, even with the ongoing deployment of Internet Protocol version 6 (IPv6), its successor.

<span class="mw-page-title-main">IPv6</span> Version 6 of the Internet Protocol

Internet Protocol version 6 (IPv6) is the most recent version of the Internet Protocol (IP), the communications protocol that provides an identification and location system for computers on networks and routes traffic across the Internet. IPv6 was developed by the Internet Engineering Task Force (IETF) to deal with the long-anticipated problem of IPv4 address exhaustion, and was intended to replace IPv4. In December 1998, IPv6 became a Draft Standard for the IETF, which subsequently ratified it as an Internet Standard on 14 July 2017.

The Internet Protocol (IP) is the network layer communications protocol in the Internet protocol suite for relaying datagrams across network boundaries. Its routing function enables internetworking, and essentially establishes the Internet.

Classless Inter-Domain Routing is a method for allocating IP addresses for IP routing. The Internet Engineering Task Force introduced CIDR in 1993 to replace the previous classful network addressing architecture on the Internet. Its goal was to slow the growth of routing tables on routers across the Internet, and to help slow the rapid exhaustion of IPv4 addresses.

<span class="mw-page-title-main">Subnet</span> Logical subdivision of an IP network

A subnetwork or subnet is a logical subdivision of an IP network. The practice of dividing a network into two or more networks is called subnetting.

A Martian packet is an IP packet seen on the public Internet that contains a source or destination address that is reserved for special-use by Internet Assigned Numbers Authority (IANA) as defined in RFC 1812, Appendix B Glossary. On the public Internet, such a packet either has a spoofed source address, and it cannot actually originate as claimed, or the packet cannot be delivered. The requirement to filter these packets is found in RFC 1812, Section 5.3.7.

In Internet networking, a private network is a computer network that uses a private address space of IP addresses. These addresses are commonly used for local area networks (LANs) in residential, office, and enterprise environments. Both the IPv4 and the IPv6 specifications define private IP address ranges.

6to4 is an Internet transition mechanism for migrating from Internet Protocol version 4 (IPv4) to version 6 (IPv6) and a system that allows IPv6 packets to be transmitted over an IPv4 network without the need to configure explicit tunnels. Special relay servers are also in place that allow 6to4 networks to communicate with native IPv6 networks.

In computer networking, Teredo is a transition technology that gives full IPv6 connectivity for IPv6-capable hosts that are on the IPv4 Internet but have no native connection to an IPv6 network. Unlike similar protocols such as 6to4, it can perform its function even from behind network address translation (NAT) devices such as home routers.

An IPv6 transition mechanism is a technology that facilitates the transitioning of the Internet from the Internet Protocol version 4 (IPv4) infrastructure in use since 1983 to the successor addressing and routing system of Internet Protocol Version 6 (IPv6). As IPv4 and IPv6 networks are not directly interoperable, transition technologies are designed to permit hosts on either network type to communicate with any other host.

IP networks are divided logically into subnetworks. Computers in the same subnetwork have the same address prefix. For example, in a typical home network with legacy Internet Protocol version 4, the network prefix would be something like 192.168.1.0/24, as expressed in CIDR notation.

The deployment of IPv6, the latest version of the Internet Protocol (IP), has been in progress since the mid-2000s. IPv6 was designed as the successor protocol for IPv4 with an expanded addressing space. IPv4, which has been in use since 1982, is in the final stages of exhausting its unallocated address space, but still carries most Internet traffic.

<span class="mw-page-title-main">IPv6 address</span> Label to identify a network interface of a computer or other network node

An Internet Protocol Version 6 address is a numeric label that is used to identify and locate a network interface of a computer or a network node participating in a computer network using IPv6. IP addresses are included in the packet header to indicate the source and the destination of each packet. The IP address of the destination is used to make decisions about routing IP packets to other networks.

<span class="mw-page-title-main">Carrier-grade NAT</span> Type of network address translation

Carrier-grade NAT, also known as large-scale NAT (LSN), is a type of network address translation (NAT) used by ISPs in IPv4 network design. With CGNAT, end sites, in particular residential networks, are configured with private network addresses that are translated to public IPv4 addresses by middlebox network address translator devices embedded in the network operator's network, permitting the sharing of small pools of public addresses among many end users. This essentially repeats the traditional customer-premise NAT function at the ISP level.

NAT64 is an IPv6 transition mechanism that facilitates communication between IPv6 and IPv4 hosts by using a form of network address translation (NAT). The NAT64 gateway is a translator between IPv4 and IPv6 protocols, for which function it needs at least one IPv4 address and an IPv6 network segment comprising a 32-bit address space. The "well-known prefix" reserved for this service is 64:ff9b::/96.

IPv4 Residual Deployment (4rd) is an IPv6 transition mechanism for Internet service providers for deployment of Internet Protocol version 6 (IPv6), while maintaining IPv4 service to customers. The protocol and sample applications are specified in RFC 7600.

dIVI Translation IPv4/IPv6 translation technique

dIVI Translation refers to a dual stateless IPv4/IPv6 translation technique. dIVI is an extension of 1:1 stateless IPv4/IPv6 translation with features of IPv4 address sharing and dual translation. dIVI-PD is a further extension of dIVI to be well used in Wireline and Wireless (3G/4G) access environment, where the prefix delegation is preferred. dIVI-PD is now standardized as MAP-T in the IETF.

<span class="mw-page-title-main">Rémi Després</span>

Rémi Després is a French engineer and entrepreneur known for his contributions on data networking.

In order to ensure proper working of carrier-grade NAT (CGN), and, by doing so, alleviating the demand for the last remaining IPv4 addresses, a /10 size IPv4 address block was assigned by Internet Assigned Numbers Authority (IANA) to be used as shared address space. This block of addresses is specifically meant to be used by Internet service providers that implement carrier-grade NAT, to connect their customer-premises equipment (CPE) to their core routers.

References

  1. 1 2 3 RFC 5569 IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)
  2. 1 2 3 4 RFC 5969 IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification
  3. "Les visionnaires" [Visionaries] (in French). Archived from the original on 2009-02-04. Retrieved 2010-01-05.
  4. "IPv6 @ Free" (PDF).
  5. 1 2 "Free déploie l'IPv6" [Free deploys IPv6](PDF) (in French).
  6. "IPv6 Rapid Deployment on IPv4 infrastructures (6rd)". Ietf Datatracker. Initial draft
  7. "Comcast releases open source 6rd software".
  8. "What is 6to4, and how is 6rd an improvement?".
  9. Global IPv6 Statistics - Measuring the current state of IPv6 for ordinary users, Lorenzo Colitti (Google), RIPE 57 (Dubai, Oct 2008)
  10. "Comcast sees end of IPv4 tunnel, beginning IPv6 trial". 29 January 2010.
  11. "Comcast IPv6 Information Center".
  12. "Google IPv6 Implementors Conference: Comcast IPv6 trials – John Jason Brzozowski, Comcast". YouTube . Archived from the original on 2021-12-20.
  13. "Comcast releases open source 6rd software".
  14. "How to configure 6rd for use on the Comcast network". Archived from the original on 2010-11-18.
  15. "6RD Deactivation Planned".
  16. "IPv6".
  17. "ipv6 sit: 6rd (IPv6 Rapid Deployment) Support".
  18. "IPv6インターネットサービスの提供について" [IPv6 for Internet service] (in Japanese). Archived from the original on 2011-09-30. Retrieved 2010-02-25.
  19. "Swisscom IPv6 sneak preview". Archived from the original on 2011-04-30. Retrieved 2011-04-27.
  20. "Introduction DualStack for IPv6 | Swisscom". www.swisscom.ch. Retrieved 2023-03-22.
  21. "IPv6接続テストサービス「さくらの6rd」(トライアル)提供のお知らせ" [IPv6 trial service using 6rd] (in Japanese). Archived from the original on 2011-03-07.
  22. "Videotron IPV6 FAQ". Archived from the original on 2011-11-03. Retrieved 2011-07-31.
  23. "IPv6 FAQs". Qwest.CenturyLink.com. Retrieved May 18, 2013.
  24. "ZeelandNet IPv6 Rapid Deployment test". (in Dutch)
  25. "70.000 kunder får tilbud om IPv6" [70,000 customers are offered IPv6] (in Norwegian).
  26. "Tweet from @finnsen about Altibox' 6rd".
  27. "Fusion IPv6 Tool". help.sonic.com. 2021-11-13. Retrieved 2022-04-11.
  28. "Overall IPv6 and v4 protocol support in Finland".
  29. "Tweak IPv6 wiki page".
  30. "Alaska Communications IPv6 Tunnels".