RFC 3587: IPv6 Global Unicast Address Format
In plain English — editorial summary, not part of the RFC
This document obsoletes RFC 2374, "An IPv6 Aggregatable Global Unicast Address Format". It defined an IPv6 address allocation structure that includes Top Level Aggregator (TLA) and Next Level Aggregator (NLA). This document makes RFC 2374 and the TLA/NLA structure historic. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3587
- Published
- August 2003
- Authors
- R. Hinden; S. Deering; E. Nordmark
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 5
- Also known as
- —
- Obsoletes:
- RFC 2374
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2073 (1997)
- RFC 2374 (1998)
- RFC 3587 (2003)
Read the full history of IPv6 Global Unicast Address Format →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3178IPv6 Multihoming Support at Site Exit RoutersCurrent
October 2001
- 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 2236Internet Group Management Protocol, Version 2Updated
November 1997
- RFC 2103Mobility Support for Nimrod : Challenges and Solution ApproachesCurrent
February 1997
- RFC 2081RIPng Protocol Applicability StatementCurrent
January 1997
- RFC 2080RIPng for IPv6Current
January 1997
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?