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

Italo Busi <Italo.Busi@huawei.com> Tue, 18 June 2019 17:24 UTC

Return-Path: <Italo.Busi@huawei.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE06A120091; Tue, 18 Jun 2019 10:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rKZe2zNGv81h; Tue, 18 Jun 2019 10:24:13 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9011C12006E; Tue, 18 Jun 2019 10:24:13 -0700 (PDT)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 7CC09FE25A2207D21960; Tue, 18 Jun 2019 18:24:11 +0100 (IST)
Received: from LHREML504-MBS.china.huawei.com ([10.201.109.59]) by lhreml701-cah.china.huawei.com ([10.201.108.42]) with mapi id 14.03.0415.000; Tue, 18 Jun 2019 18:24:03 +0100
From: Italo Busi <Italo.Busi@huawei.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
CC: Andy Bierman <andy@yumaworks.com>, "teas@ietf.org" <teas@ietf.org>, "Tarek Saad" <tsaad.net@gmail.com>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] [Teas] Key collision between configured and ephemeral list entries
Thread-Index: AQHVIGv3uNMq5vuvr0+PtfoTsE5mlKaWijaAgAAB7wCAABg74P///YkAgAASdtCAAAMxAIAK8ZbA
Date: Tue, 18 Jun 2019 17:24:02 +0000
Message-ID: <91E3A1BD737FDF4FA14118387FF6766B27769528@lhreml504-mbs>
References: <BYAPR11MB26314CD2365C6AEC39E696EDB51F0@BYAPR11MB2631.namprd11.prod.outlook.com> <BL0PR06MB4321DA01042ECAAD88E8420AFC1F0@BL0PR06MB4321.namprd06.prod.outlook.com> <91E3A1BD737FDF4FA14118387FF6766B2774E51F@lhreml504-mbs> <028b01d51933$1015fa80$4001a8c0@gateway.2wire.net> <91E3A1BD737FDF4FA14118387FF6766B2775CF49@lhreml504-mbs> <CABCOCHTFSfizdqszABgyv+SBHW2+5W5WF-HJvVo=EAJFcUnvJA@mail.gmail.com> <20190611160106.5o3pslwmnhaoyjzx@anna.jacobs.jacobs-university.de> <91E3A1BD737FDF4FA14118387FF6766B2775D052@lhreml504-mbs> <20190611171900.xzzwofx5nwtj77cv@anna.jacobs.jacobs-university.de> <91E3A1BD737FDF4FA14118387FF6766B2775D16D@lhreml504-mbs> <20190611183630.4ymx7libdotuqfbo@anna.jacobs.jacobs-university.de>
In-Reply-To: <20190611183630.4ymx7libdotuqfbo@anna.jacobs.jacobs-university.de>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.203.246.126]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/jYRJlYCak1DQCO_xU3CxaM5CpGo>
Subject: Re: [netmod] [Teas] Key collision between configured and ephemeral list entries
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2019 17:24:16 -0000

Hi Juergen,

What is the DS architecture you have in mind with multiple client creating entries?

Are the two clients creating entries in the same <running> DS or in two different <running> DS?

In the latter case, the two clients could also rely on different <operational> DS and therefore can assign the same name to different entries (since they will be instantiated in different DS). There is no need for them to avoid name clash

In the former case, a name clash would cause one client to override the configuration of another client

Are the two clients aware of each other?

I take the opportunity to clarify one point (not sure I have been clear about it). I do not think we need to define any rule which is enforced by the server to avoid name clashes since the server cannot understand whether the name clash is intentional or not. I think we just need to define some known/common/standard rules that allow the client(s) to avoid creating unintended name clashes.

Thanks, Italo

-----Original Message-----
From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de] 
Sent: martedì 11 giugno 2019 20:37
To: Italo Busi <Italo.Busi@huawei.com>;
Cc: Andy Bierman <andy@yumaworks.com>;; teas@ietf.org; Tarek Saad <tsaad.net@gmail.com>;; netmod@ietf.org
Subject: Re: [netmod] [Teas] Key collision between configured and ephemeral list entries

On Tue, Jun 11, 2019 at 05:43:27PM +0000, Italo Busi wrote:

> [Italo Busi] If the client knows the prefix used by the server, it can 
> pick up a different prefix and use it to tag its own entries. I think 
> this rule is not really complex and it seems much simpler than 
> managing unintended name clashes

A prefix only helps a little. Once you have multiple clients creating entries, you will have to handle collisions again. Sometimes solving the more general case leads to solutions that also work nicely in simpler special cases.
	
/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/>