[Roll] turnon-8138 review

[Rahul Arvind Jadhav <[e-mail]>]

Hello Authors,

Following is my review of draft-thubert-roll-turnon-rfc8138-02:

Section 5.4. "Rolling Back", says, the administrator SHOULD make sure that all nodes have converged to the "T" flag reset before allowing nodes that do not support the compression in the network.
[RJ] How would a root know that all the nodes have accepted the T-reset? Doesn't this require use of capability flag ? Also I'm not sure if the same capability flag used before can be used here?

Section 5.3. "Double Instance Scenario", says that nodes that do not support 8138 would either not be configured for the new instance, or would be configured to join it as leaves only.
[RJ] Thus I believe there is some non-RPL management involved to tell the legacy nodes to not join the Instance-with-T-flag.

Section 5.2. "Single Instance Scenario", The root encapsulates packets to the leaves all the way to the parent, which decapsulates and distribute the uncompresses inner packet to the leaf.
[RJ] When it says encapsulate/decapsulate, it means IP-in-IP encapsulation/decapsulation, right?

Section 4. "Updating RFC 8138"
[RJ] I didn't find any updates to 8138! I believe the text in the section does not result in 8138 update.

Regards,
Rahul