Subject: [Roll] FW: Clarification on parent / destination prefix / route removal

From: "Mathilde Durvy (mdurvy)" <[email-masked]>
Date: Thu, 12 Nov 2009 13:55:10 +0100

Hi JP,
 
Are you already tracking this issue? I would appreciate some clarification on how lifetimes are used / or not used...
Best,
Mathilde

________________________________

From: [email-masked] [mailto:[email-masked]] On Behalf Of Mathilde Durvy (mdurvy)
Sent: mardi, 3. novembre 2009 11:48
To: roll
Subject: [Roll] Clarification on parent / destination prefix / route removal

Hi All,
 
This is my current understanding:
 
- Parents are removed based on OF selection (decision to move within the DAG, change DAG, etc)
- Destination prefixes are removed after the retry / RemoveTimer procedure described in section 5.10.1.1.1. This is essentially a keep alive mechanism based on DIO (D bit set) - DAO exchanges.
- Route corresponding to destination prefixes are removed when DAO lifetime expires? Are they also removed when the corresponding destination prefix is removed? 
- When are routes corresponding to parents removed? Do they also have a lifetime?
- What happens when a neighbor disappears, are the corresponding parents/destination/routes removed?
 
The current behavior seems quite asymmetric... There is some kind of keep alive mechanism for destination prefixes, but not for parents. There is a lifetime associated with routes corresponding to destination prefixes but not for routes corresponding to parents. Is that a design choice? I would appreciate some clarifications.
 
Best,
Mathilde

Durvy Mathilde
Software Engineer
Technology center

[email-masked]
Phone: +41 21 822 1725
Mobile: +41 76 396 8116

Cisco Systems International Sàrl
Av. des Uttins, 5
CH-1180 Rolle

Cisco home page <http://www.cisco.com/> 

 Think before you print.	
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.	

_______________________________________________
Roll mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/roll