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

Tarek Saad <tsaad.net@gmail.com> Thu, 19 May 2022 19:08 UTC

Return-Path: <tsaad.net@gmail.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 8A13BC20D6A9; Thu, 19 May 2022 12:08:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 rKNJdFBPsGv2; Thu, 19 May 2022 12:08:44 -0700 (PDT)
Received: from mail-il1-x12c.google.com (mail-il1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 AF991C20D6A8; Thu, 19 May 2022 12:08:44 -0700 (PDT)
Received: by mail-il1-x12c.google.com with SMTP id s12so4265808iln.11; Thu, 19 May 2022 12:08:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :mime-version; bh=UBiAGznsimW3Al2yW7gsW1EERZv5PwaHCFZx0brmUf4=; b=XD2rm3qVszyidtyAAld+WInfaGJ36EukFO/6dfDgZTHjbz31SHso7NHYOTiJ1R1DFK ykB6MevUpn1Pco0w5ogbzqm8ODtWBMJbjw6OcxVc0wgWL5tM7eLAdbZNAfGCUk2qaSgJ HLdHYsl9oXyKxyWdgY6Hg3xylnYHcGSrlYUtSQQAZvEOEVBbgN06oTx7gYgn8HzvsdnS ioAu6jKzjxfxpCl5r075mcdnL4HK4JBQtkh1p17p0HGq3IY5SUkQp0Mussc60b1ouDu0 reba3ers7zX2H0ub4ex5c/EmbB2L3Bfjg373usg54Agl9YrIuhPwOGndUH7dEyVUsD8S sDBA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:mime-version; bh=UBiAGznsimW3Al2yW7gsW1EERZv5PwaHCFZx0brmUf4=; b=FHsXSBMgY0wAWWZuBiipSmelXI/UXeQVasTeeKGaay/SQyZyU1AJgUpYBhZ+SdbeOh jRUXe74HG+6Rx+h3aFCleQB6aLb6RJLFRY2hBjYJytXMPTzZD04/uLtk+63nKEGgH2cb WfGsRHksD9MJ4UnOXR2M7eXurg3UAlPHP8JSQWibISYTYdtCghJyn/j8DkAX5fcXi843 zMehxIOGs/Ib4CPNK3we/Ryc+fH7wQqzOguhTrKyHDCGAXWprQnE7bg4E4Hgyf+0N9rB fGRMcDJEgEnbjbpWj3U8ROH/P3MCbvg2xojhSyyA/+fGxAjFlD2rMRabHc1ah0gdOdFQ UKww==
X-Gm-Message-State: AOAM530PJn3aa+mYbWt+Yovduiue1A9PGmg9hByl2y/VJY0sUG/leoZ/ +CyRy5vxz46MA+yvz/4CoT28RJgvRrw=
X-Google-Smtp-Source: ABdhPJwXRibwhkY0QkkqmaliVWsJcApe/eIJQFC83bb9BkWeNqQrRWZag46REQTxpiutR8Aq9srycQ==
X-Received: by 2002:a05:6e02:194e:b0:2cf:9d32:fefc with SMTP id x14-20020a056e02194e00b002cf9d32fefcmr3737517ilu.217.1652987322943; Thu, 19 May 2022 12:08:42 -0700 (PDT)
Received: from DS0PR19MB6501.namprd19.prod.outlook.com ([40.99.160.253]) by smtp.gmail.com with ESMTPSA id x1-20020a920601000000b002cde6e352e1sm1459165ilg.43.2022.05.19.12.08.41 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 May 2022 12:08:42 -0700 (PDT)
From: Tarek Saad <tsaad.net@gmail.com>
To: "teas@ietf.org" <teas@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
CC: Adrian Farrel <adrian@olddog.co.uk>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, tom petch <ietfa@btconnect.com>
Thread-Topic: IANA managed modules for TE object types
Thread-Index: AQHYZu00/CYCgIxnhE63/yTZYmtjDK0mmI2M
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Thu, 19 May 2022 19:08:37 +0000
Message-ID: <DS0PR19MB6501EC15B411FF2A87233BBDFCD09@DS0PR19MB6501.namprd19.prod.outlook.com>
References: <DS0PR19MB6501657ADCF336B0C1CB3957FCCA9@DS0PR19MB6501.namprd19.prod.outlook.com>
In-Reply-To: <DS0PR19MB6501657ADCF336B0C1CB3957FCCA9@DS0PR19MB6501.namprd19.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-CA
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator:
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: multipart/alternative; boundary="_000_DS0PR19MB6501EC15B411FF2A87233BBDFCD09DS0PR19MB6501namp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/u052O1n82HkQR24dJg5LJKxoY-0>
Subject: Re: [netmod] IANA managed modules for TE object types
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.34
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: Thu, 19 May 2022 19:08:48 -0000

+ netmod WG, and YANG Drs.
Widening scope to gather more opinions.

So far, we have some opinions that are proto adding such IANA managed modules.
However, thers have raised concerns at transferring full ownership/control to IANA --  especially when mapping from IANA Identifiers to string based YANG identityref is required.
We are also aware of a proposal in netmod in draft-boucadair-netmod-iana-registries – we are wondering if we have further input that will help YANG document authors moving forward.

Regards,
Tarek

From: Tarek Saad <tsaad.net@gmail.com>
Date: Friday, May 13, 2022 at 1:59 PM
To: teas@ietf.org <teas@ietf.org>
Cc: Adrian Farrel <adrian@olddog.co.uk>
Subject: 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)