Hi, Thank you for the constructive meeting. Here are my notes:
Date: 2016-12-15, 8-9:30 am CET Participants: Yi Yang, Danny Zhou, Zoltan Balogh, Jan Scheurich Summary: * Went through the proposed solution for NSH based on PTAP and generic encap/decap in the doc: https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit?usp=sharing * Clarified some questions regarding the example NSH pipelines. The example shows a co-located Classifier and SFF but that is not a limitation. Will clarify this. * It is crucial that we restrict NSH match fields to packet header fields and not allow them to keep values after decap because there is already a use case specified that requires stacks of NSH tunnel headers. * We strongly recommend to implement the straightforward support for MD1 fixed size header as a first increment and work on the more complex aspects of the MD2 TLV fields in a second step (significant work, some not yet resolved technical questions). There are plenty of use cases that only require MD1. * Ericsson is already working on PTAP and support for versatile tunnel ports. This is the first building block for NSH. Then we will implement the generic parts of the encap/decap actions and the Ethernet use case as described in doc. * Intel would adjust the implementation of NSH support accordingly (NSH match fields, encap/decap for NSH). * Recently Pravin has agreed to merge compatibility code to the kernel datapath module in OVS tree to support VXLAN-GPE configuration through NETLNK API. With that we'd no longer depend on RTNETLINK API in recent kernels. This allows wider deployment and eases the dependency on the RTNETKLINK tunnel configuration patches in net-next. * The aim is to have L3 tunnels for non-PTAP bridges (for MPLS over GRE), PTAP bridges and versatile tunnels, generic encap/decap and support for NSH MD1 upstreamed in Q1 in time for OVS 2.7. * I will add a chapter to the document that outlines the decomposition of the solution into patch sets with an integration anatomy. Based on that we can assign work items to contributing parties and discuss how to collaborate and the time line. * Jan to invite next week for a final sync meeting with the American & European participants this year to review the document and discuss the plan. Regards, Jan -----Original Appointment----- From: Jan Scheurich Sent: Monday, 12 December, 2016 13:09 To: Jan Scheurich; Yang, Yi Y (yi.y.y...@intel.com); danny.z...@intel.com; Zoltán Balogh (zoltan.bal...@ericsson.com) Cc: Jiri Benc (jb...@redhat.com) Subject: Sync on PTAP, EXT-382 and NSH When: Thursday, 15 December, 2016 08:00-09:00 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Where: Skype Meeting Updated to 8-9am CET to accommodate Yi Yang. Hi Yi/Danny, Would you have time to go through the latest proposal on NSH support in OVS built on PTAP and EXT-382 as outlined in Google doc https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit?usp=sharing BR, Jan ......................................................................................................................................... --> Join Skype Meeting<https://meet.ericsson.com/jan.scheurich/KT34JR2Q> This is an online meeting for Skype for Business, the professional meetings and communications app formerly known as Lync. Join by phone +492115343925<tel:+492115343925,281130796%23> (Germany) English (United States) 89925<tel:+89925,281130796%23> (Germany) English (United States) Find a local number<https://dialin.ericsson.com?id=281130796> Conference ID: 281130796 Forgot your dial-in PIN?<https://dialin.ericsson.com> |Help<http://o15.officeredir.microsoft.com/r/rlidLync15?clid=1033&p1=5&p2=2009> To join a Lync / Skype for Business meeting from an Ericsson standard video room, add 77 before the Conference ID (e.g. 771234567 where 1234567 is the conference ID). To join from a video room outside of Ericsson add one of the domains after 77 and Conference ID (e.g. 771234567@ xxxx.ericsson.net, where xxxx=emea/apac/amcs). For assistance contact the IT Service Desk. [!OC([1033])!] ......................................................................................................................................... _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
