[I2nsf] about the SUPA BoF (complementary work)
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 17 June 2015 13:23 UTC
Return-Path: <dromasca@avaya.com>
X-Original-To: i2nsf@ietfa.amsl.com
Delivered-To: i2nsf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74E1B1AC3BA for <i2nsf@ietfa.amsl.com>; Wed, 17 Jun 2015 06:23:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 s6Wv3dEBUBfL for <i2nsf@ietfa.amsl.com>; Wed, 17 Jun 2015 06:23:11 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E5901AC3CC for <i2nsf@ietf.org>; Wed, 17 Jun 2015 06:23:11 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvYJAHvmdlXGmAcV/2dsb2JhbABcgkUhKiMxXgaDGKlHAQEBAQEBBoNGjUVPgW0dAQuFdwIcgSxMAQEBAQEBgQALhCQBAQMBAQEPEQpBHQEVAxIgAgQlCyYBBBsaiAwBDJwzhQmKVqQoAQEIAQEBAQEdhhmJTDMtgjgMLxIdgRYFhRKOLIRCglOBf4NMQIYwC49AERNigxZvAQGBRIEBAQEB
X-IronPort-AV: E=Sophos;i="5.13,581,1427774400"; d="scan'208,217";a="125519963"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 17 Jun 2015 09:23:08 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 17 Jun 2015 09:23:08 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0174.001; Wed, 17 Jun 2015 15:23:07 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: about the SUPA BoF (complementary work)
Thread-Index: AdCpAL5I0fMYWt1jQC6KFdU+f2AN1A==
Date: Wed, 17 Jun 2015 13:23:07 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5CA6B8BC@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.48]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5CA6B8BCAZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2nsf/WHzDm1wbfXYiFpVyrrZYKIMurWA>
Subject: [I2nsf] about the SUPA BoF (complementary work)
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 17 Jun 2015 13:23:13 -0000
Hi I2NSF-ers,
In parallel to the preparation of our own successful BoF I would like to draw the attention of the participants in I2NSF to another WG-forming BoF which was approved for IETF 93 – the Simplified Use of Policy Abstractions (SUPA) BoF. SUPA is defining an interface to a network management function that takes high-level, possibly network-wide policies as input and creates element configurations snippets as output. In the terms of our work, if the output of SUPA is an NSF, this type of interface belongs to the Service Layer, which is out of scope for I2NSF. SUPA and NSF seem to be complementary in the security functionality area. It is however useful to read and review what they are doing in order to confirm this assessment as well as the path they take which may lead to a simplification of the definition of network-wide policies.
A few useful links:
* Mailing List: https://www.ietf.org/mailman/listinfo/supa<https://www.ietf.org/mailman/listinfo/supa>
* Draft charter: http://cnds.eecs.jacobs-university.de/users/schoenw/supa/supa-charter-2015-06-09.txt<http://cnds.eecs.jacobs-university.de/users/schoenw/supa/supa-charter-2015-06-09.txt>
* Q&A: https://github.com/IETF-SUPA/SUPA/wiki/Q-&-A<https://github.com/IETF-SUPA/SUPA/wiki/Q-&-A>
* Internet-Drafts:
* Value proposition: http://datatracker.ietf.org/doc/draft-klyus-supa-proposition<http://datatracker.ietf.org/doc/draft-klyus-supa-proposition>
* Converged from
* http://datatracker.ietf.org/doc/draft-karagiannis-supa-problem-statement/<http://datatracker.ietf.org/doc/draft-karagiannis-supa-problem-statement/>
* http://datatracker.ietf.org/doc/draft-bi-supa-gap-analysis/<http://datatracker.ietf.org/doc/draft-bi-supa-gap-analysis/>
* http://datatracker.ietf.org/doc/draft-zhou-supa-framework/<http://datatracker.ietf.org/doc/draft-zhou-supa-framework/>
* Information model: http://datatracker.ietf.org/doc/draft-strassner-supa-generic-policy-info-model/<http://datatracker.ietf.org/doc/draft-strassner-supa-generic-policy-info-model/>
* Data model: TBD
* Converged from http://datatracker.ietf.org/doc/draft-wang-netmod-yang-policy-dm/<http://datatracker.ietf.org/doc/draft-wang-netmod-yang-policy-dm/>
Thanks and Regards,
Dan
- [I2nsf] about the SUPA BoF (complementary work) Romascanu, Dan (Dan)