On Nov 26, 2008, at 09:26 , Pascal Thubert (pthubert) wrote:
What the context information is is out of scope. Actions in
response to unknown and/or invalid contexts are out of scope.
A couple of things:
We need to decide whether "the context" is singular or plural.
I.e., is the context the information shared in the lowpan or is the
information shared in the lowpan structured into multiple contexts.
Second, "What the context information is is out of scope" will only
work insofar as HC is not concerned.
HC needs 16 byte strings, indexed by a number from 0 to 15. This
clearly defines "What the context information is" to a certain extent.
I would prefer to state this as an interface to the context, as in:
This specification can make use of some form of context that is
shared between the node that compresses a packet and the node(s)
that need to decompress it. The specification enables a node to
obtain up to 16 values from this context, indexed by a number from 0
to 15, each containing a byte string of 0 to 16 bytes. How the
context is shared and maintained, including its representation, is
out of scope.
I don't know what the following is supposed to mean:
Actions in response to unknown and/or invalid contexts are out of
scope.
Gruesse, Carsten
_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan
