[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> Wed, 25 May 2022 19:32 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 9ADC4C07B7AB for <i2nsf@ietfa.amsl.com>; Wed, 25 May 2022 12:32:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.629
X-Spam-Level:
X-Spam-Status: No, score=-0.629 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 DuHyMAg2yNFQ for <i2nsf@ietfa.amsl.com>; Wed, 25 May 2022 12:32:28 -0700 (PDT)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [192.0.33.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 C4940C07B7A7 for <i2nsf@ietf.org>; Wed, 25 May 2022 12:32:28 -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 436DAE47D8; Wed, 25 May 2022 19:32:28 +0000 (UTC)
Received: by request4.lax.icann.org (Postfix, from userid 48) id 2F6F521AEB; Wed, 25 May 2022 19:32:28 +0000 (UTC)
RT-Owner: amanda.baber
From: Amanda Baber via RT <drafts-approval@iana.org>
Reply-To: drafts-approval@iana.org
In-Reply-To: <165271593403.62203.5600183016982303411@ietfa.amsl.com>
References: <RT-Ticket-1230766@icann.org> <165271593403.62203.5600183016982303411@ietfa.amsl.com>
Message-ID: <rt-4.4.3-29534-1653507148-1474.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
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Wed, 25 May 2022 19:32:28 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/4N0txclx3hR8n77EAGqb0gYxgns>
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: Wed, 25 May 2022 19:32:32 -0000
Hi Paul, Can you confirm that these revised actions for draft-ietf-i2nsf-capability-data-model-32 are OK? 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-32] 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: i2nsfcap Reference: [RFC-ietf-i2nsf-capability-data-model-32] Notes: [RFC-ietf-i2nsf-capability-data-model-32]'s module file will be posted upon the document's publication as an RFC Please see https://www.iana.org/assignments/yang-parameters Best regards, Amanda Baber IANA Operations Manager
- [I2nsf] [IANA #1230766] Protocol Action: 'I2NSF C… Amanda Baber via RT
- Re: [I2nsf] [IANA #1230766] Protocol Action: 'I2N… Mr. Jaehoon Paul Jeong