Hi Jonathan,
thanks for the comments.
On Jul 08 2008, at 04:12, Jonathan Hui wrote:
it explicitly separates the context ID space from the address
compression mode. In my mind, the compression prefix and address
compression mode are orthogonal concepts. A single context ID can be
used to support different address compression modes. For example, a
single /64 prefix could be used along with 64-bit, 16-bit, or 0-bit
compressed addresses.
Do you have an example how that would work in practice?
I tried to separate out the contexts for the different prefix lengths
because I couldn't quite imagine a useful case where you would use the
same prefix bits at different lengths.
The separation allows a larger number of contexts to be available
(while spending the same small number of per-packet bits), which helps
with transitions between different context settings.
If I correctly read your diagram, you would only have four contexts;
given that half of them might be tied up in a transition, this would
leave about two, one for the prefix of the local link and one for
exactly one potential correspondent.
Gruesse, Carsten
_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan
