Re: [I2nsf] WG scope follow-up

양현식 <yangun@dcn.ssu.ac.kr> Sun, 28 July 2019 14:08 UTC

Return-Path: <yangun@dcn.ssu.ac.kr>
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 B78551200B5 for <i2nsf@ietfa.amsl.com>; Sun, 28 Jul 2019 07:08:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FROM_EXCESS_BASE64=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dcn-ssu-ac-kr.20150623.gappssmtp.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 So_xpySCXvJV for <i2nsf@ietfa.amsl.com>; Sun, 28 Jul 2019 07:08:20 -0700 (PDT)
Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (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 26EA81200B4 for <i2nsf@ietf.org>; Sun, 28 Jul 2019 07:08:19 -0700 (PDT)
Received: by mail-pf1-x429.google.com with SMTP id y15so26681607pfn.5 for <i2nsf@ietf.org>; Sun, 28 Jul 2019 07:08:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dcn-ssu-ac-kr.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=4Onh2OfOc1SVqjP0iKYPOfv19oWlScrp0HvmTpWpQRY=; b=Bc+VPdUuJoZdP49OAuSswHTcJ01HYb6HXRp7Fg/4lF/vm3Fqck7gJQjbYKileCTgXN F4eKi1E3Rh97CBCC6E5A9dSfP/S0J90/6s3Vjsg9VTETvg0ylhXYc7baPnqI64GBzfO9 dHXcNxT14jLprUwHqRSk7ZYUlasHuhZxn+0Ux2OrHLL9R/uigvQuH095W7VULx5lGDl8 5tLHJMU7J/AxvLQwXx/nGuTClGT6Abaa8w4U1jID/eHFRlXT5rhS6ZWzfbZYMiUDzPE/ G5w527Cju2jJBf+2E6AEOjAF8VXMHktBjpR3ge43O7ckJ/8gW07ZVYynMHmo/KFkMJU2 pI5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=4Onh2OfOc1SVqjP0iKYPOfv19oWlScrp0HvmTpWpQRY=; b=ffPMAq4oivJt5rMsgRfvTcKmLejQ485OFKNG1WOc+6iNYt+A+N2fqyMeCVoruLlOjg OA+r3xn0k0QcOa0kYZMrc0gFENRYmTJXcJSaDzLPhgkvHDvjVtyFQU21+mXFiV8v7KjR voSsGAzYPQhe7pClvZHrqgiBHDkwDxDs19GdFv7xiHxcPyCLSSdMctEg2S7vLfRjr5uw NO6ZUUFm2Uuk2+TSOEWmF3T9JdGelSpEP7oiepjx7CjeGDhbj1/Q2anv42h990Fe1Bp9 MWW8uTNK9VsaCGCqZGybR2QTOBWlPEz9YwUtWfD4KtU/OnVvMv18fP3wZ28RLu+FKLVS 0DnQ==
X-Gm-Message-State: APjAAAXpgHCa/jub3Urkiae9NfN/LQZY3cBc90nORAfKNb8V4gEbYsMh aS6B4t8mC0+tFC58z0+S6+2mXkUS
X-Google-Smtp-Source: APXvYqw/spW7U0YzZY+d/RBJ6NFkH5usHNG7hGygJSnY8pKUslQbs0ITl/Hl2p6/tTRQ2Rg1WCSVpw==
X-Received: by 2002:a17:90a:ad86:: with SMTP id s6mr108019962pjq.42.1564322898870; Sun, 28 Jul 2019 07:08:18 -0700 (PDT)
Received: from [192.168.1.100] ([221.138.10.201]) by smtp.gmail.com with ESMTPSA id z19sm50986441pgv.35.2019.07.28.07.08.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 28 Jul 2019 07:08:17 -0700 (PDT)
From: 양현식 <yangun@dcn.ssu.ac.kr>
Message-Id: <CC40C7C0-9AB0-4983-A7D3-4D9940F506A1@dcn.ssu.ac.kr>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5D21C5BC-A8A6-4A2D-84CB-A5961C52C69E"
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Date: Sun, 28 Jul 2019 23:10:10 +0900
In-Reply-To: <CAPK2DezL4_DrinvkZEp3jMfz27EBB6tdEyX9iuFABLXBk+LrJA@mail.gmail.com>
Cc: Roman Danyliw <rdd@cert.org>, skku_iotlab_seminar@googlegroups.com, skku_secu-brain_all@googlegroups.com, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
To: "i2nsf@ietf.org" <i2nsf@ietf.org>
References: <359EC4B99E040048A7131E0F4E113AFC01B33E96A6@marchand> <CAPK2DezL4_DrinvkZEp3jMfz27EBB6tdEyX9iuFABLXBk+LrJA@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/H2YE79yHv5UmMtbcc7I3g193oSk>
Subject: Re: [I2nsf] WG scope follow-up
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: Sun, 28 Jul 2019 14:08:24 -0000

+1 
Hi. I am Hyunsik Yang. I joined I2NSF hackathon from IETF102 to IETF105  and I am an author of NFV draft. 

I agree with Paul's opinion based on my experience of I2NSF Hackathon.

 In order to use I2NSF in a real environment, I think we should  provide a document for guidelines on how to use it in addition to the basic framework. Although the document couldn't reflect all use cases, I think we can provide a basic direction to user who use I2NSF Framework. Therefore,  security policy translator draft also can be a good guideline.

 In addition, from an implementation point of view, I think current interface is not enough since it only deal with internal interface. We also need to define additional interfaces or information model to use I2NSF in real world such as interface for VNFM and SFC controller. I knew that this is not part of the current I2NSF WG scope, but, if I2NSF WG is going to re-chartering phase, I think it is necessary to add those item to re-chartering.


> 2019. 7. 26. 오후 12:40, Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com> 작성:
> 
> Hi Roman and I2NSF WG,
> Though the system components of the I2NSF system (e.g., security policy translator) are not in the scope of 
> I2NSF WG, key components such as I2NSF User, Security Controller, and Developer's Management System (DMS) 
> need standard documents to let developers and operators grasp what information and parameters are required and 
> exchanged among those components.
> 
> Those documents can be published as Informational RFCs to provide the developers and operators with
> the guidelines to build their own components interoperable with other components in the I2NSF system. 
> 
> For an example, the security policy translation draft provides the audience with such guidelines
> in terms of the design of implementation of their own security policy translator.
> https://tools.ietf.org/html/draft-yang-i2nsf-security-policy-translation-04 <https://tools.ietf.org/html/draft-yang-i2nsf-security-policy-translation-04>  
>  
> To let the security policy translator perform security policy translation, it requires 
> the relationship between the consumer-facing interface and the nsf-facing interface data models.
> This document explains such relationship (or mapping) between the two interfaces.
> With the explicit representation of such a mapping, the developers need to figure it out. 
> It will be time-consuming and may mislead them.
> 
> It also explains what information (e.g., IP addresses of a user's devices and website URLs) should 
> be populated into the NSF database for security policy translation in the Security Controller.
> This information needs to delivered from the I2NSF User to the Security Controller.
> Assuming that the I2NSF User and the Security Controller are developed by two different operators and vendors,
> an interface between them should be standardized for interoperability.
> As said during today's WG session, this security policy translation draft will target at an Informational RFC.
> 
> For another example, the draft of I2NSF on NFV reference architecture provides the operators and 
> developers with the guidelines of how to build the I2NSF system on the NFV architecture.
> https://tools.ietf.org/html/draft-yang-i2nsf-nfv-architecture-05 <https://tools.ietf.org/html/draft-yang-i2nsf-nfv-architecture-05>  
> 
> The draft explains the initial configuration procedure in NFV architecture.
> When a proper NSF is not activated yet in the I2NSF system, the Security Controller 
> sends an NSF initiation request to the DMSs which has (or may have) the required NSF, 
> as shown in Figure 2 in the draft.
> In this case, the DMS sends an NSF initiation request  to the VNF Manager (VNFM) using the Ve-Vnfm interface 
> that is an ETSI NFV interface. This DMS NSF initiation request should be specified by 
> the I2NSF system. This draft will describe the contents and format of the request in 
> the next revision. Thus, this will help the vendors and operators easily implement the I2NSF
> in the NSF architecture.
> 
> During the last 9 I2NSF hackathon projects, my team recognized the necessity of 
> the drafts for the functionality and parameters of the I2NSF system components. 
> I believe that these drafts will accelerate the development and development of 
> I2NSF in the real world.
> 
> I think our I2NSF WG needs to recharter toward the second phase. 
> 
> Thanks.
> 
> Best Regards,
> Paul
> 
> 
> On Thu, Jul 25, 2019 at 4:45 PM Roman Danyliw <rdd@cert.org <mailto:rdd@cert.org>> wrote:
> Hello!
> 
> During today's F2F meeting, we discussed the need to check the charter scope of the work proposed in draft-yang-i2nsf-security-policy-translation.  Making no value judgement on the utility of the work, in my review of the current charter, this class of work is not in scope.  The current charter doesn't currently cover standardization activity inside the NSF/DMS/controller.
> 
> If the WG wants to re-charter, by all means, let's have that conversation.
> 
> Roman
> 
> 
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org <mailto:I2nsf@ietf.org>
> https://www.ietf.org/mailman/listinfo/i2nsf <https://www.ietf.org/mailman/listinfo/i2nsf>
> 
> 
> -- 
> ===========================
> Mr. Jaehoon (Paul) Jeong, Ph.D.
> Associate Professor
> Department of Software
> Sungkyunkwan University
> Office: +82-31-299-4957
> Email: jaehoon.paul@gmail.com <mailto:jaehoon.paul@gmail.com>, pauljeong@skku.edu <mailto:pauljeong@skku.edu>
> Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php <http://cpslab.skku.edu/people-jaehoon-jeong.php>
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf