Protocol: IPv6 ( Internet Protocol version 6 )

IPv6 ( Internet Protocol version 6 )

Update: 2006-08-30 14:46:14 I have words to say about this protocol

On this page

SUMMARY
DESCRIPTION
EXAMPLES
PROTOCOL RELATIONS
GLOSSARY
REFERENCES
OTHER PROTOCOLS

SUMMARY
Protocol	:	Internet Protocol version 6
Protocol suite	:	TCP/IP
Layer	:	Network Layer
Type	:	Connectionless network layer protocol
EtherType	:	0x86DD
SNMP MIBs	:	iso.org.dod.internet.mgmt.mib-2.ipv6MIB (1.3.6.1.2.1.55). iso.org.dod.internet.mgmt.mib-2.ipv6FlowLabelMIB (1.3.6.1.2.1.103). iso.org.dod.internet.experimental.ipv6UdpMIB (1.3.6.1.3.87).
Related protocols	:	IP , IPv4 , TCP , UDP , ICMP , SNMP , FTP , TELNET , SMTP , ARP , RARP , RPC, XDR, NFS
Working groups	:	IPv6, IP Version 6 Working Group NGTRANS, Next Generation Transition

DESCRIPTION

IP version 6 (IPv6) is a new version of the Internet Protocol based on IPv4. IPv4 and IPv6 are demultiplexed at the media layer. For example, IPv6 packets are carried over Ethernet with the content type 86DD (hexadecimal) instead of IPv4¡¯s 0800.

IPv6 increases the IP address size from 32 bits to 128 bits, to support more levels of addressing hierarchy, a much greater number of addressable nodes and simpler auto-configuration of addresses. Scalability of multicast addresses is introduced. A new type of address called an anycast address is also defined, to send a packet to any one of a group of nodes.

IP version 6 (IPv6) is a new version of the Internet Protocol, designed as the successor to IP version 4 (IPv4). The changes from IPv4 to IPv6 fall primarily into the following categories:

Expanded Addressing Capabilities
IPv6 increases the IP address size from 32 bits to 128 bits, to support more levels of addressing hierarchy, a much greater number of addressable nodes, and simpler auto-configuration of addresses. The scalability of multicast routing is improved by adding a "scope" field to multicast addresses. And a new type of address called an "anycast address" is defined, used to send a packet to any one of a group of nodes.

Header Format Simplification
Some IPv4 header fields have been dropped or made optional, to reduce the common-case processing cost of packet handling and to limit the bandwidth cost of the IPv6 header.

Improved Support for Extensions and Options
Changes in the way IP header options are encoded allows for more efficient forwarding, less stringent limits on the length of options, and greater flexibility for introducing new options in the future.

Flow Labeling Capability
A new capability is added to enable the labeling of packets belonging to particular traffic "flows" for which the sender requests special handling, such as non-default quality of service or "real-time" service.

Authentication and Privacy Capabilities
Extensions to support authentication, data integrity, and (optional) data confidentiality are specified for IPv6.

IPv6 header

4	12	16	24	32
Version	Traffic Class	Flow Label
Payload Length			Next Header	Hop Limit
Source address
Destination address
Data

Version
Internet Protocol Version number (IPv6 is 6).

Traffic Class
Traffic class field enables a source to identify the desired delivery priority of the packets. Priority values are divided into ranges: traffic where the source provides congestion control and non-congestion control traffic.

Flow label
Used by a source to label those products for which it requests special handling by the IPv6 router. The flow is uniquely identified by the combination of a source address and a non-zero flow label.

Payload length
Specifies the length of the data in the packet. When cleared to zero, the option is a hop-by-hop Jumbo payload.

Next header
Identifies the type of header immediately following the IPv6 header. Uses the same values as the IPv4 Protocol field.

Hop limit
For each router that forwards the packet, the hop limit is decremented by 1. When the hop limit field reaches zero, the packet is discarded. This replaces the TTL field in the IPv4 header that was originally intended to be used as a time based hop limit.

Source address
128-bit address of the originator of the packet.

Destination address
128-bit address of the intended recipient of the packet.

IPv6 Extension Headers
In IPv6, optional internet-layer information is encoded in separate headers that may be placed between the IPv6 header and the upper- layer header in a packet. There are a small number of such extension headers, each identified by a distinct Next Header value. As illustrated in these examples, an IPv6 packet may carry zero, one, or more extension headers, each identified by the Next Header field of the preceding header:

With one exception, extension headers are not examined or processed by any node along a packet's delivery path, until the packet reaches the node (or each of the set of nodes, in the case of multicast) identified in the Destination Address field of the IPv6 header. There, normal demultiplexing on the Next Header field of the IPv6 header invokes the module to process the first extension header, or the upper-layer header if no extension header is present. The contents and semantics of each extension header determine whether or not to proceed to the next header. Therefore, extension headers must be processed strictly in the order they appear in the packet; a receiver must not, for example, scan through a packet looking for a particular kind of extension header and process that header prior to processing all preceding ones.

The exception referred to in the preceding paragraph is the Hop-by- Hop Options header, which carries information that must be examined and processed by every node along a packet's delivery path, including the source and destination nodes. The Hop-by-Hop Options header, when present, must immediately follow the IPv6 header. Its presence is indicated by the value zero in the Next Header field of the IPv6 header.

If, as a result of processing a header, a node is required to proceed to the next header but the Next Header value in the current header is unrecognized by the node, it should discard the packet and send an ICMP Parameter Problem message to the source of the packet, with an ICMP Code value of 1 ("unrecognized Next Header type encountered") and the ICMP Pointer field containing the offset of the unrecognized value within the original packet. The same action should be taken if a node encounters a Next Header value of zero in any header other than an IPv6 header.

Each extension header is an integer multiple of 8 octets long, in order to retain 8-octet alignment for subsequent headers. Multi- octet fields within each extension header are aligned on their natural boundaries, i.e., fields of width n octets are placed at an integer multiple of n octets from the start of the header, for n = 1, 2, 4, or 8.

A full implementation of IPv6 includes implementation of the following extension headers:

Hop-by-Hop Options
The Hop-by-Hop Options header is used to carry optional information that must be examined by every node along a packet's delivery path. The Hop-by-Hop Options header is identified by a Next Header value of 0 in the IPv6 header.

Routing (Type 0)
The Routing header is used by an IPv6 source to list one or more intermediate nodes to be "visited" on the way to a packet's destination. This function is very similar to IPv4's Loose Source and Record Route option. The Routing header is identified by a Next Header value of 43 in the immediately preceding header.

Fragment
The Fragment header is used by an IPv6 source to send a packet larger than would fit in the path MTU to its destination. (Note: unlike IPv4, fragmentation in IPv6 is performed only by source nodes, not by routers along a packet's delivery path -- see section 5.) The Fragment header is identified by a Next Header value of 44 in the immediately preceding header.

Destination Options
The Destination Options header is used to carry optional information that need be examined only by a packet's destination node(s). The Destination Options header is identified by a Next Header value of 60 in the immediately preceding header.

Authentication
The IP Authentication Header (AH) is used to provide connectionless integrity and data origin authentication for IP datagrams, and to provide protection against replays. The protocol header (IPv4, IPv6, or Extension) immediately preceding the AH header will contain the value 51 in its Protocol (IPv4) or Next Header (IPv6, Extension) field.

Encapsulating Security Payload
The Encapsulating Security Payload (ESP) header is designed to provide a mix of security services in IPv4 and IPv6. ESP may be applied alone, in combination with the IP Authentication Header (AH), or in a nested fashion, e.g., through the use of tunnel mode.

Top of Page

EXAMPLES

Example 1

If an option X required two data fields, one of length 8 octets and one of length 

4 octets, it would be laid out as follows:



                                          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                                          | Option Type=X |Opt Data Len=12|

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |                         4-octet field                         |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |                                                               |

          +                         8-octet field                         +

          |                                                               |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+



Its alignment requirement is 8n+2, to ensure that the 8-octet field starts at a 

multiple-of-8 offset from the start of the enclosing header. A complete Hop-by-Hop 

or Destination Options header containing this one option would look as follows:



          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |  Next Header  | Hdr Ext Len=1 | Option Type=X |Opt Data Len=12|

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |                         4-octet field                         |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |                                                               |

          +                         8-octet field                         +

          |                                                               |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Example 2

If an option Y required three data fields, one of length 4 octets, one of length 

2 octets, and one of length 1 octet, it would be laid out as follows:



                                                          +-+-+-+-+-+-+-+-+

                                                          | Option Type=Y |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |Opt Data Len=7 | 1-octet field |         2-octet field         |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |                         4-octet field                         |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+



Its alignment requirement is 4n+3, to ensure that the 4-octet field starts at a 

multiple-of-4 offset from the start of the enclosing header. A complete Hop-by-Hop 

or Destination Options header containing this one option would look as follows:



          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |  Next Header  | Hdr Ext Len=1 | Pad1 Option=0 | Option Type=Y |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |Opt Data Len=7 | 1-octet field |         2-octet field         |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |                         4-octet field                         |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          | PadN Option=1 |Opt Data Len=2 |       0       |       0       |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Example 3

A Hop-by-Hop or Destination Options header containing both options X and Y 

from Examples 1 and 2 would have one of the two following formats, depending 

on which option appeared first:



          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |  Next Header  | Hdr Ext Len=3 | Option Type=X |Opt Data Len=12|

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |                         4-octet field                         |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |                                                               |

          +                         8-octet field                         +

          |                                                               |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          | PadN Option=1 |Opt Data Len=1 |       0       | Option Type=Y |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |Opt Data Len=7 | 1-octet field |         2-octet field         |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |                         4-octet field                         |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          | PadN Option=1 |Opt Data Len=2 |       0       |       0       |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+



          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |  Next Header  | Hdr Ext Len=3 | Pad1 Option=0 | Option Type=Y |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |Opt Data Len=7 | 1-octet field |         2-octet field         |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |                         4-octet field                         |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          | PadN Option=1 |Opt Data Len=4 |       0       |       0       |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |       0       |       0       | Option Type=X |Opt Data Len=12|

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |                         4-octet field                         |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

          |                                                               |

          +                         8-octet field                         +

          |                                                               |

          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Top of Page

PROTOCOL RELATIONS

■ Parent layer
■ Child layer

IP
MPLS
Ethernet
IPv6
ICMP
ICMPv6
IGMP
EGP
IGRP
EIGRP
SCTP
TCP
UDP
PUP
OSPF
VRRP
ESP
AH
GRE
RSVP
PIM
IPv6
Other

Top of Page

GLOSSARY

Anycast
Anycast is an identifier for a set of interfaces (typically belonging to different nodes). A packet sent to an anycast address is delivered to one of the interfaces identified by that address (the "nearest" one, according to the routing protocol's measure of distance). Note that an anycast address is syntactically indistinguishable from a unicast address. Thus, nodes sending packets to anycast addresses don't generally know that an anycast address is being used.

Authorization
The process of identifying an individual, usually based on a username and password. In security systems, authentication is distinct from authorization , which is the process of giving individuals access to system objects based on their identity. Authentication merely ensures that the individual is who he or she claims to be, but says nothing about the access rights of the individual.

Deprecated address
Deprecated address is an address assigned to an interface whose use is discouraged, but not forbidden. A deprecated address should no longer be used as a source address in new communications, but packets sent to deprecated addresses are delivered as expected. A deprecated address may continue to be used as a source address in communications where switching to a preferred address causes hardship to a specific upper-layer activity (e.g., an existing TCP connection).

IP address
IP address is an identifier for a computer or device on a TCP/IP network. Networks using the TCP/IP protocol route messages based on the IP address of the destination. The format of an IP address is a 32-bit numeric address written as four numbers separated by periods. Each number can be zero to 255. For example, 1.160.10.240 could be an IP address. Within an isolated network, you can assign IP addresses at random as long as each one is unique. However, connecting a private network to the Internet requires using registered IP addresses (called Internet addresses) to avoid duplicates.

The four numbers in an IP address are used in different ways to identify a particular network and a host on that network. Four regional Internet registries -- ARIN, RIPE NCC, LACNIC and APNIC -- assign Internet addresses from the following three classes.
Class A - supports 16 million hosts on each of 126 networks
Class B - supports 65,000 hosts on each of 16,000 networks
Class C - supports 254 hosts on each of 2 million networks

The number of unassigned Internet addresses is running out, so a new classless scheme called CIDR is gradually replacing the system based on classes A, B, and C and is tied to adoption of IPv6.

IPv4
IPv4 is version 4 of the Internet Protocol (IP). It was the first version of the Internet Protocol to be widely deployed, and forms the basis for most of the current Internet. IPv4 uses 32-bit addresses, limiting it to 4,294,967,296 unique addresses, many of which are reserved for special purposes such as local networks or multicast addresses, reducing the number of addresses that can be allocated as public Internet addresses.

IPv6
IPv6 is designed as an evolutionary upgrade to the Internet Protocol and will, in fact, coexist with the older IPv4 for some time. IPv6 is designed to allow the Internet to grow steadily, both in terms of the number of hosts connected and the total amount of data traffic transmitted.

Node
In networks, node is a processing location. A node can be a computer or some other device, such as a printer. Every node has a unique network address, sometimes called a Data Link Control (DLC) address or Media Access Control (MAC) address.

In tree structures, node is a point where two or more lines meet.

Preferred address
Preferred address is an address assigned to an interface whose use by upper layer protocols is unrestricted. Preferred addresses may be used as the source (or destination) address of packets sent from (or to) the interface.

Top of Page

REFERENCES

Related links:
                address space
                anycast
                multicast
                multicast groups
                IPv6 parameters
                TLAs
                www.ipv6.org

RFCs:
[RFC 1719] A Direction for IPng.
[RFC 1726] Technical Criteria for Choosing IP The Next Generation (IPng).
[RFC 1752] The Recommendation for the IP Next Generation Protocol.
[RFC 1809] Using the Flow Label Field in IPv6.
[RFC 1881] IPv6 Address Allocation Management.
[RFC 1887] An Architecture for IPv6 Unicast Address Allocation.
[RFC 1888] OSI NSAPs and IPv6.
[RFC 1981] Path MTU Discovery for IP version 6.
[RFC 2126] ISO Transport Service on top of TCP (ITOT).
[RFC 2170] Application REQuested IP over ATM (AREQUIPA).
[RFC 2185] Routing Aspects Of IPv6 Transition.
[RFC 2375] IPv6 Multicast Address Assignments.
[RFC 2401] Security Architecture for the Internet Protocol.
[RFC 2450] Proposed TLA and NLA Assignment Rules.
[RFC 2460] Internet Protocol, Version 6 (IPv6) Specification.
                Obsoletes: RFC 1883.
[RFC 2461] Neighbor Discovery for IP Version 6 (IPv6).
                Obsoletes: RFC 1970.
[RFC 2462] IPv6 Stateless Address Autoconfiguration.
                Obsoletes: RFC 1971.
[RFC 2464] Transmission of IPv6 Packets over Ethernet Networks.
                Obsoletes: RFC 1972.
[RFC 2465] Management Information Base for IP Version 6: Textual Conventions and General Group.
                Defines SNMP MIB iso.org.dod.internet.mgmt.mib-2.ipv6MIB (1.3.6.1.2.1.55).
[RFC 2467] Transmission of IPv6 Packets over FDDI Networks.
                Obsoletes: RFC 2019.
[RFC 2470] Transmission of IPv6 Packets over Token Ring Networks.
[RFC 2472] IP Version 6 over PPP.
                Obsoletes: RFC 2023.
[RFC 2473] Generic Packet Tunneling in IPv6 Specification.
[RFC 2474] Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers.
[RFC 2475] An Architecture for Differentiated Services.
[RFC 2491] IPv6 over Non-Broadcast Multiple Access (NBMA) networks.
[RFC 2492] IPv6 over ATM Networks.
[RFC 2497] Transmission of IPv6 Packets over ARCnet Networks.
[RFC 2507] IP Header Compression.
[RFC 2508] Compressing IP/UDP/RTP Headers for Low-Speed Serial Links.
[RFC 2526] Reserved IPv6 Subnet Anycast Addresses.
[RFC 2529] Transmission of IPv6 over IPv4 Domains without Explicit Tunnels.
[RFC 2590] Transmission of IPv6 Packets over Frame Relay Networks Specification.
[RFC 2675] IPv6 Jumbograms.
                Obsoletes: RFC 2147.
[RFC 2711] IPv6 Router Alert Option.
[RFC 2765] Stateless IP/ICMP Translation Algorithm (SIIT).
[RFC 2766] Network Address Translation - Protocol Translation (NAT-PT).
[RFC 2767] Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS).
[RFC 2780] IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers.
[RFC 2874] DNS Extensions to Support IPv6 Address Aggregation and Renumbering.
[RFC 2893] Transition Mechanisms for IPv6 Hosts and Routers.
                Obsoletes: RFC 1933.
[RFC 2928] Initial IPv6 Sub-TLA ID Assignments.
[RFC 3041] Privacy Extensions for Stateless Address Autoconfiguration in IPv6.
[RFC 3053] IPv6 Tunnel Broker.
[RFC 3056] Connection of IPv6 Domains via IPv4 Clouds.
[RFC 3111] Service Location Protocol Modifications for IPv6.
[RFC 3142] An IPv6-to-IPv4 Transport Relay Translator.
[RFC 3146] Transmission of IPv6 Packets over IEEE 1394 Networks.
[RFC 3178] IPv6 Multihoming Support at Site Exit Routers.
[RFC 3306] Unicast-Prefix-based IPv6 Multicast Addresses.
                Updated by: RFC 3956.
[RFC 3307] Allocation Guidelines for IPv6 Multicast Addresses.
[RFC 3314] Recommendations for IPv6 in Third Generation Partnership Project (3GPP) Standards.
[RFC 3316] Internet Protocol Version 6 (IPv6) for Some Second and Third Generation Cellular Hosts.
[RFC 3484] Default Address Selection for Internet Protocol version 6 (IPv6).
[RFC 3493] Basic Socket Interface Extensions for IPv6.
                Defines IPv6 modifications for the socket programming library.
                Obsoletes: RFC 2553.
[RFC 3513] Internet Protocol Version 6 (IPv6) Addressing Architecture.
                Obsoletes: RFC 2373.
[RFC 3531] A Flexible Method for Managing the Assignment of Bits of an IPv6 Address Block.
[RFC 3542] Advanced Sockets Application Program Interface (API) for IPv6.
                Obsoletes: RFC 2292.
[RFC 3545] Enhanced Compressed RTP (CRTP) for Links with High Delay, Packet Loss and Reordering.
[RFC 3572] Internet Protocol Version 6 over MAPOS (Multiple Access Protocol Over SONET/SDH).
[RFC 3582] Goals for IPv6 Site-Multihoming Architectures.
[RFC 3587] IPv6 Global Unicast Address Format.
                Obsoletes: RFC 2374.
[RFC 3595] Textual Conventions for IPv6 Flow Label.
                Defines SNMP MIB iso.org.dod.internet.mgmt.mib-2.ipv6FlowLabelMIB (1.3.6.1.2.1.103).
[RFC 3627] Use of /127 Prefix Length Between Routers Considered Harmful.
[RFC 3697] IPv6 Flow Label Specification.
[RFC 3736] Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6.
[RFC 3750] Unmanaged Networks IPv6 Transition Scenarios.
[RFC 3756] IPv6 Neighbor Discovery (ND) Trust Models and Threats.
[RFC 3769] Requirements for IPv6 Prefix Delegation.
[RFC 3831] Transmission of IPv6 Packets over Fibre Channel.
[RFC 3849] IPv6 Address Prefix Reserved for Documentation.
[RFC 3879] Deprecating Site Local Addresses.
                Deprecates IPv6 site-local unicast prefix FEC0::/10.
[RFC 3904] Evaluation of IPv6 Transition Mechanisms for Unmanaged Networks.
[RFC 3919] Remote Network Monitoring (RMON) Protocol Identifiers for IPv6 and Multi Protocol Label Switching (MPLS).
[RFC 3956] Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address.
                Updates: RFC 3306.
[RFC 3964] Security Considerations for 6to4.
[RFC 4007] IPv6 Scoped Address Architecture.
[RFC 4029] Scenarios and Analysis for Introducing IPv6 into ISP Networks.
[RFC 4038] Application Aspects of IPv6 Transition.
[RFC 4048] RFC 1888 Is Obsolete.
[RFC 4057] IPv6 Enterprise Network Scenarios.
[RFC 4113] Management Information Base for the User Datagram Protocol (UDP).
                Defines SNMP MIB iso.org.dod.internet.mgmt.mib-2.udp (1.3.6.1.2.1.7).
                Defines SNMP MIB iso.org.dod.internet.mgmt.mib-2.udpMIB (1.3.6.1.2.1.50).
                Obsoletes: RFC 2013, RFC 2454.
[RFC 4159] Deprecation of "ip6.int".
[RFC 4177] Architectural Approaches to Multi-homing for IPv6.

Obsolete RFCs:
[RFC 1883] Internet Protocol, Version 6 (IPv6) Specification.
                Obsoleted by: RFC 2460.
[RFC 1884] IP Version 6 Addressing Architecture.
                Obsoleted by: RFC 2373.
[RFC 1897] IPv6 Testing Address Allocation.
                Obsoleted by: RFC 2471.
[RFC 1933] Transition Mechanisms for IPv6 Hosts and Routers.
                Obsoleted by: RFC 2893.
[RFC 1970] Neighbor Discovery for IP Version 6 (IPv6).
                Obsoleted by: RFC 2461.
[RFC 1971] IPv6 Stateless Address Autoconfiguration.
                Obsoleted by: RFC 2462.
[RFC 1972] A Method for the Transmission of IPv6 Packets over Ethernet Networks.
                Obsoleted by: RFC 2464.
[RFC 2019] A Method for the Transmission of IPv6 Packets over FDDI Networks.
                Obsoleted by: RFC 2467.
[RFC 2023] IP Version 6 over PPP.
                Obsoleted by: RFC 2472.
[RFC 2073] An IPv6 Provider-Based Unicast Address Format.
                Obsoleted by: RFC 2374.
[RFC 2133] Basic Socket Interface Extensions for IPv6.
                Obsoleted by: RFC 2553.
                Defines IPv6 modifications for the socket programming library.
[RFC 2147] TCP and UDP over IPv6 Jumbograms.
                Obsoleted by: RFC 2675.
                Updates: RFC 1883.
[RFC 2292] Advanced Sockets API for IPv6.
                Obsoleted by: RFC 3542.
[RFC 2553] Basic Socket Interface Extensions for IPv6.
                Obsoleted by: RFC 3493.
                Defines IPv6 modifications for the socket programming library.
                Obsoletes: RFC 2133.
[RFC 2373] IP Version 6 Addressing Architecture.
                Obsoleted by: RFC 3513.
                Defines the IPv6 addressing architecture.
                Obsoletes: RFC 1884.
[RFC 2374] An IPv6 Aggregatable Global Unicast Address Format.
                Obsoleted by: RFC 3587.
                Obsoletes: RFC 2073.
[RFC 2452] IP Version 6 Management Information Base for the Transmission Control Protocol.
                Obsoleted by: RFC 4022.
[RFC 2454] IP Version 6 Management Information Base for the User Datagram Protocol.
                Obsoleted by: RFC 4113.
                Defines SNMP MIB iso.org.dod.internet.experimental.ipv6UdpMIB (1.3.6.1.3.87).
[RFC 2471] IPv6 Testing Address Allocation.
                Obsoleted by: RFC 3701.
                Obsoletes: RFC 1897.
[RFC 2732] Format for Literal IPv6 Addresses in URL's.
                Obsoleted by: RFC 3986.

Publications:
[ISBN 0138505055] IPv6: The New Internet Protocol.

Top of Page

OTHER PROTOCOLS OF TCP/IP SUITE