RFC 4941
Privacy Extensions for Stateless Address Autoconfiguration in IPv6, September 2007
- File formats:
- Status:
- DRAFT STANDARD
- Obsoletes:
- RFC 3041
- Obsoleted by:
- RFC 8981
- Authors:
- T. Narten
R. Draves
S. Krishnan - Stream:
- IETF
- Source:
- ipv6 (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC4941
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 4941
Abstract
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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.