Re: [I2nsf] Request for Checking I2NSF Data Models with NSF Capabilities Information Model

Cataldo Basile <cataldo.basile@polito.it> Sun, 04 November 2018 13:59 UTC

Return-Path: <cataldo.basile@polito.it>
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 067DE1200D7 for <i2nsf@ietfa.amsl.com>; Sun, 4 Nov 2018 05:59:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 WrRVvOlPEvsW for <i2nsf@ietfa.amsl.com>; Sun, 4 Nov 2018 05:59:25 -0800 (PST)
Received: from antispam.polito.it (fm1nodo1.polito.it [130.192.180.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC67D120072 for <i2nsf@ietf.org>; Sun, 4 Nov 2018 05:59:24 -0800 (PST)
Received: from polito.it (frontmail2.polito.it [130.192.180.42]) by antispam.polito.it with ESMTP id wA4DxFXN031481-wA4DxFXP031481 (version=TLSv1.0 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=CAFAIL); Sun, 4 Nov 2018 14:59:15 +0100
X-AttachExt: p7s
X-ExtScanner: Niversoft's FindAttachments (free)
Received: from [95.249.227.137] (account d011649@polito.it HELO [192.168.1.199]) by polito.it (CommuniGate Pro SMTP 6.2.5) with ESMTPSA id 81385325; Sun, 04 Nov 2018 14:59:15 +0100
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>, "Xialiang (Frank)" <frank.xialiang@huawei.com>
Cc: "i2nsf@ietf.org" <i2nsf@ietf.org>, skku_secu-brain_all@googlegroups.com
References: <CAPK2Dexg6TtcuJ5-pzoOfjOYKRH0=c=9yi-YbZf8DaGvChdXVg@mail.gmail.com>
From: Cataldo Basile <cataldo.basile@polito.it>
Message-ID: <66f6d960-5b2d-510b-8350-91b2e1006942@polito.it>
Date: Sun, 04 Nov 2018 14:59:12 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CAPK2Dexg6TtcuJ5-pzoOfjOYKRH0=c=9yi-YbZf8DaGvChdXVg@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms040703080000010708000307"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/S3a6pGSmaO5tut0R5lSOLiGeglk>
Subject: Re: [I2nsf] Request for Checking I2NSF Data Models with NSF Capabilities Information Model
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, 04 Nov 2018 13:59:28 -0000

Dear Paul,

thanks for sending references to these data models, I'll do this double 
check in depth as soon as I can, you can expect a first iteration in a 
couple of weeks.

Nevertheless, as a first glance, the models are not very well 
synchronized. Since the version 0.2, the capability model uses the 
decorator pattern. I2NSF capabilities are metadata that thus 'attached' 
to NSF via an aggregation. The documents you have referred to list 
capabilities in form of conditions, events, and actions, thus as policy 
'components' (sorry for the abuse of terminology).  However, since the 
capability model is inspired by the MEF model, these components can also 
be thought as decorations, thus, the distance between the approaches is 
not huge.

It is worth noting that several of the categories of actions, 
conditions, events you list in your data models can be made part of an 
instance of the Capability IM with limited effort.

However, you may understand I need to further expand my analysis and 
discuss with the other authors of the capability IM the formal 
implications before circulating something that can be considered an 
official report in the WG.

Regards,
Aldo


On 04/11/2018 11:40, Mr. Jaehoon Paul Jeong wrote:
> Hi Frank, Diego, Basile, andJohn,
> I have posted the revised WG documents of Data Models of I2NSF NSF 
> Capability and Interfaces.
> Could you doublecheck whether they are well-synchronized with your NSF 
> Capabilities Information Model document (draft-ietf-i2nsf-capability-04)?
> 
> - I2NSF Capability YANG Data Model
> https://tools.ietf.org/html/draft-ietf-i2nsf-capability-data-model-02
> 
> - I2NSF Network Security Function-Facing Interface YANG Data Model
> https://tools.ietf.org/html/draft-ietf-i2nsf-nsf-facing-interface-dm-02
> 
> - I2NSF Consumer-Facing Interface YANG Data Model
> https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-interface-dm-02
> 
> - I2NSF Registration Interface YANG Data Model
> https://tools.ietf.org/html/draft-ietf-i2nsf-registration-interface-dm-01
> 
> 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 <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
>