Re: [Teas] IANA managed modules for TE object types

mohamed.boucadair@orange.com Mon, 16 May 2022 05:01 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE540C2B6E60 for <teas@ietfa.amsl.com>; Sun, 15 May 2022 22:01:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0tgxsyJ5f4zx for <teas@ietfa.amsl.com>; Sun, 15 May 2022 22:01:09 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3315C2B3821 for <teas@ietf.org>; Sun, 15 May 2022 22:01:08 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar27.francetelecom.fr (ESMTP service) with ESMTPS id 4L1nC613pwz2xj3; Mon, 16 May 2022 07:01:06 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1652677266; bh=ri2QsCijovsQWLbTbMo7a03HFdNjR6yzphTaqBbq8gA=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=powGdnpUK1QGbIBYaYSRE+JxEsJ2sLIuuynbTeGBX33hclywh7roaLAVVmEtjPKde 6LCAbt+9jVw+CCK0nPaMWjXgdwDJqZf7xySkx/qVJA7M4XNXv9YHP8Kpvg7l4OX9qD Iq7PTBK98Y1er+mX+btBUqduDIcHh2vfh/HaBKmYn+1U10vxWWlhJZSqQ39tPkokzI 5GyaAeIr+TkCN6qeiDlRzD3ZbHnztvL9+BlfnhcadP8KYcgVODCX3m+0IgUBaT5bPa hvaPQhnOTEmQHhg/Oa9LX0xNXl9Y+ljxGkwRWnB+2EVe4LC+J+jiA//1LJnv6cD+th i9iOCxo9Az6kg==
From: mohamed.boucadair@orange.com
To: Tarek Saad <tsaad.net@gmail.com>, "teas@ietf.org" <teas@ietf.org>
CC: Adrian Farrel <adrian@olddog.co.uk>
Thread-Topic: IANA managed modules for TE object types
Thread-Index: AQHYZu00/CYCgIxnhE63/yTZYmtjDK0g9TuA
Content-Class:
Date: Mon, 16 May 2022 05:01:05 +0000
Message-ID: <1456_1652677266_6281DA92_1456_294_1_60256cb0479244db9cd010fb5268972e@orange.com>
References: <DS0PR19MB6501657ADCF336B0C1CB3957FCCA9@DS0PR19MB6501.namprd19.prod.outlook.com>
In-Reply-To: <DS0PR19MB6501657ADCF336B0C1CB3957FCCA9@DS0PR19MB6501.namprd19.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-05-16T04:58:16Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=10972f87-5422-4f8b-803a-5f96a9e7a3a1; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.27.51]
Content-Type: multipart/alternative; boundary="_000_60256cb0479244db9cd010fb5268972eorangecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/mL03khc-ueLLHaAZOQTnl_aeguE>
Subject: Re: [Teas] IANA managed modules for TE object types
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2022 05:01:12 -0000

Hi Tarek, all,

I fully agree with Adrian.

FWIW, we trying to have this be part of the YANG authors guidelines: see more details at:
https://datatracker.ietf.org/doc/draft-boucadair-netmod-iana-registries/

Cheers,
Med

De : Teas <teas-bounces@ietf.org> De la part de Tarek Saad
Envoyé : vendredi 13 mai 2022 19:59
À : teas@ietf.org
Cc : Adrian Farrel <adrian@olddog.co.uk>
Objet : [Teas] IANA managed modules for TE object types

Hi WG,

During the review of draft-ietf-teas-yang-te, Adrian raised an important point about IANA managing some YANG module that models specific TE types. For example, ID draft-ietf-teas-yang-te was modelling 'no-path' some error reasons as listed in https://www.iana.org/assignments/pcep/pcep.xhtml#no-path-vector-tlv or association types as defined in  https://www.iana.org/assignments/pcep/pcep.xhtml#association-type-field.

There are obvious advantages to having such YANG types in separate modules and letting IANA manage them. For example,

  1.  Other TE modules can freely import such types modules (without needing to import feature modules such as one defined in draft-ietf-teas-yang-te).
  2.  Allowing IANA to manage these modules may facilitate extensions in the future (IANA can automatically ensure that IANA types and YANG module are in sync).

The authors discussed this suggestion and would like to proceed with it, but want to make sure this is the recommended approach for other types that are managed by IANA and may be modelled in YANG in the future.

Regards,
Tarek (for the co-authors of draft-ietf-teas-yang-te)


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.