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

Benoit Claise <benoit.claise@huawei.com> Thu, 12 January 2023 17:04 UTC

Return-Path: <benoit.claise@huawei.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 D9499C16FE2E; Thu, 12 Jan 2023 09:04:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 Ubxqx00SGu0L; Thu, 12 Jan 2023 09:04:32 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FCA1C16FE2D; Thu, 12 Jan 2023 09:04:08 -0800 (PST)
Received: from frapeml500001.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Nt9n30CDmz67TN2; Fri, 13 Jan 2023 01:01:27 +0800 (CST)
Received: from [10.48.135.45] (10.48.135.45) by frapeml500001.china.huawei.com (7.182.85.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.34; Thu, 12 Jan 2023 18:04:03 +0100
Message-ID: <ab763386-7668-39a7-a080-1bc202eb992e@huawei.com>
Date: Thu, 12 Jan 2023 18:03:56 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1
Content-Language: en-GB
To: tom petch <ietfc@btconnect.com>, Italo Busi <Italo.Busi@huawei.com>, "netmod@ietf.org" <netmod@ietf.org>
CC: "ccamp@ietf.org" <ccamp@ietf.org>
References: <900fcde63e90473b8424658bc7095818@huawei.com> <ede7a11a-bc66-26a5-f33a-83b15fc61fde@huawei.com> <AM7PR07MB624874275BBD327AEB38C004A0FD9@AM7PR07MB6248.eurprd07.prod.outlook.com>
From: Benoit Claise <benoit.claise@huawei.com>
In-Reply-To: <AM7PR07MB624874275BBD327AEB38C004A0FD9@AM7PR07MB6248.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.48.135.45]
X-ClientProxiedBy: dggems704-chm.china.huawei.com (10.3.19.181) To frapeml500001.china.huawei.com (7.182.85.94)
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/xvJpwGiXNfhLo4g3L0Qw59knl1I>
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: Thu, 12 Jan 2023 17:04:36 -0000

Hi Tom,

On 1/12/2023 5:51 PM, tom petch wrote:
> From: netmod <netmod-bounces@ietf.org> on behalf of Benoit Claise <benoit.claise=40huawei.com@dmarc.ietf.org>
> Sent: 12 January 2023 14:45
>
> Dear all,
>
> >From the initial problem statement:
> During a WG adoption poll we have received a comment that the URL
> should be added in the reference statement when importing a YANG
> module maintained by IANA
> The important question to me is: is this reference text supposed to be read by a machine or a human?
> It seems to me that the answer is "a human". https://datatracker.ietf.org/doc/html/rfc6020#section-7.19.4
>
> If this is true, why do we care about having a URL in there?
>
> <tp>
> One of the requirements in the design of URL was that they could be easily used by humans, written on  a napkin and handed over from one human to another to be consumed later so URL are designed for human consumption.
>
> Also,  the version of the module in an RFC is obsolete as soon as the RFC is published because IANA has change control so including an RFC number is directing users to out-of-date information, misleading them.  A well-written RFC will make this point and direct the reader to the IANA website (but most RFC are not well written).  Often the aim of putting data into IANA is to make it more readily available to others outside the IETF process and while experts like you will know the caveats, others may think that a reference to e.g.
> X.690 is a reference to the current, latest version.  So, if you want to mislead such people, point users at the RFC.
Oh, because you conclude that, if we put a RFC number in the reference, 
the community will (be stupid enough to) conclude that it has to extract 
the YANG module from the RFC text directly ... as opposed to look for a 
location where it's already store? IANA, yangcatalog.
Ok, if you think that this is really a problem...

Regards, Benoit
>
> Tom Petch
>
> Regards, Benoit
>
> On 1/12/2023 1:20 PM, Italo Busi wrote:
> Hi all,
>
> Happy New Year
>
> During a WG adoption poll we have received a comment that the URL should be added in the reference statement when importing a YANG module maintained by IANA and we are not sure how to address this comment
>
> See: https://mailarchive.ietf.org/arch/msg/ccamp/zD6gAfEUlYJ4W3qQlz6Y_gfX5TY/
>
> I have checked RFC8407 but I have not found any guideline on what to reference when importing an IANA module
>
> I have checked a couple of examples I knew (RFC8343 and RFC8348) and noted that the IANA modules are imported with no reference
>
> I have also noted that within the IANA YANG model registry, the reference for the IANA modules is the RFC where the module has been initially defined:
>
> https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml
>
> What would be your suggestion?
>
> Are there any guidelines I have missed?
>
> Do you know if there are other examples of published RFCs importing an IANA module?
>
> Thanks in advance
>
> Italo
>
>
>
>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org<mailto:netmod@ietf.org>
> https://www.ietf.org/mailman/listinfo/netmod
>
>
>