Re: [6lo] Proceeding with draft-ietf-6lo-multicast-registration

[Pascal Thubert <[e-mail]>]

Hello Eric:

done and published as -18.

guessing that you meant "the update-tag I-D definition of Amends and
Extends in this I-D"

all the best

Pascal


Le mar. 16 avr. 2024 à 08:03, Eric Vyncke (evyncke) <[e-mail]> a
écrit :

> As you know, I am the new shepherding Area Director for 6LO since March.
>
>
>
> As Erik Kline, the previous AD in copy, has already done the job until the
> IETF Last Call, I am fully trusting him about an AD review, therefore I
> won’t do my own ;-) Thanks Erik !
>
>
>
> Nevertheless, I spotted a couple of easy-to-fix issues/nits that would
> ease the way through the IESG ballot, which I will request today anyway.
> Here there are:
>
>
>
> - some fields are described as `6-bits unsigned integer`while it should be
> ‘6-bit unsigned integer’
>
> - IPv6 addresses should not be written in all uppercase (e.g., FF02::1)
> but in lowercase per RFC 5952
>
> - draft-kuehlewind-update-tag is expired and is no more active, it would
> be nicer to paraphrase the update-tag I-D definition of Amends and Updates
> in this I-D (you may want to keep the informative reference though) notably
> because the update-tag must be normative (i.e., blocking this I-D until the
> update-tag is published)
>
> - section 1, please fix ` in the a 6LoWPAN Router`
>
> - section 2.3 ` subsriptions` and ` that merges becomes`
>
> - section 12 ` subscribtion` ,  ` owernship.`, ` prevent an rogue`, `
> authorize in a advance`
>
>
>
> The issue around the update-tag draft is critical IMHO and should be
> quickly addressed.
>
>
>
> Regards,
>
>
>
> -éric
>
>
>
>

-- 
Pascal