Internet Protocol version 6 (IPv6) is an Internet Protocol The Internet Protocol is a protocol used for communicating data across a packet-switched internetwork using the Internet Protocol Suite, also referred to as TCP/IP version which is designed to succeed IPv4 Internet Protocol version 4 is the fourth revision in the development of the Internet Protocol (IP) and it is the first version of the protocol to be widely deployed. Together with IPv6, it is at the core of standards-based internetworking methods of the Internet. IPv4 is still by far the most widely deployed Internet Layer protocol. As of 2010[, the first implementation which is still in dominant use currently[update]. It is an Internet Layer The Internet Layer is a group of internetworking methods in the TCP/IP protocol suite which is the foundation of the Internet . It is the group of methods, protocols, and specifications which are used to transport datagrams (packets) from the originating host across network boundaries, if necessary, to the destination host specified by a network protocol for packet In information technology, a packet is a formatted unit of data carried by a packet mode computer network. Computer communications links that do not support packets, such as traditional point-to-point telecommunications links, simply transmit data as a series of bytes, characters, or bits alone. When data is formatted into packets, the bitrate of-switched internetworks Internetworking is the practice of connecting a computer network with other networks through the use of gateways that provide a common method of routing information packets between the networks. The resulting system of interconnected networks is called an internetwork, or simply an internet. The main driving force for the redesign of Internet Protocol is the foreseeable IPv4 address exhaustion IPv4 address exhaustion is the decreasing supply of unallocated IPv4 addresses available at the Internet Assigned Numbers Authority and the regional Internet registries for assignment to end users and local Internet registries, such as Internet service providers. IPv6 was defined in December 1998 by the Internet Engineering Task Force The Internet Engineering Task Force develops and promotes Internet standards, cooperating closely with the W3C and ISO/IEC standards bodies and dealing in particular with standards of the TCP/IP and Internet protocol suite. It is an open standards organization, with no formal membership or membership requirements. All participants and managers are (IETF) with the publication of an Internet standard In computer network engineering, an Internet Standard is a normative specification of a technology or methodology applicable to the Internet. Internet Standards are created and published by the Internet Engineering Task Force (IETF) specification, RFC 2460.

IPv6 has a vastly larger address space than IPv4. This results from the use of a 128-bit address, whereas IPv4 uses only 32 bits. The new address space thus supports 2128 (about 3.4×1038) addresses. This expansion provides flexibility in allocating addresses and routing traffic and eliminates the primary need for network address translation In computer networking, network address translation is the process of modifying network address information in datagram (IP) packet headers while in transit across a traffic routing device for the purpose of remapping a given address space into another (NAT), which gained widespread deployment as an effort to alleviate IPv4 address exhaustion.

IPv6 also implements new features that simplify aspects of address assignment (stateless address autoconfiguration) and network renumbering (prefix and router announcements) when changing Internet connectivity providers. The IPv6 subnet A subnetwork, or subnet, is a logically visible, distinctly addressed part of a single Internet Protocol network. The process of subnetting is the division of a computer network into groups of computers that have a common, designated IP address routing prefix 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 In computer networking, the Link Layer is the lowest layer in the Internet Protocol Suite, the networking architecture of the Internet . It is the group of methods or protocols that only operate on a host's link. The link is the physical and logical network components used to interconnect hosts or nodes in the network and a link protocol is a media addressing information (MAC address In computer networking, a Media Access Control address is a unique identifier assigned to most network adapters or network interface cards (NICs) by the manufacturer for identification, and used in the Media Access Control protocol sub-layer. If assigned by the manufacturer, a MAC address usually encodes the manufacturer's registered).

Network security In the field of networking, the specialist area of network security consists of the provisions made in an underlying computer network infrastructure, policies adopted by the network administrator to protect the network and the network-accessible resources from unauthorized access, and consistent and continuous monitoring and measurement of its is integrated into the design of the IPv6 architecture. Internet Protocol Security (IPsec) Internet Protocol Security is a protocol suite for securing Internet Protocol (IP) communications by authenticating and encrypting each IP packet of a data stream. IPsec also includes protocols for establishing mutual authentication between agents at the beginning of the session and negotiation of cryptographic keys to be used during the session was originally developed for IPv6, but found widespread optional deployment first in IPv4 (into which it was back-engineered). The IPv6 specifications mandate IPsec Internet Protocol Security is a protocol suite for securing Internet Protocol (IP) communications by authenticating and encrypting each IP packet of a data stream. IPsec also includes protocols for establishing mutual authentication between agents at the beginning of the session and negotiation of cryptographic keys to be used during the session implementation as a fundamental interoperability requirement.

In December 2008, despite marking its 10th anniversary as a Standards Track protocol, IPv6 was only in its infancy in terms of general worldwide deployment Internet Protocol Version 6 is the next generation of the Internet Protocol that is currently in various stages of deployment on the Internet. It was designed as a replacement of the current version, IPv4, that has been in use since 1982 and is in the final stages of exhausting its unallocated address space. A 2008 study[1] by Google Inc. Google Inc. is an American public corporation, earning revenue from advertising related to its Internet search, e-mail, online mapping, office productivity, social networking, and video sharing services as well as selling advertising-free versions of the same technologies. Google has also developed an open source web browser and a mobile operating indicated that penetration was still less than one percent of Internet-enabled hosts in any country. IPv6 has been implemented on all major operating systems in use in commercial, business, and home consumer environments.[2]

Contents

Motivation and origins

The first publicly used version of the Internet Protocol The Internet Protocol is a protocol used for communicating data across a packet-switched internetwork using the Internet Protocol Suite, also referred to as TCP/IP, Version 4 (IPv4 Internet Protocol version 4 is the fourth revision in the development of the Internet Protocol (IP) and it is the first version of the protocol to be widely deployed. Together with IPv6, it is at the core of standards-based internetworking methods of the Internet. IPv4 is still by far the most widely deployed Internet Layer protocol. As of 2010[), provides an addressing capability of about 4 billion addresses (232). This was deemed sufficient in the early design stages of the Internet The Internet is a global system of interconnected computer networks that use the standard Internet Protocol Suite to serve billions of users worldwide. It is a network of networks that consists of millions of private, public, academic, business, and government networks of local to global scope that are linked by a broad array of electronic and when the explosive growth and worldwide proliferation of networks was not anticipated.

During the first decade of operation of the TCP/IP-based 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 introduction of classless network Classless Inter-Domain Routing is a mechanism introduced to slow the growth of routing tables on routers across the internet, and to help prevent wastage of IP addresses by allocating a subset (as opposed to whole chunks) of a Class A, B ,or C network to ISP's and organisations. It allows for address specified in CIDR notation, address aggregation redesign, it became clear that this would not suffice to prevent IPv4 address exhaustion IPv4 address exhaustion is the decreasing supply of unallocated IPv4 addresses available at the Internet Assigned Numbers Authority and the regional Internet registries for assignment to end users and local Internet registries, such as Internet service providers and that further changes to the Internet infrastructure were needed.[3] By the beginning of 1992, several proposed systems were being circulated, and by the end of 1992, the IETF announced a call for white papers (RFC 1550) and the creation of the "IP Next Generation" (IPng) area of working groups A working group is an interdisciplinary collaboration of researchers working on new research activities that would be difficult to develop under traditional funding mechanisms (e.g. federal agencies). The lifespan of the WG can last anywhere between a few months and several years. Such groups have the tendency to develop a quasi-permanent.[3][4]

The Internet Engineering Task Force adopted IPng on July 25, 1994, with the formation of several IPng working groups.[3] By 1996, a series of RFCs In computer network engineering, a Request for Comments is a memorandum published by the Internet Engineering Task Force (IETF) describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems were released defining Internet Protocol Version 6 (IPv6), starting with RFC 1883.

Incidentally, the IPng architects could not use version number 5 as a successor to IPv4, because it had been assigned to an experimental flow-oriented streaming Streaming media are multimedia that are constantly received by, and normally presented to, an end-user while being delivered by a streaming provider . The name refers to the delivery method of the medium rather than to the medium itself. The distinction is usually applied to media that are distributed over telecommunications networks, as most protocol (Internet Stream Protocol The Internet Stream Protocol is an experimental protocol defined in Internet Engineering Note IEN-119 (1979), which was later revised in RFC 1190 (ST2) and RFC 1819 (ST2+). ST packets carried the experimental non-IP real-time stream protocol), similar to IPv4, intended to support video and audio.

It is widely expected that IPv4 will be supported alongside IPv6 for the foreseeable future. IPv4-only nodes are not able to communicate directly with IPv6 nodes, and will need assistance from an intermediary; see Transition mechanisms below.

IPv4 exhaustion

IPv4 exhaustion, between 1995 and 2010. The y axis represents free blocks of 16 millions addresses (/8). Main article: IPv4 address exhaustion IPv4 address exhaustion is the decreasing supply of unallocated IPv4 addresses available at the Internet Assigned Numbers Authority and the regional Internet registries for assignment to end users and local Internet registries, such as Internet service providers

Estimates of the time frame until complete exhaustion of IPv4 addresses varied widely. In 2003, Paul Wilson (director of APNIC The Asia Pacific Network Information Centre is the Regional Internet Registry for the Asia Pacific region) stated that, based on then-current rates of deployment, the available space would last for one or two decades.[5] In September 2005, a report by Cisco Systems Cisco Systems, Inc. is an American multinational corporation that designs and sells consumer electronics, networking and communications technology and services. Headquartered in California, Cisco has more than 65,000 employees and annual revenue of US$36.11 billion as of 2009. The stock was added to the Dow Jones Industrial Average on June 8, 2009, suggested that the pool of available addresses would dry up in as little as 4 to 5 years.[6] As of May 2009[update], a daily updated report projected that the IANA The Internet Assigned Numbers Authority is the entity that oversees global IP address allocation, root zone management for the Domain Name System (DNS), media types, and other Internet Protocol related assignments. It is operated by the Internet Corporation for Assigned Names and Numbers, better known as ICANN pool of unallocated addresses would be exhausted in June 2011, with the various Regional Internet Registries A regional Internet registry is an organization overseeing the allocation and registration of Internet number resources within a particular region of the world. Resources include IP addresses (both IPv4 and IPv6) and autonomous system numbers (for use in BGP routing) using up their allocations from IANA in March 2012.[7] There is now consensus among Regional Internet Registries that final milestones of the exhaustion process will be passed in 2010 or 2011 at the latest, and a policy process has started for the end-game and post-exhaustion era.[8]

Features and differences from IPv4

In most regards, 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 File Transfer Protocol is a standard network protocol used to copy a file from one host to another over a TCP/IP-based network, such as the Internet. FTP is built on a client-server architecture and utilizes separate control and data connections between the client and server applications, which solves the problem of different end host or NTPv3 The Network Time Protocol is a protocol for synchronizing the clocks of computer systems over packet-switched, variable-latency data networks. NTP uses UDP on port 123 as its transport layer. It is designed particularly to resist the effects of variable latency by using a jitter buffer. NTP also refers to a reference software implementation that.

IPv6 specifies a new packet format, designed to minimize packet-header processing. Since the headers of IPv4 packets and IPv6 packets are significantly different, the two protocols are not interoperable.

Larger address space

The most important feature of IPv6 is a much larger address space than that of IPv4: addresses in IPv6 are 128 bits long, compared to 32-bit addresses in IPv4.

An illustration of an IP address (version 6), in hexadecimal In mathematics and computer science, hexadecimal is a positional numeral system with a radix, or base, of 16. It uses sixteen distinct symbols, most often the symbols 0–9 to represent values zero to nine, and A, B, C, D, E, F (or alternatively a through f) to represent values ten to fifteen. For example, the hexadecimal number 2AF3 is equal, in and binary The binary numeral system, or base-2 number system, represents numeric values using two symbols, 0 and 1. More specifically, the usual base-2 system is a positional notation with a radix of 2. Owing to its straightforward implementation in digital electronic circuitry using logic gates, the binary system is used internally by all modern computers.

The very large IPv6 address space supports a total of 2128 (about 3.4×1038) addresses—or approximately 5×1028 (roughly 295) addresses for each of the roughly 6.8 billion (6.8×109) people alive in 2010.[9] In another perspective, this is the same number of IP addresses per person as the number of atoms in a metric ton of carbon.

While these numbers are impressive, it was not the intent of the designers of the IPv6 address space to assure geographical saturation with usable addresses. Rather, the longer addresses allow a better, systematic, hierarchical allocation of addresses and efficient route aggregation. With IPv4, complex Classless Inter-Domain Routing Classless Inter-Domain Routing is a methodology of allocating IP addresses and routing Internet Protocol packets. It was introduced in 1993 to replace the prior addressing architecture of classful network design in the Internet with the goal to slow the growth of routing tables on routers across the Internet, and to help prevent the rapid (CIDR) techniques were developed to make the best use of the small address space. Renumbering an existing network for a new connectivity provider with different routing prefixes is a major effort with IPv4, as discussed in RFC 2071 and RFC 2072. 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 size of a subnet in IPv6 is 264 addresses (64-bit subnet mask), the square of the size of the entire IPv4 Internet. Thus, actual address space utilization rates will likely be small in IPv6, but network management and routing will be more efficient because of the inherent design decisions of large subnet space and hierarchical route aggregation A supernet is an Internet Protocol network that is formed from the combination of two or more networks (or subnets) with a common Classless Inter-Domain Routing (CIDR) routing prefix. The new routing prefix for the combined network aggregates the prefixes of the constituent networks. It must not contain other prefixes of networks that do not lie.

Stateless address autoconfiguration

IPv6 hosts can configure themselves automatically when connected to a routed IPv6 network using ICMPv6 Internet Control Message Protocol Version 6 is the implementation of the Internet Control Message Protocol (ICMP) for Internet Protocol version 6 (IPv6). ICMPv6 is an integral part of IPv6 and performs error reporting, diagnostic functions (e.g., ping), neighbor discovery, and a framework for extensions to implement future Internet Protocol router discovery messages. When first connected to a network, a host sends a link-local multicast Multicast addressing is a network technology for the delivery of information to a group of destinations simultaneously using the most efficient strategy to deliver the messages over each link of the network only once, creating copies only when the links to the multiple destinations split router solicitation 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.[10]

If IPv6 stateless address autoconfiguration is unsuitable for an application, a network may use stateful configuration with the Dynamic Host Configuration Protocol The Dynamic Host Configuration Protocol is a computer networking protocol used by hosts (DHCP clients) to retrieve IP address assignments and other configuration information for IPv6 (DHCPv6 DHCPv6 is the Dynamic Host Configuration Protocol for IPv6. Although IPv6's stateless address autoconfiguration removes the primary motivation for DHCP in IPv4, DHCPv6 can still be used to statefully assign addresses if the network administrator desires more control over addressing. It can also be used to distribute information which is not) 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.[11]

Multicast

Multicast, the ability to send a single packet to multiple destinations, is part of the base specification in IPv6. This is unlike IPv4, where it is optional (although usually implemented).

IPv6 does not implement broadcast, which is the ability to send a packet to all hosts on the attached link. The same effect can be achieved by sending a packet to the link-local all hosts multicast group. It therefore lacks the notion of a broadcast address—the highest address in a subnet (the broadcast address for that subnet in IPv4) is considered a normal address in IPv6. Most environments, however, do not currently[update] have their network infrastructures configured to route multicast packets; multicasting on a single subnet will work, but global multicasting might not.

IPv6 multicast shares common features and protocols with IPv4 multicast, but also provides changes and improvements. When even the smallest IPv6 global routing prefix is assigned to an organization, the organization is also assigned the use of 4.2 billion globally routable source-specific IPv6 multicast groups to assign for inner-domain or cross-domain multicast applications [RFC 3306]. In IPv4 it was very difficult for an organization to get even one globally routable cross-domain multicast group assignment and implementation of cross-domain solutions was very arcane [RFC 2908]. IPv6 also supports new multicast solutions, including Embedded Rendezvous Point [RFC 3956] which simplifies the deployment of cross domain solutions.

Mandatory network layer security

Internet Protocol Security (IPsec) Internet Protocol Security is a protocol suite for securing Internet Protocol (IP) communications by authenticating and encrypting each IP packet of a data stream. IPsec also includes protocols for establishing mutual authentication between agents at the beginning of the session and negotiation of cryptographic keys to be used during the session, the protocol for IP encryption and authentication, forms an integral part of the base protocol suite in IPv6. IPsec support is mandatory in IPv6; this is unlike IPv4, where it is optional (but usually implemented). IPsec, however, is not widely used at present except for securing traffic between IPv6 Border Gateway Protocol The Border Gateway Protocol is the core routing protocol of the Internet. It maintains a table of IP networks or 'prefixes' which designate network reachability among autonomous systems (AS). It is described as a path vector protocol. BGP does not use traditional Interior Gateway Protocol (IGP) metrics, but makes routing decisions based on path, routers.

Simplified processing by routers

A number of simplifications have been made to the packet header, and the process of packet forwarding has been simplified, in order to make packet processing by routers simpler and hence more efficient. Specifically:

Mobility

Unlike mobile IPv4, Mobile IPv6 Mobile IPv6 is a version of Mobile IP - a network layer IP standard used by electronic devices to exchange data across a packet switched internetwork. Mobile IPv6 allows an IPv6 node to be mobile—to arbitrarily change its location on an IPv6 network—and still maintain existing connections (MIPv6) avoids triangular routing and is therefore as efficient as normal IPv6. IPv6 routers may also support Network Mobility (NEMO, RFC 3963) which allows entire subnets to move to a new router connection point without renumbering. However, since neither MIPv6 nor MIPv4 or NEMO are widely deployed today, this advantage is mostly theoretical.

Options extensibility

IPv4 has a fixed size (40 octets) of option parameters. In IPv6, 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 allows IPv6 to be easily 'extended' to support future services for QoS In the field of computer networking and other packet-switched telecommunication networks, the traffic engineering term quality of service refers to resource reservation control mechanisms rather than the achieved service quality. Quality of service is the ability to provide different priority to different applications, users, or data flows, or to, security, mobility, etc. without a redesign of the basic protocol.

Jumbograms

IPv4 limits packets to 65535 (216 - 1) octets of payload. IPv6 has optional support for 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.

Packet format

Main article: IPv6 packet

The IPv6 packet is composed of three main parts: the fixed header, optional extension headers and the payload.

The fixed header makes up the first 40 octets Octet refers to an entity having exactly eight bits. As such, it is often used where the term byte might be ambiguous. For that reason, computer networking standards almost exclusively use octet. It is prominently used in Requests for Comments published by the Internet Engineering Task Force. The earliest example is RFC 635 from 1974. In France, (320 bits) of an IPv6 data packet. The header contains the source and destination address, traffic classification options, a hop counter, and a indication of the next header. The Next Header field points to a chain of zero or more extension headers (chained by Next Header fields); the last Next Header 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 along the way or at its destination, routing, fragmenting, and for security using the IPsec framework.

The payload can have a size of up to 64 KB in standard mode, or larger with a "jumbo payload" option in a Hop-By-Hop Options extension header.

Fragmentation is handled only in the sending host in IPv6: routers never fragment a packet, and hosts are expected to use Path MTU discovery.

Addressing

Main article: IPv6 address

The increased length of network addresses emphasizes a most important change when moving from IPv4 to IPv6. IPv6 addresses are 128 bits long,[12] whereas IPv4 addresses are 32 bits; where the IPv4 address space contains roughly 4.3×109 (4.3 billion) addresses, IPv6 has enough room for 3.4×1038 (340 trillion trillion trillion) unique addresses.

IPv6 addresses are normally written with hexadecimal digits and colon separators like 2001:db8:85a3::8a2e:370:7334, as opposed to the dot-decimal notation of the 32 bit IPv4 addresses. IPv6 addresses are typically composed of two logical parts: a 64-bit (sub-)network prefix, and a 64-bit host part.

IPv6 addresses are classified into three types: unicast addresses which uniquely identify network interfaces, anycast addresses which identify a group of interfaces—mostly at different locations—for which traffic flows to the nearest one, and multicast addresses which are used to deliver one packet to many interfaces. Broadcast addresses are not used in IPv6. Each IPv6 address also has a 'scope', which specifies in which part of the network it is valid and unique. Some addresses have node scope or link scope; most addresses have global scope (i.e. they are unique globally).

Some IPv6 addresses are used for special purposes, like the loopback address. Also, some address ranges are considered special, like link-local addresses (for use in the local network only) and solicited-node multicast addresses (used in the Neighbor Discovery Protocol).

IPv6 in the Domain Name System

Main article: IPv6 address#IPv6 addresses in the Domain Name System

A quad-A record (AAAA) is defined in the DNS for returning IPv6 addresses to forward queries; a new format of PTR record is also defined for reverse queries.

Transition mechanisms

IPv6 transition mechanisms
Current
4in6

6in4

6over4

6rd

6to4

ISATAP

Teredo

TSP

TRT

SIIT
Deprecated
NAT-PT • NAPT-PT

Until IPv6 completely supplants IPv4, a number of transition mechanisms[13] 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:

Dual IP stack implementation

A fundamental IPv4-to-IPv6 transition technology involves the presence of two Internet Protocol software implementations in an operating system, one for IPv4 and another for IPv6. Such dual-stack IP hosts may run IPv4 and IPv6 completely independently, or they may use a hybrid implementation, which is the form commonly implemented in modern operating systems on server and end-user computers. Dual-stack hosts are described in RFC 4213.

Modern hybrid dual-stack implementations of TCP/IP 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 IPv6 semantics internally and represent IPv4 addresses in a special IPv6 address format, the IPv4-mapped address.

IPv4-mapped addresses

Hybrid dual-stack IPv6/IPv4 implementations typically support a special class of addresses, the IPv4-mapped 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 is the IPv4-mapped IPv6 address for IPv4 address 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 might not work 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., Linux, NetBSD, 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.

Automatic tunneling

Automatic tunneling refers to a technique where the routing infrastructure automatically determines the tunnel endpoints. RFC 3056 recommends 6to4 tunneling for automatic tunneling, which uses protocol 41 encapsulation.[14] 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.[15] IPv6, including 6to4 and Teredo tunneling, are enabled by default in Windows Vista.[16] Most Unix systems only implement native support for 6to4, but Teredo can be provided by third-party software such as Miredo.

ISATAP[17] 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,[18] 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

Main article: IPv6 transition mechanisms

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 translation mechanisms must be deployed.

One form of translation is the use of a dual-stack application-layer proxy; for example a web proxy.

NAT-like techniques for application-agnostic translation at the lower layers have also been proposed. Most have been found to be too unreliable in practice because of the wide range of functionality required by common application-layer protocols, and are considered by many to be obsolete.

IPv6 readiness

Adoption issues

This section needs additional citations for verification. Please help improve this article by adding reliable references. Unsourced material may be and removed. (June 2010)

Barriers to IPv6 adoption include:

Even though consumers are most likely to suffer when their equipment has to be replaced they tend to look at networking devices like household appliances that only rarely need repairs and never have to be configured or updated. Commercial grade equipment is more likely to support IPv6, so it is the small consumer with his cost-effective disposable networking technology who will be most affected by the eventual change from IPv4 to IPv6.

Smart equipment that contains software needs explicit IPv6 support. Lower-level equipment like cables, network adapters, and switches may not be affected by the change. In general, layer-1 and layer-2 equipment won't require updates.

As of 2010, IPv6 readiness is not considered in most consumer purchasing decisions. We could be only years from a universal upgrade to IPv6 driven internet where devices without IPv6 support will not function.[original research?]

IPv6 compatibility is mainly a software/firmware issue like the year-2000. Unlike the year-2000 issue, there is little interest in ensuring compatibility of older equipment and software by manufacturers.[citation needed] The realization that IPv4 exhaustion is imminent is recent and manufacturers haven't shown much initiative in updating equipment. There is hope that a combined IPv4/IPv6 internet will streamline the transition. The internet community is divided on the issue of whether the transition should be a quick switch or a longer process. It has been suggested[by whom?] that all internet servers be prepared to serve IPv6-only clients by 2012. Universal access to IPv6-only servers will be even more of a challenge.

Most equipment would be fully IPv6 capable with a software or firmware update if the device has sufficient storage and memory space for the new IPv6 stack. However, as with 64-bit Windows, UEFI and Wi-Fi Protected Access support, manufacturers are unlikely to spend on development costs for hardware they have already sold when they are poised to make more sales from "IPv6-ready" equipment.

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.[19][20] It is expected that only 60% of cable modems' servers and 40% of cable modems will be DOCSIS 3.0 by 2011.[21]

Other equipment which is typically not IPv6-ready ranges from Skype and SIP phones to oscilloscopes and printers. Professional network routers in use should be IPv6-ready. Most personal computers should also be IPv6-ready because the network stack resides in the operating system. Most applications with network capabilities are not ready but could be upgraded with support from the developers. Since Java 1.4 (February 2002) all applications that are 100% Java compatible have support for IPv6 addresses.[22]

IPv6 testing and evaluation

This article may contain material not appropriate for an encyclopedia. Please discuss this issue on the talk page. (March 2010)

A few organizations are involved, locally and internationally, with IPv6 testing and evaluation ranging from the United States Department of Defense to the University of New Hampshire. Fuzzing, Fault injection and mutation test equipment and software is available from companies such as Mu Dynamics, Ixia, Candela Technologies:[23] and Codenomicon;[24] which all also provide capability for creating and customizing your own IPv6 tests. Other classes of test equipment, including load and performance and conformance are available from companies like Spirent, Ixia, Candela Technologies and Agilent Technologies.

Deployment

Main article: IPv6 deployment

Although IPv4 address exhaustion has been slowed by the introduction of classless inter-domain routing (CIDR) and the extensive use of network address translation (NAT), address uptake has accelerated again in recent years.[citation needed] Most forecasts expect complete depletion between 2011 and 2012.[7]

As of 2008, IPv6 accounts for a minuscule fraction of the used addresses and the traffic in the publicly-accessible Internet which is still dominated by IPv4.[25]

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 (IP addresses 2001:252:0:1::2008:6 and 2001:252:0:1::2008:8) and all network operations of the Games were conducted using IPv6.[26] It is believed that the Olympics provided the largest showcase of IPv6 technology since the inception of IPv6.[27]

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 due to the impending IPv4 address exhaustion. In the U.S., cellular operator Verizon has released technical specifications for devices operating on its future networks.[28] 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 extensive use of IPv6 to avoid NAT issues.[29]

Major announcements and availability

Year Announcements and availability
1996 Alpha quality IPv6 support in Linux kernel development version 2.1.8.[30]
6bone (an IPv6 virtual network for testing) is started.
1997 By the end of 1997 IBM's AIX 4.3 is the first commercial platform supporting IPv6.[31][32]
Also in 1997, Early Adopter Kits for DEC's operating systems, Tru64 and OpenVMS, are made available.[33]
1998 Microsoft Research[34] releases its first experimental IPv6 stack. This support is not intended for use in a production environment.
1999 The Freenet6 tunnel broker service is launched.
2000 Production-quality BSD support for IPv6 becomes generally available in early to mid-2000 in FreeBSD, OpenBSD, and NetBSD via the KAME project.[35]
Microsoft releases an IPv6 technology preview version for Windows 2000 in March 2000.[34]
Sun Solaris supports IPv6 in Solaris 8 in February.[36]
Compaq ships IPv6 with Tru64.[33]
2001 In January, Compaq ships IPv6 with OpenVMS.[33]
Cisco Systems introduces IPv6 support on Cisco IOS routers and L3 switches.[37]
HP introduces IPv6 with HP-UX 11i v1.[38]
2002 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.[39]
IBM z/OS supports IPv6 since version 1.4 (generally availability in September 2002).[40]
2003 Apple Mac OS X v10.3 "Panther" (2003) supports IPv6 which is enabled by default.[41]
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.
2005 Linux 2.6.12 removes experimental status from its IPv6 implementation.[42]
2007 Microsoft Windows Vista (2007) supports IPv6 which is enabled by default.[39]
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.[43] (Note: 6to4 was disabled by default in later firmware revisions.)
2008 On February 4, 2008, IANA adds AAAA records for the IPv6 addresses of six root name servers.[44][45] With this transition, it is now possible for two Internet hosts to fully communicate without using IPv4.
On March 12, 2008, Google launches a public IPv6 web interface to its popular search engine at the URL http://ipv6.google.com.[46]
2009 In January 2009, Google extends its IPv6 initiative with Google over IPv6, which offers IPv6 support for Google services to compatible networks.
2010 In January 2010, Comcast announces public trials of IPv6 on its production network.[47][48] In April 2010, XS4ALL announced public trials[49] & Verizon announced testing on its FiOS network.[50]
In May/June 2010, Facebook became accessible on IPv6 via http://www.v6.facebook.com/

See also

References

  1. ^ Global IPv6 Statistics - Measuring the current state of IPv6 for ordinary users, S. H. Gunderson (Google), RIPE 57 (Dubai, Oct 2008)
  2. ^ Google: more Macs mean higher IPv6 usage in US
  3. ^ a b c RFC 1752 The Recommendation for the IP Next Generation Protocol, S. Bradner, A. Mankin, January 1995.
  4. ^ History of the IPng Effort
  5. ^ Exec: No shortage of Net addresses By John Lui, CNETAsia
  6. ^ A Pragmatic Report on IPv4 Address Space Consumption by Tony Hain, Cisco Systems
  7. ^ a b IPv4 Address Report
  8. ^ Proposed Global Policy for the Allocation of the Remaining IPv4 Address Space
  9. ^ U.S. Census Bureau
  10. ^ RFC 4862 IPv6 Stateless Address Autoconfiguration, S. Thomson, T. Narten, T. Jinmei, September 2007.
  11. ^ RFC 2894 Router Renumbering for IPv6, M. Crawford, August 2000.
  12. ^ RFC 4291 IP Version 6 Addressing Architecture, R. Hinden, S. Deering, February 2006.
  13. ^ IPv6 Transition Mechanism / Tunneling Comparison
  14. ^ RFC 3056 Connection of IPv6 Domains via IPv4 Clouds, B. Carpenter, Februari 2001.
  15. ^ RFC 4380 Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs), C. Huitema, Februari 2006
  16. ^ The Windows Vista Developer Story: Application Compatibility Cookbook
  17. ^ RFC 5214 Intra-Site Automatic Tunnel Addressing Protocol (ISATAP), F. Templin, T. Gleeson, D. Thaler, March 2008.
  18. ^ RFC 3053 IPv6 Tunnel Broker, A. Durand, P. Fasano, I. Guardini, D. Lento, January 2001.
  19. ^ "DOCSIS 2.0 Interface". Cablemodem.com. 2007-10-29. http://www.cablemodem.com/specifications/specifications20.html. Retrieved 2009-08-31.
  20. ^ RMV6TF.org
  21. ^ ABI Research (2007-08-23). "DOCSIS 3.0 Network Equipment Penetration to Reach 60% by 2011". Press release. http://www.abiresearch.com/abiprdisplay.jsp?pressid=710. Retrieved 2007-09-30.
  22. ^ "Networking IPv6 User Guide for JDK/JRE 5.0". http://java.sun.com/j2se/1.5.0/docs/guide/net/ipv6_guide/index.html. Retrieved 2007-09-30.
  23. ^ Candela Technologies
  24. ^ Codenomicon Defensics: IPv6 test suite datasheet
  25. ^ Geoff Huston - An Update on IPv6 Deployment (RIPE 56)
  26. ^ The Beijing Organizing Committee for the Games of the XXIX Olympiad (2008-05-30). "Beijing2008.cn leaps to next-generation Net". Press release. http://en.beijing2008.cn/news/official/preparation/n214384681.shtml.
  27. ^ Das, Kaushik (2008). "IPv6 and the 2008 Beijing Olympics". IPv6.com. http://ipv6.com/articles/general/IPv6-Olympics-2008.htm. Retrieved 2008-08-15. "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."
  28. ^ Derek Morr (2009-06-09). "Verizon Mandates IPv6 Support for Next-Gen Cell Phones". CircleID. http://www.circleid.com/posts/20090609_verizon_mandates_ipv6_support_for_next_gen_cell_phones/.
  29. ^ Rob Issac (2008), Welcome to your IPv6 enabled transit network. Whether you like it, or not, http://www.ausnog.net/files/ausnog-03/presentations/ausnog03-ward-IPv6_enabled_network.pdf
  30. ^ Linux IPv6 Development Project
  31. ^ IPv6 support shipping in AIX 3.3
  32. ^ Its AIX 4.3.
  33. ^ a b c DEC/Compaq IPv6 history
  34. ^ a b Internet Protocol Version 6 (old Microsoft Research IPv6 release)
  35. ^ KAME project
  36. ^ Sun Solaris 8 changes from Solaris 7
  37. ^ Cisco main IPv6 site
  38. ^ HP main IPv6 site
  39. ^ a b Microsofts main IPv6 site
  40. ^ "IBM: z/OS operating system". 03.ibm.com. http://www-03.ibm.com/servers/eserver/zseries/announce/zos_r4/. Retrieved 2009-08-31.
  41. ^ Mac OS X 10.3 Using IPv6 *** Document not found error message *** 2008-11-14
  42. ^ Linux 2.6.12 changelog
  43. ^ Apple AirPort Extreme technical specifications.
  44. ^ IPv6: coming to a root server near you
  45. ^ IANA - IPv6 Addresses for the Root Servers
  46. ^ Official Google Blog
  47. ^ Comcast6.net
  48. ^ Networkworld.com
  49. ^ XS4all.nl
  50. ^ CNN.com

External links

Internet Protocol Version 6
General IPv6 · IPv6 address · IPv6 packet · Mobile IPv6 · Comparison of IPv6 application support · List of IPv6 tunnel brokers
IPv4 to IPv6 Topics IPv4 address exhaustion · IPv6 transition mechanisms · IPv6 deployment
Related protocols DHCPv6 · ICMPv6 · Site Multihoming by IPv6 Intermediation

Categories: IPv6 | Internet Protocol | Internet Layer protocols | Network layer protocols

 

The above information uses material from Wikipedia and is licensed under the GNU Free Documentation License.
Some facts may not have been fully verified for accuracy. [Disclaimers]
This page was last archived by our server on Tue Jul 27 03:23:32 2010. [ refresh local cache ]
Displaying this page or its contents does not use any Wikimedia Foundation's resources.
The owners of this site proudly support the Wikimedia Foundation.

[Hide]▼
'IPv6' News
NTT America Speaks on Next Generation Services at PTC'10 - SYS-CON Media (press release)
news.google.com
NTT America Speaks on Next Generation Services at PTC'10

SYS-CON Media (press release)

With real-world IPv6 experience, both architecturally and operationally, Mr. Christman joins IPv6 subject matter experts and leaders from around the world ...



and more »
Google News Search: IPv6,
Sat Jan 23 21:12:49 2010
'IPv6' Images
5 3 ipv6 lg2 jpg
calit2.net
5 3 ipv6 lg2 jpg
240px x 119px | 11.20kB

[source page]

Plan to Attend IPv6 Summit in June Calit2 to Co sponsor 5 3 04 Calit is a repeat sponsor for this biannual event which focuses on IPv6 described as preserving everything that s good about today s Internet and adding much more

Yahoo Images Search: IPv6,
Wed Aug 12 04:10:45 2009
'IPv6' Blogs
IPv6 Comparison - Networking
daniweb.com
IPv6 Comparison - Networking

mnewsome

Sun, 06 Jun 2010 13:24:56 GM

IPv6. Comparison Networking.

Google Blogs Search: IPv6,
Sun Jul 4 03:13:03 2010
'IPv6' Answers
How do I check my IPv6 IP?
Q. All the IP telling sites i know tell the IPv4 IP. Where can I get the IPv6 one?
Asked by Seedrick - Wed Jul 25 13:23:38 2007 - - 1 Answers - 0 Comments

A.
Answered by jiqqaman - Wed Jul 25 13:33:07 2007

Yahoo Answers Search: IPv6,
Sun Sep 27 15:31:02 2009
[Hide]▲