- Separate the Prefix Information and Context Information into
separate
options. This clarifies what is a prefix and what is context.
- Use either the standard RFC4861 Prefix Information Option or an
optimized one to save overhead.
The 4861 PIO is about twice the size of the 6LoWPAN one, as 4861
always sends all 16 bytes of a prefix and then needs to add padding
(and a reserved field).
Combining 6LoWPAN-PIO and CID-IO into one option makes it unnecessary
to send all the global prefix(es) of the LoWPAN twice.
There is still enough space in the option to indicate whether the CID
number is valid or not (the A bit already tells us whether this is a
valid subnet prefix).
When we went CBHC, I heard some noises that the context info might get
somewhat large for distribution in RAs.
With this changes, yes, they will.
I still haven't heard a rationale for this change. If there is indeed
a need to clarify, do so in the text, not the encoding.
Gruesse, Carsten
_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan
