Re: [CCAMP] [netmod] What to reference when importing an IANA module?

mohamed.boucadair@orange.com Fri, 20 January 2023 08:20 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC93FC151520; Fri, 20 Jan 2023 00:20:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level:
X-Spam-Status: No, score=-2.797 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 TrvCeTyvQoMl; Fri, 20 Jan 2023 00:20:32 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (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 4BB74C14F749; Fri, 20 Jan 2023 00:20:32 -0800 (PST)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) (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 opfednr23.francetelecom.fr (ESMTP service) with ESMTPS id 4NysrG4l7mz5vqj; Fri, 20 Jan 2023 09:20:30 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1674202830; bh=EdLMo3feoYb6Q5gF3hudfVbuRZo/4cW17AsUNU26sAI=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=m2ox1OomI5oDV0vZN6jjcue9bCGXEq0fLiYeGMzYpmzgmoIMYNEWVo+bqppXaQXPW tf3TyUzzt6yV2DTj/ZrKfFKLrKopGmxPKP6WoCLMAZNlJYIWyYXHqHjc711SR4d4qN et+YRWPjjofjLNa6/Yh2tvdvp2F699NQSUXdhSDBtFNOL4ISIeAAIepmOfTGUYK93V /GN2MPvuPW5cTAVgWm610QtQVk0SfauIj4NOR5H56S0pHfvZe9ccwmNoaLJjPcY17E bliyf2Jd49f8i8L+9wuvDqp2RUKtRQskOh//RZmKRsutvjVYLZShxOwljh8MzKyvIk LWe8/9cHp0RGQ==
From: mohamed.boucadair@orange.com
To: tom petch <ietfc@btconnect.com>, Benoit Claise <benoit.claise=40huawei.com@dmarc.ietf.org>, Randy Presuhn <randy_presuhn@alumni.stanford.edu>, "ccamp@ietf.org" <ccamp@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] What to reference when importing an IANA module?
Thread-Index: AQHZK+Bx4N+mfLU7N0Cm7j3oDDOYmq6lkuOAgAFkAIA=
Content-Class:
Date: Fri, 20 Jan 2023 08:20:30 +0000
Message-ID: <22002_1674202830_63CA4ECE_22002_427_1_70d5112be75f4f15b68ca25aadee1ae5@orange.com>
References: <900fcde63e90473b8424658bc7095818@huawei.com> <ede7a11a-bc66-26a5-f33a-83b15fc61fde@huawei.com> <AM7PR07MB624874275BBD327AEB38C004A0FD9@AM7PR07MB6248.eurprd07.prod.outlook.com> <ab763386-7668-39a7-a080-1bc202eb992e@huawei.com> <AM7PR07MB6248DE5396AC76C0101B233BA0C29@AM7PR07MB6248.eurprd07.prod.outlook.com> <b4dd6eae-7cab-5c87-5e1e-d90a0859b466@huawei.com> <01000185ac5c8328-452eee8e-b8d8-4ef0-955a-e2ead0c557b2-000000@email.amazonses.com> <072be8fa-3801-1236-752a-e44df9347d18@alumni.stanford.edu> <953da02a-b364-cdda-0c6d-89d4ea1ec2fa@huawei.com> <19871_1673963186_63C6A6B2_19871_391_1_2e73a81d1de54970998730c9b27f6934@orange.com> <1f5c2c08-ffc6-6fb8-6b84-ad518d8516d6@huawei.com> <AM7PR07MB6248C52714B106B8192138C0A0C49@AM7PR07MB6248.eurprd07.prod.outlook.com>
In-Reply-To: <AM7PR07MB6248C52714B106B8192138C0A0C49@AM7PR07MB6248.eurprd07.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=2023-01-20T08:15:19Z; 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=4358e3b3-8ddd-479b-b220-dee1b7261357; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.27.51]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/3Iuyl3mKsvKK7mDjzwvGD9qIuxQ>
Subject: Re: [CCAMP] [netmod] What to reference when importing an IANA module?
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2023 08:20:36 -0000

Hi Benoit, Tom, all, 

FWIW, I went with the following changes in https://author-tools.ietf.org/iddiff?url2=draft-boucadair-netmod-iana-registries-07:

Added this NEW:

    Examples of IANA URLs from where to retrieve the latest version of an
    IANA-maintained module are: [IANA_BGP-L2_URL], [IANA_PW-Types_URL],
    and [IANA_BFD_URL].  [IANA_FOO_URL] is used in the following to refer
    to such URLs.  These URLs are expected to be sufficiently permanent
    and stable.

and updated the IANA considerations that will be included in RFCs as follows:

OLD:
      When this registry is modified, the YANG module "iana-foo"
      must be updated as defined in RFCXXXX.

NEW:
      When this registry is modified, the YANG module "iana-foo"
      [IANA_FOO_URL] must be updated as defined in RFCXXXX.

Cheers,
Med

> -----Message d'origine-----
> De : tom petch <ietfc@btconnect.com>
> Envoyé : jeudi 19 janvier 2023 13:01
> À : Benoit Claise <benoit.claise=40huawei.com@dmarc.ietf.org>;
> BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>; Randy
> Presuhn <randy_presuhn@alumni.stanford.edu>; ccamp@ietf.org;
> netmod@ietf.org
> Objet : Re: [netmod] What to reference when importing an IANA
> module?
> 
> From: netmod <netmod-bounces@ietf.org> on behalf of Benoit Claise
> <benoit.claise=40huawei.com@dmarc.ietf.org>
> Sent: 19 January 2023 08:31
> 
> Hi Med,
> 
> On 1/17/2023 2:46 PM,
> mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>
> wrote:
> If we want to add an IANA link to update RFC 8407, Section 3.9, a
> couple of remarks:
> - It's not clear what "a normative reference with the IANA URL"
> is.
>     Is it https://www.iana.org/assignments/yang-parameters/yang-
> parameters.xhtml?
>     Or is it https://www.iana.org/assignments/yang-
> parameters/iana-if-type@2022-08-24.yang?
>     The more precise the later, right?
> 
> [Med] None of them. IANA is using dedicated URLs:
> * https://www.iana.org/assignments/iana-bgp-l2-encaps/iana-bgp-l2-
> encaps.xhtml
> * https://www.iana.org/assignments/iana-pseudowire-types/iana-
> pseudowire-types.xhtml
> * https://www.iana.org/assignments/iana-bfd-types/iana-bfd-
> types.xhtml
> That would work.
> We would need
>     - to get the guarantee (from IANA) that those URLs are
> permanent
>     - to clearly mention that THIS URL type is required for IETF
> YANG modules
> 
> <tp>
> No chance.  Just as the IETF has reorganised its pages rendering
> URL in most RFC obsolete, so IANA occasionally re-arranges their
> website.  Such is life.  Hopefully a tombstone would survive to
> direct users where to go.
> 
> I note that an IANA-maintained module says that the latest version
> can be obtained from the IANA website but does not give a URL!
> 
> Still I think that a URL such as the above which points not to the
> module itself but to the summary page about the module is the best
> we can do for an RFC.
> 
> Tom Petch
> 
> Regards, Benoit
> 
>     However, the latter, which is a typical example of IANA
> maintained YANG module does NOT work, as the revision in the URL
> changes with any IAN update
> - So this leads to have both RFC and IANA, so
> https://www.iana.org/assignments/yang-parameters/yang-
> parameters.xhtml + RFC7224 (in the above example)
> - Also, we should make more generic for some other SDOs, as IANA
> is for IETF only.
>   And the guidelines are followed by others: BBF, IEEE, etc.


_________________________________________________________________________________________________________________________

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.