> For now, RFC4919 takes the stance that L2 routing ("mesh") is an
> integral part of the 6lowpan requirements.

First comment is that mesh is a networking protocol, not a data-link
protocol.  Thus, it cannot be an L2 "routing" requirement.

Since IP is at L3, I agree with Kris--mesh can either be L2.5 (which
is a bit weird IMHO), it can co-exist with IP (in an undefined way),
or it can be leveraged above IP similar to overlays.

-Joe

_______________________________________________
6lowpan mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/6lowpan

Reply via email to