Hi Carsten: RPL recognizes a movement when a DAO information has a stale DAOSequence. The DAOSequence is an information that the owner of the advertised target increments. If we define an interaction whereby we redistribute ND-15 into RPL, then (probably) the RPL router will inject a host route on behalf of the host. When the RPL router injects such a route and then maintains that route, it still has has to provide an idea of the freshness of the information that it is injecting in a DAOSequence. When the host moves to an alternate router, it would have to provide something so that the new router sets an updated DAOSequence that the routing update percolates up the DODAG. IOW, without a TID, a host cannot efficiently move from a router to the next.
People can find more on TID interactions with RPL and ND in http://tools.ietf.org/html/draft-thubert-6lowpan-backbone-router-02 . I'll see what I do with that draft; probably propose it to ROLL. Pascal http://www.xtranormal.com/watch/7011357/ > -----Original Message----- > From: Carsten Bormann [mailto:[email protected]] > Sent: Tuesday, March 29, 2011 7:20 PM > To: Pascal Thubert (pthubert) > Cc: Erik Nordmark; Mukul Goyal; 6lowpan > Subject: Re: [6lowpan] "Advertize on Behalf" flag in ARO > > On Mar 29, 2011, at 18:25, Pascal Thubert (pthubert) wrote: > > > But then, RPL, like the backbone router draft operation, needs the TID > > Can you explain why RPL needs a sequence number here? > > Gruesse, Carsten _______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
