RFC 8064
Recommendation on Stable IPv6 Interface Identifiers, February 2017
- File formats:
- Status:
- PROPOSED STANDARD
- 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
- Authors:
- F. Gont
A. Cooper
D. Thaler
W. Liu - Stream:
- IETF
- Source:
- 6man (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8064
Discuss this RFC: Send questions or comments to the mailing list ipv6@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8064
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.