Re: [Iot-directorate] Iotdir last call review of draft-ietf-roll-turnon-rfc8138-09

[Alvaro Retana <[e-mail]>]

Pascal:

Hi!

The MOP currently has a value up to 7…let’s avoid more questions/confusion;
please take the "(and above when extended)” part out.

Thanks!

Alvaro.

On August 5, 2020 at 7:35:07 AM, Pascal Thubert (pthubert) (
[e-mail]) wrote:


> - Section 3: “A MOP value of 7 and above”. If the MOP is a 3-bit field,
the

> highest MOP value is 7 (assuming that the lowest value is 0). Why state
here

> "and above"? Are there plans to extend the MOP field size?



Yes, there is. See https://tools.ietf.org/html/draft-ietf-roll-mopex-01.
This is why. Yet what you are saying makes sense, as written it cannot go
beyond 7. I can change to "(and above when extended)"





> - Section 3, after “A MOP value of 7 and above”. s/MUST use

> compression/indicates that compression MUST be used



The following text

"

   Section 6.3.1 of [RFC6550] defines a 3-bit Mode of Operation (MOP)

   in the DIO Base Object.  For MOP values 0 to 6, the use of compression is

   as specified in this document.  A MOP value of 7 MUST use compression by

   default and ignore the setting of the “T” flag.



"

was suggested by Alvaro during his A-D review. But I believe that your
proposal does not alter the meaning so I'm picking it.



Resulting sentence:

"

   Section 6.3.1 of [RFC6550] defines a 3-bit Mode of Operation (MOP) in

   the DIO Base Object.  This specification applies to MOP values 0 to

   6.  For a MOP value of 7 (and above when extended), the compression

   MUST be used by default regardless of the setting of the "T" flag."





> - Section 4, 1st paragraph: “if and only if the "T" flag is set.” Should
we

> perhaps append “or if the MOP value is 7.”  ?



With the change above, I believe that we are good.