[I2nsf] [IANA #1369291] Request for IANA Registration for I2NSF Draft

Amanda Baber via RT <iana-issues@iana.org> Thu, 01 August 2024 00:10 UTC

Return-Path: <iana-shared@icann.org>
X-Original-To: i2nsf@ietfa.amsl.com
Delivered-To: i2nsf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 536A2C15152F for <i2nsf@ietfa.amsl.com>; Wed, 31 Jul 2024 17:10:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.657
X-Spam-Level:
X-Spam-Status: No, score=-6.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 JS0I4Evvs_lS for <i2nsf@ietfa.amsl.com>; Wed, 31 Jul 2024 17:10:09 -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 B90BBC1519AC for <i2nsf@ietf.org>; Wed, 31 Jul 2024 17:10:09 -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 15896E1403; Thu, 1 Aug 2024 00:10:09 +0000 (UTC)
Received: by request7.lax.icann.org (Postfix, from userid 48) id 13211C100F09; Thu, 1 Aug 2024 00:10:09 +0000 (UTC)
RT-Owner: amanda.baber
From: Amanda Baber via RT <iana-issues@iana.org>
In-Reply-To: <CAPK2Deyb+qKMkx2VMvXNOrUGyOD2eox7-cfsAbJsDFMT_R3R_Q@mail.gmail.com>
References: <RT-Ticket-1369291@icann.org> <CAPK2Deyb+qKMkx2VMvXNOrUGyOD2eox7-cfsAbJsDFMT_R3R_Q@mail.gmail.com>
Message-ID: <rt-5.0.3-946942-1722471008-905.1369291-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1369291
X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
To: jaehoon.paul@gmail.com
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Thu, 01 Aug 2024 00:10:09 +0000
MIME-Version: 1.0
Message-ID-Hash: YK4QGBWHQ24US3BBEMYVJUI3IJ5P6MFF
X-Message-ID-Hash: YK4QGBWHQ24US3BBEMYVJUI3IJ5P6MFF
X-MailFrom: iana-shared@icann.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-i2nsf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: ynir.ietf@gmail.com, rfc-ise@rfc-editor.org, patricklink888@gmail.com, linda.dunbar@futurewei.com, i2nsf@ietf.org, cyc79@etri.re.kr
X-Mailman-Version: 3.3.9rc4
Reply-To: iana-issues@iana.org
Subject: [I2nsf] [IANA #1369291] Request for IANA Registration for I2NSF Draft
List-Id: "*I2NSF: Interface to Network Security Functions mailing list*" <i2nsf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/GefkC6JwNL6gUBMn0QWQcfc0MWg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2nsf>
List-Help: <mailto:i2nsf-request@ietf.org?subject=help>
List-Owner: <mailto:i2nsf-owner@ietf.org>
List-Post: <mailto:i2nsf@ietf.org>
List-Subscribe: <mailto:i2nsf-join@ietf.org>
List-Unsubscribe: <mailto:i2nsf-leave@ietf.org>

Hi Paul, all,

I see that this document will IANA add entries to the IETF XML ns and YANG Module Name registries. 

Section 14 of RFC 6020 says, "The module name prefix 'ietf-' is reserved for IETF stream documents [RFC4844], while the module name prefix 'irtf-' is reserved for IRTF stream documents.  Modules published in other RFC streams MUST have a similar suitable prefix."

I don't have any insight into how this module would need to be renamed. Looking at https://www.iana.org/assignments/yang-parameters, all of the module names we've registered so far begin with either "iana-" (for IANA-maintained modules, which isn't being requested here) or "ietf-". Note that the registration procedure for YANG Module Names is "RFC Required," which doesn't rule out independent-stream documents.

As for more general IANA requirements: 

For the XML registration, we'll need to ask the IESG-designated experts to approve. For IETF-stream documents, we typically contact the experts during IETF Last Call, so that the experts can have at least two weeks before the IESG telechat to complete their review. In this case, we would expect the review to be triggered by the Conflict Review announcement, unless the ISE requests an earlier review.

For the YANG module registration, no special IANA review is required, beyond our usual Conflict Review check that the IANA Considerations section makes sense. We'll register the module name in the YANG Module Names registry when the ISE notifies us and the RFC Editor that the document is ready to be processed, and we'll publish the module file itself when the RFC Editor notifies us that they've published the document as an RFC. (Offhand, I think that module publication may be the only type of IANA action that we put off until the RFC has been published.)

When we receive the Conflict Review announcement, we'll check this document again and send an email that says "here's the list of actions we understand you want IANA to perform when the document is ready to be processed" (as opposed to "when the IESG approves the document" for an IETF-stream I-D).

Best regards,

Amanda Baber
IANA Operations Manager

On Tue Jul 30 10:34:42 2024, jaehoon.paul@gmail.com wrote:
> Hi IANA,
> This is Paul Jeong.
> I would like to ask for IANA Registration for I2NSF Draft with a YANG
> Module:
> 
> - Draft: draft-lingga-i2nsf-analytics-interface-dm-04
> - Title: I2NSF Analytics Interface YANG Data Model for Closed-Loop
> Security
> Control in the I2NSF Framework
> - URL:
> https://datatracker.ietf.org/doc/html/draft-lingga-i2nsf-analytics-
> interface-dm-04
> 
> This document will be submitted to the IETF Independent Submission
> Stream
> according to the I2NSF WG Chair, Linda Dunbar.
> 
> Thanks.
> 
> Best Regards,
> Paul