[dhcwg] Benjamin Kaduk's No Objection on draft-ietf-dhc-mac-assign-08: (with COMMENT)

Benjamin Kaduk via Datatracker <noreply@ietf.org> Thu, 06 August 2020 06:31 UTC

Return-Path: <noreply@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 E46F03A0F1E; Wed, 5 Aug 2020 23:31:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-dhc-mac-assign@ietf.org, dhc-chairs@ietf.org, dhcwg@ietf.org, Tomek Mrugalski <tomasz.mrugalski@gmail.com>, Ian Farrer <ianfarrer@gmx.com>, ianfarrer@gmx.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.12.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <159669550146.18291.3896477762234142130@ietfa.amsl.com>
Date: Wed, 05 Aug 2020 23:31:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/XGB-pENch--0o8v3Kf0WJeUqQM8>
Subject: [dhcwg] Benjamin Kaduk's No Objection on draft-ietf-dhc-mac-assign-08: (with COMMENT)
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: Thu, 06 Aug 2020 06:31:42 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-dhc-mac-assign-08: 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-mac-assign/



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

Thank you for the updates addressing my discuss and comment points; I
just have a couple remaining suggestions.

Section 4.2

   Note that a client that operates as above that does not have a
   globally unique link-layer address on any of its interfaces MUST NOT
   use a link-layer based DUID (DHCP Unique Identifier).  For more

Is this MUST NOT scoped to the interface(s) in question?

Section 10.1

   The Identity Association for Link-Layer Addresses option (IA_LL
   option) is used to carry an IA_LL option, the parameters associated
   with the IA_LL, and the address blocks associated with the IA_LL.

If I'm reading RFC 8415 correctly, the typical construction would be
more like "Identity Associateion for Link-Layer Addresses (IA_LL)
option is used to carry an IA_LL, [...]".