[I2nsf] updated I2NSF problem statement to reflect the narrower scoped charter

Linda Dunbar <linda.dunbar@huawei.com> Thu, 21 May 2015 22:42 UTC

Return-Path: <linda.dunbar@huawei.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 D3E861A87B1 for <i2nsf@ietfa.amsl.com>; Thu, 21 May 2015 15:42:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 TPVpbnXMnzNX for <i2nsf@ietfa.amsl.com>; Thu, 21 May 2015 15:42:53 -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 357071A90DC for <i2nsf@ietf.org>; Thu, 21 May 2015 15:42:53 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BWJ26419; Thu, 21 May 2015 22:42:51 +0000 (GMT)
Received: from DFWEML705-CHM.china.huawei.com (10.193.5.142) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 21 May 2015 23:42:50 +0100
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml705-chm ([10.193.5.142]) with mapi id 14.03.0158.001; Thu, 21 May 2015 15:42:39 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "'i2nsf@ietf.org'" <i2nsf@ietf.org>
Thread-Topic: updated I2NSF problem statement to reflect the narrower scoped charter
Thread-Index: AQHQlBdwcaMbS56nSk+pGJr4g/BqUg==
Date: Thu, 21 May 2015 22:42:39 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F657C46D13@dfweml701-chm>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.134.154]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2nsf/Nrh__RmVK-cg23PEBKNgKgCSuzI>
Subject: [I2nsf] updated I2NSF problem statement to reflect the narrower scoped charter
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: Thu, 21 May 2015 22:42:57 -0000

We updated the I2NSF problem statement to reflect the narrower scoped charter. 

The primary issues and challenges facing NSFs hosted by different domains are:

      3.1. Challenges Facing Security Service Providers..............5
         3.1.1. Diverse types of Security Functions..................5
         3.1.2. No Standard Characterization of NSFs.................6
         3.1.3. More Distributed NSFs and vNSFs......................7
         3.1.4. More Demand to Control NSFs Dynamically..............7
         3.1.5. Diverse Interfaces to Control and Monitor NSFs.......7
         3.1.6. Lack of mechanism to monitor the behavior of NSFs....8
      3.2. Challenges Facing Customers...............................8
         3.2.1. Need to integrate on-premises NSFs with Remote NSFs..8
         3.2.2. Today's Policy Expressions are Vendors Specific......9
         3.2.3. Difficulty to Monitor the Execution of Desired Policies
         ...........................................................10
      3.3. Difficulty to Validate Policies across Multiple Domains..10
      3.4. Lack of Standard Interface to Inject Feedback to NSF.....11

Your comments and suggestions are highly appreciated. 

Linda

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Thursday, May 21, 2015 5:37 PM
To: Mohamed Boucadair; Shaibal Chakrabarty; Linda Dunbar; Christian Jacquenet; Myo Zarny; Christian Jacquenet; Myo Zarny; Shaibal Chakrabarty; Linda Dunbar; Mohamed Boucadair
Subject: New Version Notification for draft-dunbar-i2nsf-problem-statement-04.txt


A new version of I-D, draft-dunbar-i2nsf-problem-statement-04.txt
has been successfully submitted by Linda Dunbar and posted to the IETF repository.

Name:		draft-dunbar-i2nsf-problem-statement
Revision:	04
Title:		Interface to Network Security Functions (I2NSF) Problem Statement
Document date:	2015-05-21
Group:		Individual Submission
Pages:		20
URL:            https://www.ietf.org/internet-drafts/draft-dunbar-i2nsf-problem-statement-04.txt
Status:         https://datatracker.ietf.org/doc/draft-dunbar-i2nsf-problem-statement/
Htmlized:       https://tools.ietf.org/html/draft-dunbar-i2nsf-problem-statement-04
Diff:           https://www.ietf.org/rfcdiff?url2=draft-dunbar-i2nsf-problem-statement-04

Abstract:
   This document describes the motivation and the problem statement for
   Interface to Network Security Functions (I2NSF).

                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat