[netmod] [IANA #1373241] RE: Regarding draft-ietf-netmod-rfc8407bis

Amanda Baber via RT <iana-issues@iana.org> Fri, 06 September 2024 05:52 UTC

Return-Path: <iana-shared@icann.org>
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 8C9F0C19ECBE for <netmod@ietfa.amsl.com>; Thu, 5 Sep 2024 22:52:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.959
X-Spam-Level:
X-Spam-Status: No, score=-3.959 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ORAMjFNs2TM1 for <netmod@ietfa.amsl.com>; Thu, 5 Sep 2024 22:52:04 -0700 (PDT)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [IPv6:2620:0:2d0:201::1:81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11BE2C19ECB6 for <netmod@ietf.org>; Thu, 5 Sep 2024 22:52:04 -0700 (PDT)
Received: from request7.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id C0631E1494; Fri, 6 Sep 2024 05:52:03 +0000 (UTC)
Received: by request7.lax.icann.org (Postfix, from userid 48) id BC0DBC17B27E; Fri, 6 Sep 2024 05:52:03 +0000 (UTC)
RT-Owner: amanda.baber
From: Amanda Baber via RT <iana-issues@iana.org>
In-Reply-To: <DU2PR02MB10160D6248418F58946C299CF889C2@DU2PR02MB10160.eurprd02.prod.outlook.com>
References: <RT-Ticket-1373241@icann.org> <0100019142c4d265-f73a9832-440b-4945-83d8-7ab566fcbef0-000000@email.amazonses.com> <DU2PR02MB10160D6248418F58946C299CF889C2@DU2PR02MB10160.eurprd02.prod.outlook.com>
Message-ID: <rt-5.0.3-1234062-1725601923-990.1373241-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1373241
X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
To: kent+ietf@watsen.net, mohamed.boucadair@orange.com
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Fri, 06 Sep 2024 05:52:03 +0000
MIME-Version: 1.0
Message-ID-Hash: RE6OK2H2JE4S5DF2NFCYP3UN7VAPVCUW
X-Message-ID-Hash: RE6OK2H2JE4S5DF2NFCYP3UN7VAPVCUW
X-MailFrom: iana-shared@icann.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netmod.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: netmod@ietf.org
X-Mailman-Version: 3.3.9rc4
Reply-To: iana-issues@iana.org
Subject: [netmod] [IANA #1373241] RE: Regarding draft-ietf-netmod-rfc8407bis
List-Id: NETMOD WG list <netmod.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/qie6Gc4VZEqfKaXtjBZXgAS5iMo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Owner: <mailto:netmod-owner@ietf.org>
List-Post: <mailto:netmod@ietf.org>
List-Subscribe: <mailto:netmod-join@ietf.org>
List-Unsubscribe: <mailto:netmod-leave@ietf.org>

Hi Med, Kent,

I apologize for missing this. 

In the 4.30.3 note about creating names, a replacement like this might be better for IANA:

OLD: (e.g., "3des-cbc" will be "triple-des-cbc" (Section 6.3 of [RFC4253]))

NEW: (e.g., "3des-cbc" will be "triple-des-cbc" (Section 6.3 of [RFC4253]); "6to4" will be "sixToFour")

The "6to4"/"sixToFour" example is taken from the iana-if-type module, published in Section 2 of RFC 7224.

The reasoning here is that the note says that "the procedure MUST detail how IANA can generate legal identifiers from such a name." 

Because we're being told that this is an example of an IANA Considerations section providing sufficient detail for future registrations, it would be helpful for us if the note were to acknowledge, at least implicitly, that future authors may not be able to supply a single naming pattern that we can always apply automatically.

The missing piece of information here, I think, is that IANA operations staff didn't know (and, in the future, may not know again) that "3des" is pronounced "triple-des." As such, it's possible for us to read the current example and wonder whether IANA is being told to replace any leading number in an identifier with a multiplicative. 

thanks,
Amanda