From nobody Tue Jul 25 23:45:38 2023 Return-Path: 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 18D3CC15109F; Tue, 25 Jul 2023 23:45:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.094 X-Spam-Level: X-Spam-Status: No, score=-1.094 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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] autolearn=no 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 2gqsDHmyPiSC; Tue, 25 Jul 2023 23:45:33 -0700 (PDT) Received: from mail-vk1-xa2a.google.com (mail-vk1-xa2a.google.com [IPv6:2607:f8b0:4864:20::a2a]) (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 890FAC151520; Tue, 25 Jul 2023 23:45:33 -0700 (PDT) Received: by mail-vk1-xa2a.google.com with SMTP id 71dfb90a1353d-486518f0ed4so68100e0c.3; Tue, 25 Jul 2023 23:45:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690353932; x=1690958732; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/o3ko6LewMDKlGf0dxwZlnpkMYTuQxQSx13dVYVsahM=; b=NLZp4gO20PeJuqBUPBCrlLNl6E8f6/Rhsqy8ase+bjxoQzlxLMAgCc0gaNF/EMEaOV JmGHhji9GD/0ZdLqJZUEoERkEEGAFw7Hygv49ybxJCYmvhlomNQDkjpNGKpouIJjmXZL JspAkwkpnx0fzFhzKYUw2RTLEqdDs6LJAQmZJ7wtDnVIh6HFRlv5UfB8mAC3z6Lf1t8d QpEeKiL6GdPEtey9FNc/4uGN4kSxvfI2XSRZm5UoLP1ThXGlUzim6vkrEabWCTw0Ig9f 1K00zZpu0X7o0AaRa5NeIGCcd0iqltUSaPzAEAcoSgZL0ndL24WlZNV/Lagxf+AJDvS0 l7FQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690353932; x=1690958732; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/o3ko6LewMDKlGf0dxwZlnpkMYTuQxQSx13dVYVsahM=; b=MnkkBtNKGi+0aXMYxSWnDyjkJ5FBGsTFl5RXpnUQ8K9UgpsnvlLVLv+Lm4E7C2X6b6 HXgMyx2+2GISunyKuHpfRzjf4S60Wz6LzlmSlw8X799cRhK6g7yDwiR90wmBdMlLrqYb 7c6yo0ctRQDWSAQdqXf+sbJNr1kw507kereK+YNx79gT9ps5+h9LNYrwzQZznD3MQQlS cbaS3C42Q5Rok6CdDRy6gIeKToC9o4grvDlN7GfkR2W2pSx7iUBhWj+SlywnFkjbBBPH C98D9gDaXgpNCvrsrMADSJI6H/ZXH4S1FL2tO2+a4xboxy4yJ0rxSbFZgWGwrkuivak/ 8/Cg== X-Gm-Message-State: ABy/qLZ9RJRaTu3r3Nw+EaUpy+71FBwFQmt9CeClZp/OfHv0V7ISgW1M MqH0afTXDgQDsX3tw5oa3MfXXbZ5aIM0V5S0rJ4= X-Google-Smtp-Source: APBJJlGWH+C4ycuHJEOkV4JUec7YS28bUXKY5xHLG7qQYNYzcT75eYTtezDTs4j72VjJhmYYV03+zGZM+GcpRClzn+8= X-Received: by 2002:a1f:5e96:0:b0:486:4686:5a76 with SMTP id s144-20020a1f5e96000000b0048646865a76mr801227vkb.14.1690353932127; Tue, 25 Jul 2023 23:45:32 -0700 (PDT) MIME-Version: 1.0 References: <61B52D16-EDA4-486F-9899-FE611B18DFE2@cisco.com> <89ea1507-6c08-ffee-abd0-f2ac87fbe880@rfc-editor.org> In-Reply-To: <89ea1507-6c08-ffee-abd0-f2ac87fbe880@rfc-editor.org> From: "Mr. Jaehoon Paul Jeong" Date: Tue, 25 Jul 2023 23:44:55 -0700 Message-ID: To: "Independent Submissions Editor (Eliot Lear)" Cc: Adrian Farrel , Roman Danyliw , "i2nsf@ietf.org" , "sec-ads@ietf.org" , "opsawg-chairs@ietf.org" , secdispatch-chairs@ietf.org, "Mr. Jaehoon Paul Jeong" Content-Type: multipart/alternative; boundary="000000000000ab52b506015e31b3" Archived-At: Subject: Re: [I2nsf] I2NSF Drafts for Independent Submission Stream X-BeenThere: i2nsf@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: "*I2NSF: Interface to Network Security Functions mailing list*" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jul 2023 06:45:38 -0000 --000000000000ab52b506015e31b3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Eliot, I answer your comments and questions inline below. On Tue, Jul 25, 2023 at 1:35=E2=80=AFAM Independent Submissions Editor (Eli= ot Lear) wrote: > Hi Paul and thanks for contacting me, and thanks Adrian. Before we > proceed further, it may be desirable to either SECDISPATCH > or present to OPSAREA these works back into the IETF. > Has that been discussed? > =3D> These three I2NSF drafts were discussed in the I2NSF WG in the past. However, since their topics were out of scope of the I2NSF WG, they could not be adopted by the I2NSF WG. Even though I tried to proceed with the standardization of those drafts through the rechartering of the I2NSF WG, the rechartering was declined by Roman Danyliw, who is a SEC AD, due to the low energy of the I2NSF WG. Roman also declined to shepherd them as an AD sponsor in the case of Independent Submission Stream due to some reasons announced to the I2NSF WG. By this background, I think that the discussion in SECDISPATCH may not b= e appropriable for these drafts. OPSAWG may be appropriable for these drafts since they are related to operations and management for the closed-loop security control by the I2NSF framework. However, many active WG documents are handled and overloaded by OPSAWG, I am afraid that these drafts cannot be discussed and handled by OPSAWG. > > A working group closure on its own should not preclude further IETF work. > Also, you may wish to present this work to iotops if you have not already > done so. > =3D> Thanks for your encouragement on these drafts. IOTOPS handles the issues related to IoT devices, so these drafts may not be interesting to IOTOPS because these I2NSF drafts are related to the virtualized security functions for cloud-based security service systems. I believe that Adrian will be able to suggest a good way for these drafts after his review on these drafts after this IETF 117. I CC Roman Danyliw who was the responsible AD of the I2NSF WG since he may give us his more opinions. Thanks. Best Regards, Paul Eliot (ISE) > > On 25 Jul 2023, at 09:33, Mr. Jaehoon Paul Jeong > wrote: > > Hi Adrian, > As I told you yesterday, > I2NSF WG has finished all the chartered work items including the five YAN= G > data model drafts recently, > and it is concluded now: > https://datatracker.ietf.org/wg/i2nsf/about/ > > However, to deploy the I2NSF framework and interfaces in the industry, > the following three drafts will be quite useful: > > - Security Management Automation of Cloud-Based Security Services in I2NS= F > Framework > . URL: > https://datatracker.ietf.org/doc/draft-jeong-i2nsf-security-management-au= tomation/ > . Summary: This draft proposes an extension of the I2NSF framework for > closed-loop > security control in Intent-Based Networking (IBN). It suggests a new > component called > I2NSF Analyzer and a new interface called Analytics Interface. > . Purpose: Informational RFC > > - I2NSF Analytics Interface YANG Data Model > . URL: > https://datatracker.ietf.org/doc/draft-lingga-i2nsf-analytics-interface-d= m/ > . Summary: This draft proposes an Analytics Interface YANG Data Model to > deliver either > policy reconfiguration or feedback information from I2NSF Analyzer to > Security > Controller. > . Purpose: Experimental RFC > > - Guidelines for Security Policy Translation in Interface to Network > Security Functions > . URL: > https://datatracker.ietf.org/doc/draft-yang-i2nsf-security-policy-transla= tion/ > . Summary: This draft proposes the guidelines for security policy > translation > in the I2NSF framework, that is, the translation from a high-level > security policy > to the corresponding low-level security policy. It focuses on the > mapping between > Consumer-Facing Interface and Network Security Function (NSF)-Facing > Interface. > > The basic concepts of these works are proved through the I2NSF Hackathon > Projects. > The open-source I2NSF hackathon project is located at the Github: > https://github.com/jaehoonpaul/i2nsf-framework > > I would like to submit those three drafts to the IETF independent > submission stream this week: > https://www.rfc-editor.org/about/independent/ > > If you have comments on this matter, please let us know. > > I CC Eliot Lear who is the Independent Submissions Editor (ISE) in the > IETF. > > Thanks for your support. > > Best Regards, > Paul > -- > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D > Mr. Jaehoon (Paul) Jeong, Ph.D. > Associate Professor > 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 > > > --000000000000ab52b506015e31b3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Eliot,
I answer your comments and = questions inline below.

On Tue, Jul 25, 2023 at 1:35=E2=80=AFAM Indep= endent Submissions Editor (Eliot Lear) <rfc-ise@rfc-editor.org> wrote:
=20 =20 =20

Hi Paul and thanks for contacting me, and thanks Adrian.=C2=A0 Befor= e we proceed further, it may be desirable to either SECDISPATCH

or present to OPSAREA these works back into the IETF.=C2=A0=C2=A0

H= as that been discussed?=C2=A0=C2=A0

=C2=A0=3D> These= three I2NSF drafts were discussed in the I2NSF WG in the past.
=C2=A0= =C2=A0However, since their topics were out of scope of the I2NSF WG, they = could not
=C2=A0 =C2=A0be adopted by the I2NSF WG.
=C2=A0 =C2=A0Even = though I tried to proceed with the standardization of those drafts
=C2= =A0 =C2=A0through the rechartering of the I2NSF WG, the rechartering was de= clined by
=C2=A0 =C2=A0Roman Danyliw, who is a SEC AD, due to the low en= ergy of the I2NSF WG.
=C2=A0 =C2=A0Roman also declined to shepherd them = as an AD sponsor in the case of
=C2=A0 =C2=A0Independent Submission Str= eam due to some reasons announced to the I2NSF WG.
=C2=A0 =C2=A0By this = background, I think that the discussion in SECDISPATCH=C2=A0may not be
= =C2=A0 =C2=A0appropriable for these drafts.
=C2=A0 =C2=A0
=C2=A0 =C2= =A0OPSAWG may be appropriable for these drafts since they are related to=C2=A0 =C2=A0operations and management for the closed-loop security contro= l by the I2NSF
=C2=A0 =C2=A0framework.
=C2=A0 =C2=A0However, many act= ive WG documents are handled and overloaded by OPSAWG,
=C2=A0 =C2=A0I am= afraid that these drafts cannot be discussed and handled by OPSAWG.=C2=A0<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">

A working group cl= osure on its own should not preclude further IETF work.=C2=A0

Also, you may wish to present this work= to iotops if you have not already done so.

=3D= > Thanks for your encouragement on these drafts.
=C2=A0 =C2=A0IOTOPS = handles the issues related to IoT devices, so these drafts
=C2=A0 =C2= =A0may not be interesting to=C2=A0IOTOPS because these I2NSF drafts are rel= ated to
=C2=A0 =C2=A0the virtualized security functions for cloud-based = security service systems.

=C2=A0 =C2=A0I believe that Adr= ian will be able to suggest a good way for these drafts after his review on=
=C2=A0 =C2=A0these drafts after this IETF 117.

=C2=A0 =C2=A0I CC Roman Danyli= w who was the responsible AD of the I2NSF WG since he may give
=C2=A0 =C2=A0us his more opinions.

=C2=A0 =C2=A0= Thanks.

=C2=A0 =C2=A0Best Regards,
=C2=A0 =C2=A0Paul
=C2= =A0

<= div>

Eliot (ISE)
On 25 Jul 2023, at 09:33, Mr. Jaehoon Paul Jeong <= ;jaehoon.paul@gmail.com> wrote:

=20
Hi Adrian,
As I told you yesterday,
I2NSF WG has finished all the chartered work items including=C2=A0the five YANG data model drafts recently,=C2= =A0
and it is concluded now:

However, to deploy the I2NSF framework and interfaces in the industry,=C2=A0
the following three drafts will be quite useful:

- Security Management Automation of Cloud-Based Security Services in I2NSF Framework
. URL: https://data= tracker.ietf.org/doc/draft-jeong-i2nsf-security-management-automation/<= br> . Summary: This draft proposes an extension of the I2NSF framework for closed-loop
=C2=A0 security control in Intent-Based Networking (IBN). It suggests a new component called
=C2=A0 I2NSF Analyzer and a new interface called Analytic= s Interface.
. Purpose: Informational RFC

- I2NSF Analytics Interface YANG Data Model
. URL: https://datatracker= .ietf.org/doc/draft-lingga-i2nsf-analytics-interface-dm/
. Summary: This draft proposes an Analytics Interface YANG Data Model to deliver either
=C2=A0 policy reconfiguration or feedback information fro= m I2NSF Analyzer to Security
=C2=A0 Controller.
. Purpose: Experimental RFC

- Guidelines for Security Policy Translation in Interface to Network Security Functions
. URL: https://datatrac= ker.ietf.org/doc/draft-yang-i2nsf-security-policy-translation/
. Summary: This draft proposes the guidelines for security policy translation
=C2=A0 =C2=A0in the I2NSF framework, that is, the transla= tion from a high-level security policy
=C2=A0 =C2=A0to the corresponding low-level security poli= cy. It focuses on the mapping between
=C2=A0 =C2=A0Consumer-Facing Interface and Network Securi= ty Function (NSF)-Facing Interface.
=C2=A0 =C2=A0
The basic concepts of these works are proved through the I2NSF Hackathon Projects.
The open-source I2NSF hackathon project is located at the Github:
https://github.com/jaehoonpaul/i2nsf-framework

I would like to submit those three drafts to the IETF independent submission stream this week:
https://www.rfc-editor.org/about/independent/

If you=C2=A0have comments on this=C2=A0matter, please let= us know.

I CC Eliot Lear who is the Independent Submissions Editor (ISE) in the IETF.

Thanks for your support.

Best Regards,
Paul
--
=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Mr. Jaehoon (Paul) Jeong, Ph.D.
Associate Professor
Department of Computer Science and Engineering
Sungkyunkwan University
Office: +82-31-299-4957
Email: pauljeong@skku.edu,=C2= =A0jaehoon.paul= @gmail.com
Personal Homepage: http://iotlab.skku.ed= u/people-jaehoon-jeong.php

--000000000000ab52b506015e31b3--