Re: [I2nsf] need more review and support to close the WGLC for draft-ietf-i2nsf-consumer-facing-interface-dm

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Mon, 08 August 2022 10:43 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 EDF5DC157B47 for <i2nsf@ietfa.amsl.com>; Mon, 8 Aug 2022 03:43:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.084
X-Spam-Level:
X-Spam-Status: No, score=-7.084 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, 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] 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 EW6jjbwBIHWf for <i2nsf@ietfa.amsl.com>; Mon, 8 Aug 2022 03:43:04 -0700 (PDT)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (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 19306C157B36 for <i2nsf@ietf.org>; Mon, 8 Aug 2022 03:43:04 -0700 (PDT)
Received: by mail-pf1-x436.google.com with SMTP id z187so7713524pfb.12 for <i2nsf@ietf.org>; Mon, 08 Aug 2022 03:43:04 -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=Atg2iglOTgGQxMsgVu57RSZb414tXafQiam8W/la13E=; b=K+VkKHk+VVxgIXwTxokQgVoaTvypgXEg+2fm73GFoUj2aJbyHjNThgf3t1Yrn6M98A O7alxEyK+tuOQwUsJRpskBKjjvraERFmkzl7+pAm7uuV5tbQHfWSyxHncSyWnj/H2tne 9SaK0r+h2ZmoEG637aaW2bIInu7XLPZemOXzzZQNeREV9PCYy9Mg6XtFQRb0/V+a2sVd W3zXKtxKDFXOIjigs19L9GWNhMHUTiOK6MeNRrvPBnSEV3xydLDl9dNT1HGBmlAfRfOV NdimM5dXN8CkYcR2OYM2BruEmS2G08ViHlWS2HM43FLvRsupeEB0U80CWzsiDfbeMf28 JC2w==
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=Atg2iglOTgGQxMsgVu57RSZb414tXafQiam8W/la13E=; b=UuQoNRX8Ju8k40DDpU3v85rve2VnC93V2xk7I7zz1aHJUt2I90GzkBxKWC0ePyEZk5 YSBOoJExxU/IdLyyEbDccTBh1tXotPIp3FuUGj4u9H9orcY0R+DnCab/61ZSrHLcQyYZ PkNUjBIgVcsdwu6rR+NY595LR0YBoZrGtSaPyLOCDn2alOGwkYh/ifBAzqvyJVKAa7ql dsiIIIhQ4m/Gulc+UMnjQogFAtj6N4X+RnSqNF4ryXJ+BaO6TT8s1yPAHza2X6IKLs4R im9Fuazue6959reagKBBQg0jf2nyszYW6IGFuzT1Ae79wWbe4m5KVz+1x6KKwAzbHJ3c BYNg==
X-Gm-Message-State: ACgBeo29VPH6LXJJlxJkrXq9AKN8VwQnZYk6xBXfazR7CYRtG18jOT7W qTB+5hX82Bx/DWv2dpVqcCYC0IhPDUNjGVt1o68=
X-Google-Smtp-Source: AA6agR5076K4ESReRsyg0qjOJYB5q/hbfJuMWCwP7CKWHFurbVSOZMH3ZKANQjcjC7TYZtq0pnegfqt6GKp04772HQM=
X-Received: by 2002:a63:1e09:0:b0:41d:a570:96bc with SMTP id e9-20020a631e09000000b0041da57096bcmr901256pge.78.1659955383084; Mon, 08 Aug 2022 03:43:03 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR13MB49200B723C19BDC266EA98EC85869@CO1PR13MB4920.namprd13.prod.outlook.com> <BYAPR08MB487221C91BF204B34F337304B3869@BYAPR08MB4872.namprd08.prod.outlook.com> <CO1PR13MB4920C96E21FDD1536B27A0A685869@CO1PR13MB4920.namprd13.prod.outlook.com> <62EAA528.1070405@btconnect.com>
In-Reply-To: <62EAA528.1070405@btconnect.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Mon, 08 Aug 2022 19:42:10 +0900
Message-ID: <CAPK2Dezc3UVfDn1pHAeN449yJjym=M0JYh1TTG61JtXDFBYU=A@mail.gmail.com>
To: t petch <ietfa@btconnect.com>
Cc: Roman Danyliw <rdd@cert.org>, Linda Dunbar <linda.dunbar@futurewei.com>, Susan Hares <shares@ndzh.com>, "i2nsf@ietf.org" <i2nsf@ietf.org>, tom petch <daedulus@btconnect.com>, skku-iotlab-members <skku-iotlab-members@googlegroups.com>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/mixed; boundary="000000000000f3f16c05e5b87aae"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/9XiZQvDhmnHqkru4Ml_VLLd5K10>
Subject: Re: [I2nsf] need more review and support to close the WGLC for draft-ietf-i2nsf-consumer-facing-interface-dm
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: Mon, 08 Aug 2022 10:43:05 -0000

Hi Tom,
Here is the revision of CFI with your comments:
https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-consumer-facing-interface-dm-23

Patrick and I have reflected your comments on the revision, and
I attach the revision letter.

Thanks.

Best Regards,
Paul

On Thu, Aug 4, 2022 at 1:40 AM t petch <ietfa@btconnect.com> wrote:

> On 12/07/2022 18:44, Linda Dunbar wrote:
> > Sue,
> >
> > Thank you very much for the offer.
> >
> > The unsolved comments are from Tom Petch: Re: [I2nsf] WGLC for
> draft-ietf-i2nsf-consumer-facing-interface-dm-16<
> https://mailarchive.ietf.org/arch/msg/i2nsf/d_Wk5fH35Jo_cdz4D0QZN5VNhFA/>
> > There are several responses to address Tom Petch's comments. Just Tom
> hasn't sent feedback if he is satisfied with the response.
>
> Weelll, probably as satisfied as I am going to get.
>
> I have reviewed cfi (customer facing interface-dm)-22 and compared some
> of it with capability-32.  I have not - but hope to - compare against
> nsf-facing; nor have I re-read all the posts to the list but will.
>
> I do think that cfi is now in much better shape.  I do see capability as
> the key, the base, set of definitions against which the others should be
> judged.  capability says whether or not the box can do it, the others
> tell you how to do it.
>
> With that in mind, I am unconvinced about the response to my comments
> about icmp.  The treatment is different.  capability deals in
> icmpv4/icmpv6, type/code; cfi deals in echo/echo-reply which is the sort
> of user interface I am used to and would expect a security practitioner
> to be familiar with so some words about the mapping, referring to the
> IANA website for all the detail, could help users.  I would put that in
> the body of the text not the YANG module
>
> Likewise, cfi has primary and secondary action which makes a lot of
> sense but what is the capability that makes that possible? capability
> has ingress-action, egress-action, default-action which seems a
> different axis to me.  Again, some words about how the two relate could
> help, in the body of the document.
>
> Again continent is present in cfi but not in capability.  Can a user
> tell if the capability is present?  I expect not; as ever, worth a note.
>
> signature-set and signature-type sound the same but seem different.
> This is an aspect of security that I am not familiar with, at least not
> in those terms.
>
> Finally, there are some minor editorial glitches.
>
> RFC8075 I see in the YANG module; it needs adding to the I-D References.
>
> page 17 text version last sentence I cannot parse; perhaps a missing
> preposition
>
> the two rate-limit objects could do with units - I note that they are
> present in the examples
>
> page 55 text version [STIX] looks like an XML anchor but YANG modules
> must be plain text.
>
> Tom Petch
>
> >
> > Linda
> >
> > From: Susan Hares <shares@ndzh.com>
> > Sent: Tuesday, July 12, 2022 12:21 PM
> > To: Linda Dunbar <linda.dunbar@futurewei.com>; i2nsf@ietf.org
> > Subject: RE: [I2nsf] need more review and support to close the WGLC for
> draft-ietf-i2nsf-consumer-facing-interface-dm
> >
> > Linda:
> >
> > I will review the document by  Thursday (7/14) and send in a review of
> the document.   Would you let me know what WG LC comments were not
> addressed?
> >
> > Cheers, Sue
> >
> > From: I2nsf <i2nsf-bounces@ietf.org<mailto:i2nsf-bounces@ietf.org>> On
> Behalf Of Linda Dunbar
> > Sent: Tuesday, July 12, 2022 1:17 PM
> > To: i2nsf@ietf.org<mailto:i2nsf@ietf.org>
> > Subject: [I2nsf] need more review and support to close the WGLC for
> draft-ietf-i2nsf-consumer-facing-interface-dm
> >
> >
> > I2NF WG,
> >
> > draft-ietf-i2nsf-consumer-facing-interface-dm WGLC was inconclusive due
> to lack of support and some LC comments not properly addressed. There
> appeared to be limited reviews of the document during the WGLC
> > See the discussion history: [I2nsf] WGLC for
> draft-ietf-i2nsf-consumer-facing-interface-dm-16<
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fi2nsf%2FMFOohjnJ9fbylLB9eyccMRhrp04%2F&data=05%7C01%7Clinda.dunbar%40futurewei.com%7Cc95feb0ac382419474b808da642adfd0%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637932432560667469%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=f9Jlz0HgQw7NO%2BKer356WyaN9toprO8WCPEUBGhkAXI%3D&reserved=0
> >
> >
> > To proceed to publication more reviews and support from the WG for
> publication is needed.
> > We really appreciate more people reviewing the document, especially the
> people who are not the authors.
> >
> > Thank you
> > Linda Dunbar
> >
> >
> >
> > _______________________________________________
> > I2nsf mailing list
> > I2nsf@ietf.org
> > https://www.ietf.org/mailman/listinfo/i2nsf
> >
>
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf
>