Re: [Roll] No path DAO treated as new

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

Hello Rahul :

The section is not about ignoring the DAO, it is about scheduling a DAO to parent. If the NP DAO does not cause the removal of the last route, then there is nothing to tell the parent, this node can still forward.

Your assertion that the route in B is removed in your scenario appears incorrect. Let’s look in details:

An (NP) DAO installs and remove adjacencies* between a parent and a child. A NP DAO can only clean the adjacency between that parent and that child. A NP DAO from C cannot clean the adjacency via D.

Let’s look at the adjacencies in each nodes along your scenario, see if I have it right:

At T=0 B has a route to Target below E via C (I expect from your description, you’re not 100% clear), and C has a route to Target via E.

At T=1 E sends a NP DAO to its old parent (that’s C), effectively invalidating the adjacency in C via E. C has no more route to Target. B does not know yet

At T=2 E sends a DAO to D, D now has a route to Target via E.

At T=3 D sends a DAO to B, B now has 2 adjacencies for Target, one via C and one via D. It can select either for his route to Target, or load balance. At this point, B may still use C, and that would be a bad idea since C cannot forward anymore to Target.

At T=4 C sends the NP DAO to B. B cleans the adjacency via C, but retains the one via D. So now it still has a route via B and no alternative to it. At this point, the routing is correct again.

I do not see that we ned to change RPL there…

*  Adjacencies are the possible next hops learnt from various routing protocols with various costs; this is what the routing protocols exchange; the routing table is a local decision by the router that retains the subset of adjacencies that it selects for forwarding.


Pascal

From: Roll [mailto:[e-mail]] On Behalf Of Rahul Jadhav
Sent: vendredi 3 février 2017 06:00
To: [e-mail]
Subject: [Roll] No path DAO treated as new

Hello All,

Section 9.2.2. of RFC6550 says that a No-Path DAO message should always be processed as a "new" message (i.e. igoring the PathSequence value related to the target) ...
I have problem with a scenario where if a node sends NPDAO (to old path) and DAO to the new path for the same target ... and if for some reason NPDAO reaches after the DAO to the common parent then it will clear the routes because NPDAO is alway processed as "new" message.
Consider an eg network,
    A
    |
    B
   / \
  /   \
 C     D
  :   /
   : /
    E
Node E switches from C to D, E sends an NPDAO to C, and regular DAO to D. If B receives NPDAO after DAO, then won't it result in incorrect invalidation of routes. My point is, the NPDAO processing should also have honored the PathSequence value before processing. But the spec text clearly and specifically talks about treating NPDAOs as "new".
Any thoughts on why special treatment for NPDAO was considered?

Thanks,
Rahul