This is the side pre I2NSF F2F meeting among the authors who contributed drafts on NSF Facing Interface (listed below) to discuss if there are overlaps or/and the differentiation among their proposed schemes.
For the drafts below, please designate at least one author to participate in the pre meeting: - NSF Facing interface: * draft-xia-i2nsf-capability-interface-im-06 * draft-baspez-i2nsf-capabilities-00 * hares-i2nsf-capability-yang-00 * draft-zhang-i2nsf-info-model-monitoring-01 * draft-jeong-i2nsf-sdn-security-services-04 * draft-jeong-i2nsf-capability-interface-yang-00 * draft-hyun-i2nsf-sfc-enabled-i2nsf-00 * Rafa: IPSec policy exchange between Controller and network functions * draft-you-i2nsf-user-group-policy-capability Please enter your available time at this poll: http://doodle.com/poll/7vcpm7agpx7ci5da Thank you very much. Linda From: Linda Dunbar Sent: Friday, July 08, 2016 10:46 AM To: [email protected] Cc: [email protected] Subject: Berlin I2NSF F2F meeting agenda consideration, and how to align mutliple drafts on the "Customer Facing Interface" and "NSF facing interface" I2NSF Participants, At Berlin I2NSF F2F meeting, we are going to group presentations based on the if they are applicable to "Customer Facing Interface (A)" or "NSF Facing Interface (B)", as shown in the I2NSF reference model. After glancing through the drafts contributed so far, we have grouped them in the following categories. Please let us know if we are wrong. - Service Requester facing interface (was Client facing interface) * draft-mglt-i2nsf-ssf-collaboration-00 (Flow Policy between Cloud network and Provider network) * draft-kumar-i2nsf-controller-northbound-framework (Rakesh Kumar) * draft-pastor-i2nsf-vnsf-attestation-02 (Requester to controller validation) * draft-kim-i2nsf-security-management-architecture-01 * draft-you-i2nsf-user-group-based-policy (10 minutes) - NSF Facing interface: * draft-xia-i2nsf-capability-interface-im-06 * draft-baspez-i2nsf-capabilities-00 * hares-i2nsf-capability-yang-00 * draft-zhang-i2nsf-info-model-monitoring-01 * draft-jeong-i2nsf-sdn-security-services-04 * draft-jeong-i2nsf-capability-interface-yang-00 * draft-hyun-i2nsf-sfc-enabled-i2nsf-00 * Rafa: IPSec policy exchange between Controller and network functions * draft-you-i2nsf-user-group-policy-capability To make the Face to Face meeting more productive, we are going to have a side pre-meeting among the authors on each interface to discuss if there are overlaps or/and the differentiation among their proposed schemes. I will send out a Doodle poll for each of the side discussion. +-----------------------------------------------------+ | I2NSF Client | | E.g. Overlay Network Mgnt, Enterprise network Mgnt | | another network domain's mgnt, etc. | +----------+------------------------------------------+ | | Client Facing Interface (A) | +-----+---------------+ |Network Operator mgmt| +-------------+ | Security Controller | < --------- > | Developer's | +---------------+-----+ Registration | Mgnt System | | Interface +-------------+ | | NSF Facing Interface (B) | +---------------------------+-----------------------+ | | | | +---+--+ +------+ +------+ +--+---+ + NSF-1+ ------- + NSF-n+ +NSF-1 + ----- +NSF-m + . . . +------+ +------+ +------+ +------+ Developer A Developer B Figure 1: I2NSF Reference Model Thank you very much for the contributions, Linda and Adrian.
_______________________________________________ I2nsf mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2nsf
