Re: [dhcwg] Benjamin Kaduk's Discuss on draft-ietf-dhc-mac-assign-07: (with DISCUSS and COMMENT)

Benjamin Kaduk <kaduk@mit.edu> Mon, 08 June 2020 21:15 UTC

Return-Path: <kaduk@mit.edu>
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 D08373A00C0; Mon, 8 Jun 2020 14:15:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 wH72Jnm4aLZu; Mon, 8 Jun 2020 14:15:58 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A83F13A00B2; Mon, 8 Jun 2020 14:15:58 -0700 (PDT)
Received: from mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 058LFqC8004051 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 8 Jun 2020 17:15:54 -0400
Date: Mon, 08 Jun 2020 14:15:51 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: The IESG <iesg@ietf.org>, draft-ietf-dhc-mac-assign@ietf.org, dhc-chairs@ietf.org, ianfarrer@gmx.com, Tomek Mrugalski <tomasz.mrugalski@gmail.com>, dhcwg@ietf.org
Message-ID: <20200608211551.GA58497@mit.edu>
References: <159159050144.17160.2937263097536871303@ietfa.amsl.com> <20200608211431.GZ58497@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20200608211431.GZ58497@mit.edu>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/zWwZn6YwHfznw-dc2OtOEFoNkq4>
Subject: Re: [dhcwg] Benjamin Kaduk's Discuss on draft-ietf-dhc-mac-assign-07: (with DISCUSS and COMMENT)
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: Mon, 08 Jun 2020 21:16:00 -0000

On Mon, Jun 08, 2020 at 02:14:31PM -0700, Benjamin Kaduk wrote:
> On Sun, Jun 07, 2020 at 09:28:21PM -0700, Benjamin Kaduk via Datatracker wrote:
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> > 
> > I have a couple points that might require a bit of discussion, but I
> > expect to be pretty easy to resolve:
> > 
> > (1) Can we double-check this text in Section 10.1:
> > 
> >    The Identity Association for Link-Layer Addresses option (IA_LL
> >    option) is used to carry one or more IA_LL options, the parameters
> >    associated with the IA_LL, and the address blocks associated with the
> >    IA_LL.
> > 
> > I am pretty sure that the "is used to carry one or more IA_LL options"
> > should actually be talking about IA_LLADDR options.  But if I'm wrong,
> > and this is saying that IA_LL can carry IA_LL, we should have a lot more
> > discussion about this recursive structure and how to interpret it.
> 
> We may also want to check the "one or more" part, as Figure 3 of
> draft-ietf-dhc-slap-quadrant seems to show a workflow where IA_LL carries
> just QUAD and zero LLADDR.

... and I just got to the prose description thas says "MUST contain a
LLADDR option", oops.

Sorry for the noise.

-Ben