IETF Logo Mail Archive

[Teas] IANA managed modules for TE object types

Tarek Saad <tsaad.net@gmail.com> Fri, 13 May 2022 17:59 UTC

Return-Path: <tsaad.net@gmail.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 A8613C15EB3D for <teas@ietfa.amsl.com>; Fri, 13 May 2022 10:59:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 j0_Vizn56miA for <teas@ietfa.amsl.com>; Fri, 13 May 2022 10:59:17 -0700 (PDT)
Received: from mail-il1-x12b.google.com (mail-il1-x12b.google.com [IPv6:2607:f8b0:4864:20::12b]) (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 E0A4EC15E3EA for <teas@ietf.org>; Fri, 13 May 2022 10:59:17 -0700 (PDT)
Received: by mail-il1-x12b.google.com with SMTP id j12so6178123ila.12 for <teas@ietf.org>; Fri, 13 May 2022 10:59:17 -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 :accept-language:content-language:mime-version; bh=OEKJXSCdPrVPUT7fGI6C90jnS9Y65qnNMIflbXs5azw=; b=puU7U3bXYKvX8RegL+GjJKpMm/768P0aKWscLY4bsryMn9RwocAeTyzFmRBd6vhph7 d4IpfbybiV6gob9yz2Mts0LciFLxzP8lNUHZo9NPjInj7fmmWW2OqONIVQM+ShLcFrTk 17GbZ1uFJvDupAbOlZ6gIJ603h8D9iRlbbDZcQYKNbsNENTRP+28hT7FhMsjCJP3Wn6f 4tCmdBbwbgPfCOlLf1XQIFEFi1a0EiCEH303TU+S/AKk5Y2hYSu6HH9oYxQ2WCWM6w4s wsg4KyWjZT0NqCeK4bpbXheaGmIBnp75Qv3EFrO0t7NEGaJbqXZcPBIx/xCp+8Jd6DFe wDRg==
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:accept-language:content-language:mime-version; bh=OEKJXSCdPrVPUT7fGI6C90jnS9Y65qnNMIflbXs5azw=; b=N6JpLojlyIpnPoYLDkHJO6vAvtizUdolDiALhwq1yWpLVrS8HXg98e4iT131z/Uv44 iV8LtNoeLTCpMiPycC/EnbgRr6Y85CYimviEmQDqeTjspV7ZJGdl6pMAgayRwWaf6BQD KSjNUiB7N/stMUHfiUIAiWl7zEdT/3yO+8ga3XXatGZdfoOUj+q5dNl6IwTYjhPMZhKe Uaewcr1HdUhdb5jIw8iZcFZEcBDjkYP43+xxvFH8PTwo7JnfWKuQHLc0IIJt6xFL/hdv Mirl0fqXpnRs9aGII5Zgbe5PyNJx8qVbjGcW49ey8FH4G7jAoM945+pwGcfLtsGSQOtk xsIg==
X-Gm-Message-State: AOAM530/u3JBa0T60yojRkOH9a7fTGc9/vxgcAl++LIhRaf/w5kwKYNX 0/w/z6NB5GUQXolhG5mCtLxLH1r1/zw=
X-Google-Smtp-Source: ABdhPJyaS/fOemXK9o/UTpIDaYL6JS6sVMnw8V1lLtFN9bn5Ohk/wrGGwjscwf4MYviBm9pl6jxs4g==
X-Received: by 2002:a05:6e02:1c27:b0:2cf:6de9:5342 with SMTP id m7-20020a056e021c2700b002cf6de95342mr3174197ilh.176.1652464756350; Fri, 13 May 2022 10:59:16 -0700 (PDT)
Received: from DS0PR19MB6501.namprd19.prod.outlook.com ([40.99.160.253]) by smtp.gmail.com with ESMTPSA id m9-20020a0566380ac900b0032b3a78177csm844227jab.64.2022.05.13.10.59.14 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 May 2022 10:59:15 -0700 (PDT)
From: Tarek Saad <tsaad.net@gmail.com>
To: "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/yTZYmtjDA==
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Fri, 13 May 2022 17:59:13 +0000
Message-ID: <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_DS0PR19MB6501657ADCF336B0C1CB3957FCCA9DS0PR19MB6501namp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/TtifXeJM38Ju7KrvDlmFRiPHH40>
Subject: [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: Fri, 13 May 2022 17:59:21 -0000

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)

v2.23.0 | Report a Bug | By Email