HI Paul, I plan to do soon (few hours).
Thanks Rakesh From: "Mr. Jaehoon Paul Jeong" <[email protected]<mailto:[email protected]>> Date: Monday, July 3, 2017 at 3:07 PM To: Rakesh Kumar <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [I2nsf] I-D Action: draft-ietf-i2nsf-client-facing-interface-req-02.txt Hi Rakesh, when you will post your updated information model later, I will update our data model correspondingly. Thanks. Best Regards, Paul 2017. 7. 4. 오전 6:42에 "Rakesh Kumar" <[email protected]<mailto:[email protected]>>님이 작성: Hi, I updated number of sections based on past feedback and added/updated few sections based on customer interaction in industry forums (ONUG). Thanks Rakesh On 7/3/17, 2:39 PM, "I2nsf on behalf of [email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]> on behalf of [email protected]<mailto:[email protected]>> wrote: > >A New Internet-Draft is available from the on-line Internet-Drafts directories. >This draft is a work item of the Interface to Network Security Functions of >the IETF. > > Title : Requirements for Client-Facing Interface to Security > Controller > Authors : Rakesh Kumar > Anil Lohiya > Dave Qi > Nabil Bitar > Senad Palislamovic > Liang Xia > Filename : draft-ietf-i2nsf-client-facing-interface-req-02.txt > Pages : 24 > Date : 2017-07-03 > >Abstract: > This document captures requirements for Client-Facing interface to > the Security Controller as defined by [I-D.ietf-i2nsf-framework]. > The interface is expressed using objects and constructs understood by > Security Admin as opposed to vendor or device specific expressions > associated with individual product and feature. This document > identifies a broad set of requirements needed to express Security > Policies based on User-constructs which are well understood by the > User Community. This gives ability to decouple policy definition > from policy enforcement on a specific security functional element, be > it a physical or virtual. > > >The IETF datatracker status page for this draft is: >https://datatracker.ietf.org/doc/draft-ietf-i2nsf-client-facing-interface-req/ > >There are also htmlized versions available at: >https://tools.ietf.org/html/draft-ietf-i2nsf-client-facing-interface-req-02 >https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-client-facing-interface-req-02 > >A diff from the previous version is available at: >https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-client-facing-interface-req-02 > > >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<http://tools.ietf.org>. > >Internet-Drafts are also available by anonymous FTP at: >ftp://ftp.ietf.org/internet-drafts/ > >_______________________________________________ >I2nsf mailing list >[email protected]<mailto:[email protected]> >https://www.ietf.org/mailman/listinfo/i2nsf _______________________________________________ I2nsf mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/i2nsf
_______________________________________________ I2nsf mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2nsf
