|
Internet Protocol version 6 (IPv6) is a network layer IP standard used by electronic devices to exchange data across a packet-switched internetwork. It follows IPv4 as the second version of the Internet Protocol to be formally adopted for general use. The main improvement brought by IPv6 is the increase in the number of addresses available for networked devices, allowing, for example, each cell phone and mobile electronic device to have its own address. IPv4 supports 232 (about 4.3 billion) addresses, which is inadequate for giving even one address to every living person, much less for supporting the burgeoning market for connective devices. IPv6, however, supports 2128 addresses; this is approximately 5×1028 addresses for each of the roughly 6.5 billion people alive today, or the possibility of assigning an address to each atom in the average person's body. (Note: statements that IPv6 provides enough address space to give an address for each atom in the universe or even for each atom on Earth are highly exaggerated). Invented by Steve Deering and Craig Mudge at Xerox PARC, IPv6 was adopted by the Internet Engineering Task Force in 1994, when it was called "IP Next Generation" (IPng). (Incidentally, IPv5 was not a successor to IPv4, but an experimental flow-oriented streaming protocol intended to support video and audio.) As of December 2005, IPv6 accounts for a tiny percentage of the live addresses in the publicly-accessible Internet, which is still dominated by IPv4. The adoption of IPv6 has been slowed by the introduction of classless inter-domain routing (CIDR) and network address translation (NAT), each of which has partially alleviated the impact of address space exhaustion. Nevertheless, as of August 2006, the primary IANA pool is expected to run out in the 2009 to 2011 timeframe if current trends continue. The U.S. Government has specified that the network backbones of all federal agencies must deploy IPv6 by 2008.* Meanwhile China is planning to get a head start implementing IPv6 with their 5 year plan for the China Next Generation Internet. It is expected that IPv4 will be supported alongside IPv6 for the foreseeable future. However, ipv4-only clients/servers will not be able to communicate directly with IPv6 clients/servers, and will require service-specific intermediate servers or NAT-PT protocol-translation servers. Features of IPv6 To a great extent, IPv6 is a conservative extension of IPv4. Most transport- and application-layer protocols need little or no change to work over IPv6; exceptions are applications protocols that embed network-layer addresses (such as FTP or NTPv3; NTPv4 supports IPv6). Larger address space The main feature of IPv6 is the larger address space: addresses in IPv6 are 128 bits long versus 32 bits in IPv4. The larger address space avoids the potential exhaustion of the IPv4 address space without the need for NAT and other devices that break the end-to-end nature of Internet traffic. 128 bits might seem overkill to achieve that goal. However, since IPv6 addresses are plentiful, it is reasonable to allocate addresses in large blocks, which makes administration easier and avoids fragmentation of the address space, which in turn leads to smaller routing tables. The current allocation policies allocate 64 bits of address space to each network segment (VLAN), and the "standard enterprise allocation" will be a /48 (leaving 16bits-worth of subnets; that is - each "average enterprise" will have ~64k VLANs to allocate as they see fit). A technical reason for selecting 128-bit for the address length is that since most future network products will be based on 64 bit processors, it is more efficient to manipulate 128-bit addresses. The drawback of the large address size is that IPv6 is less efficient in bandwidth usage, and this may hurt regions where bandwidth is limited. Another advantage of the larger address space is that it makes scanning certain IP blocks for vulnerabilities significantly more difficult than in IPv4, which makes IPv6 more resistant to malicious traffic. This apparent advantage is somewhat blunted by distributed attack techniques and access to the very techniques that will enable users and devices to connect in IPv6 -- with such things as all hosts multicasts and Directory Service tables which will list which IPv6 addresses in the range actually have machines attached. Similarly when new spoofing techniques are invented it will be much harder to track down those rogue malware machines especially if they are unlisted. Stateless autoconfiguration of hosts IPv6 hosts can be configured automatically when connected to a routed IPv6 network. When first connected to a network, a host sends a link-local multicast (broadcast) 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 autoconfiguration is not suitable, a host can use stateful autoconfiguration (DHCPv6) or be configured manually. Stateless autoconfiguration is only suitable for hosts; routers must be configured manually or by other means. Multicast Multicast is part of the base protocol suite in IPv6. This is in opposition to IPv4, where multicast is optional. Most environments do not currently have their network infrastructures configured to route multicast; that is - the link-scoped aspect of multicast will work but the site-scope, organization-scope and global-scope multicast will not be routed. IPv6 does not have a link-local broadcast facility; the same effect can be achieved by multicasting to the all-hosts group (FF02: 1). Jumbograms In IPv4, packets are limited to 64 KiB of payload. When used between capable communication partners, IPv6 has support for packets over this limit, referred to as jumbograms. The use of jumbograms improves performance over high-throughput networks. Faster routing By using a simpler and more systematic header structure, IPv6 was supposed to improve the performance of routing. Recent advances in router technology, however, may have made this improvement obsolete. Network-layer security IPsec, the protocol for IP network-layer encryption and authentication, is an integral part of the base protocol suite in IPv6. It is, however, not yet deployed widely except for securing BGP traffic between IPv6 routers. 128-bit length The primary change from IPv4 to IPv6 is the length of network addresses. IPv6 addresses are 128 bits long (as defined by RFC 4291), whereas IPv4 addresses are 32 bits; while the IPv4 address space contains 4,294,967,296 addresses, IPv6 has enough room for 340,282,366,920,938,463,463,374,607,431,768,211,456 unique addresses. IPv6 addresses are typically composed of two logical parts: a 64-bit (sub-)network prefix, and a 64-bit host part, which is either automatically generated from the interface's MAC address or assigned sequentially. Because the globally unique MAC addresses offer an opportunity to track user equipment, and so users, across time and IPv6 address changes, RFC 3041 was developed to reduce the prospect of user identity being permanently tied to an IPv6 address, thus restoring some of the possibilities of anonymity existing at IPv4. RFC 3041 specifies a mechanism by which variable over time random bit strings can be used as interface circuit identifiers, replacing unchanging and traceable MAC addresses. Notation IPv6 addresses are normally written as eight groups of four hexadecimal digits. For example, 2001:0db8:85a3:08d3:1319:8a2e:0370:7334 is a valid IPv6 address. If a four-digit group is 0000, the zeros may be omitted. For example, 2001:0db8:85a3:0000:1319:8a2e:0370:1337 can be shortened as 2001:0db8:85a3: 1319:8a2e:0370:1337. Following this rule, any group of consecutive 0000 groups may be reduced to two colons, as long as there is only one double colon used in an address. Leading zeros in a group can also be omitted. Thus, the addresses below are all valid and equivalent: 2001:0db8:0000:0000:0000:0000:1428:57ab 2001:0db8:0000:0000:0000: 1428:57ab 2001:0db8:0:0:0:0:1428:57ab 2001:0db8:0:0: 1428:57ab 2001:0db8: 1428:57ab 2001:db8: 1428:57ab Having more than one double-colon abbreviation in an address is invalid as it would make the notation ambiguous. A sequence of 4 bytes at the end of an IPv6 address can also be written in decimal, using dots as separators. This notation is often used with compatibility addresses (see below). Thus, ffff:1.2.3.4 is the same address asffff:102:304. Additional information can be found in RFC 4291 - IP Version 6 Addressing Architecture. Literal IPv6 Addresses in URLs In a URL the IPv6-Address is enclosed in squared brackets. Example: This notation allows parsing a URL without confusing the IPv6 address and port number: Additional information can be found in "RFC 2732 - Format for Literal IPv6 Addresses in URL's" and "RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax" Network notation IPv6 networks are written using CIDR notation. An IPv6 network (or subnet) is a contiguous group of IPv6 addresses the size of which must be a power of two; the initial bits of addresses which are identical for all hosts in the network are called the network's prefix. A network is denoted by the first address in the network and the size in bits of the prefix (in decimal), separated with a slash. For example, 2001:0db8:1234: /48 stands for the network with addresses 2001:0db8:1234:0000:0000:0000:0000:0000 through 2001:0db8:1234:FFFF:FFFF:FFFF:FFFF:FFFF Because a single host can be seen as a network with a 128-bit prefix, you will sometimes see host addresses written followed with /128. Special addresses There are a number of addresses with special meaning in IPv6: /128 – the address with all zeroes is an unspecified address, and is only to be used in software. 1/128 – the loopback address is a localhost address. If an application in a host sends packets to this address, the IPv6 stack will loop these packets back to the same host (corresponding to 127.0.0.1 in IPv4). /96 – the zero prefix was used for IPv4-compatible addresses (see Transition mechanisms below) ffff:0:0/96 – this prefix is used for IPv4 mapped addresses (see Transition mechanisms below) /32 – this prefix is used in documentation (RFC3849), anywhere where an example IPv6 address is given, addresses from this prefix should be used. /7 – Unique Local IPv6 Unicast Addresses are only routable within a set of cooperating sites. They were defined in RFC 4193 as a replacement for site-local addresses (see below). The addresses include a 40-bit pseudorandom number that minimizes the risk of conflicts if sites merge or packets somehow leak out. /10 – The link-local prefix specifies that the address only is valid in the local physical link. This is analogous to the Autoconfiguration IP address 169.254.x.x in IPv4. /10 – The site-local prefix specifies that the address is only valid inside the local organisation. Its use has been deprecated in September 2004 by RFC 3879 and future systems must not implement any support for this special type of address anymore. /8 – The multicast prefix is used for multicast addresses. There are no address ranges reserved for broadcast in IPv6 — applications are supposed to use multicast to the all-hosts group instead. IPv6 packet
IPv6 and the Domain Name System IPv6 addresses are represented in the Domain Name System by AAAA records (so-called quad-A records) for forward lookups; reverse lookups take place under ip6.arpa (previously ip6.int), where address space is delegated on nibble boundaries. This scheme, which is a straightforward adaptation of the familiar A record and in-addr.arpa schemes, is defined in RFC 3596. The AAAA scheme was one of two proposals at the time the IPv6 architecture was being designed. The other proposal, designed to facilitate network renumbering, would have had A6 records for the forward lookup and a number of other innovations such as bit-string labels and DNAME records. It is defined in the experimental RFC 2874 and its references (with further discussion of the pros and cons of both schemes in RFC 3364). IPv6 scope IPv6 defines 3 unicast address scopes: global, site and link. Site-local addresses are non-link-local address which are valid within the scope of an administratively-defined site and cannot be exported beyond it. Site-local addresses are deprecated by RFC 3879; note that this does not deprecate other site-scoped address types (e.g. - site-scoped multicast) Companion IPv6 specifications further define that only link-local address can be used when generating ICMP Redirect Messages ND and as next hop addresses in most routing protocols. These restrictions do imply that an IPv6 router must have a link-local next hop address for all directly connected routes (routes for which the given router and the next hop router share a common subnet prefix). IPv6 deployment In February 1999, The IPv6 Forum was founded by the IETF Deployment WG to drive deployment worldwide creating by now over 30 IPv6 Country Fora and IPv6 Task Forces IPv6 FORUM. On 20 July 2004 ICANN announced* that the root DNS servers for the Internet had been modified to support both IPv6 and IPv4. A global view into the IPv6 routing tables which displays also which ISPs are already deploying IPv6 can be found by looking at the SixXS Ghost Route Hunter pages, these pages display a list of all allocated IPv6 prefixes and giving colors to the ones that are actually being announced in BGP. When a prefix is announced that means that the ISP at least can receive IPv6 packets for their prefix. They might then actually also offer IPv6 services, maybe even to end users/sites directly. ISP's that provide IPv6 connectivity to their customers can be found in the Where can I get native IPv6 FAQ. Transition mechanisms Until IPv6 completely supplants IPv4, which is not likely to happen in the foreseeable future, a number of so-called 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. IPv6 Transition Mechanism / Tunneling Comparison contains an overview of the below mentioned transition mechanisms. Dual stack Since IPv6 is a conservative extension of IPv4, it is relatively easy to write a network stack that supports both IPv4 and IPv6 while sharing most of the code. Such an implementation is called a dual stack, and a host implementing a dual stack is called a dual-stack host. This approach is described in RFC 4213. Most current implementations of IPv6 use a dual stack. Some early experimental implementations used independent IPv4 and IPv6 stacks. There are no known implementations that implement IPv6 only. Tunneling In order to reach the IPv6 Internet, an isolated host or network must be able to use the existing IPv4 infrastructure to carry IPv6 packets. This is done using a technique somewhat misleadingly known as tunnelling which consists in encapsulating IPv6 packets within IPv4, in effect using IPv4 as a link layer for IPv6. IPv6 packets can be directly encapsulated within IPv4 packets using a protocol number of 41. They can also be encapsulated within UDP packets e.g. in order to cross a router or NAT device that blocks protocol 41 traffic. They can of course also use generic encapsulation schemes, such as AYIYA or GRE. Automatic tunneling Automatic tunneling refers to a technique where the tunnel endpoints are automatically determined by the routing infrastructure. The recommended technique for automatic tunneling is 6to4* 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 is claimed to be able to cross multiple NAT boxes. Teredo is not widely deployed today, but an experimental version of Teredo is installed with the Windows XP SP2 IPv6 stack and Teredo will reportedly be enabled by default in Windows Vista *. Configured tunneling Configured tunneling is a technique where the tunnel endpoints are configured explicitly, either by a human operator or by an automatic service known as a Tunnel Broker*. Configured tunneling is usually more deterministic and easier to debug than automatic tunneling, and is therefore recommended for large, well-administered networks. Configured tunneling typically uses either protocol 41 (recommended) or raw UDP encapsulation. Proxying and translation When an IPv6-only host needs to access an IPv4-only service (for example a web server), some form of translation is necessary. The one form of translation that actually works is the use of a dual-stack application-layer proxy, for example a web proxy. Techniques for application-agnostic translation at the lower layers have also been proposed, but they have been found to be too unreliable in practice due to the wide range of functionality required by common application-layer protocols, and are commonly considered to be obsolete. See for example SIIT*, NAT-PT*, TCP-UDP Relay*, Socks-based Gateway*, Bump-in-the-Stack or Bump-in-the-API*. See also Major IPv6 announcements and availability Related IETF working groups Core specifications Stateless autoconfiguration Programming Books There are a number of IPv6 books: Address Space Software (Operating Systems + Applications) Task Forces / Projects / Vendors Misc | |||||||||
|
| ||||||||||
 |
|
| |