RFC 3041: Privacy Extensions for Stateless Address Autoconfiguration in IPv6
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4941.
Current document in this lineage: RFC 8981 — Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6
In plain English — editorial summary, not part of the RFC
This document describes an extension to IPv6 stateless address autoconfiguration for interfaces whose interface identifier is derived from an IEEE identifier. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3041
- Published
- January 2001
- Authors
- T. Narten; R. Draves
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 17
- Also known as
- —
- Obsoleted by:
- RFC 4941
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3041 (2001)
- RFC 4941 (2007)
- RFC 8981 (2021) ✓
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 2732Format for Literal IPv6 Addresses in URL'sObsoleted
December 1999
- RFC 3493Basic Socket Interface Extensions for IPv6Current
March 2003
- RFC 2553Basic Socket Interface Extensions for IPv6Obsoleted
March 1999
- RFC 2133Basic Socket Interface Extensions for IPv6Obsoleted
April 1997
- RFC 3012Mobile IPv4 Challenge/Response ExtensionsObsoleted
November 2000
- RFC 2977Mobile IP Authentication, Authorization, and Accounting RequirementsCurrent
October 2000
- RFC 2939Procedures and IANA Guidelines for Definition of New DHCP Options and Message TypesCurrent
September 2000
- RFC 3178IPv6 Multihoming Support at Site Exit RoutersCurrent
October 2001
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?