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

Kent Watsen <kent+ietf@watsen.net> Fri, 13 January 2023 18:20 UTC

Return-Path: <01000185ac5c8328-452eee8e-b8d8-4ef0-955a-e2ead0c557b2-000000@amazonses.watsen.net>
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 92430C15257D; Fri, 13 Jan 2023 10:20:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.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 q2vrFaq2reNi; Fri, 13 Jan 2023 10:20:23 -0800 (PST)
Received: from a48-90.smtp-out.amazonses.com (a48-90.smtp-out.amazonses.com [54.240.48.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EF3CC1524BF; Fri, 13 Jan 2023 10:20:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1673634022; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=0BXdzLvI1AyIfWhWXQxf+aTK6bCsyQSgYb8TBXz5jhs=; b=BVdgzDvW/8T4a4BtoRm9MaiDoxhUy3SMNeCIMGjuvEJd/dqS+P3oHU+wgLNNGzeG E51ZFGP7kWFraEd7CVbVCkOaeqcTH/QiYDL1EHgLmMhTcPLR5oi8KimZXQnzLTWBcyp 6NWogGuRxZY5M8IR2UXfzvF/nXlN5SxMGz5uXTQI=
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Kent Watsen <kent+ietf@watsen.net>
In-Reply-To: <b4dd6eae-7cab-5c87-5e1e-d90a0859b466@huawei.com>
Date: Fri, 13 Jan 2023 18:20:22 +0000
Cc: tom petch <ietfc@btconnect.com>, Italo Busi <Italo.Busi@huawei.com>, "netmod@ietf.org" <netmod@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <01000185ac5c8328-452eee8e-b8d8-4ef0-955a-e2ead0c557b2-000000@email.amazonses.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>
To: Benoit Claise <benoit.claise=40huawei.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2023.01.13-54.240.48.90
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/eiPSAg8ceEIGWz9eVltvHhWgrbg>
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, 13 Jan 2023 18:20:25 -0000


> On Jan 13, 2023, at 11:25 AM, Benoit Claise <benoit.claise=40huawei.com@dmarc.ietf.org> wrote:
> 
> Hi Tom,
>> Yes I do think that people outside the IETF may be ignorant of the nuances of the way the IETF works and  may not realise that a URL to the IANA website must be used in preference to an RFC.  There is more to YANG modules than extracting the code from somewhere in order to incorporate it into something.  I have even seen RFC reference the obsolete list of possibilities  in the RFC that set up an IANA registry
> If this is the case (And Randy supports this), then we should update RFC 8047.

Agreed - as a hold for document update?

Currently RFC 8407, Section 3.9 says:

   For every import or include statement that appears in a module
   contained in the specification that identifies a module in a separate
   document, a corresponding normative reference to that document MUST
   appear in the Normative References section.  The reference MUST
   correspond to the specific module version actually used within the
   specification.

Want to take a swing at it?

K.