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

Sorry to chime in.
If my understanding is correct, I think in most cases the DS should be shared by multiple clients. In the first case, the <lock> operation should be used to prevent two clients from writing the content into the same datastore at the same time.

-Qin
-----邮件原件-----
发件人: Teas [mailto:teas-bounces@ietf.org] 代表 Italo Busi
发送时间: 2019年6月19日 1:24
收件人: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
抄送: netmod@ietf.org; Tarek Saad <tsaad.net@gmail.com>; Andy Bierman <andy@yumaworks.com>; teas@ietf.org
主题: Re: [Teas] [netmod] Key collision between configured and ephemeral list entries

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

_______________________________________________
Teas mailing list
Teas@ietf.org
https://www.ietf.org/mailman/listinfo/teas