[dhcwg] Protocol Action: 'SLAP quadrant selection option for DHCPv6' to Proposed Standard (draft-ietf-dhc-slap-quadrant-12.txt)

The IESG <iesg-secretary@ietf.org> Tue, 13 October 2020 15:21 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dhcwg@ietf.org
Delivered-To: dhcwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 076053A08DC; Tue, 13 Oct 2020 08:21:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: draft-ietf-dhc-slap-quadrant@ietf.org, dhcwg@ietf.org, Ian Farrer <ianfarrer@gmx.com>, ianfarrer@gmx.com, dhc-chairs@ietf.org, The IESG <iesg@ietf.org>, evyncke@cisco.com, rfc-editor@rfc-editor.org, Tomek Mrugalski <tomasz.mrugalski@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Message-ID: <160260246900.12288.16415853499520814632@ietfa.amsl.com>
Date: Tue, 13 Oct 2020 08:21:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/D2IrLuiFG0n1oPLxEiRywQqM2OY>
X-Mailman-Approved-At: Tue, 13 Oct 2020 08:24:09 -0700
Subject: [dhcwg] Protocol Action: 'SLAP quadrant selection option for DHCPv6' to Proposed Standard (draft-ietf-dhc-slap-quadrant-12.txt)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 13 Oct 2020 15:21:09 -0000

The IESG has approved the following document:
- 'SLAP quadrant selection option for DHCPv6'
  (draft-ietf-dhc-slap-quadrant-12.txt) as Proposed Standard

This document is the product of the Dynamic Host Configuration Working Group.

The IESG contact persons are Erik Kline and Éric Vyncke.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-slap-quadrant/





Technical Summary

IEEE 802c includes new assignment approaches for MAC addresses. This defines four regions (quadrants) of the local MAC address space, each with their own set of semantics.
draft-ietf-dhc-mac-assign (another draft) defines a new mechanism enabling clients to request leasing of link-layer addressing by extending existing DHCPv6 processes. This draft extends
draft-ietf-dhc-mac-assign giving DHCP clients and relays a mechanism to indicate preferences for the SLAP quadrant that the server should allocate L2 addresses from.
One new DHCPv6 option is defined for this purpose.

Working Group Summary

This document has been progressed through the DHC workgroup. There is consensus in the WG for the publication of this document. No points or controversy has been raised during the authoring or review process.

Document Quality

Are there existing implementations of the protocol? Have a significant number of vendors indicated their plan to implement the specification? Are there any reviewers that merit special mention as having done a thorough review, e.g., one that resulted in important changes or a conclusion that the document had no substantive issues? If there was a MIB Doctor, YANG Doctor, Media Type or other expert review, what was its course (briefly)? In the case of a Media Type review, on what date was the request posted?

There are no existing implementations of the specification. One of the authors (C. Bernandos) stated that he is involved in an EU project which may implement.

Personnel

Ian Farrer is the Document Shepherd.
Éric Vyncke is the Area Director

IANA Note

The IANA considerations section requests the assignment of a new DHCPv6 option code for the new DHCPv6 option defined in the document's body text. The data that is provided contains the necessary parameters for the option code assignment, including the "Client ORO" and "singleton option" values as described in section 24. of RFC8415.