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. This document obsoletes RFC 3513, "IP Version 6 Addressing Architecture". [STANDARDS-TRACK]
Document record
- Document ID
- RFC4291
- Published
- February 2006
- Authors
- R. Hinden; S. Deering
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 25
- Also known as
- —
- Obsoletes:
- RFC 3513
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
6 later RFCs formally update or obsolete part of this document.
- RFC 5952A Recommendation for IPv6 Address Text RepresentationCurrent
August 2010
- RFC 6052IPv6 Addressing of IPv4/IPv6 TranslatorsCurrent
October 2010
- RFC 7136Significance of IPv6 Interface IdentifiersCurrent
February 2014
- RFC 7346IPv6 Multicast Address ScopesCurrent
August 2014
- RFC 7371Updates to the IPv6 Multicast Addressing ArchitectureCurrent
September 2014
- RFC 8064Recommendation on Stable IPv6 Interface IdentifiersCurrent
February 2017
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2373IP Version 6 Addressing ArchitectureObsoleted
July 1998
- RFC 4629RTP Payload Format for ITU-T Rec. H.263 VideoCurrent
January 2007
- RFC 3853S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)Current
July 2004
- RFC 4916Connected Identity in the Session Initiation Protocol (SIP)Current
June 2007
- RFC 3292General Switch Management Protocol (GSMP) V3Current
June 2002
- RFC 3265Session Initiation Protocol (SIP)-Specific Event NotificationObsoleted
July 2002
- RFC 3264An Offer/Answer Model with Session Description Protocol (SDP)Updated
July 2002
- RFC 3263Session Initiation Protocol (SIP): Locating SIP ServersUpdated
July 2002
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?