IETF Logo Mail Archive

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

Randy Presuhn <randy_presuhn@alumni.stanford.edu> Thu, 12 January 2023 18:35 UTC

Return-Path: <randy_presuhn@alumni.stanford.edu>
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 98705C16FE52 for <netmod@ietfa.amsl.com>; Thu, 12 Jan 2023 10:35:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 8u82jEvvOtrq for <netmod@ietfa.amsl.com>; Thu, 12 Jan 2023 10:35:29 -0800 (PST)
Received: from mail-pj1-f45.google.com (mail-pj1-f45.google.com [209.85.216.45]) (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 37F5FC15C524 for <netmod@ietf.org>; Thu, 12 Jan 2023 10:35:29 -0800 (PST)
Received: by mail-pj1-f45.google.com with SMTP id o1-20020a17090a678100b00219cf69e5f0so24518815pjj.2 for <netmod@ietf.org>; Thu, 12 Jan 2023 10:35:29 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:cc:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=rsd8xC2e5lX4dVkAtLdtpp222KH0R8hwrG0lDHYHsBs=; b=2CO/qIIpd6oImslmtC54sTXLyEmh3TSHw4xkQZSQOMmxJh808dtYPQbwW//4lTb8MA HuSfHwSHLpRcQqACbA7RCxmgcQZHYlVgUiafMpNf2iZ24pUlZcO7t5DIKBE0Vqy2h6wf hjhkSc9xE5bcOPfJ18soU1AqJpSUlceC4/mDdWYyYbhf3QxuaTxeV4TkwyoOkbGMejlB BMgjMX2jaUuseJznes7ljyOX4c5fVBC8yjGUIMWd2LYCEveuiua/EEIw4f+QweuYTB0G RjuGJ0FJP7jLUw/8T9Q5py/U81rAMl3ui+hBO97swpimUOcN2fs5TZY6NnriANuj7anj nKKw==
X-Gm-Message-State: AFqh2krC84kqjtAfTR8zWRzyr/O6L0jotpDY1r9PyUmg1ZZoRlhgBybR ZLBMd8uecviFe/X4SussIquADPt8tc9w9WhF
X-Google-Smtp-Source: AMrXdXsF6f8A/xObDrPNKMY8uIbVbtXZsq6+N0RpZh3mmxLy+iJyWDvk7HTFKLtn1Y/DDWT1jnLzaw==
X-Received: by 2002:a17:902:ea02:b0:191:271f:477c with SMTP id s2-20020a170902ea0200b00191271f477cmr83721063plg.32.1673548528699; Thu, 12 Jan 2023 10:35:28 -0800 (PST)
Received: from ?IPV6:2601:646:9300:b1e:54d3:153d:9d0c:d183? ([2601:646:9300:b1e:54d3:153d:9d0c:d183]) by smtp.gmail.com with ESMTPSA id f5-20020a170902ce8500b00178b9c997e5sm12532869plg.138.2023.01.12.10.35.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 12 Jan 2023 10:35:28 -0800 (PST)
Message-ID: <16944a1e-e893-825f-b13d-bf0867b390e6@alumni.stanford.edu>
Date: Thu, 12 Jan 2023 10:35:26 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1
To: 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>
Content-Language: en-US
Cc: ccamp@ietf.org
From: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
In-Reply-To: <ab763386-7668-39a7-a080-1bc202eb992e@huawei.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/8YLBXspqd4rhcSy26uOSoMuEo4k>
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, 12 Jan 2023 18:35:29 -0000

Hi -

On 2023-01-12 9:03 AM, Benoit Claise wrote:
...
> 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...
...

This was enough of a problem with vendors' implementations of MIB
modules that I think Tom's concern is well-founded.  I like the
idea of pointing to the relevant specification in general, but in
the particular case of registries, experience seems to show that
pointing directly to the registry reduces the likelihood of
some types of implementation error.

Randy

v2.23.0 | Report a Bug | By Email