Re: [Teas] [netmod] Key collision between configured and ephemeral list entries

Italo Busi <> Tue, 11 June 2019 16:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A479D120075; Tue, 11 Jun 2019 09:36:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6ZlBQVRgV1Le; Tue, 11 Jun 2019 09:36:24 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0BC8F120376; Tue, 11 Jun 2019 09:36:17 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id 4AE02994A7AD18363AF8; Tue, 11 Jun 2019 17:36:15 +0100 (IST)
Received: from ([]) by ([]) with mapi id 14.03.0415.000; Tue, 11 Jun 2019 17:36:09 +0100
From: Italo Busi <>
To: Juergen Schoenwaelder <>, Andy Bierman <>
CC: "" <>, Tarek Saad <>, "" <>
Thread-Topic: [netmod] [Teas] Key collision between configured and ephemeral list entries
Thread-Index: AQHVIGv3uNMq5vuvr0+PtfoTsE5mlKaWijaAgAAB7wCAABg74A==
Date: Tue, 11 Jun 2019 16:36:08 +0000
Message-ID: <91E3A1BD737FDF4FA14118387FF6766B2775D052@lhreml504-mbs>
References: <91E3A1BD737FDF4FA14118387FF6766B2774D314@lhreml504-mbs> <017f01d515f9$d0c662c0$> <91E3A1BD737FDF4FA14118387FF6766B2774DF6C@lhreml504-mbs> <062401d5160d$a568ea80$> <> <> <91E3A1BD737FDF4FA14118387FF6766B2774E51F@lhreml504-mbs> <028b01d51933$1015fa80$> <91E3A1BD737FDF4FA14118387FF6766B2775CF49@lhreml504-mbs> <> <>
In-Reply-To: <>
Accept-Language: it-IT, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [Teas] [netmod] Key collision between configured and ephemeral list entries
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 11 Jun 2019 16:36:27 -0000

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 ...


-----Original Message-----
From: Juergen Schoenwaelder [] 
Sent: martedì 11 giugno 2019 18:01
To: Andy Bierman <>
Cc: Italo Busi <>om>;; Tarek Saad <>om>;
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.


Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <>