Document Action: 'Using DHCPv6-PD to Allocate Unique IPv6 Prefix per Client in Large Broadcast Networks' to Informational RFC (draft-ietf-v6ops-dhcp-pd-per-device-08.txt)

The IESG <iesg-secretary@ietf.org> Thu, 04 April 2024 17:39 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'Using DHCPv6-PD to Allocate Unique IPv6 Prefix per Client in Large Broadcast Networks' to Informational RFC (draft-ietf-v6ops-dhcp-pd-per-device-08.txt)
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, draft-ietf-v6ops-dhcp-pd-per-device@ietf.org, rfc-editor@rfc-editor.org, tim@qacafe.com, v6ops-chairs@ietf.org, v6ops@ietf.org, warren@kumari.net
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <171225239385.23672.2001121976825999594@ietfa.amsl.com>
Date: Thu, 04 Apr 2024 10:39:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/l8XYYYP48y0XB5KMsOpKQr0TvFU>

The IESG has approved the following document:
- 'Using DHCPv6-PD to Allocate Unique IPv6 Prefix per Client in Large
   Broadcast Networks'
  (draft-ietf-v6ops-dhcp-pd-per-device-08.txt) as Informational RFC

This document is the product of the IPv6 Operations Working Group.

The IESG contact persons are Warren Kumari and Mahesh Jethanandani.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-v6ops-dhcp-pd-per-device/




Technical Summary

   This document discusses an IPv6 deployment scenario when individual
   clients connected to large broadcast networks (such as enterprise
   networks or public Wi-Fi networks) are allocated unique prefixes via
   DHCPv6 Prefix Delegation (DHCPv6-PD).

Working Group Summary

   This document had a large email discussion over its lifecycle, with
   some individuals expressing reservations. There was also a robust
   discussion after the working group chairs declared consensus. These
   are summarized in the Shepherd Writeup.

   While it is always nicer to have unanimous consensus on a document,
   I believe that the concerns raised were truly considered by the working group,
   that the working group made an informed decision, that the objections 
   are not enough of a technical problem to prevent moving forward, and
   that individuals raising concerns accept being in the rough. 
   


Document Quality

   The document is well written, and easy to understand.
   It documents and recommends a deployment model, 
   using existing technologies.

Personnel

   Timothy Winters is DS.
   Warren "Ace" Kumari is RAD!!!!

Document Action: 'Using DHCPv6-PD to Allocate Uni… The IESG