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

Roman Danyliw <rdd@cert.org> Tue, 24 May 2022 20:35 UTC

Return-Path: <rdd@cert.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 0A467C26D47E for <i2nsf@ietfa.amsl.com>; Tue, 24 May 2022 13:35:09 -0700 (PDT)
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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=seicmu.onmicrosoft.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 maVqSkW_5eyh for <i2nsf@ietfa.amsl.com>; Tue, 24 May 2022 13:35:05 -0700 (PDT)
Received: from USG02-CY1-obe.outbound.protection.office365.us (mail-cy1usg02on0127.outbound.protection.office365.us [23.103.209.127]) (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 07CB1C26D466 for <i2nsf@ietf.org>; Tue, 24 May 2022 13:35:04 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector5401; d=microsoft.com; cv=none; b=KSWM5X4gGYbvKj5mGD76giF6sG/8Xbq35NKbAuDvGL9Go+VmdRf6sTfvIP3gmNsYEEDJCZvBXFeVyLNOPxdRCvTJ33e7RG3qWsH+n+Fnu3TX9DMexGeS8ZZpxCTCauYt8J0vIHJx5UMdqXIvw+yCF1ZTtNhmFlEPBeRHDGhjujY04VhS1+Z0F3oNy65x115UIy8K3RTQOKaToQPYTbMEFTFQHniSkDUMy13VZasBkkdedaPq7vzQsAKjbdQFa7GFv0iNInTWKhTLfPhMnoEs3RUXTUYFFPKSNVH1Zu6ZJmzuH6D+or9LoB34HKWR2awi4KsCYonezO3Pj+g6OHrGfw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector5401; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=w/nNM44s37RsIr67y0+kwj6LhNSkRGBVhDMOB7Ho7WU=; b=lxZa+vw8a6qRJDrVEuJmJvfGlyB/4HZWDiZLUINB/1PYgRLp/UqKwws/cvPz9QoGgXJrrrzhDV1ARt5GmnihGu3qIkWraal5RVkW9KoUhxt3pVnH3fNxPNCwMON7avK5h+nfEg6aghSZUgIMKIdrIFiaVKPq8oiNdEpJNUnlsCHU+Fx8h/U3pj04kJI/7drWPsaAQA4PuEPYwO+fgeMuKZ/Ms2cr8uLIBSe6q78Wr7j/tTD6YKZJY7eMfj4xpvZE2Zov3It4ocuGwgZWkPaDAmzHmnhU7vBh8oBRaa81qjZu4ABsf1fqvkZksVtWXGej9j09vqdTXKN7hBTKxGVNlw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cert.org; dmarc=pass action=none header.from=cert.org; dkim=pass header.d=cert.org; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=seicmu.onmicrosoft.com; s=selector1-seicmu-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=w/nNM44s37RsIr67y0+kwj6LhNSkRGBVhDMOB7Ho7WU=; b=BhYYo0WlZfvhqO9Xga4fErvT6+dL+scZVESmf6AdPH3BxauO4zt+As1jK35rVBzE7Y4g/TQijjqwCcl0YZcyrDAl6+CRk8IHzAQUxqvFKZL0th6bJma0meeXycYaPuxNV0WK+4sNMiOGCC+nUgOqZtGvlTeM8WvQvMpDmlAVS8o=
Received: from BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM (2001:489a:200:168::11) by BN2P110MB1557.NAMP110.PROD.OUTLOOK.COM (2001:489a:200:17b::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5273.16; Tue, 24 May 2022 20:34:52 +0000
Received: from BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM ([fe80::557e:44e5:6959:7c65]) by BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM ([fe80::557e:44e5:6959:7c65%4]) with mapi id 15.20.5273.023; Tue, 24 May 2022 20:34:52 +0000
From: Roman Danyliw <rdd@cert.org>
To: "drafts-approval@iana.org" <drafts-approval@iana.org>
CC: "ynir.ietf@gmail.com" <ynir.ietf@gmail.com>, "timkim@skku.edu" <timkim@skku.edu>, "shares@ndzh.com" <shares@ndzh.com>, "rgm@htt-consult.com" <rgm@htt-consult.com>, "pauljeong@skku.edu" <pauljeong@skku.edu>, "paul.wouters@aiven.io" <paul.wouters@aiven.io>, "patricklink888@gmail.com" <patricklink888@gmail.com>, "linqiushi@huawei.com" <linqiushi@huawei.com>, "linda.dunbar@futurewei.com" <linda.dunbar@futurewei.com>, "jaehoon.paul@gmail.com" <jaehoon.paul@gmail.com>, "i2nsf@ietf.org" <i2nsf@ietf.org>, "dunbar.ll@gmail.com" <dunbar.ll@gmail.com>
Thread-Topic: [IANA #1230766] Protocol Action: 'I2NSF Capability YANG Data Model' to Proposed Standard (draft-ietf-i2nsf-capability-data-model-31.txt)
Thread-Index: AQHYaVEZEBP7e7GfC0+5SX2vyLd90K0rBv4AgAEuS4CAAIplkoAByRWA
Date: Tue, 24 May 2022 20:34:52 +0000
Message-ID: <BN2P110MB1107EA6701AA930E5C739FE1DCD79@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
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> <rt-4.4.3-26662-1653326311-862.1230766-37-0@icann.org>
In-Reply-To: <rt-4.4.3-26662-1653326311-862.1230766-37-0@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=cert.org;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: fbc1237a-bed1-429c-4b8c-08da3dc4daf5
x-ms-traffictypediagnostic: BN2P110MB1557:EE_
x-microsoft-antispam-prvs: <BN2P110MB1557231233C62F3326AB36BCDCD79@BN2P110MB1557.NAMP110.PROD.OUTLOOK.COM>
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: bdmLiioDMeIYRJFBMGV37hkZOu7juBYarUlwYOn+AlpB33B+1rNsOKCGR/0RPA3DC6i+swMoYx9tK+M1PIRZ3r3pEo5seJTklFI+XgutmdJ9BfLap0bxunedkYyBVpubAe80JjOYf71LmIELgYfewtv0zbemCfTMwIAQNk2tgFC1cMKIxbyw0BmKM0QS4mMozoJY7SJMP17nAQVgJaQ1l5+3AqtI9py9zY2c3KP+2sC6+nP0R/jb2+Rs5H/2GzMsvaBs+qdnQhKWA+2swJriP3Dyg5LN3uiZ/dBvcwBjaMQqTWFiat4uCriwtesx4FukjCIk/oiUcgRAAbqe3dQJbuNrIb+WxgMOAGszAvymQoJLwEOLqyg6aOAbPbvNeNVJDGEmQwZvZzIQVLK50Xu02C7G/HV3Z06qlXHWqkl76APWuCwefeiR6wcQo1XPKxHiScCoAtIr3Sc6eq0toUB4LfolIPgb/xuaZO+Axuf2m8iSGopUR6pgea5+GtMLT/QbfogSXFzvoIceX61/awLc0JMJkobL1WOB4vUHXDAUcIwCDofsPmwToagcDyemaKi95oEiEsxV6Pg7vt7XbVZBYMKEWxFFOMfnIF15/Crf52g4C57MRSeggFvaoFHO5dlfVknTCrVWhP8PeF6epPipwEdYUhVEJqS4IN3gy/IPYECSLAJ6xDNhgPrHXKnThBnK3gTDxjJR+zV73/OgBO+ejg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFS:(13230001)(366004)(66476007)(8676002)(4326008)(498600001)(966005)(64756008)(76116006)(83380400001)(82960400001)(71200400001)(122000001)(54906003)(66946007)(38070700005)(66446008)(86362001)(6916009)(55016003)(26005)(9686003)(186003)(38100700002)(53546011)(7696005)(6506007)(33656002)(2906002)(52536014)(8936002)(5660300002)(66556008)(7416002); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: PumJ27kVM3wUEZizaMbdR22KfYYmMC+j2emi/8Vr4ssX/v+k+ewVLvcnwZ1rYZFpo0eoRr936ldW100lcN8yHC1wcadjZukXiNJjSUX08j61VBRkFWy+w88GzvrahjuCxTW94NXi19iM6kryZ6gaIwh+6Es9rj3oWgGlkZoaVMib1JfcFgFlFCqDUjPH1iywUDC7J/XO6IujfDNXNt68OyUfFn/mhRvDykUrkGHVw5JAQeWRgdIp35J2zzIEfL0V3caUpmuxPPHG6VGCs6G5Mc3OBehKkaj7jcfMUIPTJKF2R+NM2lHXN5cT+dORBDIT3v/4Leu0FdfAeXp+KPhrfB+hpnsrn4zxPrTNXBPEBDhL2swUZtVMe03vDdPCpvU2jT5CpKSQLNTYR3B/bRskYN+JpwvTotsQrp/vWfwTfvI=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: cert.org
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: fbc1237a-bed1-429c-4b8c-08da3dc4daf5
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 May 2022 20:34:52.2270 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 95a9dce2-04f2-4043-995d-1ec3861911c6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN2P110MB1557
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/BD_oNDUedQxkbjMyRHPInIaJPP8>
Subject: Re: [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
Precedence: list
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: Tue, 24 May 2022 20:35:09 -0000

Approved.

Roman

> -----Original Message-----
> From: Amanda Baber via RT <drafts-approval@iana.org>
> Sent: Monday, May 23, 2022 1:19 PM
> Cc: ynir.ietf@gmail.com; timkim@skku.edu; shares@ndzh.com; rgm@htt-
> consult.com; Roman Danyliw <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; Roman Danyliw <rdd@cert.org>
> Subject: [IANA #1230766] Protocol Action: 'I2NSF Capability YANG Data Model'
> to Proposed Standard (draft-ietf-i2nsf-capability-data-model-31.txt)
> 
> 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
> > >>
> > >>
> > >>
> > >>