|Internet protocol suite|
Internet Protocol version 6 (IPv6) is the latest 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.
IPv6 is intended to replace IPv4, which still carries more than 96% of Internet traffic worldwide as of May 2014. As of June 2014[update], the percentage of users reaching Google services with IPv6 surpassed 4% for the first time.
Every device on the Internet is assigned an IP address for identification and location definition. With the rapid growth of the Internet after commercialization in the 1990s, it became evident that far more addresses than the IPv4 address space has available were necessary to connect new devices in the future. By 1998, the Internet Engineering Task Force (IETF) had formalized the successor protocol. IPv6 uses a 128-bit address, allowing 2128, or approximately 3.4×1038 addresses, or more than 7.9×1028 times as many as IPv4, which uses 32-bit addresses and provides approximately 4.3 billion addresses. The two protocols are not designed to be interoperable, complicating the transition to IPv6. However, several IPv6 transition mechanisms have been devised to permit communication between IPv4 and IPv6 hosts.
IPv6 provides other technical benefits in addition to a larger addressing space. In particular, it permits hierarchical address allocation methods that facilitate route aggregation across the Internet, and thus limit the expansion of routing tables. The use of multicast addressing is expanded and simplified, and provides additional optimization for the delivery of services. Device mobility, security, and configuration aspects have been considered in the design of the protocol.
IPv6 addresses are represented as eight groups of four hexadecimal digits separated by colons, for example 2001:0db8:85a3:0042:1000:8a2e:0370:7334, but methods of abbreviation of this full notation exist.
- 1 Technical overview
- 2 Motivation and origin
- 3 Comparison with IPv4
- 4 Packet format
- 5 Addressing
- 6 Transition mechanisms
- 7 IPv6 readiness
- 8 Deployment
- 9 See also
- 10 References
- 11 External links
IPv6 is an Internet Layer protocol for packet-switched internetworking and provides end-to-end datagram transmission across multiple IP networks, closely adhering to the design principles developed in the previous version of the protocol, Internet Protocol Version 4 (IPv4). IPv6 was first formally described in Internet standard document RFC 2460, published in December 1998. In addition to offering more addresses, IPv6 also implements features not present in IPv4. It simplifies aspects of address assignment (stateless address autoconfiguration), network renumbering and router announcements when changing network connectivity providers. It simplifies processing of packets by routers by placing the need for packet fragmentation into the end points. The IPv6 subnet size is standardized by fixing the size of the host identifier portion of an address to 64 bits to facilitate an automatic mechanism for forming the host identifier from link layer addressing information (MAC address). Network security was a design requirement of the IPv6 architecture, and included the original specification of IPsec.
IPv6 does not specify interoperability features with IPv4, but essentially creates a parallel, independent network. Exchanging traffic between the two networks requires translator gateways employing one of several transition mechanisms, such as NAT64, the tunneling protocols 6to4, 6in4, Teredo.
Motivation and origin
Internet Protocol Version 4 (IPv4) was the first publicly used version of the Internet Protocol. IPv4 was developed as a research project by the Defense Advanced Research Projects Agency (DARPA), a United States Department of Defense agency, before becoming the foundation for the Internet and the World Wide Web. It is currently described by IETF publication RFC 791 (September 1981), which replaced an earlier definition (RFC 760, January 1980). IPv4 included an addressing system that used numerical identifiers consisting of 32 bits. These addresses are typically displayed in quad-dotted notation as decimal values of four octets, each in the range 0 to 255, or 8 bits per number. Thus, IPv4 provides an addressing capability of 232 or approximately 4.3 billion addresses. Address exhaustion was not initially a concern in IPv4 as this version was originally presumed to be a test of DARPA's networking concepts.
During the first decade of operation of the Internet, by the late 1980s, it became apparent that methods had to be developed to conserve address space. In the early 1990s, even after the redesign of the addressing system using a classless network model, it became clear that this would not suffice to prevent IPv4 address exhaustion, and that further changes to the Internet infrastructure were needed.
The last unassigned top-level address blocks of 16 million IPv4 addresses were allocated in February 2011 by the Internet Assigned Numbers Authority (IANA) to the five regional Internet registries (RIRs). However, each RIR still has available address pools and is expected to continue with standard address allocation policies until one /8 Classless Inter-Domain Routing (CIDR) block remains. After that, only blocks of 1024 addresses (/22) will be provided from the RIRs to a local Internet registry (LIR). As of September 2012, both the Asia-Pacific Network Information Centre (APNIC) and the Réseaux IP Européens Network Coordination Centre (RIPE_NCC) had reached this stage.
By the beginning of 1992, several proposals appeared for an expanded Internet addressing system and by the end of 1992 the IETF announced a call for white papers. In September 1993, the IETF created a temporary, ad-hoc IP Next Generation (IPng) area to deal specifically with IPng issues. The new area was led by Allison Mankin and Scott Bradner, and had a directorate with 15 engineers from diverse backgrounds for direction-setting and preliminary document review: The working-group members were J. Allard (Microsoft), Steve Bellovin (AT&T), Jim Bound (Digital Equipment Corporation), Ross Callon (Wellfleet), Brian Carpenter (CERN), Dave Clark (MIT), John Curran (NEARNET), Steve Deering (Xerox), Dino Farinacci (Cisco), Paul Francis (NTT), Eric Fleischmann (Boeing), Mark Knopper (Ameritech), Greg Minshall (Novell), Rob Ullmann (Lotus), and Lixia Zhang (Xerox).
The Internet Engineering Task Force adopted the IPng model on 25 July 1994, with the formation of several IPng working groups. By 1996, a series of RFCs was released defining Internet Protocol version 6 (IPv6), starting with RFC 1883. (Version 5 was used by the experimental Internet Stream Protocol.)
It is widely expected that the Internet will use IPv4 alongside IPv6 for the foreseeable future. IPv4-only and IPv6-only nodes cannot communicate directly, and need assistance from an intermediary gateway or must use other transition mechanisms.
Comparison with IPv4
On the Internet, data is transmitted in the form of network packets. IPv6 specifies a new packet format, designed to minimize packet header processing by routers. Because the headers of IPv4 packets and IPv6 packets are significantly different, the two protocols are not interoperable. However, in most respects, IPv6 is a conservative extension of IPv4. Most transport and application-layer protocols need little or no change to operate over IPv6; exceptions are application protocols that embed internet-layer addresses, such as FTP and NTPv3, where the new address format may cause conflicts with existing protocol syntax.
Larger address space
The main advantage of IPv6 over IPv4 is its larger address space. The length of an IPv6 address is 128 bits, compared with 32 bits in IPv4. The address space therefore has 2128 or approximately 3.4×1038 addresses. This would be about 40,000 addresses for every atom on the surface of the earth[not in citation given] and almost four /64s per square centimeter of the planet.
In addition, the IPv4 address space is poorly allocated, with approximately 14% of all available addresses utilized. While these numbers are large, it wasn't the intent of the designers of the IPv6 address space to assure geographical saturation with usable addresses. Rather, the longer addresses simplify allocation of addresses, enable efficient route aggregation, and allow implementation of special addressing features. In IPv4, complex Classless Inter-Domain Routing (CIDR) methods were developed to make the best use of the small address space. The standard size of a subnet in IPv6 is 264 addresses, the square of the size of the entire IPv4 address space. Thus, actual address space utilization rates will be small in IPv6, but network management and routing efficiency is improved by the large subnet space and hierarchical route aggregation.
Renumbering an existing network for a new connectivity provider with different routing prefixes is a major effort with IPv4. With IPv6, however, changing the prefix announced by a few routers can in principle renumber an entire network, since the host identifiers (the least-significant 64 bits of an address) can be independently self-configured by a host.
Multicasting, the transmission of a packet to multiple destinations in a single send operation, is part of the base specification in IPv6. In IPv4 this is an optional although commonly implemented feature. IPv6 multicast addressing shares common features and protocols with IPv4 multicast, but also provides changes and improvements by eliminating the need for certain protocols. IPv6 does not implement traditional IP broadcast, i.e. the transmission of a packet to all hosts on the attached link using a special broadcast address, and therefore does not define broadcast addresses. In IPv6, the same result can be achieved by sending a packet to the link-local all nodes multicast group at address
ff02::1, which is analogous to IPv4 multicast to address
220.127.116.11. IPv6 also provides for new multicast implementations, including embedding rendezvous point addresses in an IPv6 multicast group address, which simplifies the deployment of inter-domain solutions.
In IPv4 it is very difficult for an organization to get even one globally routable multicast group assignment, and the implementation of inter-domain solutions is very arcane. Unicast address assignments by a local Internet registry for IPv6 have at least a 64-bit routing prefix, yielding the smallest subnet size available in IPv6 (also 64 bits). With such an assignment it is possible to embed the unicast address prefix into the IPv6 multicast address format, while still providing a 32-bit block, the least significant bits of the address, or approximately 4.2 billion multicast group identifiers. Thus each user of an IPv6 subnet automatically has available a set of globally routable source-specific multicast groups for multicast applications.
Stateless address autoconfiguration (SLAAC)
IPv6 hosts can configure themselves automatically when connected to an IPv6 network using the Neighbor Discovery Protocol via Internet Control Message Protocol version 6 (ICMPv6) router discovery messages. When first connected to a network, a host sends a link-local router solicitation multicast request for its configuration parameters; routers respond to such a request with a router advertisement packet that contains Internet Layer configuration parameters.
If IPv6 stateless address autoconfiguration is unsuitable for an application, a network may use stateful configuration with the Dynamic Host Configuration Protocol version 6 (DHCPv6) or hosts may be configured manually using static methods.
Routers present a special case of requirements for address configuration, as they often are sources of autoconfiguration information, such as router and prefix advertisements. Stateless configuration of routers can be achieved with a special router renumbering protocol.
Internet Protocol Security (IPsec) was originally developed for IPv6, but found widespread deployment first in IPv4, for which it was re-engineered. IPsec was a mandatory specification of the base IPv6 protocol suite, but has since been made optional.
Simplified processing by routers
In IPv6, the packet header and the process of packet forwarding have been simplified. Although IPv6 packet headers are at least twice the size of IPv4 packet headers, packet processing by routers is generally more efficient, thereby extending the end-to-end principle of Internet design. Specifically:
- The packet header in IPv6 is simpler than that used in IPv4, with many rarely used fields moved to separate optional header extensions.
- IPv6 routers do not perform fragmentation. IPv6 hosts are required to either perform path MTU discovery, perform end-to-end fragmentation, or to send packets no larger than the IPv6 default MTU size of 1280 octets.
- The IPv6 header is not protected by a checksum; integrity protection is assumed to be assured by both link-layer and higher-layer (TCP, UDP, etc.) error detection. UDP/IPv4 may actually have a checksum of 0, indicating no checksum; IPv6 requires UDP to have its own checksum. Therefore, IPv6 routers do not need to recompute a checksum when header fields (such as the time to live (TTL) or hop count) change. This improvement may have been made less necessary by the development of routers that perform checksum computation at link speed using dedicated hardware, but it is still relevant for software-based routers.
- The TTL field of IPv4 has been renamed to Hop Limit in IPv6, reflecting the fact that routers are no longer expected to compute the time a packet has spent in a queue.
Unlike mobile IPv4, mobile IPv6 avoids triangular routing and is therefore as efficient as native IPv6. IPv6 routers may also allow entire subnets to move to a new router connection point without renumbering.
The IPv6 packet header has a fixed size (40 octets). Options are implemented as additional extension headers after the IPv6 header, which limits their size only by the size of an entire packet. The extension header mechanism makes the protocol extensible in that it allows future services for quality of service, security, mobility, and others to be added without redesign of the basic protocol.
IPv4 limits packets to 65535 (216−1) octets of payload. An IPv6 node can optionally handle packets over this limit, referred to as jumbograms, which can be as large as 4294967295 (232−1) octets. The use of jumbograms may improve performance over high-MTU links. The use of jumbograms is indicated by the Jumbo Payload Option header.
Like IPv4, IPv6 supports globally unique IP addresses by which the network activity of each device can potentially be tracked.
The design of IPv6 intended to re-emphasize the end-to-end principle of network design that was originally conceived during the establishment of the early Internet. In this approach each device on the network has a unique address globally reachable directly from any other location on the Internet.
- Network prefix
- Network prefix tracking is less of a concern if the user's ISP assigns a dynamic network prefix via DHCP. Privacy extensions do little to protect the user from tracking if the ISP assigns a static network prefix. In this scenario, the network prefix is the unique identifier for tracking and the Interface indetifier is secondary.
- Interface identifier
- In IPv4 the effort to conserve address space with network address translation (NAT) obfuscates network address spaces, hosts, and topologies. In IPv6 when using address auto-configuration, the Interface Identifier (MAC address) of an interface port is used to make its public IP address unique, exposing the type of hardware used and providing a unique handle for a user's online activity.
It is not a requirement for IPv6 hosts to use address auto-configuration, however. Yet, even when an address is not based on the MAC address, the interface's address is globally unique, in contrast to NAT-masqueraded private networks. Privacy extensions for IPv6 have been defined to address these privacy concerns, although Silvia Hagen describes these as being largely due to "misunderstanding". When privacy extensions are enabled, the operating system generates random host identifiers to combine with the assigned network prefix. These ephemeral addresses are used to communicate with remote hosts making it more difficult to track a single device.
An IPv6 packet has two parts: a header and payload.
The header consists of a fixed portion with minimal functionality required for all packets and may be followed by optional extensions to implement special features.
The fixed header occupies the first 40 octets (320 bits) of the IPv6 packet. It contains the source and destination addresses, traffic classification options, a hop counter, and the type of the optional extension or payload which follows the header. This Next Header field tells the receiver how to interpret the data which follows the header. If the packet contains options, this field contains the option type of the next option. The "Next Header" field of the last option, points to the upper-layer protocol that is carried in the packet's payload.
Extension headers carry options that are used for special treatment of a packet in the network, e.g., for routing, fragmentation, and for security using the IPsec framework.
Without special options, a payload must be less than 64KB. With a Jumbo Payload option (in a Hop-By-Hop Options extension header), the payload must be less than 4 GB.
Unlike for IPv4, routers never fragment a packet. Hosts are expected to use Path MTU Discovery to make their packets small enough to reach the destination without needing to be fragmented. See IPv6 packet fragmentation.
Compared to IPv4, the most obvious advantage of IPv6 is its larger address space. IPv4 addresses are 32 bits long and number about 4.3×109 (4.3 billion). IPv6 addresses are 128 bits long and number about 3.4×1038 (340 undecillion). IPv6's addresses are deemed enough for the foreseeable future.
IPv6 addresses are written in eight groups of four hexadecimal digits separated by colons, such as
2001:0db8:85a3:0000:0000:8a2e:0370:7334. IPv6 unicast addresses other than those that start with binary 000 are logically divided into two parts: a 64-bit (sub-)network prefix, and a 64-bit interface identifier.
IPv6 lets any host generate its own IP address and check if it's unique in the scope where it will be used. IPv6 addresses consist of two parts. The leftmost 64 bits are the subnet prefix to which the host is connected, and the rightmost 64 bits are the identifier of the host's interface on the subnet. This means that the identifier need only be unique on the subnet to which the host is connected, which makes it much easier for the host to check for uniqueness on its own.
|Subnet Prefix 64 bits | Interface identifier 64 bits |
Link local address
The first step a host takes on startup or (re)initialization is to form a link-local address from its MAC address and the link-local prefix FE80::0. This is done by putting the prefix into the leftmost bits and the MAC address (in EUI-64 format) into the rightmost bits, and if there are any bits left in between, those are set to zero.
When the host has formed an address it will test if it is unique on the subnet. This is done with an algorithm called Duplicate Address Detection.
Check for uniqueness
To find out if an address is already in use, host A will send a neighbor solicitation message asking for the Link-layer address of the IP address it wants to use. If any other host are using that address, they will respond and host A will note that the address is in use and stop the auto configure process. In that case manual configuration will be necessary. Fortunately, this happens rarely, because MAC addresses are designed to be unique on each network card and so the only reason for an address to be in use is if the network is poorly set up or if there has been an error in the conversion of the address.
Now that the address is unique on the link, the host can proceed to try to make the address global. It first determines if the network is connected to any routers at all, because if not then all nodes are reachable using the link-local address that already is assigned to the host. The host will send out a Router Solicitation message to the all-nodes multicast group with its link local address as source. If there is no answer after a predetermined number of attempts, the host concludes that no routers are connected. If it does get a response from a router, there will be network information inside that is needed to create a globally unique address. There are also two flag bits that tell the host whether it should use DHCP to get further information and addresses:
- The Manage bit
- Indicates whether or not the host should use DHCP to obtain additional addresses
- The Other bit
- If set, the host should obtain other information through DHCP.
The other information consists of one or more prefix information options for the subnets that the host is attached to, a lifetime for the prefix, and two flags:
- If this flag is set, the host will treat all addresses on the specific subnet as being on-link, and send packets directly to them instead of sending them to a router for the duration of the given lifetime.
- This is the flag that tells the host to actually create a global address.
Create a global address
This is done in the same fashion as the link-local address, but instead of the link-local prefix FE80:: it will use the prefix supplied by the router and put it together with its identifier (which by default is the MAC address in EUI-64 format). There is no need to perform a DAD check because the identifier is already unique on the link, and the subnet prefix specifies a specific link. If the information from the router contained several subnet prefixes, the host will create one address for each one.
For stateless address autoconfiguration (SLAAC) to work, subnets require a /64 address block, as defined in RFC 4291 section 2.5.1. Local Internet registries get assigned at least /32 blocks, which they divide among ISPs. The obsolete RFC 3177 recommended the assignment of a /48 to end-consumer sites. This was replaced by RFC 6177, which "recommends giving home sites significantly more than a single /64, but does not recommend that every home site be given a /48 either". /56s are specifically considered. It remains to be seen if ISPs will honor this recommendation. For example, during initial trials, Comcast customers were given a single /64 network.
IPv6 addresses are classified by three types of networking methodologies: unicast addresses identify each network interface, anycast addresses identify a group of interfaces, usually at different locations of which the nearest one is automatically selected, and multicast addresses are used to deliver one packet to many interfaces. The broadcast method is not implemented in IPv6. Each IPv6 address has a scope, which specifies in which part of the network it is valid and unique. Some addresses are unique only on the local (sub-)network. Others are globally unique.
Some IPv6 addresses are reserved for special purposes, such as loopback, 6to4 tunneling, and Teredo tunneling, as outlined in RFC 5156. Also, some address ranges are considered special, such as link-local addresses for use on the local link only, Unique Local addresses (ULA), as described in RFC 4193, and solicited-node multicast addresses used in the Neighbor Discovery Protocol.
IPv6 in the Domain Name System
In the Domain Name System, hostnames are mapped to IPv6 addresses by AAAA resource records, so-called quad-A records. For reverse resolution, the IETF reserved the domain
ip6.arpa, where the name space is hierarchically divided by the 1-digit hexadecimal representation of nibble units (4 bits) of the IPv6 address. This scheme is defined in RFC 3596.
The 128 bits of an IPv6 address are represented in 8 groups of 16 bits each. Each group is written as 4 hexadecimal digits and the groups are separated by colons (:). The address 2001:0db8:0000:0000:0000:ff00:0042:8329 is an example of this representation.
For convenience, an IPv6 address may be abbreviated to shorter notations by application of the following rules, where possible.
- One or more leading zeroes from any groups of hexadecimal digits are removed; this is usually done to either all or none of the leading zeroes. For example, the group 0042 is converted to 42.
- Consecutive sections of zeroes are replaced with a double colon (::). The double colon may only be used once in an address, as multiple use would render the address indeterminate. RFC 5952 recommends that a double colon must not be used to denote an omitted single section of zeroes.
An example of application of these rules:
- Initial address: 2001:0db8:0000:0000:0000:ff00:0042:8329
- After removing all leading zeroes: 2001:db8:0:0:0:ff00:42:8329
- After omitting consecutive sections of zeroes: 2001:db8::ff00:42:8329
The loopback address, 0000:0000:0000:0000:0000:0000:0000:0001, may be abbreviated to ::1 by using both rules.
Until IPv6 completely supplants IPv4, several IPv6 transition mechanisms are needed to enable IPv6-only hosts to reach IPv4 services and to allow isolated IPv6 hosts and networks to reach each other over IPv4-only infrastructure.
Many of these transition mechanisms use tunneling to encapsulate IPv6 traffic within IPv4 networks. This is an imperfect solution, which reduces the maximum transmission unit MTU of a link and therefore complicate Path MTU Discovery, and may increase latency. Tunneling protocols are a temporary solution for networks that do not support native dual-stack, where both IPv6 and IPv4 run independently.
Dual IP stack implementation
Dual-stack (or native dual-stack) refers to side-by-side implementation of IPv4 and IPv6. That is, both protocols run on the same network infrastructure, and there's no need to encapsulate IPv6 inside IPv4 (using tunneling) or vice-versa. Dual-stack is defined in RFC 4213.
Although this is the most desirable IPv6 implementation during the transition from IPv4 to IPv6, as it avoids the complexities and pitfalls of tunneling (such as security, increased latency, management overhead, and a reduced PMTU), it is not always possible, since outdated network equipment may not support IPv6. A good example is cable TV-based internet access. In modern cable TV networks, the core of the HFC network (such as large core routers) is likely to support IPv6. However, other network equipment (such as a CMTS) or customer equipment (like cable modems) may require software updates or hardware upgrades to support IPv6. This means cable network operators must resort to tunneling until the backbone equipment supports native dual-stack.
The dual-stack should only be considered as a transitional technique to facilitate the adoption and deployment of IPv6, as it has some major drawbacks and consequences: it will not only more than double the security threats from both IPv4 and IPv6 for the existing network infrastructure, but also ultimately overburden the global networking infrastructure with both dramatically increased Internet traffic. The ultimate objective is to deploy the single stack of IPv6 globally.
Many current internet users do not have IPv6 dual-stack support, and thus cannot reach IPv6 sites directly. Instead, they must use IPv4 infrastructure to carry IPv6 packets. This is done using a technique known as tunneling, which encapsulates IPv6 packets within IPv4, in effect using IPv4 as a link layer for IPv6.
IP protocol 41 indicates IPv4 packets which encapsulate IPv6 datagrams. Some routers or network address translation devices may block protocol 41. To pass through these devices, UDP packets may be used to encapsulate IPv6 datagrams. Other encapsulation schemes, such as AYIYA or Generic Routing Encapsulation, are also popular.
Conversely, on IPv6-only internet links, when access to IPv4 network facilities is needed, tunneling of IPv4 over IPv6 protocol occurs, using the IPv6 as a link layer for IPv4.
Automatic tunneling refers to a technique by which the routing infrastructure automatically determines the tunnel endpoints. Some automatic tunneling techniques are below.
6to4 is recommended by RFC 3056. It uses protocol 41 encapsulation. Tunnel endpoints are determined by using a well-known IPv4 anycast address on the remote side, and embedding IPv4 address information within IPv6 addresses on the local side. 6to4 is the most common tunnel protocol currently deployed.
Teredo is an automatic tunneling technique that uses UDP encapsulation and can allegedly cross multiple NAT nodes. IPv6, including 6to4 and Teredo tunneling, are enabled by default in Windows Vista and Windows 7. Most Unix systems implement only 6to4, but Teredo can be provided by third-party software such as Miredo.
ISATAP (Intra-Site Automatic Tunnel Addressing Protocol) uses the IPv4 network as a virtual IPv6 local link, with mappings from each IPv4 address to a link-local IPv6 address. Unlike 6to4 and Teredo, which are inter-site tunneling mechanisms, ISATAP is an intra-site mechanism, meaning that it is designed to provide IPv6 connectivity between nodes within a single organization.
Configured and automated tunneling (6in4)
6in4 tunneling requires the tunnel endpoints to be explicitly configured, either by an administrator manually or the operating system's configuration mechanisms, or by an automatic service known as a tunnel broker; this is also referred to as automated tunneling. Configured tunneling is usually more deterministic and easier to debug than automatic tunneling, and is therefore recommended for large, well-administered networks. Automated tunneling provides a compromise between the ease of use of automatic tunneling and the deterministic behavior of configured tunneling.
Raw encapsulation of IPv6 packets using IPv4 protocol number 41 is recommended for configured tunneling; this is sometimes known as 6in4 tunneling. As with automatic tunneling, encapsulation within UDP may be used in order to cross NAT boxes and firewalls.
Proxying and translation for IPv6-only hosts
After the regional Internet registries have exhausted their pools of available IPv4 addresses, it is likely that hosts newly added to the Internet might only have IPv6 connectivity. For these clients to have backward-compatible connectivity to existing IPv4-only resources, suitable IPv6 transition mechanisms must be deployed.
One form of address translation is the use of a dual-stack application-layer proxy server, for example a web proxy.
NAT-like techniques for application-agnostic translation at the lower layers in routers and gateways have been proposed. The NAT-PT standard was dropped because of criticisms, however more recently the continued low adoption of IPv6 has prompted a new standardization effort of a technology called NAT64.
Compatibility with IPv6 networking is mainly a software or firmware issue. However, much of the older hardware that could in principle be upgraded is likely to be replaced instead. The American Registry for Internet Numbers (ARIN) suggested that all Internet servers be prepared to serve IPv6-only clients by January 2012. Sites will only be accessible over NAT64 if they do not use IPv4 literals as well.
Host software can be IPv4-only, IPv6-only, dual-stack, or hybrid dual-stack. Most personal computers running recent operating system versions are operable on IPv6. Many popular applications with network capabilities are compliant, and most others could be easily upgraded with help from the developers.
IPv4-mapped IPv6 addresses
Hybrid dual-stack IPv6/IPv4 implementations recognize a special class of addresses, the IPv4-mapped IPv6 addresses. In these addresses, the first 80 bits are zero, the next 16 bits are one, and the remaining 32 bits are the IPv4 address. One may see these addresses with the first 96 bits written in the standard IPv6 format, and the remaining 32 bits written in the customary dot-decimal notation of IPv4. For example,
::ffff:192.0.2.128 represents the IPv4 address
192.0.2.128. A deprecated format for IPv4-compatible IPv6 addresses was
Because of the significant internal differences between IPv4 and IPv6, some of the lower-level functionality available to programmers in the IPv6 stack does not work identically with IPv4-mapped addresses. Some common IPv6 stacks do not implement the IPv4-mapped address feature, either because the IPv6 and IPv4 stacks are separate implementations (e.g., Microsoft Windows 2000, XP, and Server 2003), or because of security concerns (OpenBSD). On these operating systems, a program must open a separate socket for each IP protocol it uses. On some systems, e.g., the Linux kernel, NetBSD, and FreeBSD, this feature is controlled by the socket option
IPV6_V6ONLY, as specified in RFC 3493.
Hardware and embedded systems
Low-level equipment such as network adapters and network switches may not be affected by the change, since they transmit link-layer frames without inspecting the contents. However, networking devices that obtain IP addresses or perform routing of IP packets do need to understand IPv6.
Most equipment would be IPv6 capable with a software or firmware update if the device has sufficient storage and memory space for the new IPv6 stack. However, manufacturers may be reluctant to spend on software development costs for hardware they have already sold when they are poised for new sales from IPv6-ready equipment.
In some cases, non-compliant equipment needs to be replaced because the manufacturer no longer exists or software updates are not possible, for example, because the network stack is implemented in permanent read-only memory.
The CableLabs consortium published the 160 Mbit/s DOCSIS 3.0 IPv6-ready specification for cable modems in August 2006. The widely used DOCSIS 2.0 does not support IPv6. The new 'DOCSIS 2.0 + IPv6' standard supports IPv6, which may on the cable modem side require only a firmware upgrade. It is expected that only 60% of cable modems' servers and 40% of cable modems will be DOCSIS 3.0 by 2011. However, most ISPs that support DOCSIS 3.0 do not support IPv6 across their networks.
Other equipment which is typically not IPv6-ready ranges from Voice over Internet Protocol devices to laboratory equipment and printers.
A side effect of IPv6 implementation may be the emergence of so-called "shadow networks" caused by IPv6 traffic flowing into IPv4 networks when IPv6 enabled nodes are added to the existing network, and the IPv4 security in place is unable to properly identify it. This may occur with operating system upgrades, when the newer OS enables IPv6 support by default, while the older one did not. Failing to update the security infrastructure to accommodate IPv6 can lead to IPv6 traffic bypassing it. Shadow networks have been found occurring on business networks in which enterprises are replacing Windows XP systems, that do not have an IPv6 stack enabled by default, with Windows 7 systems, which do.
The introduction of Classless Inter-Domain Routing (CIDR) in the Internet routing and IP address allocation methods in 1993 and the extensive use of network address translation (NAT) delayed the inevitable IPv4 address exhaustion, but the final phase of exhaustion started on 3 February 2011. However, despite a decade long development and implementation history as a Standards Track protocol, general worldwide deployment is still in its infancy. As of September 2013[update], about 4% of domain names and 16.2% of the networks on the internet have IPv6 protocol support.
IPv6 has been implemented on all major operating systems in use in commercial, business, and home consumer environments. Since 2008, the domain name system can be used in IPv6. IPv6 was first used in a major world event during the 2008 Summer Olympic Games, the largest showcase of IPv6 technology since the inception of IPv6. Some governments including the Federal U.S. Government and China are also starting to require IPv6 capability on their equipment.
In recent years, the increasing market demand for more data and smart devices with pervasive connectivity has propelled the rapid new development and adoption of the Internet of Things (IoT) technology. All of the sensors and machine-readable identifiers needed to make the Internet of Things a reality will have to use IPv6 to accommodate the extremely large address space required. Even if the current supply of IPv4 addresses were not to be exhausted soon, the size of IPv4 itself is not large enough to support the future requirement of IoT. Consequently, it is strongly believed that the Internet of Things will be the ultimate driver for the global adoption of IPv6 in the coming years.
- China Next Generation Internet
- Comparison of IPv6 application support
- Comparison of IPv6 support by major transit providers
- Comparison of IPv6 support in operating systems
- Comparison of IPv6 support in routers
- DoD IPv6 Product Certification
- List of IPv6 tunnel brokers
- University of New Hampshire InterOperability Laboratory
- David Frost (20 April 2011). "Ipv6 traffic volumes going backwards". iTWire. Retrieved 19 February 2012.
- "IPv6". Google Statistics. Google. Retrieved 17 July 2014.
- RFC 2460, Internet Protocol, Version 6 (IPv6) Specification, S. Deering, R. Hinden (December 1998)
- Google IPv6 Conference 2008: What will the IPv6 Internet look like?. Event occurs at 13:35.
- Bradner, S.; Mankin, A. (January 1995). "The Recommendation for the IP Next Generation Protocol". RFC 1752.
- Rashid, Fahmida. "IPv4 Address Exhaustion Not Instant Cause for Concern with IPv6 in Wings". eWeek. Retrieved 23 June 2012.
- Ward, Mark. "Europe hits old internet address limits". BBC. Retrieved 15 September 2012.
- Bradner, S.; Mankin, A. (December 1993). "IP: Next Generation (IPng) White Paper Solicitation". RFC 1550.
- "History of the IPng Effort". Sun.
- "The Recommendation for the IP Next Generation Protocol – Appendix B". RFC 1752.
- Partridge, C.; Kastenholz, F. (December 1994). "Technical Criteria for Choosing IP The Next Generation (IPng)". RFC 1726.
- Gold (mid-size) atoms in a rectangular array with the area of an Earth-size ideal sphere
- "IPv6 Size". subnettingpractice.com. Retrieved 11 July 2014.
- "Moving to IPv6: Now for the hard part (FAQ)". Deep Tech. CNET News. Retrieved 3 February 2011.
- Ferguson, P.; Berkowitz, H. (January 1997). "Network Renumbering Overview: Why would I want it and what is it anyway?". RFC 2071.
- Berkowitz, H. (January 1997). "Router Renumbering Guide". RFC 2072.
- Thomson, S.; Narten, T.; Jinmei, T. (September 2007). "IPv6 Stateless Address Autoconfiguration". RFC 4862.
- RFC 1112, Host extensions for IP multicasting, S. Deering (August 1989)
- RFC 3956, Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address, P. Savola, B. Haberman (November 2004)
- RFC 2908, The Internet Multicast Address Allocation Architecture, D. Thaler, M. Handley, D. Estrin (September 2000)
- RFC 3306, Unicast-Prefix-based IPv6 Multicast Addresses, B. Haberman, D. Thaler (August 2002)
- RFC 2894, Router Renumbering for IPv6, M. Crawford, August 2000.
- RFC 4301, IPv6 Node Requirements", J. Loughney (April 2006)
- RFC 6434, "IPv6 Node Requirements", E. Jankiewicz, J. Loughney, T. Narten (December 2011)
- RFC 3963, Network Mobility (NEMO) Basic Protocol Support, V. Devarapalli, R. Wakikawa, A. Petrescu, P. Thubert (January 2005)
- RFC 2675, IPv6 Jumbograms, D. Borman, S. Deering, R. Hinden (August 1999)
- Statement on IPv6 Address Privacy, Steve Deering & Bob Hinden, Co-Chairs of the IETF's IP Next Generation Working Group, 6 November 1999.
- "Neues Internet-Protokoll erschwert anonymes Surfen". Spiegel.de. Retrieved 19 February 2012.
- T. Narten, R. Draves (January 2001). "Privacy Extensions for Stateless Address Autoconfiguration in IPv6".
- IPv6 Essentials by Silvia Hagen, p. 28, chapter 3.5.
- Privacy Extensions (IPv6), Elektronik Kompendium.
- Overview of the Advanced Networking Pack for Windows XP, Revision: 8.14
- IPv6: Privacy Extensions einschalten, Reiko Kaps, 13 April 2011
- "Comment #61 : Bug #176125 : Bugs: "procps" package: Ubuntu". Bugs.launchpad.net. Retrieved 19 February 2012.
- RFC 4291, IP Version 6 Addressing Architecture, R. Hinden, S. Deering (February 2006)
- "The sheer size of IPv6". Pthree.org. 8 March 2009. Retrieved 20 January 2012.
- RFC 4291, p. 9
- R. Droms, J. Bound, B. Volz, T. Lemon, C. Perkins, and M. Carney, ‘Dynamic Host Configuration Protocol for IPv6 (DHCPv6)’, Internet Request for Comments, vol. RFC 3315 (Proposed Standard), Jul. 2003 [Online]. Available: http://www.rfc-editor.org/rfc/rfc3315.txt
- S. Thomson, T. Narten, and T. Jinmei, ‘IPv6 Stateless Address Autoconfiguration’, Internet Request for Comments, vol. RFC 4862 (Draft Standard), Sep. 2007 [Online]. Available: http://www.rfc-editor.org/rfc/rfc4862.txt
- T. Narten, ‘Neighbor discovery and stateless autoconfiguration in IPv6’, IEEE Internet Computing, vol. 3, no. 4, pp. 54–62, Aug. 1999. DOI: 10.1109/4236.780961
- "IPv6 Address Allocation and Assignment Policy". RIPE NCC. 8 February 2011. Retrieved 27 March 2011.
- "Comcast Activates First Users With IPv6 Native Dual Stack Over DOCSIS". Comcast. 31 January 2011.
- RFC 5952, A Recommendation for IPv6 Address Text Representation, S. Kawamura (August 2010), section 4.2.2: http://tools.ietf.org/html/rfc5952#section-4.2.2
- RFC 5952, A Recommendation for IPv6 Address Text Representation, S. Kawamura (August 2010)
- "IPv6 Transition Mechanism / Tunneling Comparison". Sixxs.net. Retrieved 20 January 2012.
- "RFC 6343–Advisory Guidelines for 6to4 Deployment". Tools.ietf.org. Retrieved 20 August 2012.
- "RFC 4213, Basic Transition Mechanisms for IPv6 Hosts and Routers". Tools.ietf.org. Retrieved 20 August 2012.
- "IPv6: Dual stack where you can; tunnel where you must". www.networkworld.com. 5 September 2007. Retrieved 27 November 2012.
- RFC 3056, Connection of IPv6 Domains via IPv4 Clouds, B. Carpenter, February 2001.
- RFC 4380, Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs), C. Huitema, Februari 2006
- "The Windows Vista Developer Story: Application Compatibility Cookbook". Msdn2.microsoft.com. 24 April 2006. Retrieved 20 January 2012.
- RFC 5214, Intra-Site Automatic Tunnel Addressing Protocol (ISATAP), F. Templin, T. Gleeson, D. Thaler, March 2008.
- RFC 3053, IPv6 Tunnel Broker, A. Durand, P. Fasano, I. Guardini, D. Lento (January 2001)
- RFC 4966, Reasons to Move the Network Address Translator-Protocol Translator (NAT-PT) to Historic Status
- Web sites must support IPv6 by 2012, expert warns. Network World. 21 January 2010. Retrieved 30 September 2010.
- "RFC4291". Tools.ietf.org. Retrieved 20 January 2012.
- "OpenBSD inet6(4) manual page". Openbsd.org. 13 December 2009. Retrieved 20 January 2012.
- "RFC 3493, Basic Socket Interface Extensions for IPv6". Tools.ietf.org. Retrieved 20 January 2012.
- "DOCSIS 2.0 Interface". Cablemodem.com. 29 October 2007. Retrieved 31 August 2009.
- "RMV6TF.org" (PDF). Retrieved 20 January 2012.[dead link]
- "DOCSIS 3.0 Network Equipment Penetration to Reach 60% by 2011" (Press release). ABI Research. 23 August 2007. Retrieved 30 September 2007.[dead link]
- Mullins, Robert (April 5, 2012), Shadow Networks: an Unintended IPv6 Side Effect, retrieved March 2, 2013
- Cicileo, Guillermo; Gagliano, Roque; O’Flaherty, Christian et al. (October 2009). IPv6 For All: A Guide for IPv6 Usage and Application in Different Environments (pdf). p. 5. Retrieved March 2, 2013.
- "IPv4 Address Report". Potaroo.net. Retrieved 20 January 2012.
- Mike Leber (2 October 2010). "Global IPv6 Deployment Progress Report". Hurricane Electric. Retrieved 19 October 2011.
- "Beijing2008.cn leaps to next-generation Net" (Press release). The Beijing Organizing Committee for the Games of the XXIX Olympiad. 30 May 2008.
- Das, Kaushik (2008). "IPv6 and the 2008 Beijing Olympics". IPv6.com. Retrieved 15 August 2008. "As thousands of engineers, technologists have worked for a significant time to perfect this (IPv6) technology, there is no doubt, this technology brings considerable promises but this is for the first time that it will showcase its strength when in use for such a mega-event."
- Derek Morr (9 June 2009). "Verizon Mandates IPv6 Support for Next-Gen Cell Phones". CircleID.
- theipv6guy (31 July 2012). "T-Mobile USA Launches External IPv6". T-Mobile.
|Wikiversity has learning materials about IPv6|
- IPv6 in the Linux Kernel by Rami Rosen.
- IPv6 at DMOZ
- Free Pool of IPv4 Address Space Depleted
- An Introduction and Statistics about IPV6
- Google IPv6 check
- IPv6 Introduction and Configuration by IBM Redbooks
- The Differences Between IPv6 and IPv4