RFC 2462: IPv6 Stateless Address Autoconfiguration
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4862.
Current document in this lineage: RFC 4862 — IPv6 Stateless Address Autoconfiguration
In plain English — editorial summary, not part of the RFC
This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2462
- Published
- December 1998
- Authors
- S. Thomson; T. Narten
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 25
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1971 (1996)
- RFC 2462 (1998)
- RFC 4862 (2007) ✓
Read the full history of IPv6 Stateless Address Autoconfiguration →
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 2939Procedures and IANA Guidelines for Definition of New DHCP Options and Message TypesCurrent
September 2000
- RFC 3679Unused Dynamic Host Configuration Protocol (DHCP) Option CodesUpdated
January 2004
- RFC 2461Neighbor Discovery for IP Version 6 (IPv6)Obsoleted
December 1998
- RFC 2460Internet Protocol, Version 6 (IPv6) SpecificationObsoleted
December 1998
- RFC 2465Management Information Base for IP Version 6: Textual Conventions and General GroupObsoleted
December 1998
- RFC 2466Management Information Base for IP Version 6: ICMPv6 GroupObsoleted
December 1998
- RFC 2452IP Version 6 Management Information Base for the Transmission Control ProtocolObsoleted
December 1998
- RFC 2472IP Version 6 over PPPObsoleted
December 1998
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?