As discussed in the Berlin meeting, we have created this new draft with contents from https://tools.ietf.org/html/draft-kumar-i2nsf-controller-northbound-framework-00 and other inputs.
This draft captures the client interface requirements for the I2NSF security controller. Regards, Rakesh On 8/2/16, 12:14 PM, "internet-dra...@ietf.org" <internet-dra...@ietf.org> wrote: > >A new version of I-D, draft-kumar-i2nsf-client-facing-interface-req-00.txt >has been successfully submitted by Rakesh Kumar and posted to the >IETF repository. > >Name: draft-kumar-i2nsf-client-facing-interface-req >Revision: 00 >Title: Client Interface for Security Controller : A Framework for >Security Policy Requirements >Document date: 2016-08-02 >Group: Individual Submission >Pages: 17 >URL: >https://www.ietf.org/internet-drafts/draft-kumar-i2nsf-client-facing-interface-req-00.txt >Status: >https://datatracker.ietf.org/doc/draft-kumar-i2nsf-client-facing-interface-req/ >Htmlized: >https://tools.ietf.org/html/draft-kumar-i2nsf-client-facing-interface-req-00 > > >Abstract: > This document provides a framework and information model for the > definition of northbound interfaces for a security controller. The > interfaces are based on user-intent instead of vendor-specific or > device-centric approaches that would require deep knowledge of vendor > products and their security features. The document identifies the > common interfaces needed to enforce the user-intent based policies > onto network security functions (NSFs) irrespective of how those > functions are realized. The function may be physical or virtual in > nature and may be implemented in networking or dedicated appliances. > > > > > >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 > _______________________________________________ I2nsf mailing list I2nsf@ietf.org https://www.ietf.org/mailman/listinfo/i2nsf
