Re: [I2nsf] Request for Your Help on I2NSF Applicability Draft

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Wed, 06 November 2019 02:26 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 0E675120826 for <i2nsf@ietfa.amsl.com>; Tue, 5 Nov 2019 18:26:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level:
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HK_NAME_FM_MR_MRS=0.01] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZBefO2N3fLkn for <i2nsf@ietfa.amsl.com>; Tue, 5 Nov 2019 18:26:07 -0800 (PST)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97FD7120154 for <i2nsf@ietf.org>; Tue, 5 Nov 2019 18:26:06 -0800 (PST)
Received: by mail-lj1-x229.google.com with SMTP id l20so5543616lje.4 for <i2nsf@ietf.org>; Tue, 05 Nov 2019 18:26:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=C6C4c5dywtls821120fFXgoZuvbdX/9KfbCNiG/zCn4=; b=oowCv0uld0nWvGY0qaK/gdsBHsvYTWlC8SFtOUp/L5sSRqolkbzVm2ZdijO/ilp5aq 3DOB8d42UJpv/wHEbUdc7o4mdB/iXg8LOjUIlaFqaSOAI9cUS9bAsne50WYiRtUIDEY3 r+KWd0UaKxuOmgu0yIYuNVJUXRXiuX9HDQANbfAsi8c/ktV9x0oElxeIGKrAtXTcGyKN FauRPsOV3xPWLIPqcoOXNTh0FwH/nCLEmHQQKiOvfz3lYhUycAxKGoryFZYrRVqZIAyp Vn21cYvn1VsgBVwJbZw/BwQOercGOBOZirVh/Ief5DFJfKNWc7IBe6Vz70fvaNGTMrMT MpQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=C6C4c5dywtls821120fFXgoZuvbdX/9KfbCNiG/zCn4=; b=LxRPCwpUEF1EICKtaS4z4hV7wdmg9z/mxk9K1jp1s+bmTKE+rR0vH6fb0XbRHTdkfR TlHmq3i+oMaU/iQP5nneN1u/cfc4zznYdz0Io9hyPzur39Ug0WtWrc+WnD/v0vyB8ZeZ 4Kx3HlBuL0wT/qQ6ACPVKEQ0alxY8xwMHgi9pBkpKwPkMgj9HoRTgqGJgseYb7Tdwgbp c8UFkWmKCkLypzXxSxQcSE0FklS1dLZGps/NrQ5zunHdlfEMTnHC7c3MGVQfEgV2oXHi AQgFIkvoNiKsKtrfLmZ5DXhxXbnk6deiM18OPqpotYSfXeN3De1mOeZGgTZNgboGG84q AkLw==
X-Gm-Message-State: APjAAAWZhgu7wmb7hTOPEvQe/ujZRRDmwRg+33W+FKUhsZcBCDOkUuVI YrPdKRtL/qzN7W5i/6uO6TEVKX3hCO+gxuKWRs8=
X-Google-Smtp-Source: APXvYqx9Yf+wLbAfjIS80gvDpUhu1WGetnJXyuPoDgDAH7eDL6Uq4H1S6JcfOUQyfi3wRsVACE372NqDzrSRRAmJkb0=
X-Received: by 2002:a2e:854b:: with SMTP id u11mr22409437ljj.85.1573007164696; Tue, 05 Nov 2019 18:26:04 -0800 (PST)
MIME-Version: 1.0
References: <CAPK2Dex09S_A394f7uHF4FgDZc29V=vywgsZeDU0=Jm7RLTayg@mail.gmail.com> <MN2PR13MB3582A6461DDD459EDDA8F60985D30@MN2PR13MB3582.namprd13.prod.outlook.com> <CAPK2DewvpgduWCJZzRorGH73Sv2kpu8mmW8dUax5PnfxnpOfBw@mail.gmail.com> <CAPK2Dezqjsf=_KLXdwvpXOoKO7jNYUjDu3ggC=G6us=C-uqJuA@mail.gmail.com>
In-Reply-To: <CAPK2Dezqjsf=_KLXdwvpXOoKO7jNYUjDu3ggC=G6us=C-uqJuA@mail.gmail.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Wed, 6 Nov 2019 11:25:29 +0900
Message-ID: <CAPK2DexjdHJ12uf7wbDhwOz=V89A8V9zFsFggCrSnyy7gNruJA@mail.gmail.com>
To: Roman Danyliw <rdd@cert.org>, Linda Dunbar <linda.dunbar@futurewei.com>
Cc: "i2nsf@ietf.org" <i2nsf@ietf.org>, skku-iotlab-members@googlegroups.com, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000047efce0596a4451a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/o49cHx-mPAAsN-oqTzv5sAfYA-c>
Subject: Re: [I2nsf] Request for Your Help on I2NSF Applicability Draft
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Nov 2019 02:26:10 -0000

Hi Roman and Linda,
I am wondering how our I2NSF Applicability Draft is going.
I expect this draft to be approved by the IESG soon.

Thanks.

Best Regards,
Paul

On Mon, Sep 16, 2019 at 4:40 PM Mr. Jaehoon Paul Jeong <
jaehoon.paul@gmail.com> wrote:

> Hi Linda and Roman,
> I have submitted a revised I-D for I2NSF Applicability:
> https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-18
>
> According to Linda's advice, I added Security Policy Translator as a new
> section, i.e., Section 5.
> Also, I enhanced two XML files for Web Filter such as a high-level
> security policy and
> the low-level security policy using the Consumer-Facing Interface and
> NSF-Facing Interface
> data models.
>
> The main changes in this version are as follows:
>
>
>    o  In Section 4
> <https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-18#section-4>,
> a high-level security policy XML file in Figure 2
>
>       and the corresponding low-level security policy XML file Figure 3
>
>       are constructed using the Consumer-Facing Interface data model and
>
>       the NSF-Facing data model, respectively.
>
>
>    o  For the applicability of I2NSF to the real world, Section 5
> <https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-18#section-5>
> is
>
>       added to support the Intent-based Security Services using I2NSF.
>
>       This section explains the security policy translation based on an
>
>       I2NSF User's intents on the required security services.  Figure 4
>
>       shows the architecture and procedure of the I2NSF security policy
>
>       translator.
>
>
> I think this version can give the audience the applicability sense of how
> to apply the I2NSF
> to the real world.
>
> Roman,
> Could you let the IESG review this revised I-D to move it forward?
>
> Thanks.
>
> Best Regards,
> Paul
>
> 2019년 8월 14일 (수) 오전 7:24, Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>님이
> 작성:
>
>> Hi Linda,
>> It seems a good suggestion to include the Security Policy Translation
>> into the I2NSF Applicability draft as a new section.
>>
>> Roman,
>> Could you guide us how to proceed with our draft in order to penetrate
>> the IESG evaluation?
>>
>> Thanks.
>>
>> Best Regards,
>> Paul
>>
>>
>> 2019년 8월 12일 (월) 오후 2:53, Linda Dunbar <linda.dunbar@futurewei.com>님이 작성:
>>
>>> Paul,
>>>
>>>
>>>
>>> I consulted some seasoned experts in IETF community on how to make the
>>> case, Adrian Farrel’s explanation is really helpful. Making me think that
>>> the content of your Translation Draft is actually more appropriate in the
>>> Applicability draft. I am not sure if it is too late to add some content.
>>>
>>>
>>>
>>> Linda
>>>
>>> -------------------------------------
>>>
>>>
>>>
>>> *Background. *
>>>
>>>
>>>
>>> *Applicability Statements have always tried to be an explanation of how
>>> to apply a technology to a use case. This differs considerably from a
>>> statement that a use case can be solved with a technology.*
>>>
>>>
>>>
>>> *Of course, over time, a number of Applicability Statements have been
>>> published that are far more dilute. Sometimes they have been just
>>> collections of use cases to which the technology could be applied.
>>> Sometimes they have been frameworks or architectures showing how the
>>> technology fits into a picture that contains many other components and
>>> technologies.*
>>>
>>>
>>>
>>> *Sadly, we should not use past failures to justify continued failure *
>>> *😊**  I think the IESG (in general) and Alvaro (in this instance) are
>>> trying to tighten up the meaning of "Applicability Statement".*
>>>
>>>
>>>
>>> *They are looking for tighter descriptions that might also be called
>>> "implementation cookbooks". That is: to deliver this use case using the new
>>> technology, you need to use this protocol configured with these values, and
>>> you need to integrate with these other components by sending these messages
>>> and using these defaults, and you have to select these options, and you
>>> have to treat the "SHOULD" on page 27 as a "MUST". Of course, part of what
>>> you get is a framework, but a lot is implementation/deployment guidance. *
>>>
>>>
>>>
>>> *As a result, applicability statements are often quite short and
>>> technical. And (of course?) they come out after most of the specification
>>> work because they are depending heavily on that work -- after all, you
>>> can't describe how to configure and use a protocol until it has been
>>> specified. That usually means that the protocol specs are normative
>>> references from the applicability statement.*
>>>
>>>
>>>
>>> *From:* Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>
>>> *Sent:* Friday, August 09, 2019 1:27 AM
>>> *To:* Susan Hares <shares@ndzh.com>om>; DIEGO LOPEZ GARCIA <
>>> diego.r.lopez@telefonica.com>
>>> *Cc:* Roman Danyliw <rdd@cert.org>rg>; Linda Dunbar <
>>> linda.dunbar@futurewei.com>gt;; Yoav Nir <ynir.ietf@gmail.com>om>; Sangwon
>>> Hyun <swhyun77@gmail.com>om>; Tae-Jin Ahn <taejin.ahn@kt.com>om>; Mr. Jaehoon
>>> Paul Jeong <jaehoon.paul@gmail.com>
>>> *Subject:* Request for Your Help on I2NSF Applicability Draft
>>>
>>>
>>>
>>> Hi Susan and Diego,
>>>
>>> As you can see, our I2NSF Applicability Draft was discussed by the IESG
>>> yesterday.
>>>
>>> Could you help me defense our I2NSF Applicability Draft as co-authors?
>>>
>>>
>>>
>>> Since Susan and Diegou are the editor of I2NSF PS and Use Cases (RFC
>>> 8192) and
>>>
>>> the editor of I2NSF Framework (RFC 8329), respectively, your voice will
>>> be helpful.
>>>
>>>
>>>
>>> We need to appeal why this applicability draft needs to be published as
>>> an Informational RFC
>>>
>>> even though the two RFCs were published for I2NSF use cases and
>>> framework.
>>>
>>>
>>>
>>> Thanks.
>>>
>>>
>>>
>>> Best Regards,
>>>
>>> Paul
>>>
>>> --
>>>
>>> ===========================
>>> Mr. Jaehoon (Paul) Jeong, Ph.D.
>>> Associate Professor
>>> Department of Software
>>> Sungkyunkwan University
>>> Office: +82-31-299-4957
>>> Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
>>> Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
>>> <https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcpslab.skku.edu%2Fpeople-jaehoon-jeong.php&data=02%7C01%7Clinda.dunbar%40futurewei.com%7C159b4b4256fe4b94f81e08d71c92abb5%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637009288598143883&sdata=0Cj1nsqhwJ%2BCJWawKD08eH1mauR3OiD4hjIKk%2B33FyU%3D&reserved=0>
>>>
>>

-- 
===========================
Mr. Jaehoon (Paul) Jeong, Ph.D.
Associate Professor
Department of Software
Sungkyunkwan University
Office: +82-31-299-4957
Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
<http://cpslab.skku.edu/people-jaehoon-jeong.php>