CurrentPROPOSED STANDARDIETF stream

RFC 8947: Link-Layer Address Assignment Mechanism for DHCPv6

In plain English — editorial summary, not part of the RFC

In certain environments, e.g., large-scale virtualization deployments, new devices are created in an automated manner. Such devices may have their link-layer addresses assigned in an automated fashion. With sufficient scale, the likelihood of a collision using random assignment without duplication detection is not acceptable. Therefore, an allocation mechanism is required. This document proposes an extension to DHCPv6 that allows a scalable approach to link-layer address assignments where preassigned link-layer address assignments (such as by a manufacturer) are not possible or are unnecessary.

Document record

Document ID
RFC8947
Published
December 2020
Authors
B. Volz; T. Mrugalski; CJ. Bernardos
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
18
Also known as

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/8947-link-layer-address-assignment-mechanism-for-dhcpv6