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

<inline>

Tom Petch

----- Original Message -----
From: "Italo Busi" <Italo.Busi@huawei.com>
To: <netmod@ietf.org>
Cc: <teas@ietf.org>
Sent: Monday, May 27, 2019 2:16 PM
Subject: [netmod] Key collision between configured and ephemeral list
entries

On Friday within the TEAS WG, we have discussed an issue which seems
generic and therefore agreed to ask for guidelines to the Netmod WG

In the TE YANG model we have defined a tunnel list with a name attribute
used as a key:

     |  +--rw tunnel* [name]
     |  |  +--ro operational-state?                  identityref
     |  |  +--rw name                                string

See: https://tools.ietf.org/html/draft-ietf-teas-yang-te-21

The issue we are facing is how to avoid name collision between
configured and ephemeral tunnels. In other words, the issue we are
trying to address is how to avoid the client to assign to a configured
tunnel a name which have been already assigned by the server to another
ephemeral tunnel and vice-versa, in particular considering NMDA rules

We believe that the issue is generic and apply to any configured and
ephemeral list entries

Has this issue been already discussed/resolved in Netmod WG?

If not, what is the Netmod WG opinion/suggestion? We are currently
considering the following option:

   Use a special character for ephemeral names - e.g. such names always
are prepended by special character "#"
   Make the special character changeable by configuration - the default
can be "#" and user can change if they desire..

<tp>

If this is to conform with YANG 1.1, RFC7950, then the constraint is

   Identifiers are used to identify different kinds of YANG items by
   name.  Each identifier starts with an uppercase or lowercase ASCII
   letter or an underscore character, followed by zero or more ASCII
   letters, digits, underscore characters, hyphens, and dots.

No # (hash) anywhere so I suspect that a lot of tooling will fail in an
unpredictable way if it encounters an illegal character in an
identifier.

Tom Petch

Thanks, Italo

Italo Busi
Principal Optical Transport Network Research Engineer
Huawei Technologies Co., Ltd.
Tel : +39 345 4721946
Email : italo.busi@huawei.com
[cid:image002.png@01D5149F.354EF420]

This e-mail and its attachments contain confidential information from
HUAWEI, which is intended only for the person or entity whose address is
listed above. Any use of the information contained herein in any way
(including, but not limited to, total or partial disclosure,
reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please
notify the sender by phone or email immediately and delete it!

From: Tarek Saad [mailto:tsaad.net@gmail.com]
Sent: venerdì 24 maggio 2019 23:13
To: Igor Bryskin <Igor.Bryskin@huawei.com>; Rakesh Gandhi
<rgandhi@cisco.com>; Xufeng <xufeng.liu.ietf@gmail.com>; Vishnu Pavan
Beeram <vbeeram@juniper.net>; Italo Busi <Italo.Busi@huawei.com>
Cc: teas@ietf.org
Subject: Discussion on modelling container TE tunnels in YANG

The team on "to" list met to discuss this subject topic. Notes from
today's discussion (please add if I missed):

Name collision between configured and ephemeral tunnels:
  This is a generic problem in NMDA.
  How to handle collisions between configured and ephemeral (or
auto-created) objects of a list, if the list uses the object (string
based) name as the key?
  Both configured and ephemeral can have the same object name but they
are different objects - how to avoid such collision.
 Proposed solution:
   Option 1:
   Use a special character for ephemeral names - e.g. such names always
are prepended by special character "#"
   Make the special character changeable by configuration - the default
can be "#" and user can change if they desire..
  Others?
AI (Italo): to send email to netmod group.

Container TE tunnels discussion:
-          Container tunnels are grouping of tunnels between same 2
endpoints to share incoming traffic towards the egress
-          Member tunnels of a container tunnel can be
auto-created/deleted on-demand and controlled by thresholds specified
under the container
-          Some attributes may apply on the container tunnel and
inherited down to member tunnels of the container
-          Q: Should model allow member tunnel to override inherited
attributes from container tunnel?
-          Q: Should all auto-created member tunnels of a container have
the same prefix/suffix - i..e prefix/suffix can be configurable

Regards,
Tarek

------------------------------------------------------------------------
--------

> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>