Recommendation on Stable IPv6 Interface Identifiers

Fernando Gont, A. Feder Cooper, Dave Thaler, W. Liu2017 · DOI

TL;DR

This paper updates the recommended default method for generating stable IPv6 interface identifiers (IIDs) when using Stateless Address Autoconfiguration (SLAAC). It strongly recommends adopting the RFC 7217 mechanism, which generates semantically opaque IIDs, and advises against embedding stable link-layer addresses (like MAC addresses) directly into IIDs due to significant security and privacy concerns.

What Problem Does This Paper Address?

When a device joins an IPv6 network, it needs an IPv6 address. Stateless Address Autoconfiguration (SLAAC) is a common method for hosts to automatically configure their IPv6 addresses without needing a DHCP server. A key part of this process is generating an Interface Identifier (IID), which is the host-specific part of the IPv6 address. Historically, a common practice was to derive this IID from the device's stable link-layer address, such as its MAC address. While this ensured the IID remained constant for a given network interface, it introduced significant security and privacy risks. These risks include the ability to track devices across networks (location tracking), correlate network activity, and exploit device-specific vulnerabilities. This paper addresses the need for a more secure and privacy-preserving default method for generating stable IPv6 IIDs.

Methods

The core of this paper's contribution is a recommendation for a change in practice. It doesn't introduce a new algorithm but rather advocates for the adoption of an existing one: RFC 7217.

  • Recommended Method: RFC 7217 provides a method for generating stable IPv6 interface identifiers that are "semantically opaque." This means the IID is generated in a way that doesn't reveal information about the underlying hardware or network interface, thus mitigating the privacy risks associated with embedding link-layer addresses.
  • Discouraged Method: The paper explicitly recommends against using schemes that embed stable link-layer addresses (like MAC addresses) into IIDs. This includes many older RFCs that defined such methods.
  • Scope: The recommendations apply specifically to the default generation of stable IPv6 addresses using SLAAC. It clarifies that this document does not alter recommendations for temporary IPv6 addresses (RFC 4941) or cases where IIDs are intentionally randomized.

Datasets

Not discussed in the paper.

Key Insights and Ideas

  • Privacy is Paramount: The paper strongly emphasizes that the security and privacy implications of embedding stable link-layer addresses in IIDs are significant and well-documented. These include tracking, correlation, and vulnerability exploitation.
  • RFC 7217 as the Solution: The document positions RFC 7217 as the de facto standard for generating stable, privacy-preserving IIDs, offering a robust alternative to the older, more vulnerable methods.
  • Default Behavior Matters: By changing the default recommendation, the paper aims to influence widespread adoption of better practices, even if administrators can still choose to configure less secure options.
  • Updating Existing Standards: The paper formally updates a long list of previous RFCs that defined or implicitly allowed the use of link-layer addresses in IIDs, signaling a clear shift in the IETF's stance.

Key Results

This paper is a recommendation and an update to existing standards, rather than a paper reporting experimental results. Its "results" are the updated recommendations:

  • Adoption of RFC 7217: Nodes SHOULD implement and employ RFC 7217 as the default scheme for generating stable IPv6 addresses with SLAAC.
  • Discouragement of Link-Layer Embedding: Nodes SHOULD NOT employ IPv6 address generation schemes that embed a stable link-layer address in the IID by default. This specifically invalidates the default generation methods specified in numerous older RFCs.
  • No Change to Temporary Addresses: Existing recommendations for temporary addresses (RFC 4941) remain unaffected.

Limitations and Future Work

  • Configurability: While the paper recommends RFC 7217 as the default, it acknowledges that link-layer-based IID generation mechanisms might still be defined by specific network technologies for efficiency. The choice of whether to enable the security- and privacy-preserving mechanism SHOULD be configurable.
  • Future Work on Related Documents: The paper notes that several other documents related to IPv6 transmission over specific network types (e.g., IEEE 802.15.4, ITU-T G.9959) might require updates to be fully compatible with these recommendations. Future revisions of these documents should consider the privacy and security issues and explain any design choices that lead to using link-layer-based IIDs.

Summary updated

Abstract

This document changes the recommended default Interface Identifier (IID) generation scheme for cases where Stateless Address Autoconfiguration (SLAAC) is used to generate a stable IPv6 address. It recommends using the mechanism specified in RFC 7217 in such cases, and recommends against embedding stable link-layer addresses in IPv6 IIDs. It formally updates RFC 2464, RFC 2467, RFC 2470, RFC 2491, RFC 2492, RFC 2497, RFC 2590, RFC 3146, RFC 3572, RFC 4291, RFC 4338, RFC 4391, RFC 5072, and RFC 5121. This document does not change any existing recommendations concerning the use of temporary addresses as specified in RFC 4941.
BibTeX
@misc{gont2017recommendation,
  author = {Fernando Gont and A. Feder Cooper and Dave Thaler and W. Liu},
  title = {{Recommendation on Stable IPv6 Interface Identifiers}},
  year = {2017},
  doi = {10.17487/rfc8064},
}

Loading related content...

Figure