Re: [I2nsf] WGLC for draft-ietf-i2nsf-registration-dm-17

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Wed, 31 August 2022 11:14 UTC

Return-Path: <jaehoon.paul@gmail.com>
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 95CE1C14CE23 for <i2nsf@ietfa.amsl.com>; Wed, 31 Aug 2022 04:14:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.088
X-Spam-Level:
X-Spam-Status: No, score=-5.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FREEMAIL_DOC_PDF=0.01, T_HK_NAME_FM_MR_MRS=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, URI_DOTEDU=1.997] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 isYiSRL0qYs6 for <i2nsf@ietfa.amsl.com>; Wed, 31 Aug 2022 04:14:35 -0700 (PDT)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD140C14CF16 for <i2nsf@ietf.org>; Wed, 31 Aug 2022 04:14:35 -0700 (PDT)
Received: by mail-pj1-x1036.google.com with SMTP id o4so13813763pjp.4 for <i2nsf@ietf.org>; Wed, 31 Aug 2022 04:14:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=mTvK/qF6OAmlEK+p339WaJJNZkrlatxjP79Fxt8U9CQ=; b=b/8hFdrJTGno82YHwDbtkCL+ItnkTTe0rgEVMDFUO0ycv8+wL0P97dYSl22+nQW6Du SDse2GibwYKLxugyDx9BCuvXc30p3DXgcMMOP1NX3nlaVhWBuqVbGq5RkJxkdTQDiQ/Y UkGCrVX/hnCxmGAH7SgpHnmFBL6qFBa/LpZQ3MxlcWRzAZVIPh6bPcz9C24pOJr/fIMx iDtA3iq+R0uNKLBLjM/xyVFHN5chqoT+hIAvIiBEvUOzMks6ikG+JUItGMoOI/ZQFSLO VY9GoEIsNyG+RHDE1YnxQhJpCTnRv8zh3/Or78rNGHNQa6Hj7PD58WklUPnWu1bQ66tb K/xg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=mTvK/qF6OAmlEK+p339WaJJNZkrlatxjP79Fxt8U9CQ=; b=P/+DLXlQP45jCEzSm6hlVIINRt9WlJaDzKXF22gh5L2M9avGntzwgEx6E7EOot34a7 uQ4aYhUmubjA4aW8+Isw+EC6w24UaauJ3nhnOAMARC4WkFNt1K+CwFaqXOdQyVa/nRgL Xex5f8Bh46+/Gq8mEiFL6XYFOUQq2R7YGi88qRTq7pr6H+huqZHMJ6AVCXnSPZIkJkqi srUduOd1HZ6JAq27+oF9dXESuslQnL39Hi41g3jwa4VMwN5fnIigFzS11NkKPARbZsCK azTfpSVGbBGonUg8tn4H946oig3zDL186kCXed24uhPJg6eEgzBJYrZ6AuXmcnMfi8v2 7Dwg==
X-Gm-Message-State: ACgBeo13v+qrXih9m3pv6bAHL63RSWqB5IWNtTdGNvPOyB4CQ+EEDARu qWBrxDNuJNlkBhkzf3M22jxzv2Rvxhg4wcidT0o=
X-Google-Smtp-Source: AA6agR7+CCvrEJuKmaXQ6XZuHfEM01SdXL2gXVqpT6A+AIBIi8kxo85MEglWtnqDrd8n6xX+JafzQRrxbplubeT4x34=
X-Received: by 2002:a17:90b:33c7:b0:1fd:f4f1:d661 with SMTP id lk7-20020a17090b33c700b001fdf4f1d661mr2760991pjb.186.1661944474623; Wed, 31 Aug 2022 04:14:34 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR13MB49207082E7EAC23911CB0FE985A69@CO1PR13MB4920.namprd13.prod.outlook.com> <CAPK2DewWXdBpzQu9KLUCT5GeKAecU5ruPSz2iryrd814pvZMkQ@mail.gmail.com> <52f533626b534781b545c2f5c6c452c7@huawei.com>
In-Reply-To: <52f533626b534781b545c2f5c6c452c7@huawei.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Wed, 31 Aug 2022 20:13:59 +0900
Message-ID: <CAPK2DexNkRA=M2Nrb68gN0fRFHwDDpU_uQWasc=DkjNO0H1i4Q@mail.gmail.com>
To: Qin Wu <bill.wu@huawei.com>
Cc: "i2nsf@ietf.org" <i2nsf@ietf.org>, Roman Danyliw <rdd@cert.org>, Linda Dunbar <linda.dunbar@futurewei.com>, Patrick Lingga <patricklink888@gmail.com>, skku-iotlab-members <skku-iotlab-members@googlegroups.com>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/mixed; boundary="0000000000000c682105e7879a68"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/ajyqIM4JedntQOcbI28MwLzRFtw>
Subject: Re: [I2nsf] WGLC for draft-ietf-i2nsf-registration-dm-17
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 31 Aug 2022 11:14:39 -0000

Hi Qin,
Here is the revision reflecting your detailed comments on the I2NSF
Registration Interface:
https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-registration-interface-dm-20

Patrick and I have revised this draft along with the attached revision
letter.

Could you confirm whether this revision looks good to you or not?

Thanks.

Best Regards,
Paul



On Wed, Aug 24, 2022 at 6:42 PM Qin Wu <bill.wu@huawei.com> wrote:

> Hi, Paul:
>
> Thank you for inviting me to review this draft.
>
> I am a little confused about the relation of this draft with
> draft-ietf-i2nsf-capability-data-model
>
> See quoted text in draft-ietf-i2nsf-capability-data-model
>
> “
>
>    This document provides an information model and the corresponding
>
>    YANG data model [RFC6020][RFC7950] that defines the capabilities of
>
>    NSFs to centrally manage the capabilities of those NSFs.  The NSFs
>
>    can register their own capabilities into a Network Operator
>
>    Management (Mgmt) System (i.e., Security Controller) with this YANG
>
>    data model through the registration interface [RFC8329].
>
>
>
> ”
>
> And quote text in draft-ietf-i2nsf-registration-dm
>
> “
>
>    This document describes an information model (see Section 4) and a
>
>    YANG [RFC7950] data model (see Section 5) for the I2NSF Registration
>
>    Interface [RFC8329] between the security controller and the
>
>    developer's management system (DMS) to support NSF capability
>
>    registration and query via the registration interface.
>
>
>
> ”
>
> I am wondering which YANG data model is exchanged in the registration
> interface.
>
> Shouldn’t YANG data model defined in draft-ietf-i2nsf-registration-dm
> augment the YANG model defined in
>
> draft-ietf-i2nsf-capability-data-model.
>
>
>
> In addition, I think registration interface seems not mandatory interface,
> security controller in some other case can
>
> Learn capability NFV orchestrators, or NSF can expose dynamic capability
> to security controller.
>
>
>
> Besides register NSF, I am wondering what other data or information can be
> registered? I assume there are a lot.
>
> Therefore I would suggest to limit the scope of this registration
> interface, only focus NSF capability registration.
>
> The title should reflect this.
>
>
>
> *For data model and information model definition, I think you should refer
> to RFC3444.*
>
> For NSF access information, I am wondering whether management protocol
> should also be part of access information.
>
> Regarding performance capability, I assume it is related to software or
> hardware, or firmware specification,
>
> Naming it as performance capability seems confusing to me.
>
>
>
> -Qin
>
> ---------- 전달된 메일 ----------
> 보낸사람: *Linda Dunbar* <linda.dunbar@futurewei.com>
> 날짜: 2022년 6월 11일 (토) 오전 3:13
> 제목: [I2nsf] WGLC for draft-ietf-i2nsf-registration-dm-17
> 받는사람: i2nsf@ietf.org <i2nsf@ietf.org>
>
>
>
> Hello Working Group,
>
>
>
> Many thanks to the authors of draft-ietf-i2nsf-registration-dm-17 to
> address all the comments from YANG Doctor review, SecDir review and OpsDIR
> review.
>
>
>
> This email starts a three weeks Working Group Last Call
> on draft-ietf-i2nsf-registration-dm-17
>
>
> https://datatracker.ietf.org/doc/draft-ietf-i2nsf-registration-interface-dm/
>
>
>
> This poll runs until July 1, 2021.
>
>
>
> We are also polling for knowledge of any undisclosed IPR that applies to
> this Document, to ensure that IPR has been disclosed in compliance with
> IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).
>
> If you are listed as an Author or a Contributor of this Document, please
> respond to this email and indicate whether or not you are aware of any
> relevant undisclosed IPR. The Document won't progress without answers from
> all the Authors and Contributors.
>
>
>
> If you are not listed as an Author or a Contributor, then please
> explicitly respond only if you are aware of any IPR that has not yet been
> disclosed in conformance with IETF rules.
>
>
>
> Thank you.
>
>
>
> Linda
>
>
>
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf
>
> --
>
> ===========================
> Mr. Jaehoon (Paul) Jeong, Ph.D.
> Associate Professor
>
> Department Head
> Department of Computer Science and Engineering
> Sungkyunkwan University
> Office: +82-31-299-4957
> Email: pauljeong@skku.edu, jaehoon.paul@gmail.com
> Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
> <http://cpslab.skku.edu/people-jaehoon-jeong.php>
>