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

[Benjamin Kaduk <[e-mail]>]

On Mon, Jun 08, 2020 at 09:19:57PM +0000, Bernie Volz (volz) wrote:
> I haven't had a chance to go through your extensive review -- thanks!
> 
> But the text here is supposed to be:
> 
>         The Identity Association for Link-Layer Addresses option (IA_LL
>         option) is used carry an IA_LL, the parameters
>         associated with the IA_LL, and the address blocks associated with the
>         IA_LL.
> 
> This was supposed to be modeled after RFC8415's text for the IA_NA, etc. That text is:

Ah, that makes sense, and does not seem to have either the recursive or
plural nature that seemed potentially problematic.
I'll look for a document update as the rest of the feedback gets
incorporated.

Thanks!

-Ben

>    The Identity Association for Non-temporary Addresses (IA_NA) option
>    is used to carry an IA_NA, the parameters associated with the IA_NA,
>    and the non-temporary addresses associated with the IA_NA.
> 
> I'm not sure when the "one or more" crept in. Thanks for finding it.
> 
> - Bernie
> 
> On 6/8/20, 5:14 PM, "Benjamin Kaduk" <[e-mail]> 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.
> 
>     -Ben
>