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

"Mr. Jaehoon Paul Jeong" <> Mon, 16 September 2019 07:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 016D212083A for <>; Mon, 16 Sep 2019 00:40:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.988
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id HnsZdW681AyR for <>; Mon, 16 Sep 2019 00:40:46 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::42b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 12463120843 for <>; Mon, 16 Sep 2019 00:40:46 -0700 (PDT)
Received: by with SMTP id h7so36700558wrw.8 for <>; Mon, 16 Sep 2019 00:40:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZAgjkrqVRpGbgBadex0hU7I/lHy1Matr3Iqmal7hbb8=; b=V/zwqBzCcTJT0dcllsuIzHnzZV05t60Vr2wuOLv8B5h4aQLaHbsDVTTcMB0JUCsgMm 47H+rAOoqE4e+aK0I4E+E5sk9B/f4qFmxYVhPFlCu9VLtZYBNr6DTz7scdF06lJRkDf4 Ivr2d36ti++vAzf2BQ3ylZjeuhelJgVBMW01nYT89dLDfzoWQupB60H8FOI/OB5unBok +W7dbkvxakvFDL0VLLSUS2QuoWyvOu2NJyGrSlMmBI+5Dyhw2kH0dt2m5BhyTJRL9mY5 puoaKMMZZqrgmFUcvMYg57RJaTHZfLGY16dTYPvbP5bLHlCla8gZdGoRDUS1a+FtIamJ gkUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZAgjkrqVRpGbgBadex0hU7I/lHy1Matr3Iqmal7hbb8=; b=IOn/fBjUdvbAjrVvkFApMilhzVLp+kV3S9lnohmnEZkM0ETAz3rkT9cHG+Ln0+zJwh PFKWHcGpG3DHOfNwT0hyHf53hSbfLMmJrbF8eDnHH8TWP3DyLpzA5ONueWeY2htNxQx8 q62iarNWIRoywJ7kA7LC7UZFDh33gXPSjus7hbz6vqewnt7KX6OKbT9NApg1BtprPlfB 7dIFkPQbpBOC9yUPnTj6A6NndIKVLI34BoW4x2BYMfq5Lh6CdS+2cGh3kWHa8UQVId8Y HxaP3jPzsTM6me8rvEFSNDNklDQtyFczmy8hcJndRf9IxqKXpUaYE79tjt/9Fi48Z3ph WIfA==
X-Gm-Message-State: APjAAAX69NI5EuFkOMstoYf05VS1csr7OBgurzI6WLbFOXMdsXgu8R5S tdOQnmVzrLBn+MRMbr2CJU0c4C4vCOTkU9DFom0=
X-Google-Smtp-Source: APXvYqzCpX6exetQhoCK6SBHf5PWJc0Gh7LijpTJ0X7MgieCOi6fctrkXBlmpaDQvifZnHudNCcWXKeL3zOjD9KfQ1Q=
X-Received: by 2002:a5d:500b:: with SMTP id e11mr43653937wrt.285.1568619644180; Mon, 16 Sep 2019 00:40:44 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <>
In-Reply-To: <>
From: "Mr. Jaehoon Paul Jeong" <>
Date: Mon, 16 Sep 2019 16:40:08 +0900
Message-ID: <>
To: Linda Dunbar <>, Roman Danyliw <>
Cc: "" <>,, "Mr. Jaehoon Paul Jeong" <>
Content-Type: multipart/alternative; boundary="000000000000adde080592a6b80f"
Archived-At: <>
Subject: Re: [I2nsf] Request for Your Help on I2NSF Applicability Draft
X-Mailman-Version: 2.1.29
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: Mon, 16 Sep 2019 07:40:57 -0000

Hi Linda and Roman,
I have submitted a revised I-D for I2NSF Applicability:

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
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
<> 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


I think this version can give the audience the applicability sense of how
to apply the I2NSF
to the real world.

Could you let the IESG review this revised I-D to move it forward?


Best Regards,

2019년 8월 14일 (수) 오전 7:24, Mr. Jaehoon Paul Jeong <>님이

> 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 <>님이 작성:
>> 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 <>
>> *Sent:* Friday, August 09, 2019 1:27 AM
>> *To:* Susan Hares <>om>; DIEGO LOPEZ GARCIA <
>> *Cc:* Roman Danyliw <>rg>; Linda Dunbar <
>>>gt;; Yoav Nir <>om>; Sangwon
>> Hyun <>om>; Tae-Jin Ahn <>om>; Mr. Jaehoon
>> Paul Jeong <>
>> *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:,
>> Personal Homepage:
>> <>