IPv6

From Wikipedia, the free encyclopedia

Jump to: navigation, search
The five-layer TCP/IP model
5. Application layer

DHCP · DNS · FTP · Gopher · HTTP · IMAP4 · IRC · NNTP · XMPP · POP3 · SIP · SMTP · SNMP · SSH · TELNET · RPC · RTP · RTCP · RTSP · TLS/SSL · SDP · SOAP · BGP · GTP · STUN · NTP · RIP· ...
4. Transport layer

TCP · UDP · DCCP · SCTP · RSVP · IGMP · OSPF· ...
3. Network/Internet Layer

IP (IPv4 · IPv6) · IS-IS · IPsec · ICMP · ARP · RARP · ...
2. Data link layer

802.11 · Wi-Fi · WiMAX · ATM · DTM · Token Ring · Ethernet · FDDI · Frame Relay · GPRS · EVDO · HSPA · HDLC · PPP · PPTP · L2TP · ...
1. Physical layer

Ethernet physical layer · ISDN · Modems · PLC · SONET/SDH · G.709 · OFDM ·Optical Fiber · Coaxial Cable · Twisted Pair · ...
This box: view • talk • edit

Internet Protocol version 6 (IPv6) is a network layer protocol for packet-switched internetworks. It is designated as the successor of IPv4, the current version of the Internet Protocol, for general use on the Internet.

The main improvement brought by IPv6 is a much larger address space that allows greater flexibility in assigning addresses. IPv6 is able to support 2128 (about 3.4×1038) addresses, or approximately 5×1028 addresses for each of the roughly 6.5 billion people[1] alive today. It was not the intention of IPv6 designers, however, to give permanent unique addresses to every individual and every computer. Rather, the extended address length eliminates the need to use network address translation to avoid address exhaustion, and also simplifies aspects of address assignment and renumbering when changing providers.

Contents

[edit] Introduction

By the early 1990s, it was clear that the change to a classless network introduced a decade earlier was not enough to prevent IPv4 address exhaustion and that further changes to IPv4 were needed.[2] 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 1650) and the creation of the "IP, the Next Generation" (IPng Area) of working groups.[2][3]

IPng was adopted by the Internet Engineering Task Force on July 25, 1994 with the formation of several "IP Next Generation" (IPng) working groups.[2] By 1996, a series of RFCs were released defining IPv6, starting with RFC 2460. (Incidentally, IPv5 was not a successor to IPv4, but an experimental flow-oriented streaming protocol intended to support video and audio.)

It is expected that IPv4 will be supported alongside IPv6 for the foreseeable future. IPv4-only nodes (clients or servers) will not be able to communicate directly with IPv6 nodes, and will need to go through an intermediary; see Transition mechanisms below.

[edit] 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).

Applications, however, usually need small changes and a recompile in order to run over IPv6.

[edit] Larger address space

The main feature of IPv6 that is driving adoption today 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 network address translation (NAT) and other devices that break the end-to-end nature of Internet traffic. NAT may still be necessary in rare cases, but Internet engineers recognize that it will be difficult in IPv6 and are trying to avoid it whenever possible. It also makes administration of medium and large networks simpler, by avoiding the need for complex subnetting schemes. Subnetting will, ideally, revert to its purpose of logical segmentation of an IP network for optimal routing and access.

The drawback of the large address size is that IPv6 carries some bandwidth overhead over IPv4, which may hurt regions where bandwidth is limited (header compression can sometimes be used to alleviate this problem). IPv6 addresses are harder to memorize than IPv4 addresses, although even IPv4 addresses are much harder to memorize than Domain Name System (DNS) names. DNS protocols have been modified to support IPv6 as well as IPv4.

[edit] 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 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.[4]

[edit] Multicast

Most environments do not currently have their network infrastructures configured to route multicast; that is — the link-scoped aspect of multicast (i.e., on a single subnet) 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).

The m6bone is catering for deployment of a global IPv6 Multicast network.

[edit] Jumbograms

In IPv4, packets are limited to 64 KiB of payload. When used between capable communication partners and on communication links with a maximum transmission unit (MTU) larger than 65,576 octets, IPv6 has optional support for packets over this limit, referred to as jumbograms which can be as large as 4 GiB. The use of jumbograms may improve performance over high-MTU networks.

[edit] Network-layer security

IPsec, the protocol for IP network-layer encryption and authentication, is an integral part of the base protocol suite in IPv6; this is unlike IPv4, where it is optional (but usually implemented). IPsec, however, is not widely deployed except for securing traffic between IPv6 Border Gateway Protocol routers.

[edit] Mobility

Unlike mobile IPv4, Mobile IPv6 (MIPv6) avoids triangular routing and is therefore as efficient as normal IPv6. This advantage is mostly hypothetical, as neither MIP nor MIPv6 are widely deployed today.

[edit] Deployment status

In February 1999, The IPv6 Forum [5] was founded by the IETF Deployment WG to drive deployment worldwide creating by now over 45 IPv6 Country Forums 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,[6] this tool provides a list of all allocated IPv6 prefixes and marks with colors the ones that are actually being announced into the Internet BGP tables. When a prefix is announced, it 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.

The mandate by the United States Government to move to an IPv6 platform for all civilian and defense vendors by summer 2008 will greatly boost deployment. The awarding of over $150 billion in contracts in spring of 2007 by the General Services Administration will in itself come close to the total amount spent on the Y2K upgrade of the previous decade, and total cost will swell far beyond that.

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.

With the notable exceptions of stateless auto-configuration, more flexible addressing and Secure Neighbor Discovery (SEND), many of the features of IPv6 have been ported to IPv4 in a more or less elegant manner. Thus IPv6 deployment is primarily driven by IPv4 address space exhaustion, which has been slowed by the introduction of classless inter-domain routing (CIDR) and the extensive use of network address translation (NAT).

Estimates as to when the pool of available IPv4 addresses will be exhausted vary widely, and should be taken with a lot of caution. In 2003, Paul Wilson (director of APNIC) stated that, based on then-current rates of deployment, the available space would last until 2023.[7] In September 2005 a report by Cisco Systems reported that the pool of available addresses would be exhausted in as little as 4 to 5 years.[8] As of November 2006, a regularly updated report projected that the IANA pool of unallocated addresses would be exhausted in May 2011, with the various Regional Internet Registries using up their allocations from IANA in August 2012.[9] This report also argues that, if assigned but unused addresses were reclaimed and used to meet continuing demand, allocation of IPv4 addresses could continue until 2024.

A number of governments, however, are starting to require support for IPv6 in new equipment. The U.S. Government, for example, has specified that the network backbones of all federal agencies must deploy IPv6 by 2008,[10] and spent the money to acquire a /16 block 281 trillion network addresses to start the deployment.[11][12][13]

. The Peoples Republic of China has a 5 year plan for deployment of IPv6 called the China Next Generation Internet.

[edit] Addressing

[edit] 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; where the IPv4 address space contains roughly 4 billion addresses, IPv6 has enough room for 3.4×1038 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 time-varying random bit strings can be used as interface circuit identifiers, replacing unchanging and traceable MAC addresses.

[edit] 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 one or more four-digit group(s) is 0000, the zeros may be omitted and replaced with two colons(::). For example, 2001:0db8:0000:0000:0000:0000:1428:57ab can be shortened to 2001:0db8::1428:57ab. Following this rule, any number 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 (as in ::1 for localhost). 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). This addressing scheme is convenient when dealing with the mixed environment of IPv4 and IPv6 addresses. The general notation is of the form x:x:x:x:x:x:d.d.d.d where x's are the 6 higher order hexadecimal digits whereas d's correspond to the decimal digits of lower order 8 bit pieces of address, as it is the IPv4 format. For example, ::ffff:12.34.56.78 is the same address as ::ffff:0c22:384e and 0:0:0:0:0:ffff:0c22:384e. Usage of this notation is deprecated and unsupported by numerous applications.

Additional information can be found in RFC 4291 - IP Version 6 Addressing Architecture.

[edit] Literal IPv6 addresses in URLs

In a URL the IPv6-Address is enclosed in brackets. Example:

http://[2001:0db8:85a3:08d3:1319:8a2e:0370:7344]/

This notation allows parsing a URL without confusing the IPv6 address and port number:

https://[2001:0db8:85a3:08d3:1319:8a2e:0370:7344]:443/

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"

[edit] 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.

[edit] Kinds of IPv6 addresses

IPv6 addresses are divided into 3 categories:[14]

  • Unicast Addresses
  • Multicast Addresses
  • Anycast Addresses

A Unicast address identifies a single network interface. A packet sent to a unicast address is delivered to that specific computer. The following types of addresses are unicast IPv6 addresses:

Multicast addresses are used to define a set of interfaces that typically belong to different nodes instead of just one. When a packet is sent to a multicast address, the protocol delivers the packet to all interfaces identified by that address. Multicast addresses begin with the prefix FF00::/8, and their second octet identifies the addresses' scope, i.e. the range over which the multicast address is propagated. Commonly used scopes include link-local (2), site-local (5) and global (E).

Anycast addresses are also assigned to more than one interface, belonging to different nodes. However, a packet sent to an anycast address is delivered to just one of the member interfaces, typically the “nearest” according to the routing protocol’s idea of distance. Anycast addresses cannot be identified easily: they have the structure of normal unicast addresses, and differ only by being injected into the routing protocol at multiple points in the network.

[edit] Special addresses

There are a number of addresses with special meaning in IPv6:

  • ::/128 — the address with all zeros is an unspecified address, and is to be used only 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; it is now obsolete.
  • ::ffff:0:0/96 — this prefix is used for IPv4 mapped addresses (see Transition mechanisms below).
  • 2001:db8::/32 — this prefix is used in documentation (RFC 3849). Anywhere where an example IPv6 address is given, addresses from this prefix should be used.
  • 2002::/16 — this prefix is used for 6to4 addressing.
  • fc00::/7 — unique local addresses (ULA) are routable only 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.
  • fe80::/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.0.0/16 in IPv4.
  • fec0::/10 — The site-local prefix specifies that the address is valid only inside the local organisation. Its use has been deprecated in September 2004 by RFC 3879 and systems must not support this special type of address.
  • ff00::/8 — The multicast prefix is used for multicast addresses[15] as defined by in "IP Version 6 Addressing Architecture" (RFC 4291).

There are no address ranges reserved for broadcast in IPv6 — applications use multicast to the all-hosts group instead. IANA maintains the official list of the IPv6 address space. Global unicast assignments can be found at the various RIR's or at the GRH DFP pages.

[edit] Zone indices

Link-local addresses present a particular problem for systems with multiple interfaces. Because each interface may be connected to different networks and the addresses all appear to be on the same subnet, an ambiguity arises that cannot be solved by routing tables.

For example, host A has two interfaces which automatically receive link-local addresses when activated (per RFC 2462): fe80::1/64 and fe80::2/64, only one of which is connected to the same physical network as host B which has address fe80::3/64, if host A attempts to contact fe80::3 how does it know which interface (fe80::1 or fe80::2) to use?

The solution defined by RFC 4007 is the addition of a unique zone index for the local interface, represented textually in the form <address>%<zone_id>, for example: http://[fe80::1122:33ff:fe11:2233%eth0]:80/ - this however may cause its own problems due to clashing with the percent-encoding used with URIs. [1]

  • Microsoft Windows IPv6 stack uses numeric zone IDs: fe80::3%1
  • BSD applications typically use the interface name as a zone ID: fe80::3%pcn0
  • Linux applications also typically use the interface name as a zone ID: fe80::3%eth0, although Linux ifconfig as of version 1.42 (part of net-tools 1.60) does not display zone IDs.

Relatively few IPv6-capable applications understand zone ID syntax (with the notable exception of OpenSSH), thus rendering link-local addresses unusable within them if multiple interfaces use link-local addresses.

[edit] IPv6 packet

The structure of an IPv6 packet header.
The structure of an IPv6 packet header.

The IPv6 packet is composed of two main parts: the header and the payload.

The header is in the first 40 octets (320 bits) of the packet and contains both source and destination addresses (128 bits each), as well as the version (4-bit IP version), traffic class (8 bits, Packet Priority), flow label (20 bits, QoS management), payload length in bytes (16 bits), next header (8 bits), and hop limit (8 bits, time to live). The payload can be up to 64KiB in size in standard mode, or larger with a "jumbo payload" option.

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

The protocol field of IPv4 is replaced with a Next Header field. This field usually specifies the transport layer protocol used by a packet's payload.

In the presence of options, however, the Next Header field specifies the presence of an extra options header, which then follows the IPv6 header; the payload's protocol itself is specified in a field of the options header. This insertion of an extra header to carry options is analogous to the handling of AH and ESP in IPsec for both IPv4 and IPv6.

[edit] 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).

AAAA record fields
NAME Domain name
TYPE AAAA (28)
CLASS Internet (1)
TTL Time to live in seconds
RDLENGTH Length of RDATA field
RDATA String form of the IPV6 address as described in RFC 3513

RFC 3484 specifies how applications should select an IPv6 or IPv4 address for use, including addresses retrieved from DNS.

[edit] IPv6 and DNS RFCs

  • DNS Extensions to support IP version 6 - RFC 1886
  • DNS Extensions to Support IPv6 Address Aggregation and Renumbering - RFC 2874
  • Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6) - RFC 3364
  • Default Address Selection for Internet Protocol version 6 (IPv6) - RFC 3484
  • Internet Protocol Version 6 (IPv6) Addressing Architecture - RFC 3513
  • DNS Extensions to Support IP Version 6 (Obsoletes 1886 and 3152) - RFC 3596

[edit] IPv6 scope

IPv6 defines 3 unicast address scopes: global, site, and link.

Site-local addresses are non-link-local addresses that 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 addresses 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).

[edit] 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. [16] contains an overview of the below mentioned transition mechanisms.

[edit] 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.

[edit] 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 tunneling which consists of 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 protocol number 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.

[edit] 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.[17] 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.

Another automatic tunneling mechanism is ISATAP.[18] This protocol treats the IPv4 network as a virtual IPv6 local link, with mappings from each IPv4 address to a link-local IPv6 address.

Teredo is an automatic tunneling technique that uses UDP encapsulation and is claimed to be able to cross multiple NAT boxes.[19] Teredo is not widely deployed today, but an experimental version of Teredo is installed with the Windows XP SP2 IPv6 stack. IPv6, 6to4 and Teredo are enabled by default in Windows Vista.[20]

[edit] 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.[21] Configured tunneling is usually more deterministic and easier to debug than automatic tunneling, and is therefore recommended for large, well-administered networks, like the Internet.

Configured tunneling uses protocol 41 in the Protocol field of the IPv4 packet. This method is also better known as 6in4.

[edit] Proxying and translation

Main article: IPv6 translation mechanisms

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.

[edit] Major IPv6 announcements and availability

1996 Linux gains alpha quality IPv6 support in kernel development version 2.1.8, released in 1996. Only as of Linux Kernel version 2.6.10 (released in 2004), the Linux IPv6 stack was actually approved by the IPv6 Forum[22] in the IPv6 Ready Logo Phase-1 Program[23]. Development still continues on improving the stack.[24]
1997 In the end of 1997 IBM's AIX 4.3 was the first commercial platform that supported IPv6.[25][26]
1998 Microsoft Research[27] first released an experimental IPv6 stack in 1998. This support is not intended for use in a production environment.
2000 Production-quality BSD support for IPv6 has been generally available since early to mid-2000 in FreeBSD, OpenBSD, and NetBSD via the KAME project[28].
Sun Solaris has IPv6 support since the Solaris 8 in February 2000[29]
2002 Microsoft Windows NT 4.0 and Windows 2000 SP1 had limited IPv6 support for research and testing since at least 2002.
Microsoft Windows XP (2001) had IPv6 support for developmental purposes. In Windows XP SP1 (2002) and Windows Server 2003, IPv6 is included as a core networking technology, suitable for commercial deployment.[30]
IBM z/OS has supported IPv6 since version 1.4 that has been generally available since September 2002.[31]
2003 Apple Mac OS X v10.3 "Panther" (2003) has IPv6 supported and enabled by default.[32]
2004 ICANN announced on 20 July 2004 that the IPv6 AAAA records for the Japan (.jp) and Korea (.kr) country code Top Level Domain (ccTLD) nameservers became visible in the DNS root server zone files with serial number 2004072000. The IPv6 records for France (.fr) were added a little later. This made IPv6 operational in a public fashion.
2007 Microsoft Windows Vista (2007) has IPv6 supported and enabled by default.[30]
Apple's AirPort Extreme 802.11n base station is an IPv6 gateway in its default configuration. It uses 6to4 tunneling and can optionally route through a manually configured IPv4 tunnel.[33]

[edit] See also

[edit] Notes and references

  1. ^ U.S. Census Bureau
  2. ^ a b c RFC 1750
  3. ^ History of the IPng Effort
  4. ^ Router Renumbering for IPv6,RFC2894,M. Crawford,August 2000
  5. ^ The IPv6 Forum
  6. ^ SixXS Ghost Route Hunter
  7. ^ Exec: No shortage of Net addresses By John Lui, CNETAsia
  8. ^ A Pragmatic Report on IPv4 Address Space Consumption by Tony Hain, Cisco Systems
  9. ^ IPv4 Address Report
  10. ^ August 2005 directive from the Office of Management Budget
  11. ^ DOD to allocate its IPv6 addresses
  12. ^ Bitten by IPv6 (correction to the first report)
  13. ^ [http://www.stsc.hill.af.mil/CrossTalk/2007/07/0707KimMacha.pdf Providing the Tools for Information Sharing: Net-Centric Enterprise Services (Department of Defense Chief Information Officer Information Policy Directorate)]
  14. ^ RFC 2373 - IP Version 6 Addressing Architecture
  15. ^ IP Version 6 multicast address
  16. ^ IPv6 Transition Mechanism / Tunneling Comparison
  17. ^ RFC 3056
  18. ^ RFC 4214
  19. ^ RFC 4380
  20. ^ The Windows Vista Developer Story: Application Compatibility Cookbook
  21. ^ RFC 3053
  22. ^ The IPv6 Forum
  23. ^ IPv6 Ready Logo Program, IPv6 Standard Compliance Certification
  24. ^ Linux IPv6 Development Project
  25. ^ IPv6 support shipping in AIX 3.3
  26. ^ Its AIX 4.3.
  27. ^ Internet Protocol Version 6 (old Microsoft Research IPv6 release)
  28. ^ KAME project
  29. ^ Sun Solaris 8 changes from Solaris 7
  30. ^ a b Microsofts main IPv6 site
  31. ^ http://www-03.ibm.com/servers/eserver/zseries/announce/zos_r4/
  32. ^ Mac OS X 10.3 Using IPv6
  33. ^ Apple AirPort Extreme technical specifications.

[edit] Further reading

[edit] Core specifications

  • RFC 2460: Internet Protocol, Version 6 (IPv6) Specification (obsoletes RFC 1883)
  • RFC 2461/RFC 4311: Neighbor Discovery for IP Version 6 (IPv6) (4311 updates)
  • RFC 2462: IPv6 Stateless Address Autoconfiguration
  • RFC 4443: Internet Control Message Protocol (ICMPv6) for the IPv6 Specification (obsoletes RFC 2463)
  • RFC 2464: Transmission of IPv6 Packets over Ethernet Networks
  • RFC 4291: Internet Protocol Version 6 (IPv6) Addressing Architecture (obsoletes RFC 3513)
  • RFC 3041: MAC address use replacement option
  • RFC 3587: An IPv6 Aggregatable Global Unicast Address Format

[edit] Stateless autoconfiguration

  • RFC 2461: Neighbor Discovery for IP Version 6 (IPv6)
  • RFC 2462: IPv6 Stateless Address Autoconfiguration

[edit] Programming

  • RFC 3493: Basic Socket Interface Extensions for IPv6 (obsoletes RFC 2553)
  • RFC 3542: Advanced Sockets Application Program Interface (API) for IPv6 (obsoletes RFC 2292)
  • RFC 4038: Application Aspects of IPv6 Transition
  • RFC 3484: Default Address Selection for Internet Protocol version 6 (IPv6)

[edit] Books

There are a number of IPv6 books:

[edit] External links

[edit] Related IETF working groups

  • ipv6 IP Version 6
  • multi6 Site Multihoming in IPv6
  • shim6 Site Multihoming by IPv6 Intermediation
  • v6ops IPv6 Operations
  • 6bone IPv6 Backbone (concluded)
  • ipng IP Next Generation (concluded)
  • ipv6mib IPv6 MIB (concluded)

Retrieved from "http://en.wikipedia.org/wiki/IPv6"
Personal tools