RFC 3513: Internet Protocol Version 6 (IPv6) Addressing Architecture
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4291.
Current document in this lineage: RFC 4291 — IP Version 6 Addressing Architecture
In plain English — editorial summary, not part of the RFC
This specification defines the addressing architecture of the IP Version 6 (IPv6) protocol. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3513
- Published
- April 2003
- Authors
- R. Hinden; S. Deering
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 26
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 1884 (1995)
- RFC 2373 (1998)
- RFC 3513 (2003)
- RFC 4291 (2006) ✓
Read the full history of IP Version 6 Addressing Architecture →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2375IPv6 Multicast Address AssignmentsCurrent
July 1998
- RFC 2269Using the MARS Model in non-ATM NBMA NetworksCurrent
January 1998
- RFC 2121Issues affecting MARS Cluster SizeCurrent
March 1997
- RFC 3170IP Multicast Applications: Challenges and SolutionsCurrent
September 2001
- RFC 2429RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+)Obsoleted
October 1998
- RFC 2236Internet Group Management Protocol, Version 2Updated
November 1997
- RFC 3493Basic Socket Interface Extensions for IPv6Current
March 2003
- RFC 3587IPv6 Global Unicast Address FormatCurrent
August 2003
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?