Re: [Roll] Benjamin Kaduk's Discuss on draft-ietf-roll-turnon-rfc8138-14: (with DISCUSS and COMMENT)

[Alvaro Retana <[e-mail]>]

On September 24, 2020 at 8:13:09 AM, Pascal Thubert wrote:


Pascal:

Hi!

> Following the meeting last Monday and subsequent the update of useofrplinfo
> by Michael (thanks Michael!) I published a new version of the turnon RFC
> 8138 draft.
>
> The major changes are
> - removed the formal update to RFC 6550
> - refer to useofrplinfo as the justification why the flag is not defined for
> MOP 7
> - defined the operation in MOP 7 as compression on iff the Link uses 6LoPWAN
> HC.

Thanks for these changes.

Because we have to cycle useofrplinfo back through (when the WG is
done with it), I asked Ben/Martin to wait for that before coming back
to this document.  It'll make it easier than tracking multiple
changes. :-)


OTOH, I do have comments on the recent change:

OLD>
   Section 4.3 of [USEofRPLinfo] updates [RFC6550] to indicate that the
   definition of the Flags applies to Mode of Operation (MOP) values
   zero (0) to six (6) only, leaving the flags reserved for MOP value
   seven (7).  For a MOP value of 7, the bit in position 2 is considered
   unallocated and [RFC8138] MUST be used on Links where 6LoWPAN Header
   Compression [RFC6282] applies and MUST NOT be used otherwise.

NEW>

   Section 4.3 of [USEofRPLinfo] updates [RFC6550] to indicate that the
   definition of the Flags applies to Mode of Operation (MOP) values zero (0)
   to six (6) only.  For a MOP value of 7, [RFC8138] MUST be used on Links
   where 6LoWPAN Header Compression [RFC6282] applies and MUST NOT be used
   otherwise.


Thanks!

Alvaro.