Subject: [Roll] Need Clarification: Candidate neighbors

From: "Mathilde Durvy (mdurvy)" <[email-masked]>
Date: Wed, 28 Oct 2009 14:15:28 +0100

Hi JP,
 
I'm resending this email as I would like to clarify the concept of candidate neighbors (see original email below). Could you add it to your open tickets? 
Candidate neighbors are "neighbors that are discovered by the ND mechanism and further qualified as statistically stable". Hence my opinion is that we can reuse the ND neighbor cache with maybe an additional flag (characterising the stability) to maintain candidate neighbors. I don't think we necessarily need a separate data structure, is my understanding correct?
 
Best,
Mathilde
________________________________

From: [email-masked] [mailto:[email-masked]] On Behalf Of Mathilde Durvy (mdurvy)
Sent: jeudi, 15. octobre 2009 13:22
To: [email-masked]
Subject: [Roll] Candidate neighbors

Hi All,
 
I'm trying to understand better the need for 'candidate neighbors'.
My current understanding is that 'candidate parents' (RPL) are a subset of 'candidate neighbors' (RPL) which are themselves a subset of 'neighbors' (ND).
My question is, do we really need to maintain 'candidate neighbors' in addition to 'neighbors' and 'candidate parents'?
If yes what should be the data structure and corresponding fields for 'candidate neighbors'? Section 5.2.1 gives very little details...
I have a feeling that 'candidate neighbors' could simply be the set of REACHABLE 'neighbors' and be associated with a DAG once they become candidate parents.
 
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