Internet Protocol version 6 (
IPv6) is a version of the
Internet Protocol (IP). It is designed to succeed the
Internet Protocol version 4 (IPv4). The
Internet operates by transferring data between hosts in small
packets that are independently
routed across networks as specified by an international
communications protocol known as the Internet Protocol.
Each host or computer on the Internet requires an IP address in order to communicate. The growth of the Internet has created a need for more addresses than are possible with IPv4. IPv6 was developed by the Internet Engineering Task Force (IETF) to deal with this long-anticipated IPv4 address exhaustion, and is described in Internet standard document RFC 2460, published in December 1998. Like IPv4, IPv6 is an Internet Layer protocol for packet-switched internetworking and provides end-to-end datagram transmission across multiple IP networks. While IPv4 allows 32 bits for an Internet Protocol address, and can therefore support 232 (4,294,967,296) addresses, IPv6 uses 128-bit addresses, so the new address space supports 2128 (approximately 340 undecillion or ) addresses. This expansion allows for many more devices and users on the internet as well as extra flexibility in allocating addresses and efficiency for routing traffic. It also eliminates the primary need for network address translation (NAT), which gained widespread deployment as an effort to alleviate IPv4 address exhaustion.
IPv6 also implements additional features not present in IPv4. It simplifies aspects of address assignment (stateless address autoconfiguration), network renumbering and router announcements when changing Internet connectivity providers. The IPv6 subnet size has been 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 media addressing information (MAC address). Network security is also integrated into the design of the IPv6 architecture, and the IPv6 specification mandates support for IPsec as a fundamental interoperability requirement.
The last top level (/8) block of free IPv4 addresses was assigned in February 2011 by IANA to the 5 RIRs, although many free addresses still remain in most assigned blocks and each RIR will continue with standard policy until it is at its last /8. After that, only 1024 addresses (a /22) are made available from the RIR for each LIR – currently, only APNIC has already reached this stage. While IPv6 is supported on all major operating systems in use in commercial, business, and home consumer environments, IPv6 does not implement interoperability features with IPv4, and creates essentially a parallel, independent network. Exchanging traffic between the two networks requires special translator gateways, but modern computer operating systems implement dual-protocol software for transparent access to both networks either natively or using a tunneling protocol such as 6to4, 6in4, or Teredo. In December 2010, despite marking its 12th anniversary as a Standards Track protocol, IPv6 was only in its infancy in terms of general worldwide deployment. A 2008 study by Google Inc. indicated that penetration was still less than one percent of Internet-enabled hosts in any country at that time.
Motivation and origins
IPv4
The first publicly used version of the Internet Protocol, Version 4 (IPv4), provides an addressing capability of 232 or approximately 4.3 billion addresses. This was deemed sufficient in the early design stages of the Internet when the explosive growth and worldwide proliferation of networks connected to the internet and the internet itself was not anticipated.
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.
Working group proposal
By the beginning of 1992, several proposals appeared 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 with 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 Internet Engineering Task Force adopted the IPng model on July 25, 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 IPv4 will be supported 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.
Exhaustion of IPv4 addresses
On February 3, 2011, in a ceremony in Miami, the Internet Assigned Numbers Authority (IANA) assigned the last batch of 5 /8 address blocks to the Regional Internet Registries., officially depleting the global pool of completely fresh blocks of addresses. Each of the address blocks represents approximately 16.7 million possible addresses, or over 80 million combined potential addresses.
These addresses could well be fully consumed within three to six months of that time at current rates of allocation. APNIC was the first RIR to exhaust its regional pool on 15 April 2011, except for a small amount of address space reserved for the transition to IPv6, which will be allocated in a much more restricted way.
In 2003, the director of Asia-Pacific Network Information Centre (APNIC), Paul Wilson, stated that, based on then-current rates of deployment, the available space would last for one or two decades. In September 2005, a report by Cisco Systems suggested that the pool of available addresses would exhaust in as little as 4 to 5 years. In 2008, a policy process started for the end-game and post-exhaustion era. In 2010, a daily updated report projected the global address pool exhaustion by the first quarter of 2011, and depletion at the five regional Internet registries before the end of 2011.
Comparison to IPv4
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.
Larger address space
The most important feature of IPv6 is a much larger address space than in IPv4. The length of an IPv6 address is 128 bits, compared to 32 bits in IPv4. The address space therefore supports 2128 or approximately addresses. By comparison, this amounts to approximately addresses for each of the 6.8 billion people alive in 2010. In addition, the IPv4 address space is poorly allocated, with approximately 14% of all available addresses utilized. While these numbers are large, it was not 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
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
224.0.0.1. IPv6 also supports new multicast solutions, including embedding rendezvous point addresses in an IPv6 multicast group address which simplifies the deployment of inter-domain solutions.
In IPv4 it was very difficult for an organization to get even one globally routable multicast group assignment and the implementation of inter-domain solutions was 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.
=== (SLAAC)===
IPv6 hosts can configure themselves automatically when connected to a routed IPv6 network using 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; if configured suitably, routers respond to such a request with a router advertisement packet that contains network-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 statically.
Routers present a special case of requirements for address configuration, as they often are sources for autoconfiguration information, such as router and prefix advertisements. Stateless configuration for routers can be achieved with a special router renumbering protocol.
Mandatory support for network layer security
Internet Protocol Security (IPsec) was originally developed for IPv6, but found widespread deployment first in IPv4, into which it was back-engineered. IPsec is an integral part of the base protocol suite in IPv6. IPsec support is mandatory in IPv6 but optional for IPv4.
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 minimum 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. Therefore, IPv6 routers do not need to recompute a checksum when header fields (such as the
time to live (TTL) or
hop count) change.
The ''TTL'' field of IPv4 has been renamed to ''Hop Limit'', reflecting the fact that routers are no longer expected to compute the time a packet has spent in a queue.
Mobility
Unlike mobile IPv4,
mobile IPv6 avoids
triangular routing and is therefore as efficient as native IPv6. IPv6 routers may also support network mobility which allows entire subnets to move to a new router connection point without renumbering.
Options extensibility
The IPv6 protocol 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 provides extensibility to support future services for
quality of service, security, mobility, and others, without redesign of the basic protocol.
Jumbograms
IPv4 limits packets to (2
16 – 1) octets of payload. IPv6 has optional support for packets over this limit, referred to as
jumbograms, which can be as large as (2
32 – 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.
Packet format
The IPv6 packet is composed of two parts: the packet header and the payload.
The header consists of a fixed portion with minimal functionality required for all packets and may contain optional extension 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 a pointer for extension headers if any. The ''Next Header'' field, present in each extension as well, points to the next element in the chain of extensions. The last field 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.
The payload can have a size of up to without special options, or larger with a jumbo payload option in a ''Hop-By-Hop Options'' extension header.
Unlike in IPv4, fragmentation is handled only in the end points of a communication session; routers never fragment a packet, and hosts are expected to use Path MTU Discovery to select a packet size that can traverse the entire communications path.
Addressing
The most important feature of IPv6 is a much larger address space than in IPv4. IPv6 addresses are 128 bits long, compared to only 32 bits previously. While the IPv4 address space contains only about (4.3 billion) addresses, IPv6 supports approximately (340 undecillion) unique addresses, deemed enough for the foreseeable future.
IPv6 addresses are written in eight groups of four hexadecimal digits separated by colons, for example, 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.
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 have been 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 the address for loopback, 6to4 tunneling, Teredo tunneling and several more. See 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.
Address Format
IPv6 addresses have two logical parts: a 64-bit network prefix, and a 64-bit host address part. (The host address is often automatically generated from the interface MAC address.) An IPv6 address is represented by 8 groups of 16-bit hexadecimal values separated by colons (:) shown as follows:
A typical example of an IPv6 address is
:2001:0db8:85a3:0000:0000:8a2e:0370:7334
The hexadecimal digits are case-insensitive.
The 128-bit IPv6 address can be abbreviated with the following rules:
Rule one: Leading zeroes within a 16-bit value may be omitted. For example, the address fe80:0000:0000:0000:0202:b3ff:fe1e:8329 may be written as fe80:0:0:0:202:b3ff:fe1e:8329
Rule two: One group of consecutive zeroes within an address may be replaced by a double colon. For example, fe80:0:0:0:202:b3ff:fe1e:8329 becomes fe80::202:b3ff:fe1e:8329
A single IPv6 address can be represented in several different ways, such as 2001:db8::1:0:0:1 and 2001:0DB8:0:0:1::1. RFC 5952 recommends a canonical textual representation.
Transition mechanisms
Until IPv6 completely supplants IPv4, a number of transition mechanisms are needed to enable IPv6-only hosts to reach IPv4 services and to allow isolated IPv6 hosts and networks to reach the IPv6 Internet over the IPv4 infrastructure.
For the period while IPv6 hosts and routers co-exist with IPv4 systems various proposals have been made:
RFC 4213, ''Basic Transition Mechanisms for IPv6 Hosts and Routers''
RFC 2766, ''Network Address Translation — Protocol Translation NAT-PT'', obsoleted as explained in RFC 4966 ''Reasons to Move the Network Address Translator — Protocol Translator NAT-PT to Historic Status''
RFC 2185, ''Routing Aspects of IPv6 Transition''
RFC 3056, ''6to4. Connection of IPv6 Domains via IPv4 Clouds''
RFC 4380, ''Teredo: Tunneling IPv6 over UDP through Network Address Translations NATs''
RFC 4798, ''Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)''
RFC 5214, ''Intra-Site Automatic Tunnel Addressing Protocol ISATAP''
RFC 3053, ''IPv6 Tunnel Broker''
RFC 3142, ''An IPv6-to-IPv4 Transport Relay Translator''
RFC 5569, ''IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)''
RFC 5572, ''IPv6 Tunnel Broker with the Tunnel Setup Protocol (TSP)''
RFC 6180, ''Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment''
RFC 6343, ''Advisory Guidelines for 6to4 Deployment''
Dual IP stack implementation
The dual-stack protocol implementation in an
operating system is a fundamental IPv4-to-IPv6 transition technology. It implements IPv4 and IPv6 protocol stacks either independently or in a hybrid form. The hybrid form is commonly implemented in modern operating systems supporting IPv6. Dual-stack hosts are described in RFC 4213.
Modern hybrid dual-stack implementations of IPv4 and IPv6 allow programmers to write networking code that works transparently on IPv4 or IPv6. The software may use hybrid sockets designed to accept both IPv4 and IPv6 packets. When used in IPv4 communications, hybrid stacks use an IPv6 application programming interface and represent IPv4 addresses in a special address format, the IPv4-mapped IPv6 address.
IPv4-mapped IPv6 addresses
Hybrid dual-stack IPv6/IPv4 implementations support a special class of addresses, the IPv4-mapped IPv6 addresses. This address type has its first 80 bits set to zero and the next 16 set to one, while its last 32 bits are filled with the
IPv4 address. These addresses are commonly represented in the standard IPv6 format, but having the last 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. It substitutes the old and deprecated IPv4-compatible IPv6 address formed by
::192.0.2.128.
Because of the significant internal differences between IPv4 and IPv6, some of the lower level functionality available to programmers in the IPv6 stack do not work identically with IPv4 mapped addresses. Some common IPv6 stacks do not support 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, it is necessary to open a separate socket for each IP protocol that is to be supported. 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.
Tunneling
In order to reach the IPv6 Internet, an isolated host or network must use the existing IPv4 infrastructure to carry IPv6 packets. This is done using a technique known as ''
tunneling'' which consists of encapsulating IPv6 packets within IPv4, in effect using IPv4 as a link layer for IPv6.
The direct encapsulation of IPv6 datagrams within IPv4 packets is indicated by IP protocol number 41. IPv6 can also be encapsulated within UDP packets e.g. in order to cross a router or NAT device that blocks protocol 41 traffic. Other encapsulation schemes, such as used in AYIYA or GRE, are also popular.
Conversely, on IPv6-only internet links, when access to IPv4 network facilities are needed, tunneling of IPv4 over IPv6 protocol occurs, using the IPv6 as a link layer for IPv4.
Automatic tunneling
''Automatic tunneling'' refers to a technique where the routing infrastructure automatically determines the tunnel endpoints.
6to4 is recommended by RFC 3056 tunneling method for automatic tunneling, which 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 widely deployed today.
''Teredo'' is an automatic tunneling technique that uses UDP encapsulation and can allegedly cross multiple NAT boxes. IPv6, including 6to4 and Teredo tunneling, are enabled by default in Windows Vista and Windows 7. Most Unix systems only implement native support for 6to4, but Teredo can be provided by third-party software such as Miredo.
''ISATAP'' treats 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'' tunnelling mechanisms, ISATAP is an ''intra-site'' mechanism, meaning that it is designed to provide IPv6 connectivity between nodes within a single organisation.
Configured and automated tunneling (6in4)
In ''configured tunneling'', the tunnel endpoints are 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 behaviour 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 due to a number of criticisms, however more recently the continued low adoption of IPv6 has prompted a new standardization effort under the name NAT64.
Application transition
RFC 4038, ''Application Aspects of IPv6 Transition'', is an informational RFC that covers the topic of IPv4 to IPv6 application transition mechanisms. Other RFCs that pertain IPv6 at the application level are:
RFC 3493, ''Basic Socket Interface Extensions for IPv6''
RFC 3542, ''Advanced Sockets Application Program Interface (API) for IPv6''
Similar to the OS-level WAN stack, applications can be:
IPv4 only
IPv6 only
dual set of IPv4 and IPv6 only
hybrid IPv4 and IPv6
IPv6 readiness
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) suggests that all Internet servers be prepared to serve IPv6-only clients by January 2012.
Software
Most personal computers running recent
operating system versions are IPv6-ready. Most popular applications with network capabilities are ready, and most others could be easily upgraded with support from the developers. Java applications adhering to Java 1.4 (February 2002) standards have support for IPv6.
Hardware and embedded systems
Low-level equipment like
network adapters and
network switches may not be affected by the change, since they transmit link layer frames without inspecting the contents. Networking devices that obtain IP addresses or perform routing based on IP address do need IPv6 support.
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.
Consumers view networking devices as household appliances that do not need maintenance. Little effort has been made to educate consumers about the need to upgrade.
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 also supports IPv6, which may on the cable modem side only require 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.
Other equipment which is typically not IPv6-ready ranges from Voice over Internet Protocol devices to laboratory equipment and printers.
Deployment
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. The final phase of exhaustion started on February 3, 2011.
In 2008, IPv6 accounted for a minuscule fraction of the used addresses and the traffic in the publicly-accessible Internet which is still dominated by IPv4. In October 2010, 243 (83%) of the 294 top-level domains (TLDs) in the Internet supported IPv6 to access their domain name servers, and 203 (69%) zones contained IPv6 glue records, and approximately 1.4 million domains (1%) had IPv6 address records in their zones. Of all networks in the global BGP routing table, 7.2% have IPv6 protocol support.
The 2008 Summer Olympic Games were a notable event in terms of IPv6 deployment, being the first time a major world event has had a presence on the IPv6 Internet at http://ipv6.beijing2008.cn/en and all network operations of the Games were conducted using IPv6. At the time of the event, it was believed that the Olympics provided the largest showcase of IPv6 technology since the inception of IPv6. Since that time, major providers of Internet services, such as Google, have begun to implement IPv6 access into their products.
Cellular telephone systems present a large deployment field for Internet Protocol devices as mobile telephone service is being transitioned from 3G systems to next generation (4G) technologies in which voice is provisioned as a Voice over Internet Protocol (VoIP) service. This mandates the use of IPv6 for such networks. In the U.S., cellular operator Verizon has released technical specifications for devices operating on its future networks. The specification mandates IPv6 operation according to the ''3GPP Release 8 Specifications (March 2009)'' and deprecates IPv4 as an optional capability.
Some implementations of the BitTorrent peer-to-peer file transfer protocol make use of IPv6 to avoid NAT issues common for IPv4 private networks.
All major operating systems in use as of 2010 on personal computers and server systems have production quality IPv6 implementations. Microsoft Windows has supported IPv6 since Windows 2000, and in production ready state beginning with Windows XP. Windows Vista and later have improved IPv6 support. Mac OS X Panther (10.3), Linux 2.6, FreeBSD, and Solaris also have mature production implementations.
Controversy
Privacy extensions are, except for the Windows platform, not enabled by default. That the unique MAC address is exposed to the internet and therefore makes devices trackable caused criticism of data privacy responsibles in various countries. Two actions are necessary to guarantee the same level as with today's IPv4 networks: the client device has the privacy extensions enabled, and the provider dynamically assigns a varying address block to the client device.
Major milestones
| Year |
Major development and availability milestones
|
|
|
| 6bone (an IPv6 virtual network for testing) is started.
|
|
|
|
| 1998
|
Microsoft Research releases its first experimental IPv6 stack. This support is not intended for use in a production environment.
|
|
Production-quality BSD support for IPv6 becomes generally available in early to mid-2000 in FreeBSD, OpenBSD, and NetBSD via the KAME project.
|
| Microsoft releases an IPv6 technology preview version for Windows 2000 in March 2000.
|
| Sun Microsystems |
| [[Compaq ships IPv6 with Tru64.
|
|
In January, Compaq ships IPv6 with OpenVMS.
|
| Cisco Systems introduces IPv6 support on Cisco IOS routers and L3 switches.
|
| HP introduces IPv6 with HP-UX 11i v1.
|
| On April 23, 2001, the European Commission launches the European IPv6 Task Force
|
|
Microsoft Windows NT 4.0 and Windows 2000 SP1 have limited IPv6 support for research and testing since at least 2002.
|
| Microsoft Windows XP (2001) supports IPv6 for developmental purposes. In Windows XP SP1 (2002) and Windows Server 2003, IPv6 is included as a core networking technology, suitable for commercial deployment.
|
| IBM z/OS supports IPv6 since version 1.4 (generally availability in September 2002).
|
|
Apple Inc. |
|
In July, [[ICANN announces that IPv6 address records for the Japan (jp) and Korea (kr) country code top-level domain nameservers are visible in the DNS root server zone files with serial number 2004072000. The IPv6 records for France (fr) are added later. This makes IPv6 DNS publicly operational.
|
|
Linux 2.6.12 removes experimental status from its IPv6 implementation.
|
|
Microsoft Windows Vista (2007) supports IPv6 which is enabled by default.
|
| Apple's AirPort Extreme 802.11n base station includes an IPv6 gateway in its default configuration. It uses 6to4 tunneling and manually configured static tunnels. (Note: 6to4 was disabled by default in later firmware revisions.)
|
|
On February 4, 2008, IANA adds AAAA records for the IPv6 addresses of six root name servers. With this transition, it is now possible to resolve domain names using only IPv6.
|
| On March 12, 2008, Google launches a public IPv6 web interface to its popular search engine at the URL http://ipv6.google.com.
|
| On March 12, 2008, IETF does an hour long IPv4 blackout at its meeting as an opportunity to capture informal experience data to inform protocol design work going forward; this led to many fixes in operating systems and applications.
|
| On May 27, 2008, the European Commission publish their Action Plan for the deployment of Internet Protocol version 6 (IPv6) in Europe, with the aim of making IPv6 available to 25% of European users by 2010.
|
|
|
|
On June 8, 2011 the Internet Society together with several other big companies and organizations held World IPv6 Day, a global 24 hour test of IPv6.
|
See also
China Next Generation Internet
Comparison of IPv6 application support
Comparison of IPv6 support in routers
Comparison of IPv6 support in operating systems
Comparison of IPv6 support by major transit providers
3GPP
List of IPv6 tunnel brokers
Miredo
SATSIX
University of New Hampshire InterOperability Laboratory involvement in the IPv6 Ready Logo Program
The US DoD Joint Interoperability Test Command DoD IPv6 Product Certification Program
National Advanced IPv6 Centre, a Research Group under Universiti Sains Malaysia, focussing on R&D; activities in IPv6
Notes
References
External links
IPv6 News – Daily Updated and IPv6 Portal + IPv6 Task Forces
IPv6 Backbone Network Topology
IPv4 Exhaustion Counter
Getipv6.info Technical information on IPv6 deployment from ARIN
6DEPLOY – IPv6 deployment support action within the European 7th Framework Programme, featuring an extensive list of tutorials
List of product, services and applications with IPv6 support
Why IPv6 matters to radio stations
Security implications of implementing IPv6
Free Pool of IPv4 Address Space Depleted
Category:IPv6
Category:Internet Protocol
Category:Internet Layer protocols
Category:Network layer protocols
Category:1996 introductions
ar:بروتوكول الإنترنت النسخة السادسة
az:IPv6
bs:IPv6
bg:IPv6
ca:IPv6
cs:IPv6
da:IPv6
de:IPv6
et:IPv6
es:IPv6
eu:IPv6
fa:پروتکل اینترنت نسخه ۶
fr:IPv6
gl:Protocolo IPv6
ko:IPv6
hr:IPv6
id:Alamat IP versi 6
is:IPv6
it:IPv6
he:IPv6
hu:IPv6
mk:IPv6
ms:Protokol Internet versi 6
nl:Internet Protocol versie 6
ja:IPv6
no:IPv6
nn:IPv6
pl:IPv6
pt:IPv6
ro:IPv6
ru:IPv6
sk:IPv6
sl:IPv6
sr:IPv6
fi:IPv6
sv:IPv6
ta:இ.நெறி ப6
tr:IPv6
uk:IPv6
yi:IPv6
yo:IPv6
zh:IPv6
