RFC 4941: 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 8981.
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
Nodes use IPv6 stateless address autoconfiguration to generate addresses using a combination of locally available information and information advertised by routers. Addresses are formed by combining network prefixes with an interface identifier. On an interface that contains an embedded IEEE Identifier, the interface identifier is typically derived from it. On other interface types, the interface identifier is generated through other means, for example, via random number generation. This document describes an extension to IPv6 stateless address autoconfiguration for interfaces whose interface identifier is derived from an IEEE identifier. Use of the extension causes nodes to generate global scope addresses from interface identifiers that change over time, even in cases where the interface contains an embedded IEEE identifier. Changing the interface identifier (and the global scope addresses generated from it) over time makes it more difficult for eavesdroppers and other information collectors to identify when different addresses used in different transactions actually correspond to the same node. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4941
- Published
- September 2007
- Authors
- T. Narten; R. Draves; S. Krishnan
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 23
- 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 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 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 9103DNS Zone Transfer over TLSCurrent
August 2021
- RFC 9724State of Affairs for Randomized and Changing Media Access Control (MAC) AddressesCurrent
March 2025
- RFC 9797Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use CasesCurrent
June 2025
- RFC 5209Network Endpoint Assessment (NEA): Overview and RequirementsCurrent
June 2008
- RFC 5246The Transport Layer Security (TLS) Protocol Version 1.2Obsoleted
August 2008
- RFC 5403RPCSEC_GSS Version 2Updated
February 2009
- RFC 4366Transport Layer Security (TLS) ExtensionsObsoleted
April 2006
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?