RFC 8948: Structured Local Address Plan (SLAP) Quadrant Selection Option for DHCPv6
In plain English — editorial summary, not part of the RFC
The IEEE originally structured the 48-bit Media Access Control (MAC) address space in such a way that half of it was reserved for local use. In 2017, the IEEE published a new standard (IEEE Std 802c) with a new optional Structured Local Address Plan (SLAP). It specifies different assignment approaches in four specified regions of the local MAC address space. The IEEE is developing protocols to assign addresses (IEEE P802.1CQ). There is also work in the IETF on specifying a new mechanism that extends DHCPv6 operation to handle the local MAC address assignments. This document proposes extensions to DHCPv6 protocols to enable a DHCPv6 client or a DHCPv6 relay to indicate a preferred SLAP quadrant to the server so that the server may allocate MAC addresses in the quadrant requested by the relay or client. A new DHCPv6 option (QUAD) is defined for this purpose.
Document record
- Document ID
- RFC8948
- Published
- December 2020
- Authors
- CJ. Bernardos; A. Mourad
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9039Uniform Resource Names for Device IdentifiersCurrent
June 2021
- RFC 8469Recommendation to Use the Ethernet Control WordCurrent
November 2018
- RFC 8947Link-Layer Address Assignment Mechanism 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
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?