Re: [Roll] Following up on seq Counter to protect the config option and others

[Abdussalam Baryun <[e-mail]>]

On Mon, Oct 14, 2019 at 6:57 PM Pascal Thubert (pthubert) <
[e-mail]> wrote:

> Dear all :
>
> *   At the interim today we refined the idea of a Sequence counter in a
> DIO that increments when there is a change in a global option.*
>

Ok, but I think the incrimination to be different per different
changes  (changes possibilities with different increment number, so any
change case can be identified and corrected)

* For the lack of an acronym that results in SEAL, I’m using the RPL
> Configuration State Sequence (RCSS) for now. This concerns options that are
> fully set by the root and propagated unchanged. Seems that this means at
> this time:        1.  The Route Information Option (RIO)    2.  The Prefix
> Information Option (PIO)    3.  The DODAG Configuration Option (DCO)    4.
> The Extended MOP Option (MOPex)    5.  The Global Capabilities Option (GCO)
> *
>

options can be more or less depending on the LLN

> *  Note that this also means that the capabilities have to be split
> between the parent capabilities (not protected) and the network-wide that
> are (item 5 above). The alternate is that the RCSS covers everything a
> parent advertises in which case it is not set by the root but by individual
> parents.   Or do we need 2 counters? *
>

one counter per parent.

AB