[i2rs] I2NSF: Interface to network security functions : problem-statement, framework, use cases, and potential solution

[Linda Dunbar <[e-mail]>]

The "i2nsf-problem-statement" draft describes the motivation and the problem space associated with service providers providing hosted security solutions to deliver cost-effective managed security services to enterprise customers who don't own or have the security functions on their premises. 

Since the i2nsf-problem-statement-01 draft, three I2NSF use case drafts, a gap analysis draft, and a packet-based paradigm draft have been published. 
We removed the redundant content from the problem statement draft, making it focus exclusively on the problem space of security functions not hosted on customer's premises and being distributed (driven by NFV and hosted security services).

In conjunction with the "i2nsf-problem-statements", there are also I2NSF framework draft, potential I2NSF solution draft, use case drafts (under process of merging), gap-analysis and data modeling draft:

http://datatracker.ietf.org/doc/draft-merged-i2nsf-framework/

http://datatracker.ietf.org/doc/draft-lopez-i2nsf-packet/

http://datatracker.ietf.org/doc/draft-xia-i2nsf-capability-interface-im/ (new revision is to be uploaded soon to reflect the discussion of F2F meetings at IETF92 Dallas). 

http://datatracker.ietf.org/doc/draft-pastor-i2nsf-access-usecases/
http://datatracker.ietf.org/doc/draft-qi-i2nsf-access-network-usecase/
http://datatracker.ietf.org/doc/draft-zarny-i2nsf-data-center-use-cases/

http://datatracker.ietf.org/doc/draft-zhang-gap-analysis/

I2NSF is about security functions management. The ultimate goal of I2NSF is to enable enterprises to utilize security functions not hosted on their own premise but instead hosted in service provider domain, to establish how to communicate desired security policies to NSF and how to get performance data or report out of NSF.  

Also copy to the I2NSF relevant IETF WGs: I2RS, NETMOD, NETCONF, SACM, MILE, PCP, DOTS, SFC, and OpAreas, in hope to get feedback and suggestions from wider audience. 

Thanks in advance, 

Linda Dunbar

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] 
Sent: Thursday, April 23, 2015 11:31 AM
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-03.txt


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

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

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