Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Authors:

B. Volz
T. Mrugalski
CJ. Bernardos

Stream:

IETF

Source:

dhc (int)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8947

Discuss this RFC: Send questions or comments to the mailing listdhcwg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8947

Abstract

In certain environments, e.g., large-scale virtualizationdeployments, new devices are created in an automated manner. Suchdevices may have their link-layer addresses assigned in an automatedfashion. With sufficient scale, the likelihood of a collision usingrandom assignment without duplication detection is not acceptable.Therefore, an allocation mechanism is required. This documentproposes an extension to DHCPv6 that allows a scalable approach tolink-layer address assignments where preassigned link-layer addressassignments (such as by a manufacturer) are not possible or areunnecessary.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.