[dhcwg] RFC 8948 on Structured Local Address Plan (SLAP) Quadrant Selection Option for DHCPv6
rfc-editor@rfc-editor.org Wed, 02 December 2020 03:02 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B6343A109D; Tue, 1 Dec 2020 19:02:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J51ynK5h8uaA; Tue, 1 Dec 2020 19:02:48 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CD8A3A1124; Tue, 1 Dec 2020 19:02:36 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id EDD70F4075D; Tue, 1 Dec 2020 19:02:33 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dhcwg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20201202030233.EDD70F4075D@rfc-editor.org>
Date: Tue, 01 Dec 2020 19:02:33 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/liSt2v6kfD6hc3zfqxHlhWHvrmI>
Subject: [dhcwg] RFC 8948 on Structured Local Address Plan (SLAP) Quadrant Selection Option for DHCPv6
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Dec 2020 03:02:57 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8948
Title: Structured Local Address Plan (SLAP)
Quadrant Selection Option for DHCPv6
Author: CJ. Bernardos,
A. Mourad
Status: Standards Track
Stream: IETF
Date: December 2020
Mailbox: cjbc@it.uc3m.es,
alain.mourad@interdigital.com
Pages: 16
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dhc-slap-quadrant-12.txt
URL: https://www.rfc-editor.org/info/rfc8948
DOI: 10.17487/RFC8948
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.
This document is a product of the Dynamic Host Configuration Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC