RFC 8064: Recommendation on Stable IPv6 Interface Identifiers
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8064
- Published
- February 2017
- Authors
- F. Gont; A. Cooper; D. Thaler; W. Liu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 9
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8065Privacy Considerations for IPv6 Adaptation-Layer MechanismsCurrent
February 2017
- RFC 8066IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) ESC Dispatch Code Points and GuidelinesCurrent
February 2017
- RFC 8074Source Address Validation Improvement (SAVI) for Mixed Address Assignment Methods ScenarioCurrent
February 2017
- RFC 8047Host Multihoming with the Host Identity ProtocolCurrent
February 2017
- RFC 8046Host Mobility with the Host Identity ProtocolCurrent
February 2017
- RFC 8039Multipath Time SynchronizationCurrent
December 2016
- RFC 8094DNS over Datagram Transport Layer Security (DTLS)Current
February 2017
- RFC 8096The IPv6-Specific MIB Modules Are ObsoleteCurrent
April 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?