The meeting room for this side meeting is "Tegel". We should finish before the IETF Plenary session by 5:30pm.
I also booked a WebEx for a few people who can't make it to Berlin: Linda Event: I2NSF side meeting for NSF Facing interface Start Event Now You can start the event by clicking Start Now. Send Event Emails You can send event emails by clicking Send Emails. Type: Listed Event Event address for attendees: https://ietf.webex.com/ietf/onstage/g.php?MTID=e0c10a12f0b6373b522adb358a442ad6a Event address for panelists: https://ietf.webex.com/ietf/onstage/g.php?MTID=e840b30e01226884be1dd63e5c5058401 Date and time: Wednesday, July 20, 2016 3:50 pm Europe Summer Time (Berlin, GMT+02:00) Wednesday, July 20, 2016 3:50 pm Europe Summer Time (Berlin, GMT+02:00) Duration: 2 hours Description: Event number: 649 084 081 From: Linda Dunbar Sent: Thursday, July 14, 2016 6:47 PM To: '[email protected]' Cc: '[email protected]' Subject: Wed, July 20 3:50pm Berlin time is set for the side meeting to address multiple drafts on the information and data models over the "NSF facing interface" Based on the doodle poll, July 20 3:50pm Berlin time is set for the side meeting to address multiple drafts on the information and data models over the "NSF facing interface". I have requested a room & WebEx for this side meeting, will let you know once the room & WebEx are assigned by the IESG secretary. Safe travel to Berlin. Linda From: Linda Dunbar Sent: Saturday, July 09, 2016 12:57 AM To: [email protected]<mailto:[email protected]> Subject: side meeting in Berlin to address multiple drafts on the information and data models over the "NSF facing interface" 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]<mailto:[email protected]> Cc: [email protected]<mailto:[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
