Parts of this article (those related to RFC 8200 and RFC 8201) need to be updated
. Please update this article to reflect recent events or newly available information. (July 2017)
Internet Protocol Version 6
Devices on the Internet are assigned a unique 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 would be needed to connect devices than the IPv4 address space had available. By 1998, the IETF had formalized the successor protocol. IPv6 uses a 128-bit address, theoretically allowing 2128
, or approximately 3.4×
addresses. The actual number is slightly smaller, as multiple ranges are reserved for special use or completely excluded from use. The two protocols are not designed to be interoperable
, and thus direct communication between them is impossible, complicating the move to IPv6. However, several transition mechanisms
have been devised to rectify this.
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, separated by colons, of four hexadecimal
digits. The full representation may be shortened; for example, 2001:0db8:0000:0000:0000:8a2e:0370:7334
Glossary of terms used for IPv6 addresses
In addition to offering more addresses, IPv6 also implements features not present in IPv4. It simplifies aspects of address configuration, network renumbering, and router announcements when changing network connectivity providers. It simplifies processing of packets in routers by placing the responsibility 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.
Motivation and origin
Decomposition of the quad-dotted IPv4 address
representation to its binary value
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
. IPv4 includes an addressing system that uses 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, 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.
RIPE NCC announced that it had fully run out of IPv4 addresses on 25 November 2019,
and called for greater progress on the adoption of IPv6.
It is widely expected that the Internet will use IPv4 alongside IPv6 for the foreseeable future.
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, 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 File Transfer Protocol
(FTP) and Network Time Protocol
(NTP), 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 size of an IPv6 address is 128 bits, compared to 32 bits in IPv4.
The address space therefore has 2128 = 340,282,366,920,938,463,463,374,607,431,768,211,456 addresses (approximately
). Some blocks of this space and some specific addresses are reserved for special uses
While this address space is very large, it was not the intent of the designers of IPv6 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, about four billion times the size of the entire IPv4 address space. Thus, actual address space utilization will be small in IPv6, but network management and routing efficiency are improved by the large subnet space and hierarchical route aggregation.
Multicast structure in IPv6
, 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 has features and protocols in common 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 is achieved by sending a packet to the link-local all nodes
multicast group at address ff02::1, which is analogous to IPv4 multicasting to address 126.96.36.199. 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 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 configure themselves automatically. Every interface has a self-generated link-local address and, when connected to a network, conflict resolution is performed and routers provide network prefixes via router advertisements.
Stateless configuration of routers can be achieved with a special router renumbering protocol.
When necessary, hosts may configure additional stateful addresses via Dynamic Host Configuration Protocol version 6
(DHCPv6) or static addresses manually.
Like IPv4, IPv6 supports globally unique IP addresses
. 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 by rendering network address translation
obsolete. Therefore, every device on the network is globally addressable directly from any other device.
A stable, unique, globally addressable IP address would facilitate tracking a device across networks. Therefore, such addresses are a particular privacy concern for mobile devices, such as laptops and cell phones.
To address these privacy concerns, the SLAAC protocol includes what are typically called "privacy addresses" or, more correctly, "temporary addresses", codified in RFC 4941, "Privacy Extensions for Stateless Address Autoconfiguration in IPv6".
Temporary addresses are random and unstable. A typical consumer device generates a new temporary address daily and will ignore traffic addressed to an old address after one week. Temporary addresses are used by default by Windows since XP SP1,
macOS since (Mac OS X) 10.7, Android since 4.0, and iOS since version 4.3. Use of temporary addresses by Linux distributions varies.
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.
The SLAAC address generation method is implementation-dependent. IETF recommends that addresses are deterministic but semantically opaque.
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 part of all IPv6 protocol implementations,
and Internet Key Exchange
(IKE) was recommended, but with RFC 6434 the inclusion of IPsec in IPv6 implementations was downgraded to a recommendation because it was considered impractical to require full IPsec implementation for all types of devices that may use IPv6. However, as of RFC 4301 IPv6 protocol implementations that do implement IPsec need to implement IKEv2 and need to support a minimum set of cryptographic algorithms
. This requirement will help to make IPsec implementations more interoperable between devices from different vendors. The IPsec Authentication Header (AH) and the Encapsulating Security Payload header (ESP) are implemented as IPv6 extension headers.
Simplified processing by routers
The packet header in IPv6 is simpler than the IPv4 header. Many rarely used fields have been moved to optional header extensions.
With the simplified IPv6 packet header the process of packet forwarding by routers
has been simplified. Although IPv6 packet headers are at least twice the size of IPv4 packet headers, processing of packets that only contain the base IPv6 header by routers may, in some case, be more efficient, because less processing is required in routers due to the headers being aligned to match common word sizes
However, many devices implement IPv6 support in software (as opposed to hardware), thus resulting in very bad packet processing performance.
Additionally, for many implementations, the use of Extension Headers causes packets to be processed by a router's CPU, leading to poor performance or even security issues.
Moreover, an IPv6 header does not include a checksum. The IPv4 header checksum
is calculated for the IPv4 header, and has to be recalculated by routers every time the time to live
(called hop limit
in the IPv6 protocol) is reduced by one. The absence of a checksum in the IPv6 header furthers the end-to-end principle
of Internet design, which envisioned that most processing in the network occurs in the leaf nodes. Integrity protection for the data that is encapsulated in the IPv6 packet is assumed to be assured by both the link layer
or error detection in higher-layer protocols, namely the Transmission Control Protocol
(TCP) and the User Datagram Protocol
(UDP) on the transport layer
. Thus, while IPv4 allowed UDP datagram headers to have no checksum (indicated by 0 in the header field), IPv6 requires a checksum in UDP headers.
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 minimum size of 40 octets (320 bits). Options are implemented as extensions. This provides the opportunity to extend the protocol in the future without affecting the core packet structure.
However, RFC 7872 notes that some network operators drop IPv6 packets with extension headers when they traverse transit autonomous systems
IPv4 limits packets to 65,535 (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 4,294,967,295 (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 extension header.
IPv6 packet header
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 class, hop count, 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
The current use of the IPv6 Traffic Class field divides this between a 6 bit Differentiated Services Code Point
and a 2-bit Explicit Congestion Notification field.
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
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 with 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
A general structure for an IPv6 unicast address
have 128 bits. The design of the IPv6 address space implements a different design philosophy than in IPv4, in which subnetting was used to improve the efficiency of utilization of the small address space. In IPv6, the address space is deemed large enough for the foreseeable future, and a local area subnet always uses 64 bits for the host portion of the address, designated as the interface identifier, while the most-significant 64 bits are used as the routing prefix.
While the myth has existed regarding IPv6 subnets being impossible to scan, RFC 7707 notes that patterns resulting from some IPv6 address configuration techniques and algorithms allow address scanning in many real-world scenarios.
The 128 bits of an IPv6 address are represented in 8 groups of 16 bits each. Each group is written as four hexadecimal digits (sometimes called hextets
or more formally hexadectets
and informally a quibble or quad-nibble
) and the groups are separated by colons (:). An example of this representation is 2001:0db8:0000:0000:0000:ff00:0042:8329
For convenience and clarity, the representation of an IPv6 address may be shortened with the following rules.
- One or more leading zeros from any group of hexadecimal digits are removed, which is usually done to all of the leading zeros. For example, the group 0042 is converted to 42.
- Consecutive sections of zeros are replaced with two colons (::). This may only be used once in an address, as multiple use would render the address indeterminate. RFC 5952 requires that a double colon not be used to denote an omitted single section of zeros.
An example of application of these rules:
Initial address: 2001:0db8:0000:0000:0000:ff00:0042:8329.
After removing all leading zeros in each group: 2001:db8:0:0:0:ff00:42:8329.
After omitting consecutive sections of zeros: 2001:db8::ff00:42:8329.
The loopback address 0000:0000:0000:0000:0000:0000:0000:0001
is defined in RFC 5156
and is abbreviated to ::1
by using both rules.
Because IPv6 addresses contain colons, and URLs use colons to separate the host from the port number, RFC2732 specifies that an IPv6 address used as the host-part of a URL should be enclosed in square brackets, e.g. http://[2001:db8:4006:812::200e] or http://[2001:db8:4006:812::200e]:8080/path/page.html.
The Link-Local Unicast Address structure in IPv6
All interfaces of IPv6 hosts require a link-local address
. IPv6 link-local addresses have the prefix fe80::/10
. This prefix is combined with a 64-bit suffix, which the host can compute and/or assign by itself—without configuration and without the presence or cooperation of an external network component like a DHCP server.
The lower 64 bits of the link-local address (the suffix) were originally derived from the MAC address of the underlying network interface card. As this method of assigning addresses would cause undesirable address changes when faulty network cards were replaced, and as it also suffered from a number of security and privacy issues, RFC 8064 has replaced the original MAC-based method with the hash-based method specified in RFC 7217.
Address uniqueness and router solicitation
A host bringing up a new IPv6 interface first generates a unique link-local address using one of several mechanisms designed to generate a unique address. Should a non-unique address be detected, the host can try again with a newly generated address. Once a unique link-local address is established, the IPv6 host determines whether the LAN is connected on this link to any router
interface that supports IPv6. It does so by sending out an ICMPv6 router solicitation message to the all-routers
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, known as a router advertisement, from a router, the response includes the network configuration information to allow establishment of a globally unique address with an appropriate unicast network prefix.
There are also two flag bits that tell the host whether it should use DHCP to get further information and addresses:
- The Manage bit, which indicates whether or not the host should use DHCP to obtain additional addresses rather than rely on an auto-configured address from the router advertisement.
- The Other bit, which indicates whether or not 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:
- On-link: 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.
- Address: This flag tells the host to actually create a global address.
The global unicast address structure in IPv6
The assignment procedure for global addresses is similar to local-address construction. The prefix is supplied from router advertisements on the network. Multiple prefix announcements cause multiple addresses to be configured.
Stateless address autoconfiguration (SLAAC) requires a /64
address block, as defined in RFC 4291
. Local Internet registries
are assigned at least /32
blocks, which they divide among subordinate networks.
The initial recommendation stated assignment of a /48
subnet to end-consumer sites (RFC 3177
). 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
s are specifically considered. It remains to be seen whether ISPs will honor this recommendation. For example, during initial trials, Comcast
customers were given a single /64
IPv6 in the Domain Name System
When a dual-stack host queries a DNS server to resolve a fully qualified domain name
(FQDN), the DNS client of the host sends two DNS requests, one querying A records and the other querying AAAA records. The host operating system may be configured with a preference for address selection rules RFC 6724
An alternate record type was used in early DNS implementations for IPv6, designed to facilitate network renumbering, the A6
records for the forward lookup and a number of other innovations such as bit-string labels
records. It is defined in RFC 2874
and its references (with further discussion of the pros and cons of both schemes in RFC 3364
), but has been deprecated to experimental status (RFC 3363
IPv6 is not foreseen to supplant IPv4 instantaneously. Both protocols will continue to operate simultaneously for some time. Therefore, IPv6 transition mechanisms
are needed to enable IPv6 hosts to reach IPv4 services and to allow isolated IPv6 hosts and networks to reach each other over IPv4 infrastructure.
According to Silvia Hagen
, a dual-stack implementation of the IPv4 and IPv6 on devices is the easiest way to migrate to IPv6.
Many other transition mechanisms use tunneling to encapsulate IPv6 traffic within IPv4 networks and vice versa. This is an imperfect solution, which reduces the maximum transmission unit
(MTU) of a link and therefore complicates Path MTU Discovery
, and may increase latency
Dual-stack IP implementation
Dual-stack IP implementations provide complete IPv4 and IPv6 protocol stacks in the operating system of a computer
or network device
on top of the common physical layer
implementation, such as Ethernet
. This permits dual-stack hosts to participate in IPv6 and IPv4 networks simultaneously. The method is defined in RFC 4213
A device with dual-stack implementation in the operating system has an IPv4 and IPv6 address, and can communicate with other nodes in the LAN or the Internet using either IPv4 or IPv6. The Domain Name System
(DNS) protocol is used by both IP protocols to resolve fully qualified domain names
(FQDN) and IP addresses, but dual stack requires that the resolving DNS server can resolve both types of addresses. Such a dual stack DNS server would hold IPv4 addresses in the A records, and IPv6 addresses in the AAAA records. Depending on the destination that is to be resolved, a DNS name server may return an IPv4 or IPv6 IP address, or both. A default address selection mechanism, or preferred protocol, needs to be configured either on hosts or the DNS server. The IETF
has published Happy Eyeballs
to assist dual stack applications, so that they can connect using both IPv4 and IPv6, but prefer an IPv6 connection if it is available. However, dual-stack also needs to be implemented on all routers
between the host and the service for which the DNS server has returned an IPv6 address. Dual-stack clients should only be configured to prefer IPv6, if the network is able to forward IPv6 packets using the IPv6 versions of routing protocols
. When dual stack networks protocols are in place the application layer
can be migrated to IPv6.
ISP customers with public-facing IPv6
IPv6 Prefix Assignment mechanism with IANA, RIRs, and ISPs
Internet service providers
(ISPs) are increasingly providing their business and private customers with public-facing IPv6 global unicast addresses. However, if in the local area network (LAN) IPv4 is still used, and the ISP can only provide a public facing IPv6, the IPv4 LAN addresses are translated into the public facing IPv6 address using NAT64
, a network address translation
(NAT) mechanism. Some ISPs cannot provide their customers with public-facing IPv4 and IPv6 addresses, thus supporting dual stack networking, because some ISPs have exhausted their globally routable IPv4 address pool. Meanwhile, ISP customers are still trying to reach IPv4 web servers
and other destinations.
While some ISPs still allocate customers only IPv4 addresses, many ISPs allocate their customers only an IPv6 or dual stack IPv4 and IPv6. ISPs report the share of IPv6 traffic from customers over their network to be anything between 20% and 40%, but by mid-2017 IPv6 traffic still only accounted for a fraction of total traffic at several large Internet exchange points
reported it to be 2% and SeattleIX
reported 7%. A 2017 survey found that many DSL customers that were served by a dual stack ISP did not request DNS servers to resolve fully qualified domain names into IPv6 addresses. The survey also found that the majority of traffic from IPv6-ready webserver resources were still requested and served over IPv4, mostly due to ISP customers that did not use the dual stack facility provided by their ISP and to a lesser extent due to customers of IPv4-only ISPs.
The technical basis for tunneling, or encapsulating IPv6 packets in IPv4 packets, is outlined in RFC 4213. When the Internet backbone was IPv4-only, one of the frequently used tunneling protocols was 6to4
. Teredo tunneling
was also frequently used for integrating IPv6 LANs with the IPv4 Internet backbone. Teredo is outlined in RFC 4380 and allows IPv6 local area networks
to tunnel over IPv4 networks, by encapsulating IPv6 packets within UDP. The Teredo relay is an IPv6 router that mediates between a Teredo server and the native IPv6 network. It was expected that 6to4 and Teredo would be widely deployed until ISP networks would switch to native IPv6, but by 2014 Google Statistics showed that the use of both mechanisms had dropped to almost 0.
IPv4-mapped IPv6 addresses
IPv4-compatible IPv6 unicast address
IPv4-mapped IPv6 unicast address
Hybrid dual-stack IPv6/IPv4 implementations recognize a special class of addresses, the IPv4-mapped IPv6 addresses. These addresses are typically written with a 96-bit prefix in the standard IPv6 format, and the remaining 32 bits written in the customary dot-decimal notation
of IPv4. IPv4-mapped addresses are specified in RFC 6890
section 2.2.3 Table 20 and are defined in RFC 4291.
Addresses in this group consist of an 80-bit prefix of zeros, the next 16 bits are ones, and the remaining, least-significant 32 bits contain the IPv4 address. For example, ::ffff:192.0.2.128 represents the IPv4 address 192.0.2.128. Another format, called "IPv4-compatible IPv6 address", is ::192.0.2.128; however, this method is deprecated.
Because of the significant internal differences between IPv4 and IPv6 protocol stacks, some of the lower-level functionality available to programmers in the IPv6 stack does not work the same when used 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
, and FreeBSD
, this feature is controlled by the socket option IPV6_V6ONLY, as specified in RFC 3493
defines a class of IPv4-embedded IPv6 addresses with the address prefix 64:ff9b::/96 for use in NAT64
transition methods. For example, 64:ff9b::192.0.2.128 represents the IPv4 address 192.0.2.128.
A number of security implications may arise from the use of IPv6. Some of them may be related with the IPv6 protocols themselves, while others may be related with implementations flaws.
The addition of nodes having IPv6 enabled by default by the software manufacturer, may result in the inadvertent creation of shadow networks
, causing IPv6 traffic flowing into networks having only IPv4 security management in place. This may also occur with operating system upgrades, when the newer operating system enables IPv6 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 occurred 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, that do.
Some IPv6 stack implementors have therefore recommended disabling IPv4 mapped addresses and instead using a dual-stack network where supporting both IPv4 and IPv6 is necessary.
IPv6 packet fragmentation
Research has shown that the use of fragmentation can be leveraged to evade network security controls, similar to IPv4. As a result, RFC 7112
requires that the first fragment of an IPv6 packet contains the entire IPv6 header chain, such that some very pathological fragmentation cases are forbidden. Additionally, as a result of research on the evasion of RA-Guard in RFC 7113
, RFC 6980
has deprecated the use of fragmentation with Neighbor Discovery, and discouraged the use of fragmentation with Secure Neighbor Discovery (SEND).
Standardization through RFCs
Due to the anticipated global growth of the Internet
, the Internet Engineering Task Force
(IETF) in the early 1990s started an effort to develop a next generation IP protocol.:209
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 such 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
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
The first RFC to standardize IPv6 was the RFC 1883
in 1995, which became obsoleted by RFC 2460
In July 2017 this RFC was obsoleted by RFC 8200
, which elevated IPv6 to "Internet Standard" (the highest maturity level for IETF protocols).
Universities were among the early adopters of IPv6. Virginia Tech
deployed IPv6 at a trial location in 2004 and later expanded IPv6 deployment across the campus network
. By 2016, 82% of the traffic on their network used IPv6. Imperial College London
began experimental IPv6 deployment in 2003 and by 2016 the IPv6 traffic on their networks averaged between 20% and 40%. A significant portion of this IPv6 traffic was generated through their high energy physics
collaboration with CERN
, which relies entirely on IPv6.
By 2011, all major operating systems in use on personal computers and server systems had production-quality IPv6 implementations. Cellular telephone systems presented a large deployment field for Internet Protocol devices as mobile telephone service made the transition from 3G
technologies, in which voice is provisioned as a voice over IP
(VoIP) service that would leverage IPv6 enhancements. In 2009, the US cellular operator Verizon
released technical specifications for devices to operate on its "next-generation" networks.
The specification mandated IPv6 operation according to the 3GPP Release 8 Specifications (March 2009)
, and deprecated IPv4 as an optional capability.
The deployment of IPv6 in the Internet backbone
continued. In 2018 only 25.3% of the about 54,000 autonomous systems advertised both IPv4 and IPv6 prefixes in the global Border Gateway Protocol
(BGP) routing database. A further 243 networks advertised only an IPv6 prefix. Internet backbone transit networks offering IPv6 support existed in every country globally, except in parts of Africa
, the Middle East
By mid-2018 some major European broadband
ISPs had deployed IPv6 for the majority of their customers. British Sky Broadcasting
provided over 86% of its customers with IPv6, Deutsche Telekom
had 56% deployment of IPv6, XS4ALL
in the Netherlands had 73% deployment and in Belgium the broadband ISPs VOO
had 73% and 63% IPv6 deployment respectively.
In the United States the broadband ISP Comcast
had an IPv6 deployment of about 66%. In 2018 Comcast reported an estimated 36.1 million IPv6 users, while AT&T
reported 22.3 million IPv6 users.
- ^ New Zealand IPv6 Task Force. "FAQs". Retrieved 26 October 2015.
- ^ a b c d e f S. Deering; R. Hinden (December 1998), Internet Protocol, Version 6 (IPv6) Specification, Internet Engineering Task Force (IETF), RFC 2460 Obsoletes RFC 1883.
- ^ a b S. Deering; R. Hinden (July 2017), "Internet Protocol, Version 6 (IPv6) Specification", Ietf Request for Comments (RFC) Pages - Test, Internet Engineering Task Force (IETF), ISSN 2070-1721, RFC 8200 Obsoletes RFC 2460.
- ^ Siddiqui, Aftab (17 July 2017). "RFC 8200 – IPv6 has been standardized". Internet Society. Retrieved 25 February 2018.
- ^ a b c d Rami Rosen (2014). Linux Kernel Networking: Implementation and Theory. New York: Apress. ISBN 9781430261971. OCLC 869747983.
- ^ Google IPv6 Conference 2008: What will the IPv6 Internet look like?. Event occurs at 13:35.
- ^ a b c Bradner, S.; Mankin, A. (January 1995). The Recommendation for the IP Next Generation Protocol. IETF. doi:10.17487/RFC1752. RFC1752.
- ^ Rashid, Fahmida. "IPv4 Address Exhaustion Not Instant Cause for Concern with IPv6 in Wings". eWeek. Retrieved 23 June 2012.
- ^ Ward, Mark (14 September 2012). "Europe hits old internet address limits". BBC News. BBC. Retrieved 15 September 2012.
- ^ Huston, Geoff. "IPV4 Address Report".
- ^ "African Network Information Center : -". my.afrinic.net. Retrieved 28 November 2018.
- ^ news, Publication date: 25 Nov 2019-; ipv4; Depletion, Ipv4; ipv6; Release, Press. "The RIPE NCC has run out of IPv4 Addresses". RIPE Network Coordination Centre. Retrieved 26 November 2019.
- ^ a b Partridge, C.; Kastenholz, F. (December 1994). "Technical Criteria for Choosing IP The Next Generation (IPng)". RFC 1726.
- ^ 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)
- ^ a b Thomson, S.; Narten, T.; Jinmei, T. (September 2007). "IPv6 Stateless Address Autoconfiguration". RFC 4862.
- ^ RFC 2894, Router Renumbering for IPv6, M. Crawford, August 2000.
- ^ T. Narten; R. Draves; S. Krishnan (September 2007). "Privacy Extensions for Stateless Address Autoconfiguration in IPv6". www.ietf.org. Retrieved 13 March 2017.
- ^ Narten, Thomas; Draves, Richard; Krishnan, Suresh. Privacy Extensions for Stateless Address Autoconfiguration in IPv6. doi:10.17487/RFC4941. RFC 4941.
- ^ "Overview of the Advanced Networking Pack for Windows XP". Archived from the original on 7 September 2017. Retrieved 15 April 2019.
- ^ "Privacy Extensions for IPv6 SLAAC". Internet Society. 8 August 2014. Retrieved 17 January 2020.
- ^ 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.
- ^ Cooper, Alissa; Gont, Fernando; Thaler, Dave. Recommendation on Stable IPv6 Interface Identifiers. doi:10.17487/RFC8064. RFC8064.
- ^ Silvia Hagen (2014). IPv6 Essentials: Integrating IPv6 into Your IPv4 Network (3rd ed.). Sebastopol, CA: O'Reilly Media. p. 196. ISBN 978-1-4493-3526-7. OCLC 881832733.
- ^ "The History of Domain Names | IPv6". www.historyofdomainnames.com. Archived from the original on 12 June 2018. Retrieved 12 June 2018.
- ^ Zack, E. (July 2013). "IPv6 Security Assessment and Benchmarking".
- ^ Gont, F. (March 2016). "Operational Implications of IPv6 Packets with Extension Headers". draft-gont-v6ops-ipv6-ehs-packet-drops-03.
- ^ 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)
- ^ RFC 2474
- ^ RFC 3168
- ^ RFC 4291, p. 9.
- ^ Graziani, Rick (2012). IPv6 Fundamentals: A Straightforward Approach to Understanding IPv6. Cisco Press. p. 55. ISBN 978-0-13-303347-2.
- ^ Coffeen, Tom (2014). IPv6 Address Planning: Designing an Address Plan for the Future. O'Reilly Media. p. 170. ISBN 978-1-4919-0326-1.
- ^ a b Horley, Edward (2013). Practical IPv6 for Windows Administrators. Apress. p. 17. ISBN 978-1-4302-6371-5.
- ^ S. Kawamura (August 2010). "A Recommendation for IPv6 Address Text Representation". section 4.2.2. RFC 5952.
- ^ S. Kawamura (August 2010). "A Recommendation for IPv6 Address Text Representation". RFC 5952.
- ^ "Format for Literal IPv6 Addresses in URL's". August 2010. RFC 2732.
- ^ a b c Narten, T. (August 1999). "Neighbor discovery and stateless autoconfiguration in IPv6". IEEE Internet Computing. 3 (4): 54–62. doi:10.1109/4236.780961.
- ^ T. Narten (September 2007). "Neighbor Discovery for IP version 6 (IPv6)". section 6.3.7. RFC 4861.
- ^ S. Thomson (September 2007). "IPv6 Stateless Address Autoconfiguration". section 5.5.1. RFC 4862.
- ^ "IPv6 Address Allocation and Assignment Policy". RIPE NCC. 8 February 2011. Retrieved 27 March 2011.
- ^ Brzozowski, John (31 January 2011). "Comcast Activates First Users With IPv6 Native Dual Stack Over DOCSIS". corporate.comcast.com. Comcast. Retrieved 15 April 2019.
- ^ Silvia Hagen (2014). IPv6 Essentials: Integrating IPv6 into Your IPv4 Network. O'Reilly Media, Inc. p. 176. ISBN 9781449335267.
- ^ "IPv6 Transition Mechanism / Tunneling Comparison". Sixxs.net. Retrieved 20 January 2012.
- ^ Silvia Hagen (2014). IPv6 Essentials: Integrating IPv6 into Your IPv4 Network. O'Reilly Media, Inc. pp. 222–223. ISBN 9781449335267.
- ^ "Advisory Guidelines for 6to4 Deployment". IETF. RFC 6343. Retrieved 20 August 2012.
- ^ "IPv6: Dual stack where you can; tunnel where you must". networkworld.com. 5 September 2007. Archived from the original on 11 May 2008. Retrieved 27 November 2012.
- ^ "Basic Transition Mechanisms for IPv6 Hosts and Routers". IETF. RFC 4213. Retrieved 20 August 2012.
- ^ Silvia Hagen (2014). IPv6 Essentials: Integrating IPv6 into Your IPv4 Network. O'Reilly Media, Inc. p. 222. ISBN 9781449335267.
- ^ Juniper TechLibrary (31 August 2017). "Understanding Dual Stacking of IPv4 and IPv6 Unicast Addresses". www.juniper.net. Retrieved 13 March 2017.
- ^ "IPv6". www.nro.net. Retrieved 13 March 2017.
- ^ Enric Pujol (12 June 2017). "What stops IPv6 traffic in a dual-stack ISP?". www.apnic.net. Retrieved 13 June 2017.
- ^ Steven J. Vaughan-Nichols (14 October 2010). "Five ways for IPv6 and IPv4 to peacefully co-exist". www.zdnet.com. Retrieved 13 March 2017.
- ^ Silvia Hagen (2014). IPv6 Essentials: Integrating IPv6 into Your IPv4 Network. O'Reilly Media, Inc. p. 33. ISBN 9781449335267.
- ^ "Special-Purpose IP Address Registries". IETF. RFC 6890.
- ^ Hinden, Robert M.; Deering, Stephen E. "RFC 4291 - IP Version 6 Addressing Architecture, section 188.8.131.52. IPv4-Compatible IPv6 Address". tools.ietf.org. Retrieved 23 September 2019.
- ^ inet6(4) – OpenBSD Kernel Interfaces Manual
- ^ "Basic Socket Interface Extensions for IPv6". IETF. February 2003. p. 22. RFC 3493. Retrieved 28 November 2017.
- ^ Gont, Fernando (10 March 2019), IPv6 Security for IPv4 Engineers (PDF), retrieved 30 August 2019
- ^ Gont, Fernando (10 January 2019), IPv6 Security Frequently Asked Questions (FAQ)(PDF), retrieved 30 August 2019
- ^ Mullins, Robert (5 April 2012), Shadow Networks: an Unintended IPv6 Side Effect, archived from the original on 11 April 2013, retrieved 2 March 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 2 March 2013.
- ^ Jun-ichiro itojun Hagino (October 2003). "IPv4-Mapped Addresses on the Wire Considered Harmful".
- ^ Bradner, S.; Mankin, A. (December 1993). "IP: Next Generation (IPng) White Paper Solicitation". RFC 1550.
- ^ "History of the IPng Effort". The Sun. Archived from the original on 23 May 2014.
- ^ "The Recommendation for the IP Next Generation Protocol – Appendix B". RFC 1752.
- ^ State of IPv6 Deployment 2018, Internet Society, 2018, p. 3
- ^ "Beijing2008.cn leaps to next-generation Net" (Press release). The Beijing Organizing Committee for the Games of the XXIX Olympiad. 30 May 2008. Archived from the original on 4 February 2009.
- ^ Das, Kaushik (2008). "IPv6 and the 2008 Beijing Olympics". IPv6.com. Retrieved 15 August 2008.
- ^ a b Derek Morr (9 June 2009). "Verizon Mandates IPv6 Support for Next-Gen Cell Phones". CircleID.
- ^ State of IPv6 Deployment 2018, Internet Society, 2018, p. 6
- ^ State of IPv6 Deployment 2018, Internet Society, 2018, p. 7
- ^ State of IPv6 Deployment 2018, Internet Society, 2018, pp. 7–8
Wikiversity has learning resources about IPv6
Last edited on 5 May 2021, at 22:45
Content is available under CC BY-SA 3.0
unless otherwise noted.