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

[tom petch <[e-mail]>]

----- Original Message -----
From: "Juergen Schoenwaelder" <[e-mail]>
Sent: Tuesday, June 11, 2019 7:36 PM

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

Picking up on the point earlier about needing a rule about what to do
when a collision occurs, the collision only occurs when the second (or
third?) entry is created and AFAICT that is unpredictable, the
configuration may occur first or the ephemeral one.  If the rule is that
one or the other datastore takes precedence, then you have a name which
changes its meaning at this point, which seems undesirable.

Hence, the only rule I can see being acceptable is that the first one
wins, regardless of which it is,  and the second and subsequent are
rejected as invalid.

But then you cannot rely on the prefix telling you where the name came
from - of course, YANG origin will still be accurate.

Tom Petch

> /js
>
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   [phone]         <https://www.jacobs-university.de/>
>
> _______________________________________________
> netmod mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/netmod