RFC 3701: 6bone (IPv6 Testing Address Allocation) Phaseout
In plain English — editorial summary, not part of the RFC
The 6bone was established in 1996 by the IETF as an IPv6 Testbed network to enable various IPv6 testing as well as to assist in the transitioning of IPv6 into the Internet. It operates under the IPv6 address allocation 3FFE::/16 from RFC 2471. As IPv6 is beginning its production deployment it is appropriate to plan for the phaseout of the 6bone. This document establishes a plan for a multi-year phaseout of the 6bone and its address allocation on the assumption that the IETF is the appropriate place to determine this. This document obsoletes RFC 2471, "IPv6 Testing Address Allocation", December, 1998. RFC 2471 will become historic. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3701
- Published
- March 2004
- Authors
- R. Fink; R. Hinden
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 6
- Also known as
- —
- Obsoletes:
- RFC 2471
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1897 (1996)
- RFC 2471 (1998)
- RFC 3701 (2004)
Read the full history of 6bone (IPv6 Testing Address Allocation) Phaseout →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3587IPv6 Global Unicast Address FormatCurrent
August 2003
- RFC 3177IAB/IESG Recommendations on IPv6 Address Allocations to SitesObsoleted
September 2001
- RFC 4305Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
December 2005
- RFC 4835Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
April 2007
- RFC 2101IPv4 Address Behaviour TodayCurrent
February 1997
- RFC 1897IPv6 Testing Address AllocationObsoleted
January 1996
- RFC 2322Management of IP numbers by peg-dhcpCurrent
April 1998
- RFC 3679Unused Dynamic Host Configuration Protocol (DHCP) Option CodesUpdated
January 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?