IPv6 transition mechanisms

IPv6 transition mechanisms
IPv6 transition
mechanisms
Standards Track
Experimental
Informational
Drafts
  • 4rd
  • AYIYA
  • dIVI
Deprecated
v · Internet from its IPv4 infrastructure to the next generation addressing system of IPv6. Specifically, they are methods that allow hosts only connected with either IPv4 or IPv6 to access resources only available using the other protocol.

The Internet Engineering Task Force (IETF) conducts working groups and discussions through the IETF Internet Drafts and Requests for Comments processes to develop these methods. Some basic IPv6 transition mechanisms are defined in RFC 4213.

Contents

Stateless IP/ICMP Translation (SIIT)

Stateless IP/ICMP Translation translates between the packet header formats in IPv6 and IPv4. The SIIT method defines a class of IPv6 addresses called IPv4-translated addresses. They have the prefix ::ffff:0:0:0/96 and may be written as ::ffff:0:a.b.c.d, in which the IPv4 formatted address a.b.c.d refers to an "IPv6-enabled" node. The prefix was chosen to yield a zero-valued checksum to avoid changes to the transport protocol header checksum.[1]

The algorithm can be used in a solution that allows IPv6 hosts, that do not have a permanently assigned IPv4 address, to communicate with IPv4-only hosts. Address assignment and routing details are not addressed by the specification.

The specification is a product of the NGTRANS IETF working group, and was initially drafted in February 2000 as RFC 2765 by E. Nordmark of Sun Microsystems. RFC 2765 was obsoleted by RFC 6145 in 2011.[2] The address format part of RFC 2765 is defined in RFC 6052. [3] The framework of IPv4/IPv6 translation is defined in RFC 6144. [4]

6rd

Main article: IPv6 rapid deployment

6rd is a mechanism to facilitate rapid deployment of the IPv6 service across IPv4 infrastructures of Internet service providers (ISPs). 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.

It has been used for the first large deployment of an IPv6 service with native addresses at the end of 2007 (RFC 5569 [5]). The standard-track specification of the protocol is in RFC 5969.[6]

Transport Relay Translation (TRT)

RFC 3142 defines the Transport Relay Translation (TRT) method. This is the most common form of NAT-PT/NAPT-PT but relies on DNS translation between AAAA and A records known as DNS-ALG as defined in RFC 2694.

NAT64

Main article: NAT64
NAT64 and DNS64.

NAT64 is a mechanism to allow IPv6 hosts to communicate with IPv4 servers. The NAT64 server is the endpoint for at least one IPv4 address and an IPv6 network segment of 32-bits (for instance 64:ff9b::/96, see RFC 6052, RFC 6146). The IPv6 client embeds the IPv4 address it wishes to communicate with using these bits, and sends its packets to the resulting address. The NAT64 server then creates a NAT-mapping between the IPv6 and the IPv4 address, allowing them to communicate.[7]

DNS64

DNS64 describes a DNS server that when asked for a domain's AAAA records, but only finds A records, synthesizes the AAAA records from the A records. The first part of the synthesized IPv6 address points to a IPv6/IPv4 translator and the second part embeds the IPv4 address from the A record. The translator in question is usually a NAT64 server. The standard-track specification of DNS64 is in RFC 6147.[8]

There are two noticeable issues with the transition mechanism:

  • It only works for cases where DNS is used to find the remote host address, if IPv4 literals are used the DNS64 server will never be involved.
  • Because the DNS64 server needs to return records not specified by the domain owner, DNSSEC validation against the root will fail in cases where the DNS server doing the translation is not the domain owner's server.

Dual-Stack Lite (DS-Lite)

DS-Lite

Because of IPv4 address exhaustion, Dual-Stack Lite was designed to let an Internet service provider omit the deployment of any IPv4 address to the customer's Customer-premises equipment (CPE). Instead, only global IPv6 addresses are provided. (Regular Dual-Stack deploys global addresses for both IPv4 and IPv6.)

The CPE distributes private IPv4 addresses for the LAN clients, the same as a NAT device. The subnet information is arbitrarily chosen by the customer, identically to the NAT model. However, instead of performing the NAT itself, the CPE encapsulates the IPv4 packet inside an IPv6 packet. The CPE uses its global IPv6 connection to deliver the packet to the ISP's Carrier Grade NAT (CGN), which has a global IPv4 address. The IPv6 packet is decapsulated, restoring the original IPv4 packet. NAT is performed upon the IPv4 packet and is routed to the public IPv4 Internet. The CGN uniquely identifies traffic flows by recording the CPE public IPv6 address, the private IPv4 address, and TCP or UDP port number as a session.[9]

Drafts

These mechanisms are still being discussed or have been abandoned by the IETF.

4rd

Main article: IPv4 Residual Deployment (4rd)

4rd is a mechanism to facilitate residual deployment of the IPv4 service across IPv6 networks. Like 6rd, it uses stateless address mappings between IPv6 and IPv4. It supports an extension of IPv4 address based on transport-layer ports. This is similar to A+P, but with each customer having a port set of up to 4 port ranges, and with port sets algorithmically derived from customer IPv6 prefixes.

Deprecated

These mechanisms have been deprecated by the IETF.

NAT-PT

Network Address Translation/Protocol Translation (or simply NAT-PT) is defined in RFC 2766 but due to numerous problems, it has been obsoleted by RFC 4966 and deprecated to historic status. It is typically used in conjunction with a DNS application-level gateway (DNS-ALG) implementation.

NAPT-PT

While almost identical to NAT-PT, Network Address Port Translation + Protocol Translation which is also described in RFC 2766 adds translation of the ports as well as the address. This is done primarily to avoid two hosts on one side of the mechanism from using the same exposed port on the other side of the mechanism, which could cause application instability and/or security flaws. This mechanism has been deprecated by RFC 4966.

See also

Implementations

External links

References

  1. ^ RFC 2765 - Stateless IP/ICMP Translation Algorithm (SIIT), E. Normark (February 2000)
  2. ^ RFC 6145 IP/ICMP Translation Algorithm
  3. ^ RFC 6052 - IPv6 Addressing of IPv4/IPv6 Translators
  4. ^ RFC 6144 - Framework for IPv4/IPv6 Translation
  5. ^ RFC 5569 IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)
  6. ^ RFC 5969 IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification
  7. ^ RFC 6146 Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers
  8. ^ RFC 6147 DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers
  9. ^ RFC 6333 - Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion
  • IPv6 in Practice, Benedikt Stockebrand (2006), ISBN 3-540-24524-3
  • RFC 2767, Bump-in-the-Stack
  • RFC 3338, Bump-in-the-API
  • RFC 3089, Socks-based Gateway
  • RFC 6219, The China Education and Research Network (CERNET) IVI Translation Design and Deployment for the IPv4/IPv6 Coexistence and Transition


v · Internet Protocol Version 6
General
Deployment
IPv4 to IPv6 topics
Related protocols

Wikimedia Foundation. 2010.

Look at other dictionaries:

  • IPv6 — Internet protocol suite Application layer BGP DHCP DNS FTP …   Wikipedia

  • IPv6 address — An Internet Protocol Version 6 address (IPv6 address) is a numerical label that is used to identify a network interface of a computer or other network node participating in an IPv6 enabled computer network. IP addresses serve the purpose of… …   Wikipedia

  • Comparison of IPv6 application support — This is a comparison of popular Internet applications in regards to their support of the IPv6 protocol. Applications Application Category IPv6 supported? Zone ID supported? Earliest version # with IPv6 support Notes Reference links AbsoluteTelnet …   Wikipedia

  • Comparison of IPv6 support in operating systems — This is a comparison of operating systems in regards to their support of the IPv6 protocol. OS Version Claimed IPv6 ready Installed by Default DHCPv6 ND RDNSS Notes AIX 4.3 Yes Yes Yes …   Wikipedia

  • DoD IPv6 Product Certification — Contents 1 Historical Testing Program 2 Background 3 DoD s IPv6 Standards 4 DoD s IPv6 Generic Test Plan …   Wikipedia

  • Comparison of IPv6 support in routers — This list is incomplete; you can help by expanding it. This is a comparison of consumer and commercial network routers in regards to their support of the IPv6 protocol. Manufactururer Model Native IPv6 support? Notes Reference links Allied… …   Wikipedia

  • Comparison of IPv6 support by major transit providers — Internet Protocol Version 6 (IPv6) is not yet universally available as of 2011, but support by major ISPs and transit providers is steadily increasing. Many major transit providers offer an IPv6 service to their customers, but do not have a… …   Wikipedia

  • Adresse IPv6 — Pour consulter un article plus général, voir : IPv6. L adresse IPv6 est une adresse IP, dans la version 6 du protocole IP (IPv6). Une adresse IPv6 est longue de 128 bits, soit 16 octets, contre 32 bits pour IPv4. On dispose ainsi d environ 3 …   Wikipédia en Français

  • NAT64 — and DNS64. IPv6 transiti …   Wikipedia

  • dIVI Translation — dIVI PD …   Wikipedia

Share the article and excerpts

Direct link
… Do a right-click on the link above
and select “Copy Link”