In responding to Carsten, I wrote:
If you think strictly in layers, you have to reassemble the packet on
each L2/L3 boundary, and then re-fragment on each L3/L2 boundary.
However, the following optimization is obvious to anyone skilled in
the art of layer violation:
[... store routing data from the initial fragment for use
in forwarding subsequent ones ...]
The difficulty is that the various fragments may easily take
different paths through the mesh. Even if no route changes
occur, there may still be multiple paths. The current RPL
draft, for example, allows a router to maintain multiple
next hops for a given DAG root. A router that alternates
between two next hops for load balancing is going to be a
bit of a problem.
Please ignore all that. I am clearly not skilled in
the art of layer violation and will need to think
about this some more.
-Richard Kelsey
_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan
