Tech Info - Ipv6

Version 6 of the IP Protocol. Defined in RFC 2460. Everything about IPv6 is BIG. An IPv4 address is 32 bits, an IPv6 address is 128 bits. This means that there are enough addresses for every person on the planet to have a couple of hundred million or so each!

IPv6 has been around since at least 1995 but the CIDR initiative of the mid-nineties pushed back any pressing need for IPv6's increased address range.

IPv6 is big and complex in comparison with IPv4. This fact alone will keep users from implementation if they have any choice in the matter. Nevertheless we think the time is getting close where there will be little choice. Here are some reasons:

The 3GPP (3rd Generation Partnership Project) decision to use IPv6 for increasingly functional mobile equipment.
5 of the 13 DNS root-servers are advertising both IPv4 and IPv6 access (as of 2004). According to a RIPE-49 presentation 8 of the 13 are actually IPv6 enabled.
Increasing demand for end user address transparency e.g. VoIP.

The IPv4 vs IPv6 debate is also about the bigger issue of end user transparency vs NAT. Between those that see NAT as being inherently evil - since it hides end user addresses thus removing address transparency - and those that see NAT as being a life saving technology that may indefinitely postpone the use of IPv6.

IPv6 may also finally remove the need for end users to know anything about their IP address - quite simply because it will be impossible for any sane human being to remember one of these gruesome strings of digits. Imagine asking your Mother to read her IPv6 address over the phone. Got the picture. DNS and DHCPv6 can be made to make the IP address disappear at the user level. For IPv6 to work we must treat any need for a visible IP address as a system failure.

You need to be fairly comfortable with Hex stuff to handle IPv6 [quick overview of Hexadecimal, Binary and Decimal]

IPv6 Overview
IPv6 Address Notation
IPv6 Prefix or Slash Notation
IPv6 Address Types
IPv6 Global Unicast Address Format
IPv6 End-User Address Format
IPv6 Link-Local Address Format
IPv6 Multicast Address Format
IPv6 - IPv4 Interworking
IPv6 Frame Format
IPv6 Header Format
IPv6 Order of Headers
IPv6 Extension Headers
IPv6 Stateless Autoconfiguration
IPv6 Discovery
IPv6 ICMP
IPv6 ping6 command
IPv6 traceroute6 command
IPv6 RFCs

IPv6 Overview

First things first. Each PC - more properly each network interface - may have more than one IPv6 address - IPv6 is naturally multi-homed. Second, an IPv6 address has a scope, that is, it can be restricted to a single LAN or a private network or be globally unique. The following table defines the types of IPv6 addresses that can be supported and contrasts them with the closest IPv4 functional equivalent.

IPv6 Name	Scope/Description	IPv4 Equivalent	Notes
Link-Local	Local LAN only. Automatically assigned based on MAC. Cannot be routed outside local LAN.	No real equivalent. Assigned IPv4 over ARP'd MAC.	Scoped address concept new to IPv6. Format.
Site-Local	Optional. Local Site only. Cannot be routed over Internet. Assigned by user.	Private network address with multi-homed interface is closest equivalent.	Scoped address concept new to IPv6. Unlike the IPv4 private network address the IPv6 device can have, and most likely will have, Link-Local, Site-Local and a Global Unicast address. Site-Local while continuing to exist in the IPv6 specification is the subject of on-going work in the IETF and is currently not supported. The address block used for this purpose has been marked Reserved by IANA.
Global Unicast	Globally unique. Fully routable. Assigned by IANA/delegated Aggregators.	Global IP address.	IPv6 and IPv4 similar but IPv6 can have other scoped addresses. Format.
Multicast	One-to-many. Hierarchy of multicasting.	Similar to IPv4 Class D.	Significantly more powerful than IPv4 version. No broadcast in IPv6, replaced by multicast. Format.
Anycast	One-to-nearest. Uses Global Unicast Addresses. Routers only. Discovery uses.	Unique protocols in IPv4 e.g. IGMP.	Some anycast addresses reserved for special functions.
Loopback	Local interface scope.	Same as IPv4 127.0.0.1	Same function

IPv6 Address Notation

An IPv6 address consists of 128 bits - an IPv4 address consists of 32 bits - and is written as a series of 8 hexadecimal strings separated by colons. Examples:

# all the following refer to the same address
2001:0000:0234:C1AB:0000:00A0:AABC:003F
# leading zeros can be omitted
2001:0:234:C1AB:0:A0:AABC:3F
# not case sensitive - any mixture allowed
2001:0:0234:C1ab:0:A0:aabc:3F

One or more zeros entries can be omitted entirely but only once in an address. The user can choose the most efficient place to omit multiple zero entries. Examples:

# raw ipv6 address
2001:0000:0234:C1AB:0000:00A0:AABC:003F
# address with single 0 dropped
2001::0234:C1ab:0:A0:aabc:003F
# alternate version - address with single 0 dropped
2001:0:0234:C1ab::A0:aabc:003F
# the following is INVALID
2001::0234:C1ab::A0:aabc:003F

Multiple zeros can be omitted entirely but only once in an address. Examples:

# omitting multiple 0's in address
2001:0:0:0:0:0:0:3F
# can be written as
2001::3F
# lots of zeros (loopback address)
0:0:0:0:0:0:0:1
# can be written as
::1
# all zeros (unspecified a.k.a unassigned IP)
0:0:0:0:0:0:0:0
# can be written as
::
# but this address
2001:0:0:1:0:0:0:3F
# cannot be reduced to this 
2001::1::3F  # INVALID
# instead it can only be reduced to
2001::1:0:0:0:3F
# or 
2001:0:0:1::3F

IPv6 Prefix or Slash Notation

IPv6 uses a similar / (forward slash) notation to IPv4 CIDR (Classless Interdomain Routing) which describes the number of contiguous bits used. Formally this way of writing and address is called an IP prefix but more commonly called the slash format. Examples:

# single user address
2001:db8::1/128
# normal user IPv6 address allocation 
# allows the user to control the low order 80 bits
2001:db8::/48
# global routing prefix - top 3 bits only with fixed value 001 (binary)
2::/3

IPv6 Address Types

The type of IP address is defined by a variable number of the top bits known as the binary prefix (BP). Only as many bits as required are used to identify the address type as shown in the following table (defined in RFC 3513):

Use	Binary Prefix	Slash	Description/Notes
Unspecified	00...0	::/128	IPv6 address = 0:0:0:0:0:0:0:0 (or ::) Used before an address allocated by DHCP (equivalent of IPv4 0.0.0.0)
Loopback	00...1	::1/128	IPv6 address = 0:0:0:0:0:0:0:1 (or ::1) Local PC Loopback (equivalent of IPv4 127.0.0.1)
Multicast	1111 1111	FF::/8	Format.
Link-Local unicast	1111 1110 10	FE8::/10	Local LAN scope. Lower bits created from MAC address. Format.
Site-Local unicast	1111 1110 11	FEC::/10	Local Site scope. Lower bits assigned by user. This binary prefix has been marked Reserved by IANA to reflect the currently unsupported state of Site-Local addressing.
Global Unicast	All other values	2::/3	A note in RFC 3513 suggests that IANA should continue to allocate only from the binary prefix 001 (as in RFC 2373 version) for the time being. Format.

The revised definition is a conceptual change and is both more flexible and cleaner than the previous (RFC 2373) definition. IPv4 and NSAP prefixes are still allowed for but are now simply unicast addresses.

IPv6 Global Unicast Address Format

The IPv6 Global Unicast 128 bits are divided into a 48 bit global routing prefix (a.k.a site prefix) which is assigned by various authorities and 80 bits which define the subnet ID and interface ID as follows:

Site Prefix of 48 bits - assigned by IANA/Aggregator.
Name	Size	Description/Notes
global routing prefix	48 bits	Variable format depending on Binary Prefix e.g. if 001 - Global Unicast Address (assigned by IANA) uses this format.
subnet ID	16 bits	Used for subnet routing.
interface ID	64 bits	The unique interface identifier (host address equivalent in IPv4).

The current IPv6 address allocation policy adopted by the various Internet Registries is based on the IETF/IAB recomendation (in RFC 3177) and allows for:

Name	Allocation	Description/Notes
Normal User	/48	The user controls the full 80 bits addresses comprising the subnet ID and interface ID
Single subnet	/64	Where it is known that only a single subnet can be used the user is assigned control of the interface ID part only
Single Device	/128	Where it is known that only one device can be used the user is assigned a single interface ID

IPv6 End-User Address Format

End-User addresses are assigned from Global Unicast pool and currently only with the binary prefix 001 (or 2::/3). The IETF 6bone currently uses a special range of 3FFe::/16 but the 6bone is being disbanded (reflecting the production ready state of IPv6) and the address range is planned to be returned to the IANA Reserved pool by June 2006. The 128 bits breakdown as follows:

global routing prefix of 48 bits - assigned by IANA/Aggregator.
Name	Size	Description/Notes
reserved	3 bits	001 - Global Unicast Address (assigned by IANA)
TLA ID	13 bits	0 0000 0000 00001 (address block 2001::/16) Top Level Aggregator (TLA). Assigned by IANA for use by the Regional Internet Registries (RIRs)
Sub-TLA	13 bits	Assigned by IANA to the RIRs. The RIRs assign blocks from this range to the National or Local Internet Registries.
NLA	19 bits	Assigned by RIR to Next Level Aggregator (NLA) (either a National or Local Internet Registry or in some cases an ISP). The NLA assigns blocks from its allocated range to end-users
80 bits - typically assigned by the user
Name	Size	Description/Notes
subnet ID	16 bits	Used for subnet routing
interface ID	64 bits	Equivalent to IPv4 host address - since this field alone is bigger that the whole IPv4 address space it is fairly generous!

IPv6 Addresses may be assigned to interfaces using one of three methods:

Stateful - Statically assigned = manual configuration
Stateful - DHCPv6 - Automatically assigned
Stateless - Automatically assigned

IPv6 Link-Local Address Format

Link-Local addresses are automatically assigned by the end user equipment and require no external configuration. The address format uses a unique binary prefix (FE8::/10) and the remaining bits (118) are built from the local interface identifier. In the case of ethernet the MAC (48 bits) is used to create the EUI-64 value as shown below. If an interface identifier has more than 118 bits the link-local address cannot be generated and the unit must be manually configured. Link-local addresses are not routable outside the local LAN. The 128 bits of a link-local address for an ethernet interface breakdown as follows:

10 bits - Binary Prefix
Name	Size	Description/Notes
Binary Prefix	10 bits	1111 1110 10 or FE8::/10 Link-Local Prefix
118 bits - constructed from interface MAC (EUI-64)
Name	Size	Description/Notes
-	54 bits	all zeros - padding from 64 to 118 bits
MAC	24 bits	top 24 bits of the 48 bit interface MAC. Vendor ID
ID	16 bits	Fixed value of FFFE inserted
MAC	24 bits	low 24 bits of the 48 bit interface MAC. Serial number.

Example

# Interface MAC
00-40-63-ca-9a-20
# IPv6 Interface ID (EUI-64)
::0040:63FF:FECA:9A20
# or
::40:63FF:FECA:9A20
# link local
FE80::40:63FF:FECA:9A20

IPv6 Multicast Address Format

The Multicast format (which also replaces broadcast in IPv4) is defined by RFC 3513 Section 2.7. The fomat of a multicast address is defined below:

Name	Bits	Size	Value	Description/Notes
Binary Prefix	0 - 7	8	1111 1111	Fixed value a.k.a the routing prefix
flags	8-11	4	000T	Where T may be either: 0 = "well-known" or permanently (IANA) assigned group 1 = "transient" group which has no IANA assignment
scope	12-15	4	-	May take one of the following assigned values: 0 - reserved 1 - interface-local scope 2 - link-local scope 3 - reserved 4 - admin-local scope 5 - site-local scope 6 - (unassigned) 7 - (unassigned) 8 - organization-local scope 9 - (unassigned) A - (unassigned) B - (unassigned) C - (unassigned) D - (unassigned) E - global scope F - reserved
Group ID	16 - 127	112	-	Uniquely assigned by IANA if "well-known" bit = 0 set in flags above. IANA IPv6 Multicast assignments

The following lists some of the more common multicast groups:

Address	Description/Notes
FF01::1	Interface local - all nodes
FF02::1	Link local - all nodes
FF01::2	Interface local - all routers
FF02::2	Link local - all routers

IPv6 - IPv4 Interworking

IPv6 allows transport of IPv4 addresses using two methods. The methods are described in RFC 2893.

The first method is termed an "IPv4-compatible IPv6 address" and must use a globally unique IPv4 address. Please note: To avoid publication of a global IPv4 the example below shows a private (non-globally unique) IPv4 address purely to illustrate the principle:

# IPv4-compatible IPv6 address
# assume the host has an IPv4 address of:
192.168.0.5
# this is represented by the hex value
C0A80005
# the IPv4-compatible IPv6 address would be
::C0A8:5
# or 
0:0:0:0:0:0:C0A8:5

The IPv4-compatible IPv6 address format is used when the end interface supports both IPv6 and IPv4 (a dual stack interface). This method is now deprecated (RFC 4291).

The second method is termed an "IPv4-mapped IPv6 address" and must use a globally unique IPv4 address. Please note: To avoid publication of a global IPv4 the example below shows a private (non-globally unique) IPv4 address purely to illustrate the principle:

# IPv4-mapped IPv6 address
# assume the host has an IPv4 address of:
192.168.0.5
# this is represented by the hex value
C0A80005
# the IPv4-mapped IPv6 address would be
::FFFF:C0A8:5
# or 
0:0:0:0:0:FFFF:C0A8:5

The IPv4-mapped IPv6 address format is used when the end interface supports only IPv4 and indicates that a configured IPv6 system e.g. a router will have to perform conversion to the IPv4 protocol prior to communicating with the interface.

IPv6 Frame Format

IPv6 headers are daisy chained. The Next Header field - present in every header except the upper layer header - indicates which header comes next as shown in the diagram below:

IPv6 Daisy chained headers

Notes:

Zero or more Extension headers may be present.
Multiple Extension headers of any type may be present.
All Extension headers are assumed to be of variable length and contain a length value (expressed in multiples of 8 octets).
Only one upper layer header may be present and is unchanged from IPv4 e.g. tcp with the exception of the format of the 'pseudo-header' used to generate the checksum.
Data (MTU) length is defined to be a minimum of 1280 octets with a recommendation of 1500+ octets. If any routing link cannot carry this size of MTU, link specific fragmentation must be carried out below (i.e. invisible to) IPv6.
When carrying UDP traffic in the upper layers the optional (in IPv4) UDP checksum MUST be present.

The pseudo header used in TCP, UDP and IPv6 ICMP is assumed be a 40 octet field and have the following format:

Name	Size	Description/Notes
Source	128 bits	IPv6 source address
Destination	128 bits	IPv6 destination address
Packet Length	32 bits	Length in octets of the upper layer data packet plus associated header.
-	24 bits	Must be zeros
Next Header	8 bits	Assumed to contain the value of the protocol carried in the upper layer e.g. 6 = TCP etc..

IPv6 Header Format

IPv6 Header Format
Name	Length	Description/Notes
version	4 bits	value = 6. Same location as IPv4 - everything after this changes.
traffic class	8 bits	None formally defined with IANA (late 2004). When used with Explicit Congestion Notification (ECN) (RFC 3168) may take values defined here and here.
Flow Label	20 bits	-
payload length	16 bits	unsigned length in octets of payload (excludes header but includes extensions)
next header	8 bits	Identifier in following header - same values as IPv4 Protocol field Some common values: 0 (0x00) IPv6 Hop-by-Hop Option 1 (0x01) ICMP protocol 2 (0x02) IGMP protocol 4 (0x04) IP over IP 6 (0x06) TCP protocol 17 (0x11) UDP protocol 41 (0x29) IPv6 protocol 58 (0x3A) IPv6 ICMP protocol 59 (0x3B) IPv6 No Next Header (terminates a no upper layer frame) Definitive list is here
hop limit	8 bits	Maximum number of hops. Formalises the current practice when using the TTL in IPv4.
source IP	128 bits	-
destination IP	128 bits	-

Order of Headers

Where multiple headers are present the recommended sender order is (but the receiver must accept in any order):

IPv6 Header
Hop-by-Hop Header
Destination Options
Routing Headers
Fragment Headers
Authentication Headers
Encapsulation Security Payload (ESP) Header
Destination Options
Upper Layer Header + data

Extension Headers

Extension headers are always multiples of 8 octets. To allow skipping and processing of extension headers they all begin with the following 16 bit stub format:

IPv6 Extension Header - Stub format
Name	Length	Description/Notes
Next Header	8 bits	Same values as IPv6 Next Header
Extension Hdr Len	8 bits	Unsigned integer. The total length of the extension header in multiples of 8 octets, excluding the first 8 octets e.g. a value of 0 = 8 octet header length, value = 2 = 24 octet header length etc. NB the length field in ICMPv6 does not use this convention - it's always good to have consistency in standards.

Header Options

The Hop-By-Hop and Destination Headers carry a variable number of options within the header and use a classic TLD (or TLV in the standards paralance) format as shown below:

Name	Length	Description/Notes
Type	8 bits	The two high order (or low order depending on your numbering convention) bits indicate what action to take if the option is not recognized and may take one of the following values: 00 = skip option - keep processing 01 = discard packet 10 = discard packet and send ICMPv6 Parameter Problem (Code 2) message 11 = discard packet and, if not Multicast address, send ICMPv6 Parameter Problem (Code 2) message The third high order bit indicates whether the option can change before reaching its destination 0 = data will not change, 1 = data may change. If the bit is set and an Authentication Header is present then an all zero option value must be assumed when computing any digest.
Length	8 bits	Length in octets of the option data - does not include the type or length value.
Data	variable	Depends on Type

In order to force so-called natural alignment of option fields two padding options are provided. An Option Type of 0 indicates a 1 octet pad (and does not have associated length or data fields), a standard Option with a Type of 1 allows for multiple octet padding. NB in this case a 2 octet pad will have an Option Length of 0.

IPv6 Hop-By-Hop Header

IPv6 Destination Header

IPv6 Configuration

IPv6 systems are typically multi-homed by default and have a link-local address configured by the host and may have a global unicast address which may be configured by one of three methods:

Stateful - Statically assigned = manual configuration
Stateful - DHCPv6 - Automatically assigned
Stateless - Automatically assigned

IPv6 Stateless Autoconfiguration

IPv6 systems may be configured to provide global unicast addresses using stateless autconfiguation. Stateless autoconfiguration requires a router to be present but not a DHCP server. In stateless autoconfiguration a default router address is provided but not a DNS and other information that is normally provided by DHCP. The process of creating a stateless IPv6 address is as follows:

Host sends a Router Solicitation message
Host waits for a Router Advertisement message.
Host takes top 64 bits from Subnet Prefix part of Router Advertisement and combines it with the 64 bit EUI-64 address (created from the MAC) to greate a Global Unicast address. The host also takes the default gateway address from the Router Advertisement message.
Host then performs a Duplicate Address Detection to ensure the address is unique. If this check fails the host immediately aborts the autoconfiguration process and must be manually configured.

IPv6 RFCs

The following RFCs define IPv6. Wow is this a list. You can get the RFCs from the IETF.

RFC	Description/Status
RFC 1809	Using the Flow Label Field in IPv6. C. Partridge. June 1995. (Format: TXT=13591 bytes) (Status: INFORMATIONAL)
RFC 1881	IPv6 Address Allocation Management. IAB, IESG. December 1995. (Format: TXT=3215 bytes) (Status: INFORMATIONAL)
RFC 1883	Internet Protocol, Version 6 (IPv6) Specification. S. Deering, R. Hinden. December 1995. (Format: TXT=82089 bytes) (Obsoleted by RFC2460) (Status: PROPOSED STANDARD)
RFC 1885	Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6). A. Conta, S. Deering. December 1995. (Format: TXT=32214 bytes) (Obsoleted by RFC2463) (Status: PROPOSED STANDARD)
RFC 1887	An Architecture for IPv6 Unicast Address Allocation. Y. Rekhter, T. Li, Eds.. December 1995. (Format: TXT=66066 bytes) (Status: INFORMATIONAL)
RFC 1888	OSI NSAPs and IPv6. J. Bound, B. Carpenter, D. Harrington, J. Houldsworth, A. Lloyd. August 1996. (Format: TXT=36469 bytes) (Status: EXPERIMENTAL)
RFC 1924	A Compact Representation of IPv6 Addresses. R. Elz. Apr-01-1996. (Format: TXT=10409 bytes) (Status: INFORMATIONAL)
RFC 1932	IP over ATM: A Framework Document. R. Cole, D. Shur, C. Villamizar. April 1996. (Format: TXT=68031 bytes) (Status: INFORMATIONAL)
RFC 2080	RIPng for IPv6. G. Malkin, R. Minnear. January 1997. (Format: TXT=47534 bytes) (Status: PROPOSED STANDARD)
RFC 2375	IPv6 Multicast Address Assignments. R. Hinden, S. Deering. July 1998. (Format: TXT=14356 bytes) (Status: INFORMATIONAL)
RFC 2428	FTP Extensions for IPv6 and NATs. M. Allman, S. Ostermann, C. Metz. September 1998. (Format: TXT=16028 bytes) (Status: PROPOSED STANDARD)
RFC 2460	Internet Protocol, Version 6 (IPv6) Specification. S. Deering, R. Hinden. December 1998. (Format: TXT=85490 bytes) (Obsoletes RFC1883) (Status: DRAFT STANDARD)
RFC 2461	Neighbor Discovery for IP Version 6 (IPv6). T. Narten, E. Nordmark, W. Simpson. December 1998. (Format: TXT=222516 bytes) (Obsoletes RFC1970) (Status: DRAFT STANDARD)
RFC 2462	IPv6 Stateless Address Autoconfiguration. S. Thomson, T. Narten. December 1998. (Format: TXT=61210 bytes) (Obsoletes RFC1971) (Status: DRAFT STANDARD)
RFC 2463	Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification. A. Conta, S. Deering. December 1998. (Format: TXT=34190 bytes) (Obsoletes RFC1885) (Status: DRAFT STANDARD)
RFC 2464	Transmission of IPv6 Packets over Ethernet Networks. M. Crawford. December 1998. (Format: TXT=12725 bytes) (Obsoletes RFC1972) (Status: PROPOSED STANDARD)
RFC 2465	Management Information Base for IP Version 6: Textual Conventions and General Group. D. Haskin, S. Onishi. December 1998. (Format: TXT=77339 bytes) (Status: PROPOSED STANDARD)
RFC 2466	Management Information Base for IP Version 6: ICMPv6 Group. D. Haskin, S. Onishi. December 1998. (Format: TXT=27547 bytes) (Status: PROPOSED STANDARD)
RFC 2467	Transmission of IPv6 Packets over FDDI Networks. M. Crawford. December 1998. (Format: TXT=16028 bytes) (Obsoletes RFC2019) (Status: PROPOSED STANDARD)
RFC 2492	IPv6 over ATM Networks. G. Armitage, P. Schulter, M. Jork. January 1999. (Format: TXT=21199 bytes) (Status: PROPOSED STANDARD)
RFC 2526	Reserved IPv6 Subnet Anycast Addresses. D. Johnson, S. Deering. March 1999. (Format: TXT=14555 bytes) (Status: PROPOSED STANDARD)
RFC 2529	Transmission of IPv6 over IPv4 Domains without Explicit Tunnels. B. Carpenter, C. Jung. March 1999. (Format: TXT=21049 bytes) (Status: PROPOSED STANDARD)
RFC 2545	Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing. P. Marques, F. Dupont. March 1999. (Format: TXT=10209 bytes) (Status: PROPOSED STANDARD)
RFC 2673	Binary Labels in the Domain Name System. M. Crawford. August 1999. (Format: TXT=12379 bytes) (Updated by RFC3363, RFC3364) (Status: EXPERIMENTAL)
RFC 2675	IPv6 Jumbograms. D. Borman, S. Deering, R. Hinden. August 1999. (Format: TXT=17320 bytes) (Obsoletes RFC2147) (Status: PROPOSED STANDARD)
RFC 2710	Multicast Listener Discovery (MLD) for IPv6. S. Deering, W. Fenner, B. Haberman. October 1999. (Format: TXT=46838 bytes) (Updated by RFC3590, RFC3810) (Status: PROPOSED STANDARD)
RFC 2711	IPv6 Router Alert Option. C. Partridge, A. Jackson. October 1999. (Format: TXT=11973 bytes) (Status: PROPOSED STANDARD)
RFC 2732	Format for Literal IPv6 Addresses in URL's. R. Hinden, B. Carpenter, L. Masinter. December 1999. (Format: TXT=7984 bytes) (Updates RFC2396) (Status: PROPOSED STANDARD)
RFC 2740	OSPF for IPv6. R. Coltun, D. Ferguson, J. Moy. December 1999. (Format: TXT=189810 bytes) (Status: PROPOSED STANDARD)
RFC 2766	Network Address Translation - Protocol Translation (NAT-PT). G. Tsirtsis, P. Srisuresh. February 2000. (Format: TXT=49836 bytes) (Updated by RFC3152) (Status: PROPOSED STANDARD)
RFC 2893	Transition Mechanisms for IPv6 Hosts and Routers. R. Gilligan, E. Nordmark. August 2000. (Format: TXT=62731 bytes) (Obsoletes RFC1933) (Status: PROPOSED STANDARD)
RFC 2894	Router Renumbering for IPv6. M. Crawford. August 2000. (Format: TXT=69135 bytes) (Status: PROPOSED STANDARD)
RFC 2928	Initial IPv6 Sub-TLA ID Assignments. R. Hinden, S. Deering, R. Fink, T. Hain. September 2000. (Format: TXT=11882 bytes) (Status: INFORMATIONAL)
RFC 3041	Privacy Extensions for Stateless Address Autoconfiguration in IPv6. T. Narten, R. Draves. January 2001. (Format: TXT=44446 bytes) (Status: PROPOSED STANDARD)
RFC 3056	Connection of IPv6 Domains via IPv4 Clouds. B. Carpenter, K. Moore. February 2001. (Format: TXT=54902 bytes) (Status: PROPOSED STANDARD)
RFC 3111	Service Location Protocol Modifications for IPv6. E. Guttman. May 2001. (Format: TXT=25543 bytes) (Status: PROPOSED STANDARD)
RFC 3122	Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification. A. Conta. June 2001. (Format: TXT=40416 bytes) (Status: PROPOSED STANDARD)
RFC 3146	Transmission of IPv6 Packets over IEEE 1394 Networks. K. Fujisawa, A. Onoe. October 2001. (Format: TXT=16569 bytes) (Status: PROPOSED STANDARD)
RFC 3152	Delegation of IP6.ARPA. R. Bush. August 2001. (Format: TXT=5727 bytes) (Obsoleted by RFC3596) (Updates RFC2874, RFC2772, RFC2766, RFC2553, RFC1886) (Also BCP0049) (Status: BEST CURRENT PRACTICE)
RFC 3162	RADIUS and IPv6. B. Aboba, G. Zorn, D. Mitton. August 2001. (Format: TXT=20492 bytes) (Status: PROPOSED STANDARD)
RFC 3175	Aggregation of RSVP for IPv4 and IPv6 Reservations. F. Baker, C. Iturralde, F. Le Faucheur, B. Davie. September 2001. (Format: TXT=88681 bytes) (Status: PROPOSED STANDARD)
RFC 3177	IAB/IESG Recommendations on IPv6 Address Allocations to Sites. IAB, IESG. September 2001. (Format: TXT=23178 bytes) (Status: INFORMATIONAL)
RFC 3266	Support for IPv6 in Session Description Protocol (SDP). S. Olson, G. Camarillo, A. B. Roach. June 2002. (Format: TXT=8693 bytes) (Updates RFC2327) (Status: PROPOSED STANDARD)
RFC 3306	Unicast-Prefix-based IPv6 Multicast Addresses. B. Haberman, D. Thaler. August 2002. (Format: TXT=12713 bytes) (Status: PROPOSED STANDARD)
RFC 3307	Allocation Guidelines for IPv6 Multicast Addresses. B. Haberman. August 2002. (Format: TXT=15742 bytes) (Status: PROPOSED STANDARD)
RFC 3314	Recommendations for IPv6 in Third Generation Partnership Project (3GPP) Standards. M. Wasserman, Ed.. September 2002. (Format: TXT=48168 bytes) (Status: INFORMATIONAL)
RFC 3315	Dynamic Host Configuration Protocol for IPv6 (DHCPv6). R. Droms, Ed., J. Bound, B. Volz, T. Lemon, C. Perkins, M. Carney. July 2003. (Format: TXT=231402 bytes) (Status: PROPOSED STANDARD)
RFC 3363	Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System (DNS). R. Bush, A. Durand, B. Fink, O. Gudmundsson, T. Hain. August 2002. (Format: TXT=11055 bytes) (Updates RFC2673, RFC2874) (Status: INFORMATIONAL)
RFC 3364	Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6). R. Austein. August 2002. (Format: TXT=26544 bytes) (Updates RFC2673, RFC2874) (Status: INFORMATIONAL)
RFC 3484	Default Address Selection for Internet Protocol version 6 (IPv6). R. Draves. February 2003. (Format: TXT=55076 bytes) (Status: PROPOSED STANDARD)
RFC 3513	Internet Protocol Version 6 (IPv6) Addressing Architecture. R. Hinden, S. Deering. April 2003. (Format: TXT=53920 bytes) (Obsoletes RFC2373) (Status: obsoleted by RFC4291)
RFC 3587	IPv6 Global Unicast Address Format. R. Hinden, S. Deering, E. Nordmark. August 2003. (Format: TXT=8783 bytes) (Obsoletes RFC2374) (Status: INFORMATIONAL)
RFC 3596	DNS Extensions to Support IP Version 6. S. Thomson, C. Huitema, V. Ksinant, M. Souissi. October 2003. (Format: TXT=14093 bytes) (Obsoletes RFC3152, RFC1886) (Status: DRAFT STANDARD)
RFC 3633	IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6. O. Troan, R. Droms. December 2003. (Format: TXT=45308 bytes) (Status: PROPOSED STANDARD)
RFC 3646	DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6). R. Droms, Ed.. December 2003. (Format: TXT=13312 bytes) (Status: PROPOSED STANDARD)
RFC 3697	IPv6 Flow Label Specification. J. Rajahalme, A. Conta, B. Carpenter, S. Deering. March 2004. (Format: TXT=21296 bytes) (Status: PROPOSED STANDARD)
RFC 3736	Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6. R. Droms. April 2004. (Format: TXT=18510 bytes) (Status: PROPOSED STANDARD)
RFC 3775	Mobility Support in IPv6. D. Johnson, C. Perkins, J. Arkko. June 2004. (Format: TXT=393514 bytes) (Status: PROPOSED STANDARD)
RFC 3776	Using IPsec to Protect Mobile IPv6 Signaling Between Mobile Nodes and Home Agents. J. Arkko, V. Devarapalli, F. Dupont. June 2004. (Format: TXT=87076 bytes) (Status: PROPOSED STANDARD)
RFC 3810	Multicast Listener Discovery Version 2 (MLDv2) for IPv6. R. Vida, Ed., L. Costa, Ed.. June 2004. (Format: TXT=153579 bytes) (Updates RFC2710) (Status: PROPOSED STANDARD)
RFC 3831	Transmission of IPv6 Packets over Fibre Channel. C. DeSanti. July 2004. (Format: TXT=53328 bytes) (Status: PROPOSED STANDARD)
RFC 3849	IPv6 Address Prefix Reserved for Documentation. G. Huston, A. Lord, P. Smith. July 2004. (Format: TXT=7872 bytes) (Status: INFORMATIONAL)
RFC 3901	DNS IPv6 Transport Operational Guidelines. A. Durand, J. Ihren. September 2004. (Format: TXT=10025 bytes) (Also BCP0091) (Status: BEST CURRENT PRACTICE)
RFC 3956	Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address. P. Savola, B. Haberman. November 2004. (Format: TXT=40136 bytes) (Updates RFC3306) (Status: PROPOSED STANDARD)
RFC 4007	IPv6 Scoped Address Architecture. S. Deering, B. Haberman, T. Jinmei, E. Nordmark, B. Zill. March 2005. (Format: TXT=53555 bytes) (Status: PROPOSED STANDARD)
RFC 4074	Common Misbehavior Against DNS Queries for IPv6 Addresses. Y. Morishita, T. Jinmei. May 2005. (Format: TXT=13073 bytes) (Status: INFORMATIONAL)
RFC 4193	Unique Local IPv6 Unicast Addresses. R. Hinden, B. Haberman. October 2005. (Format: TXT=35908 bytes) (Status: PROPOSED STANDARD)
RFC 4213	Basic Transition Mechanisms for IPv6 Hosts and Routers. E. Nordmark, R. Gilligan. October 2005. (Format: TXT=58575 bytes) (Obsoletes RFC2893) (Status: PROPOSED STANDARD)
RFC 4215	Analysis on IPv6 Transition in Third Generation Partnership Project (3GPP) Networks. J. Wiljakka, Ed.. October 2005. (Format: TXT=52903 bytes) (Status: INFORMATIONAL)
RFC 4242	Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6). S. Venaas, T. Chown, B. Volz. November 2005. (Format: TXT=14759 bytes) (Status: PROPOSED STANDARD)
RFC 4260	Mobile IPv6 Fast Handovers for 802.11 Networks. P. McCann. November 2005. (Format: TXT=35276 bytes) (Status: INFORMATIONAL)
RFC 4283	Mobile Node Identifier Option for Mobile IPv6 (MIPv6). A. Patel, K. Leung, M. Khalil, H. Akhtar, K. Chowdhury. November 2005. (Format: TXT=14653 bytes) (Status: PROPOSED STANDARD)
RFC 4283	Mobile Node Identifier Option for Mobile IPv6 (MIPv6). A. Patel, K. Leung, M. Khalil, H. Akhtar, K. Chowdhury. November 2005. (Format: TXT=14653 bytes) (Status: PROPOSED STANDARD)
RFC 4291	IP Version 6 Addressing Architecture. R. Hinden, S. Deering. February 2006. (Format: TXT=52897 bytes) (Obsoletes RFC3513) (Status: DRAFT STANDARD)
RFC 4295	Mobile IPv6 Management Information Base. G. Keeni, K. Koide, K. Nagami, S. Gundavelli. April 2006. (Format: TXT=209038 bytes) (Status: PROPOSED STANDARD)
RFC 4311	IPv6 Host-to-Router Load Sharing. R. Hinden, D. Thaler. November 2005. (Format: TXT=10156 bytes) (Updates RFC2461) (Status: PROPOSED STANDARD)
RFC 4339	IPv6 Host Configuration of DNS Server Information Approaches. J. Jeong, Ed.. February 2006. (Format: TXT=60803 bytes) (Status: INFORMATIONAL)
RFC 4380	Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs). C. Huitema. February 2006. (Format: TXT=132607 bytes) (Status: PROPOSED STANDARD)
RFC 4429	Optimistic Duplicate Address Detection (DAD) for IPv6. N. Moore. April 2006. (Format: TXT=33123 bytes) (Status: PROPOSED STANDARD)
RFC 4443	Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification. A. Conta, S. Deering, M. Gupta, Ed.. March 2006. (Format: TXT=48969 bytes) (Obsoletes RFC2463) (Updates RFC2780) (Status: DRAFT STANDARD)
RFC 4449	Securing Mobile IPv6 Route Optimization Using a Static Shared Key. C. Perkins. June 2006. (Format: TXT=15080 bytes) (Status: PROPOSED STANDARD)
RFC 4489	A Method for Generating Link-Scoped IPv6 Multicast Addresses. J-S. Park, M-K. Shin, H-J. Kim. April 2006. (Format: TXT=12224 bytes) (Updates RFC3306) (Status: PROPOSED STANDARD)
RFC 4649	Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option. B. Volz. August 2006. (Format: TXT=10940 bytes) (Status: PROPOSED STANDARD)
RFC 4704	The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option. B. Volz. October 2006. (Format: TXT=32359 bytes) (Status: PROPOSED STANDARD)

Problems, comments, suggestions, corrections (including broken links) or something to add? Please take the time from a busy life to 'mail us' (at top of screen), the webmaster (below) or info-support at zytrax. You will have a warm inner glow for the rest of the day.