Juergen, Andy, Thanks for your reply
I agree with your statements as long as we consider two sources for the same information/instance. In this case, my understanding is that the same key value is intentionally assigned by the two sources to indicate that they are representing the same information/instance and only one instance needs to be applied within the operational DS The issue we are trying to solve is slightly different. We have two different instances from different sources and both of them need to be applied within the operational DS, but unfortunately they have got assigned the same key value ... Italo -----Original Message----- From: Juergen Schoenwaelder [mailto:[email protected]] Sent: martedì 11 giugno 2019 18:01 To: Andy Bierman <[email protected]> Cc: Italo Busi <[email protected]>; [email protected]; Tarek Saad <[email protected]>; [email protected] Subject: Re: [netmod] [Teas] Key collision between configured and ephemeral list entries On Tue, Jun 11, 2019 at 08:54:11AM -0700, Andy Bierman wrote: > There are no instance naming collisions within <running> or <ephemeral>. > Only if you try to combine them, which is not how it works. The server > chooses what to put in <operational> and sets the origin attribute > accordingly. And for a robust solution, it is good to have an explicit definition of which entry takes priority if there is a name clash. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <https://www.jacobs-university.de/> _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
