That is exactly right, Qin. Cheers,
Pascal From: Qin Wang [mailto:[email protected]] Sent: mercredi 10 juin 2015 12:19 To: Pascal Thubert (pthubert); Michael Richardson; [email protected] Subject: Re: [6tisch] 6top and neighbour list Hi Pascal, What you say is that the RPL parents list should be in RPL data model (YANG model), and 6top data model only includes the parent used as time source. Right? It really makes sense to me. Thanks Qin On Thursday, June 11, 2015 12:45 AM, Pascal Thubert (pthubert) <[email protected]<mailto:[email protected]>> wrote: Hello Qin: A node has a list of RPL parents per RPL instance. But that’s a RPL problem and we probably need a RPL data model to be done at ROLL. 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. Does that make sense? Pascal From: 6tisch [mailto:[email protected]] On Behalf Of Qin Wang Sent: mardi 9 juin 2015 13:58 To: Michael Richardson; [email protected]<mailto:[email protected]> Subject: Re: [6tisch] 6top and neighbour list Hi Michael, NeighborList contains the Link information, and the information about Parent is contained in TimeSource for saving space. Make sense? Thanks Qin On Wednesday, June 10, 2015 1:33 AM, Michael Richardson <[email protected]<mailto:[email protected]>> wrote: 1) I was reading draft-ietf-6tisch-6top-interface-03. 2) It seems that we have yet to adopt draft-wang-6tisch-6top-sublayer-01, it has expired, but draft-ietf-6tisch-6top-interface-03 still references that document. I was looking for the description of the neighbour list that the PCE would need to know in order to construct the desired tracks. (The indenting of the YANG model is very inconsistent; I could pull the XML off of bitbucket, and run it through an indenter if the authors wished) I think that the information that I want about neighbours is: list NeighborList { ... }. I think that if we have received an RPL DIO from that neighbour that we ought to show it's rank in that Neighborlist. I think that we ought to also indicate if that neighbour is *the* parent, and or if it is potential parent. We might want to go further and say WHY the indicated parent was actually chosen: but I think that this might be difficult to code in a vendor independant way. I propose that we still do this, but allow the code to be vendor dependant. -- Michael Richardson <[email protected]<mailto:[email protected]>>, Sandelman Software Works -= IPv6 IoT consulting =- _______________________________________________ 6tisch mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/6tisch
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
