Re: [Roll] WGLC on draft-ietf-roll-turnon-rfc8138-04

[[e-mail]]

Hello Pascal, all,

I've read version –04 of draft-ietf-roll-turnon-rfc8138.
I've submit a Pull Request on GitHub with some nit fixes.
I have a few questions and comments:

  *   Regarding the title change to turnon-6LoRH: I understand that 8138 might get updated in the future. However, should the "T" bit mean that 6LoRH compression is in effect, irrespective of the version of this compression, or precisely that 8138 compression is in effect? If the former, what is the plan for managing the RPL nodes when successive versions of 6LoRH are introduced?
  *   Section 4, "delivering to a leaf that is not known to support RFC8138". Wouldn't a reference to the capabilities draft be appropriate here?
  *   Section 5: "A node that supports [RFC8138] but not this specification can only be used in a homogeneous network and an upgrade requires a "flag day" where all nodes are updated and then the network is rebooted with implicitly RFC 8138 compression turned on with the "T" flag set on." This sentence is too long. It could be broken in two after "flag day". "implicitely" seems strange, the RPL implementation would be hard-coded to use RFC8138 compression, very explicitly. "with the T flag set on" seems strange too, it seems to me the T flag would not be on if the nodes don't know this specification. Isn't it the whole purpose of the node configuration to explicitly override the "off" T bit? This paragraph need a little attention.
  *   Section 6, Table 1: it seems unfortunate that the second column is entitled "Capability Description". This name conflicts with the capabilities of the RPL nodes. This bit is a configuration option flag. By the way, RFC6550 20.14 does not say "Capability Description", but simply "Description". Why not stick with "Description" for this column in this table?

Notwithstanding these questions and comments, I personally support this work and wish to see it move forward.
Best regards,

Dominique

De : Roll <[e-mail]<mailto:[e-mail]>> on behalf of "Pascal Thubert (pthubert)" <pthubert=[e-mail]<mailto:pthubert=[e-mail]>>
Répondre à : "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Date : Tuesday 10 March 2020 14:50
À : "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Objet : Re: [Roll] WGLC on draft-ietf-roll-turnon-rfc8138-04

I agree with Rahul on both counts, taking the doc to the next step (as author) and changing the title (as participant).

…

Our milestone is to submit it this month and I intend to put a focus on this;

All the best, and for those who still plan to fly to IETF 107, sorry I will not be in Vancouver to meet you : (

Pascal

From: Roll <[e-mail]<mailto:[e-mail]>> On Behalf Of Rahul Jadhav
Sent: lundi 9 mars 2020 09:40
To: roll <[e-mail]<mailto:[e-mail]>>
Subject: Re: [Roll] WGLC on draft-ietf-roll-turnon-rfc8138-04

Hello All,

As someone who had previously reviewed the draft, I would like this work to be taken to the next logical step.

Also is it possible to rename the draft as "turnon-6LoRH" rather than "turnon-rfc8138"? Isn't it possible for RFC 8138 to be updated in the future? Similarly, the title may be "Configuration Option for 6LoRH" in place of "Configuration Option for 8138". Just a thought.

Best,
Rahul

________________________________
From: Roll <[e-mail]<mailto:[e-mail]>> on behalf of [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Sent: 06 March 2020 03:38 PM
To: roll <[e-mail]<mailto:[e-mail]>>
Cc: Ines Robles <[e-mail]<mailto:[e-mail]>>
Subject: Re: [Roll] WGLC on draft-ietf-roll-turnon-rfc8138-04

Working Group,

The WGLC for draft-ietf-roll-turnon-rfc8138-04 was due to expire yesterday.
No comment was received so far.
Before we equate silence with agreement, please take some time to reflect on this draft, maybe even review it and most importantly send your thoughts.
Simple responses like "yes", "I approve it" are valid, too.
As chairs, we need to gauge consensus. Please help us serving the community.
Best regards

Inès & Dominique

De : "mariainesrobles@googlemail..com<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Date : Thursday 20 February 2020 10:16
À : "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Cc : Dominique Barthel <[e-mail]<mailto:[e-mail]>>
Objet : WGLC on draft-ietf-roll-turnon-rfc8138-04

Dear all,

This is a Working Group Last call for draft-ietf-roll-turnon-rfc8138-04

Please send your comments by 5th March 2020

Thank you very much in advance,

Ines and Dominique.

_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.