[I2nsf] [IANA #1230766] Protocol Action: 'I2NSF Capability YANG Data Model' to Proposed Standard (draft-ietf-i2nsf-capability-data-model-31.txt)

Amanda Baber via RT <drafts-approval@iana.org> Mon, 23 May 2022 17:18 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 6D00AC18D825 for <i2nsf@ietfa.amsl.com>; Mon, 23 May 2022 10:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.628
X-Spam-Level:
X-Spam-Status: No, score=-5.628 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, 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 xyEXkOhWH83R for <i2nsf@ietfa.amsl.com>; Mon, 23 May 2022 10:18:32 -0700 (PDT)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [IPv6:2620:0:2d0:201::1:81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D36B7C18D821 for <i2nsf@ietf.org>; Mon, 23 May 2022 10:18:32 -0700 (PDT)
Received: from request4.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id 1F3FFE34A4; Mon, 23 May 2022 17:18:31 +0000 (UTC)
Received: by request4.lax.icann.org (Postfix, from userid 48) id 1B2A2210D9; Mon, 23 May 2022 17:18:31 +0000 (UTC)
RT-Owner: amanda.baber
From: Amanda Baber via RT <drafts-approval@iana.org>
Reply-To: drafts-approval@iana.org
In-Reply-To: <rt-4.4.3-26662-1653296665-312.1230766-37-0@icann.org>
References: <RT-Ticket-1230766@icann.org> <165271593403.62203.5600183016982303411@ietfa.amsl.com> <rt-4.4.3-29997-1652724985-1468.1230766-37-0@icann.org> <CAPK2DexQQADnMztfhcB_+6SHtMXQiPtTQXKdmGXUzxrLTmTqZw@mail.gmail.com> <CAPK2Deyio76F9j22MgpH7Rc7Cpug9gHx_1=y7p-oP6K0TPYVTA@mail.gmail.com> <rt-4.4.3-26662-1653296665-312.1230766-37-0@icann.org>
Message-ID: <rt-4.4.3-26662-1653326311-862.1230766-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1230766
X-Managed-BY: RT 4.4.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
CC: ynir.ietf@gmail.com, timkim@skku.edu, shares@ndzh.com, rgm@htt-consult.com, rdd@cert.org, pauljeong@skku.edu, paul.wouters@aiven.io, patricklink888@gmail.com, linqiushi@huawei.com, linda.dunbar@futurewei.com, jaehoon.paul@gmail.com, i2nsf@ietf.org, dunbar.ll@gmail.com, rdd@cert.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Mon, 23 May 2022 17:18:31 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/1luy31mcnflCHkQaVSW2B_WYFPk>
Subject: [I2nsf] [IANA #1230766] Protocol Action: 'I2NSF Capability YANG Data Model' to Proposed Standard (draft-ietf-i2nsf-capability-data-model-31.txt)
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.34
List-Id: "*I2NSF: Interface to Network Security Functions mailing list*" <i2nsf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2nsf/>
List-Post: <mailto:i2nsf@ietf.org>
List-Help: <mailto:i2nsf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2022 17:18:36 -0000

Hi Roman,

Can you confirm that IANA can move ahead with these changes?

thanks,
Amanda

On Mon May 23 09:04:25 2022, jaehoon.paul@gmail.com wrote:
> Hi Amanda and Roman,
> I have submitted the revised versions of those drafts as follows:
> https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-capability-
> data-model-32
> https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-nsf-facing-
> interface-dm-28
> https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-nsf-monitoring-
> data-model-19
> 
> 
> Amanda,
> Could you reflect the requested changes related to IANA Sections on
> those
> three drafts?
> 
> Thanks.
> 
> Best Regards,
> Paul
> 
> On Mon, May 23, 2022 at 12:01 AM Mr. Jaehoon Paul Jeong <
> jaehoon.paul@gmail.com> wrote:
> 
> > Hi Amanda and Roman,
> > I would like to change the YANG module names for naming consistency
> > for
> > the following three drafts:
> >
> > https://datatracker.ietf.org/doc/draft-ietf-i2nsf-capability-data-
> > model/
> > https://datatracker.ietf.org/doc/draft-ietf-i2nsf-nsf-facing-
> > interface-dm/
> >
> > https://datatracker.ietf.org/doc/draft-ietf-i2nsf-nsf-monitoring-
> > data-model/
> >
> > -----------------------------------------------------------------------
> > 1. I2NSF Capability YANG Data Model Draft
> >
> > We want to update the YANG module's prefix as follows:
> > // nsfcap => i2nsfcap
> >
> > - OLD
> > ID: yang:ietf-i2nsf-capability
> > URI: urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability
> > Filename:
> > https://www.iana.org/assignments/xml-registry/ns/yang/ietf-i2nsf-
> > capability.txt
> > Reference: [RFC-ietf-i2nsf-capability-data-model-31]
> >
> > Name: ietf-i2nsf-capability
> > Maintained by IANA: N
> > Namespace: urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability
> > Prefix: nsfcap
> > Reference: [RFC-ietf-i2nsf-capability-data-model-31]
> > Notes: [RFC-ietf-i2nsf-capability-data-model-31]'s module file will
> > be
> > posted upon the document's publication as an RFC.
> > -----
> >
> > - NEW
> > ID: yang:ietf-i2nsf-capability
> > URI: urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability
> > Filename:
> > https://www.iana.org/assignments/xml-registry/ns/yang/ietf-i2nsf-
> > capability.txt
> > Reference: [RFC-ietf-i2nsf-capability-data-model-31]
> >
> > Name: ietf-i2nsf-capability
> > Maintained by IANA: N
> > Namespace: urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability
> > Prefix: i2nsfcap
> > Reference: [RFC-ietf-i2nsf-capability-data-model-31]
> > Notes: [RFC-ietf-i2nsf-capability-data-model-31]'s module file will
> > be
> > posted upon the document's publication as an RFC.
> > -----------------------------------------------------------------------
> >
> > 2. I2NSF NSF-Facing Interface YANG Data Model Draft
> >
> > We want to update the YANG module's name and prefix as follows:
> > // ietf-i2nsf-policy-rule-for-nsf => ietf-i2nsf-nsf-facing-interface
> > // nsfintf => i2nsfnfi
> >
> > - OLD
> > ID: yang:ietf-i2nsf-policy-rule-for-nsf
> > URI: urn:ietf:params:xml:ns:yang:ietf-i2nsf-policy-rule-for-nsf
> > Filename:
> > https://www.iana.org/assignments/xml-registry/ns/yang/ietf-i2nsf-
> > policy-rule-for-nsf.txt
> > Reference: [RFC-ietf-i2nsf-nsf-facing-interface-dm-27]
> >
> > Name: ietf-i2nsf-policy-rule-for-nsf
> > Maintained by IANA: N
> > Namespace: urn:ietf:params:xml:ns:yang:ietf-i2nsf-policy-rule-for-nsf
> > Prefix: nsfintf
> > Reference: [RFC-ietf-i2nsf-nsf-facing-interface-dm-27]
> > Notes: [RFC-ietf-i2nsf-nsf-facing-interface-dm-27]'s module file will
> > be
> > posted upon the document's publication as an RFC.
> > -----
> >
> > - NEW
> > ID: yang:ietf-i2nsf-nsf-facing-interface
> > URI: urn:ietf:params:xml:ns:yang:ietf-i2nsf-nsf-facing-interface
> > Filename:
> > https://www.iana.org/assignments/xml-registry/ns/yang/ietf-i2nsf-nsf-
> > facing-interface.txt
> > Reference: [RFC-ietf-i2nsf-nsf-facing-interface-dm-27]
> >
> > Name: ietf-i2nsf-nsf-facing-interface
> > Maintained by IANA: N
> > Namespace: urn:ietf:params:xml:ns:yang:ietf-i2nsf-nsf-facing-
> > interface
> > Prefix: i2nsfnfi
> > Reference: [RFC-ietf-i2nsf-nsf-facing-interface-dm-27]
> > Notes: [RFC-ietf-i2nsf-nsf-facing-interface-dm-27]'s module file will
> > be
> > posted upon the document's publication as an RFC.
> >
> > -----------------------------------------------------------------------
> > 3. I2NSF Monitoring Interface YANG Data Model Draft
> >
> > We want to update the YANG module's name and prefix as follows:
> > // ietf-i2nsf-nsf-monitoring => ietf-i2nsf-monitoring-interface
> > // nsfmi => i2nsfmi
> >
> > - OLD
> > ID: yang:ietf-i2nsf-nsf-monitoring
> > URI: urn:ietf:params:xml:ns:yang:ietf-i2nsf-nsf-monitoring
> > Filename:
> > https://www.iana.org/assignments/xml-registry/ns/yang/ietf-i2nsf-nsf-
> > monitoring.txt
> > Reference: [RFC-ietf-i2nsf-nsf-monitoring-data-model-18]
> >
> > Name: ietf-i2nsf-nsf-monitoring
> > Maintained by IANA: N
> > Namespace: urn:ietf:params:xml:ns:ietf-i2nsf-nsf-monitoring
> > Prefix: nsfmi
> > Reference: [RFC-ietf-i2nsf-nsf-monitoring-data-model-18]
> > Notes: [RFC-ietf-i2nsf-nsf-monitoring-data-model-18]'s module file
> > will be
> > posted upon the document's publication as an RFC.
> > -----
> >
> > - NEW
> > ID: yang:ietf-i2nsf-monitoring-interface
> > URI: urn:ietf:params:xml:ns:yang:ietf-i2nsf-monitoring-interface
> > Filename:
> > https://www.iana.org/assignments/xml-registry/ns/yang/ietf-i2nsf-
> > monitoring-interface.txt
> > Reference: [RFC-ietf-i2nsf-nsf-monitoring-data-model-18]
> >
> > Name: ietf-i2nsf-monitoring-interface
> > Maintained by IANA: N
> > Namespace: urn:ietf:params:xml:ns:ietf-i2nsf-monitoring-interface
> > Prefix: i2nsfmi
> > Reference: [RFC-ietf-i2nsf-nsf-monitoring-data-model-18]
> > Notes: [RFC-ietf-i2nsf-nsf-monitoring-data-model-18]'s module file
> > will be
> > posted upon the document's publication as an RFC.
> > -----------------------------------------------------------------------
> >
> > I attach a PDF file having the updates of the name and prefix of each
> > draft in summary.
> >
> > For these updates, we need to modify the code in the YANG modules in
> > those
> > I2NSF three drafts.
> >
> > I will submit the revised drafts having those updates this Monday
> > (May 24)
> > in Korean time.
> >
> > Thanks.
> >
> > Best Regards,
> > Paul
> >
> >
> > On Tue, May 17, 2022 at 3:16 AM Amanda Baber via RT <
> > drafts-approval@iana.org> wrote:
> >
> >> Dear Authors:
> >>
> >> ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED
> >>
> >> We've completed the registry actions for the following RFC-to-be:
> >>
> >> draft-ietf-i2nsf-capability-data-model-31
> >>
> >> ACTION 1:
> >>
> >> The following entry has been added to the IETF XML ns registry:
> >>
> >> ID: yang:ietf-i2nsf-capability
> >> URI: urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability
> >> Filename:
> >> https://www.iana.org/assignments/xml-registry/ns/yang/ietf-i2nsf-
> >> capability.txt
> >> Reference: [RFC-ietf-i2nsf-capability-data-model-31]
> >>
> >> Please see
> >> https://www.iana.org/assignments/xml-registry
> >>
> >> ACTION 2:
> >>
> >> The following entry has been added to the YANG Module Names
> >> registry:
> >>
> >> Name: ietf-i2nsf-capability
> >> Maintained by IANA: N
> >> Namespace: urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability
> >> Prefix: nsfcap
> >> Reference: [RFC-ietf-i2nsf-capability-data-model-31]
> >> Notes: [RFC-ietf-i2nsf-capability-data-model-31]'s module file will
> >> be
> >> posted upon the document's publication as an RFC.
> >>
> >> Please see
> >> https://www.iana.org/assignments/yang-parameters
> >>
> >> Please let us know whether this document's registry actions have
> >> been
> >> completed correctly. Once we receive your confirmation, we'll notify
> >> the
> >> RFC Editor that the actions are complete. If a team of authors is
> >> responsible for the document, and the actions have been performed
> >> correctly, please send a single confirmation message.
> >>
> >> We'll update any references to this document in the registries when
> >> the
> >> RFC Editor notifies us that they've assigned an RFC number.
> >>
> >> Best regards,
> >>
> >> Amanda Baber
> >> IANA Operations Manager
> >>
> >>
> >>
> >>