Pascal Thubert (pthubert) <[email protected]> wrote: > As opposed to IEEE work that would have been pure RPL based L2R, my > 'natural' approach for an IETF work would be storing mode and Address > Family. Use IPv6 as signaling for all AFs and transport Short addresses > as one AF in DAO messages; that design opens to IPv4 and all sorts of > MAC layers.
I was thinking the same thing.
Just do it with a different AF, such that routing tables are now L2
objects.
> Note that the 6TiSCH backbone design is L2 in the backbone and routed
> at the IOT edge.
I would suggest that networks that want to move from mesh-under to route-over
and are already running IPv6, would be best to use RPL in the way 6tisch
uses it. Gather the topology with RPL, then establish 6tisch-like tracks
at L2.
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ 6lo mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lo
