[Roll] Eliding-Info: Abbreviated Option and RCSS of an Option

[Rahul Jadhav <[e-mail]>]

Hello All, Pascal,

Based on my understanding currently, the draft serves three purposes:
1. Helps elide common DIO options which rarely change
2. Helps elide common DAO options during route refresh cycles
3. Allow sync for individual protected options by assigning RCSS to an option (this implies the use of new AOO)

Points 1 and 2 are quite clear and easy to follow.

The whole complexity of the proposal lies in point 3 and from what I understand I believe the utility is not convincing enough for the amount of complexity it introduces.

My understanding is that with AOO, it is possible that a Root assigns a different RCSS to individual protected options such that the downstream nodes can individually query and synchronize with any of that option on change.

My rationale is that PIO/RIO/DODAG Configuration/MOPex/GCO options rarely change. IMO, if either of it changes then it is no big deal to advertise all the options. Rather than managing versions for each of these options, the RCSS can only be a common counter for all the options.

I understand that RCSS of an option is "an extension" and it is possible to only use common RCSS. But I believe the whole RCSS of an option as an extension is adding to the complexity of the draft (introducing more scenarios to handle), and also making it difficult for the reader.

Best,
Rahul