Search RFCs

RFC Editor

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 listipv6@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 interfaceidentifier that is used in the creation of many IPv6 addresses.Interface identifiers are formed by a variety of methods. Thisdocument clarifies that the bits in an interface identifier have nomeaning and that the entire identifier should be treated as an opaquevalue. In particular, RFC 4291 defines a method by which theUniversal and Group bits of an IEEE link-layer address are mappedinto an IPv6 unicast interface identifier. This document clarifiesthat those two bits are significant only in the process of derivinginterface identifiers from an IEEE link-layer address, and it updatesRFC 4291 accordingly.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.