I still have a concern about the ordering of the fragmentation and
mesh delivery headers. Can anyone offer a good argument on why
fragmentation is within mesh and not vice versa?
I think the general rule is that a node should only have to parse the
subheaders that it is concerned with.
I'm assuming a mesh forwarder does not reassemble (I don't happen to
know any good reason why it should).
So a mesh forwarder is concerned with the forwarding header only;
these therefore should come first.
Only at the L2 destination is it necessary to peek further into the
header, e.g. the fragmentation header for reassembly.
Compare this with IPv6: The forwarding header (here the IP header) is
in front of the fragmentation header, which is a destination header
(only "opened" at the destination address set in the IP header).
[WG chair hat on:]
It is exactly this kind of issue that I like to see discussed at WGLC
-- so please keep up sending in the questions!
Gruesse, Carsten
_______________________________________________
6lowpan mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/6lowpan
