Anytime a fixed identifier is used in multipleĬontexts, it becomes possible to correlate seemingly unrelated contain an embedded interface identifier, which remainsĬonstant over time. Īddresses generated using stateless address autoconfiguration "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in thisĭocument are to be interpreted as described in. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", RFC 4941 Privacy Extensions to Autoconf September 2007 1.1. The term "global scope addresses" is used in thisĭocument to collectively refer to "Global unicast addresses" asĭefined in and "Unique local addresses" as defined in
Section 4 discusses implications of changing interface Generating alternate interface identifiers and global scopeĪddresses. Help mitigate those concerns for individual users and in environments Non-changing interface identifiers within IPv6 addresses andĭescribes extensions to stateless address autoconfiguration that can This document discusses concerns associated with the embedding of May also apply to interfaces with other types of globally unique That IEEE identifiers are being used, but the techniques described Possible only in those cases where the interface identifier is Tracking of individual devices, the concern being addressed here, is
The focus of thisĭocument is on addresses derived from IEEE identifiers because Globally unique and may also change over time. (e.g., at random), and the resultant interface identifier may not be In suchĬases, an interface identifier is generated through some other means Not all nodes and interfaces contain IEEE identifiers. Additional addresses can then be created byĬombining prefixes advertised in Router Advertisements via Neighborĭiscovery with the interface identifier. Reserved link-local prefix to generate link-local addresses for theirĪttached interfaces. Identifier or generated through some other technique) with the In this document is targeted towards 64-bit interface identifiers.Īll nodes combine interface identifiers (whether derived from an IEEE
RANDOM ADDRESS 64 BITS
Necessarily have to be 64 bits in length, but the algorithm specified Interface identifier is in turn appended to a prefix to form aġ28-bit IPv6 address. Is likely to be globally unique when generated in this fashion.
RANDOM ADDRESS MAC
Link-layer MAC address), and in those cases, stateless addressĪutoconfiguration uses the IEEE identifier to generate a 64-bit Network interfaces come with an embedded IEEE Identifier (i.e., a
Node generates addresses without the need for a Dynamic HostĬonfiguration Protocol for IPv6 (DHCPv6) server. Stateless address autoconfiguration defines how an IPv6 RFC 4941 Privacy Extensions to Autoconf September 2007 1. Implications of Changing Interface Identifiers. Regeneration of Randomized Interface Identifiers. Generation of Randomized Interface Identifiers. RFC 4941 Privacy Extensions to Autoconf September 2007ġ. Transactions actually correspond to the same node. Time makes it more difficult for eavesdroppers and other informationĬollectors to identify when different addresses used in different Identifier (and the global scope addresses generated from it) over Identifiers that change over time, even in cases where the interfaceĬontains an embedded IEEE identifier. Use of the extensionĬauses nodes to generate global scope addresses from interface Identifier is derived from an IEEE identifier. Stateless address autoconfiguration for interfaces whose interface This document describes an extension to IPv6 Identifier is generated through other means, for example, via random On an interface thatĬontains an embedded IEEE Identifier, the interface identifier is
Network prefixes with an interface identifier. Nodes use IPv6 stateless address autoconfiguration to generateĪddresses using a combination of locally available information and Official Protocol Standards" (STD 1) for the standardization stateĪnd status of this protocol. Please refer to the current edition of the "Internet Internet community, and requests discussion and suggestions for This document specifies an Internet standards track protocol for the Privacy Extensions for Stateless Address Autoconfiguration in IPv6 Request for Comments: 4941 IBM CorporationĬategory: Standards Track Microsoft Research
0 kommentar(er)
