Recommendation on Stable IPv6 Interface Identifiers
RFC 8064, “Recommendation on Stable IPv6 Interface Identifiers”, is a Proposed Standard document published in February 2017 by F. Gont, A. Cooper, D. Thaler, W. Liu. It 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, RFC 5121. The canonical text is published by the RFC Editor.
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8064 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8063 Key Relay Mapping for the Extensible Provisioning Protocol
- RFC 8065 Privacy Considerations for IPv6 Adaptation-Layer Mechanisms
- RFC 8062 Anonymity Support for Kerberos
- RFC 8066 IPv6 over Low-Power Wireless Personal Area Network ESC Dispatch Code Points and Guidelines
- RFC 8061 Locator/ID Separation Protocol Data-Plane Confidentiality
- RFC 8067 Updating When Standards Track Documents May Refer Normatively to Documents at a Lower Level
- RFC 8060 LISP Canonical Address Format
- RFC 8068 Session Initiation Protocol Recording Call Flows