RFC 7217: A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC)
In plain English — editorial summary, not part of the RFC
This document specifies a method for generating IPv6 Interface Identifiers to be used with IPv6 Stateless Address Autoconfiguration (SLAAC), such that an IPv6 address configured using this method is stable within each subnet, but the corresponding Interface Identifier changes when the host moves from one network to another. This method is meant to be an alternative to generating Interface Identifiers based on hardware addresses (e.g., IEEE LAN Media Access Control (MAC) addresses), such that the benefits of stable addresses can be achieved without sacrificing the security and privacy of users. The method specified in this document applies to all prefixes a host may be employing, including link-local, global, and unique-local prefixes (and their corresponding addresses).
Document record
- Document ID
- RFC7217
- Published
- April 2014
- Authors
- F. Gont
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 19
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7219SEcure Neighbor Discovery (SEND) Source Address Validation Improvement (SAVI)Current
May 2014
- RFC 7220Description Option for the Port Control Protocol (PCP)Current
May 2014
- RFC 7222Quality-of-Service Option for Proxy Mobile IPv6Current
May 2014
- RFC 7225Discovering NAT64 IPv6 Prefixes Using the Port Control Protocol (PCP)Current
May 2014
- RFC 7227Guidelines for Creating New DHCPv6 OptionsCurrent
May 2014
- RFC 7228Terminology for Constrained-Node NetworksCurrent
May 2014
- RFC 7256Multicast Control Extensions for the Access Node Control Protocol (ANCP)Current
July 2014
- RFC 7161Proxy Mobile IPv6 (PMIPv6) Multicast Handover Optimization by the Subscription Information Acquisition through the LMA (SIAL)Current
March 2014
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?