NOTE: Most (if not all) of the IPv6 documents are still in draft status. A standard paragraph at the start of each document says :-
Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet Drafts as reference material or to cite them other than as a "working draft" or "work in progress".
A local source of RFC's and Internet Drafts is ftp://munnari.oz.au in directories /rfc and /internet-drafts. munnari also contains IETF information and the archive of the IPv6imp mailing list.
Take these RFCs with a pinch of salt. Some of the Internet Drafts modify or supersede the RFCs.
RFC 2147 TCP and UDP over IPv6 Jumbograms May 1997 RFC 2133 IPv6 Socket Interface Extensions April 1997 RFC 2080 RIPng for IPv6 January 1997 RFC 2073 IPv6 Provider-Based Unicast Address Format January 1997 RFC 2023 IP Version 6 over PPP October 1996 RFC 1981 Path MTU Discovery for IPv6 August 1996 RFC 1972 Transmission of IPv6 Packets Over Ethernet August 1996 RFC 1971 IPv6 Stateless Address Autoconfiguration August 1996 RFC 1970 Neighbor Discovery for IP Version 6 (IPv6) August 1996 RFC 1933 IPv6 Transition Mechanisms April 1996 RFC 1924 A Compact Representation of IPv6 Addresses 1 April 1996 RFC 1897 IPv6 Testing Address Allocation January 1996 RFC 1887 IPv6 Unicast Address Allocation Architecture December 1995 RFC 1886 IPv6 DNS Extensions December 1995 RFC 1885 ICMPv6 (ICMP for IPv6) December 1995 RFC 1884 IPv6 Addressing Architecture December 1995 RFC 1883 IPv6 Specification December 1995 RFC 1881 IPv6 Address Allocation Management December 1995 RFC 1809 Using the Flow Label Field in IPv6 June 1995 RFC 1719 A Direction for IPng December 1994 RFC 1705 Six Virtual Inches to the Left: IPng Problems October 1994
The set of Internet drafts is huge, IPng alone has approximately 200 drafts. Some are slides, some are obsolete proposals. My current working set is :-
Discusses the routing problem and offers possible solutions. Fairly old now (1995) but useful background.
The current (June 1997) definition of IPv6 addressing architecture. It defines how the 128 bit address is broken up, how to represent IPv6 addresses, which addresses hosts and routers must recognise.
Another hierarchical structure for the IPv6 Internet. Not being proceeded with but is an interesting alternative view.
Currently assigned multicast groups.
A replacement for RFC 1897. Describes how to construct test IPv6 addresses for the 6bone for this month's aggregation structure.
A replacement for RFC 2073. Defines the hierarchical addressing structure for the IPv6 Internet. The aim is to reduce the backbone routes to a relatively few entries, maximum 8192 at the top level.
Detailed programming interfaces for low level services such as ping, traceroute and router daemons.
In no particular order :-
Only describes IPv4 but all the IPv6 documentation assumes that you know IPv4.
Although published in 1996, this is already partly out of date. It describes the hierarchical structure of RFC 2073 rather than the newer draft-ietf-ipngwg-unicast-aggr-01.txt. Apart from that it is very detailed and extremely useful.
© Keith Owens O. C. Software P/L 1997