Search RFCs

RFC Editor

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 listipv6@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 generateaddresses using a combination of locally available information andinformation advertised by routers. Addresses are formed by combiningnetwork prefixes with an interface identifier. On an interface thatcontains an embedded IEEE Identifier, the interface identifier istypically derived from it. On other interface types, the interfaceidentifier is generated through other means, for example, via randomnumber generation. This document describes an extension to IPv6stateless address autoconfiguration for interfaces whose interfaceidentifier is derived from an IEEE identifier. Use of the extensioncauses nodes to generate global scope addresses from interfaceidentifiers that change over time, even in cases where the interfacecontains an embedded IEEE identifier. Changing the interfaceidentifier (and the global scope addresses generated from it) overtime makes it more difficult for eavesdroppers and other informationcollectors to identify when different addresses used in differenttransactions actually correspond to the same node. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.