Re: [Roll] P-DAO request

["Pascal Thubert (pthubert)" <[e-mail]>]

Hello Randy

Not sure what you mean by "Your previous track is stale, here's the new version". As it goes, the Root can redraw the Track, add segments here,  remove others there, it's still the same track as long as it is functional, and there's no provision in the draft to tell the ingress about those changes.

If that does not help, could you please rephrase?

Pascal

From: Roll <[e-mail]> On Behalf Of Turner, Randy
Sent: mardi 8 juin 2021 19:54
To: Routing Over Low power and Lossy networks <[e-mail]>
Subject: [Roll] P-DAO request

Hi Guys,

In the -17 draft for P-DAO, section 3.3, a portion of this section says:

A positive PDR-ACK indicates that the Track was built and that the Roots commits to maintain the Track for the negotiated lifetime. In the case of a complex Track, each Segment is maintained independently and asynchronously by the Root, with its own lifetime that may be shorter, the same, or longer than that of the Track. The Root may use an asynchronous PDR-ACK with an negative status to indicate that the Track was terminated before its time.


I think it will be very difficult for the root to maintain tracks, given the spurious nature of topology changes in an RF mesh --- Rather than a PDR-ACK that says the track could not be maintained, could we have something like an async notification that says, "Your previous track is stale, here's the new version"  as long as the egress point still exists.  Assuming it's possible that the egress joined another DODAG.

I haven't read the entire draft yet so I may have missed something that would preclude this capability.

Thanks,
Randy