Pascal Thubert (pthubert) <[email protected]> wrote: mcr> I would suggest that networks that want to move from mesh-under to mcr> route-over and are already running IPv6, would be best to use RPL in mcr> the way 6tisch uses it. Gather the topology with RPL, then mcr> establish 6tisch-like tracks at L2.
> [Pascal] In a green field, yes; maybe leveraging DAO projection,
> too. But then if the goal is to use an existing forwarding plane,
> certainly that's not the same story.
yeah, I'm not entirely sure I know what the existing situation is.
My impression is that the idea is to have a network that is a hybrid of both
mechanisms, because the network is being incrementally evolved.
As such I can see perhaps making L3 adjacencies (parent/child) over multi-hop
L2 mechanisms, but in some cases, also recognizing that there are L3 aware
nodes in between.
If the nodes capabilities are high (and software upgrades or incremental
replacement is possible), but the network bandwidth is such that running two
networks (on different PANIDs or something) is impossible, then this might
work.
I asked Benjamin for more details privately, and I think that we'll get some
more details soon.
--
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
