Hi Michael > > > OTOH, there is one (or more?) RPL instance that is used for 6TiSCH > > timing. I think all we need in 6top is an information of which RPL > > instance(s) is (are) used for timing and hten the admin can read the > > RPL info about that instance in the RPL data model. > There may be multiple instances, and one at least is used for ensuring a loopless structure for time sync. 6top exposes its rank in that instance in the beacons, so that's something we can expose in our data model as well since we understand its abstract semantics. But apart from that rank and the instance ID that is used for clock sync, all the RPL info should be coming from the RPL data model, else it is duplicated which looks like a bad idea as well as a layer violation.
Note that the clock sync instance is not necessarily the one used for reaching out to the PCE. It is not necessarily grounded. There can be scattered GPS-based time sources that form small dodags around them, and time is distributed independently of the DAGs used for IP traffic and PCE reachability. Cheers, Pascal > > > -- > Michael Richardson <[email protected]>, Sandelman Software Works -= > IPv6 IoT consulting =- > > _______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
