IETF Logo Mail Archive

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

Benoit Claise <benoit.claise@huawei.com> Thu, 19 January 2023 08:31 UTC

Return-Path: <benoit.claise@huawei.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 99905C1524C8; Thu, 19 Jan 2023 00:31:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 FjC2sKYzDtvv; Thu, 19 Jan 2023 00:31:38 -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 6EE55C14F74E; Thu, 19 Jan 2023 00:31:38 -0800 (PST)
Received: from frapeml500001.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4NyG706lp7z67vyB; Thu, 19 Jan 2023 16:31:08 +0800 (CST)
Received: from [10.81.222.131] (10.81.222.131) 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, 19 Jan 2023 09:31:32 +0100
Content-Type: multipart/alternative; boundary="------------uWQkF4Q0i01bRFVb3ZARNKc7"
Message-ID: <1f5c2c08-ffc6-6fb8-6b84-ad518d8516d6@huawei.com>
Date: Thu, 19 Jan 2023 09:31:27 +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: mohamed.boucadair@orange.com, Randy Presuhn <randy_presuhn@alumni.stanford.edu>, "ccamp@ietf.org" <ccamp@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
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>
From: Benoit Claise <benoit.claise@huawei.com>
In-Reply-To: <19871_1673963186_63C6A6B2_19871_391_1_2e73a81d1de54970998730c9b27f6934@orange.com>
X-Originating-IP: [10.81.222.131]
X-ClientProxiedBy: dggems702-chm.china.huawei.com (10.3.19.179) To frapeml500001.china.huawei.com (7.182.85.94)
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/5YNGHznUdIt2k8WhcY6OT7GH8Yw>
Subject: Re: [netmod] What to reference when importing an IANA module?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.39
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 Jan 2023 08:31:42 -0000

Hi Med,

On 1/17/2023 2:46 PM, 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

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 
> <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.
>

v2.23.0 | Report a Bug | By Email