Re: [I2nsf] I2NSF Drafts for Independent Submission Stream

Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com> Wed, 26 July 2023 10:22 UTC

Return-Path: <rifaat.s.ietf@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 B4D0FC151091; Wed, 26 Jul 2023 03:22:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.105
X-Spam-Level:
X-Spam-Status: No, score=-5.105 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, FREEMAIL_REPLY=1, 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_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, URI_DOTEDU=1] 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 uWFayjgYOQN0; Wed, 26 Jul 2023 03:22:44 -0700 (PDT)
Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 1D3E1C14F74A; Wed, 26 Jul 2023 03:22:44 -0700 (PDT)
Received: by mail-wr1-x435.google.com with SMTP id ffacd0b85a97d-31765aee31bso2409153f8f.1; Wed, 26 Jul 2023 03:22:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690366962; x=1690971762; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=WeWvF9M9PrZb5ahJ3uAOK2Ce+GbSh+9lWgiOyIdjBxw=; b=ASHOtHZ34DHoeCXbjTdYC4vw7odFL3Yph8+1joWpRtPTmEqCJ2ps9J8HSwQRV8n62i TL4275qzRl/JfubLzidVffOLsrtFk3q+57C1jjn6eVTvBqe1jbQgxp3SGdlCnUzGvgOJ 45bfXAi0rDLd3gjuRfIm4Vf70GlnfiFeiBD31K70zb03qDLGSaIfPA8p6cNy64y49bnh UiaaWMPF8r3sJfE/yVlgQJmen9QZHDljjFPWBpPlmx6G2obnZipGPOUZE8UXfR7OYdr4 T48Iuo4cRxvwHWjcHjx4qGbbLCAZGUMh4LA1AZ/6w76EQPqIPfuBKRMRjdOoM6OUfOCe DVvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690366962; x=1690971762; 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=WeWvF9M9PrZb5ahJ3uAOK2Ce+GbSh+9lWgiOyIdjBxw=; b=b8RJclD0LBBWiAzF/QAQrkt907JjwoTn0TfBNqvw2flq7ihwuIIPipLhKFzlkOCUo/ ilUvN6YRXSx1PyZoeWQFn/FAKB9Lfdx08ZoDqdenjkeKjhzbYt58kNeWPDFCa9GbznAs 0zipu6H28JVK0L/lRyonssMpomsL6nIHQMDqyZgh1OjnqQqz5SnCt9J3J4nku8Po7D08 l+TgWljeBE1WFQOjgcU3I4ReaFlTMqkqwAZgp85QpsF+bdJKM8AjEXSzttGqkTcB42X3 12wdK2m91oMc48PWhF8nikWke7XugEuNUqiB2ODg0e2aJjNq1X3CVqJ7IkMxd4hK0nzk Y3nw==
X-Gm-Message-State: ABy/qLawUBjXWJPw1Wcvo+SzJsKPDnROi8DTfC+GnSDMe5TEWdTa8BDs XB+kcV6wBxZf5Xtf1wM5qI3P1UW3Q6k666jWrR4OfiOv/vU=
X-Google-Smtp-Source: APBJJlFNESVDSXX1dzkEFC+3yeVyF5hdtrHWJ4ZkOCT3EPj8zEPEOpEeOaD04GHuRcfIw9XLaTMZjhUn/ayJCZ29/ao=
X-Received: by 2002:a5d:6a0c:0:b0:314:2b0a:dac7 with SMTP id m12-20020a5d6a0c000000b003142b0adac7mr1008501wru.36.1690366962206; Wed, 26 Jul 2023 03:22:42 -0700 (PDT)
MIME-Version: 1.0
References: <CAPK2Dex37mLMNTcb6aqT-DMVCjRvfdnLxexQndJD7zhmzbKsmg@mail.gmail.com> <61B52D16-EDA4-486F-9899-FE611B18DFE2@cisco.com> <89ea1507-6c08-ffee-abd0-f2ac87fbe880@rfc-editor.org> <CAPK2DeyZftNKJ9ERGv8b=kdDVYew1g-g2VDV9Q5dxa3HP9=LZw@mail.gmail.com>
In-Reply-To: <CAPK2DeyZftNKJ9ERGv8b=kdDVYew1g-g2VDV9Q5dxa3HP9=LZw@mail.gmail.com>
From: Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com>
Date: Wed, 26 Jul 2023 03:22:20 -0700
Message-ID: <CADNypP_nnT8tO7yqtmvOU5ogpT5cYLoOAC4waJ8nPrHzNdicJA@mail.gmail.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Cc: "Independent Submissions Editor (Eliot Lear)" <rfc-ise@rfc-editor.org>, Adrian Farrel <adrian@olddog.co.uk>, Roman Danyliw <rdd@cert.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>, "sec-ads@ietf.org" <sec-ads@ietf.org>, "opsawg-chairs@ietf.org" <opsawg-chairs@ietf.org>, secdispatch-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000528c130601613ad0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/4emT28wVMDfpO6HjIeTXDWn2q78>
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*" <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, 26 Jul 2023 10:22:48 -0000

On Tue, Jul 25, 2023 at 11:45 PM Mr. Jaehoon Paul Jeong <
jaehoon.paul@gmail.com> wrote:

> Hi Eliot,
> I answer your comments and questions inline below.
>
> On Tue, Jul 25, 2023 at 1:35 AM Independent Submissions Editor (Eliot
> Lear) <rfc-ise@rfc-editor.org> 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?
>>
>  => 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
> be
>    appropriable for these drafts.
>
>

I do not think that these are reasons for not to go to SecDispatch.
That's the role of SecDispatch WG; to discuss and suggest a way forward for
work that has no obvious home.

Regards,
 Rifaat





>    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.
>>
> => 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 <jaehoon.paul@gmail.com>
>> <jaehoon.paul@gmail.com> wrote:
>>
>> Hi Adrian,
>> As I told you yesterday,
>> I2NSF WG has finished all the chartered work items including the five
>> YANG 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
>> I2NSF Framework
>> . URL:
>> https://datatracker.ietf.org/doc/draft-jeong-i2nsf-security-management-automation/
>> . 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-dm/
>> . 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-translation/
>> . 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
>> --
>> ===========================
>> 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
>> <http://cpslab.skku.edu/people-jaehoon-jeong.php>
>>
>>