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.
- RFC 8948Structured Local Address Plan (SLAP) Quadrant Selection Option for DHCPv6Current
December 2020
- RFC 8932Recommendations for DNS Privacy Service OperatorsCurrent
October 2020
- RFC 8931IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Selective Fragment RecoveryCurrent
November 2020
- RFC 8930On Forwarding 6LoWPAN Fragments over a Multi-Hop IPv6 NetworkCurrent
November 2020
- RFC 8929IPv6 Backbone RouterCurrent
November 2020
- RFC 8928Address-Protected Neighbor Discovery for Low-Power and Lossy NetworksUpdated
November 2020
- RFC 8925IPv6-Only Preferred Option for DHCPv4Current
October 2020
- RFC 8915Network Time Security for the Network Time ProtocolCurrent
September 2020
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?