[dhcwg] Benoit Claise's No Objection on draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05: (with COMMENT)

"Benoit Claise" <bclaise@cisco.com> Thu, 16 February 2017 10:16 UTC

Return-Path: <bclaise@cisco.com>
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 5E74C12940E; Thu, 16 Feb 2017 02:16:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "Benoit Claise" <bclaise@cisco.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148724019438.15925.5760161471481830737.idtracker@ietfa.amsl.com>
Date: Thu, 16 Feb 2017 02:16:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/kUKvOf_BOKj8Kg9GcoTax-QSW_U>
Cc: dhc-chairs@ietf.org, volz@cisco.com, dhcwg@ietf.org, draft-ietf-dhc-dhcpv6-prefix-length-hint-issue@ietf.org
Subject: [dhcwg] Benoit Claise's No Objection on draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05: (with COMMENT)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 16 Feb 2017 10:16:34 -0000

Benoit Claise has entered the following ballot position for
draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-prefix-length-hint-issue/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

>From the draft:
   [RFC3633] is unclear about how the client and server should act in
   different situations involving the prefix-length hint. 
>From the shepherd write-up
   This document specifies information that is useful to DHCPv6 client
   and server implementers to support allowing clients to specify a
   prefix length hint when requested delegated prefixes. It clarifies
   this concept introduced in RFC 3633.

=> that implies an UPDATE, no?
Obviously, this document publication should go forward (so not a
DISCUSS), but I would like to understand why this is not an update.

Editorial nit (by Sue Hares, part of her OPS DIR review):

Page 3 section 3.1 section under problem.  Second paragraph.  Second
sentence

The best way to assure a completely new delegated prefix is to send a new
IAID in the IA_PD.
IAID – abbreviation has not been indicated prior to this use
Old:/IAID/
New: /IAID (IA_PD unique identifier)/