[I2nsf] Berlin I2NSF F2F meeting agenda consideration, and how to align mutliple drafts on the "Customer Facing Interface" and "NSF facing interface"

Linda Dunbar <linda.dunbar@huawei.com> Fri, 08 July 2016 15:45 UTC

Return-Path: <linda.dunbar@huawei.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 98E6312D1DE for <i2nsf@ietfa.amsl.com>; Fri, 8 Jul 2016 08:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.646
X-Spam-Level:
X-Spam-Status: No, score=-5.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-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 k-XCxTSK02AV for <i2nsf@ietfa.amsl.com>; Fri, 8 Jul 2016 08:45:48 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C6EF12D79B for <I2NSF@ietf.org>; Fri, 8 Jul 2016 08:45:46 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CNJ13368; Fri, 08 Jul 2016 15:45:44 +0000 (GMT)
Received: from DFWEML702-CAH.china.huawei.com (10.193.5.176) by lhreml707-cah.china.huawei.com (10.201.5.199) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 8 Jul 2016 16:45:44 +0100
Received: from DFWEML501-MBB.china.huawei.com ([10.193.5.179]) by dfweml702-cah.china.huawei.com ([10.193.5.176]) with mapi id 14.03.0235.001; Fri, 8 Jul 2016 08:45:39 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "I2NSF@ietf.org" <I2NSF@ietf.org>
Thread-Topic: Berlin I2NSF F2F meeting agenda consideration, and how to align mutliple drafts on the "Customer Facing Interface" and "NSF facing interface"
Thread-Index: AdHZL8XnWdxWET9cRGuxa2mlBuuIUg==
Date: Fri, 08 Jul 2016 15:45:38 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F657EE0FBA@dfweml501-mbb>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.132.252]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F657EE0FBAdfweml501mbb_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0205.577FCAA9.00A6, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: ce665cb305c47fd04ff64ae9a6602433
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/1SQqca4PWxXED0ZCYnwGqXC25A4>
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Subject: [I2nsf] Berlin I2NSF F2F meeting agenda consideration, and how to align mutliple drafts on the "Customer Facing Interface" and "NSF facing interface"
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 08 Jul 2016 15:45:51 -0000

I2NSF Participants,

At  Berlin I2NSF F2F meeting, we are going to group presentations based on the if they are applicable to "Customer Facing Interface (A)" or "NSF Facing Interface (B)", as shown in the I2NSF reference model.
After glancing through the drafts contributed so far, we have grouped them in the following categories. Please let us know if we are wrong.

-       Service Requester facing interface (was Client facing interface)
*        draft-mglt-i2nsf-ssf-collaboration-00 (Flow Policy between Cloud network and Provider network)
*        draft-kumar-i2nsf-controller-northbound-framework (Rakesh Kumar)
*        draft-pastor-i2nsf-vnsf-attestation-02 (Requester to controller validation)
*        draft-kim-i2nsf-security-management-architecture-01
*        draft-you-i2nsf-user-group-based-policy (10 minutes)

-       NSF Facing interface:
*        draft-xia-i2nsf-capability-interface-im-06
*        draft-baspez-i2nsf-capabilities-00
*        hares-i2nsf-capability-yang-00
*        draft-zhang-i2nsf-info-model-monitoring-01
*        draft-jeong-i2nsf-sdn-security-services-04
*        draft-jeong-i2nsf-capability-interface-yang-00
*        draft-hyun-i2nsf-sfc-enabled-i2nsf-00
*        Rafa: IPSec policy exchange between Controller and network functions
*        draft-you-i2nsf-user-group-policy-capability

To make the Face to Face meeting more productive, we are going to have a side pre-meeting among the authors on each interface to discuss if there are overlaps or/and the differentiation among their proposed schemes. I will send out a Doodle poll for each of the side discussion.


              +-----------------------------------------------------+
              |      I2NSF Client                                   |
              | E.g. Overlay Network Mgnt, Enterprise network Mgnt  |
              |  another network domain's mgnt, etc.                |
              +----------+------------------------------------------+
                         |
                         |  Client Facing Interface (A)
                         |
                   +-----+---------------+
                   |Network Operator mgmt|               +-------------+
                   | Security Controller | < --------- > | Developer's |
                   +---------------+-----+  Registration | Mgnt System |
                                   |         Interface   +-------------+
                                   |
                                   | NSF Facing Interface (B)
                                   |
      +---------------------------+-----------------------+
       |                                                   |
       |                                                   |
   +---+--+         +------+             +------+       +--+---+
   + NSF-1+ ------- + NSF-n+             +NSF-1 + ----- +NSF-m +  . . .
   +------+         +------+             +------+       +------+

   Developer A                                 Developer B
Figure 1: I2NSF Reference Model


Thank you very much for the contributions,

Linda and Adrian.