RFC 7136
Significance of IPv6 Interface Identifiers, February 2014
- File formats:
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 4291
- Authors:
- B. Carpenter
S. Jiang - Stream:
- IETF
- Source:
- 6man (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7136
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 7136
Abstract
The IPv6 addressing architecture includes a unicast interface identifier that is used in the creation of many IPv6 addresses. Interface identifiers are formed by a variety of methods. This document clarifies that the bits in an interface identifier have no meaning and that the entire identifier should be treated as an opaque value. In particular, RFC 4291 defines a method by which the Universal and Group bits of an IEEE link-layer address are mapped into an IPv6 unicast interface identifier. This document clarifies that those two bits are significant only in the process of deriving interface identifiers from an IEEE link-layer address, and it updates RFC 4291 accordingly.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.