[ovs-dev] Sync on PTAP, EXT-382 and NSH - Minutes of Meeting Wed 2017-07-19 17:00 CET

[Jan Scheurich]

Participants: Zoltan, Jan

Patch series
*   Generic Encap/Decap (EXT 382) for Ethernet
o   v2 series submitted as discussed
o   Ben P already merged the PTAP bugfix patch (1/3)
o   Jan identified lack of check on VLAN tags in translation of decap() for 
Ethernet.
Tagged packets must be dropped as decided in Google doc
o   Zoltan to test interaction of PTAP and encap/decap with .1q and QinQ 
packets
o   Should add some documentation around PTAP and generic encap/decap.
I will not make it before vacation. Can we add this later?
*   Support for NSH MD1 including Encap/Decap for NSH (Yi)
o   Several improvements/corrections on top of the v1 series posted
o   Support for NSH MD2 TLVs as encap properties in encap(nsh) implemented
o   Series ready for submission as v2.
*   Support layer3 VXLAN-GPE and GRE in kernel datapath (Eric)
o   Reviewed and applied by Joe yesterday. Thanks!

We can still include all parts in OVS 2.8 when we keep the pace up!

Next steps:
*   Ben to review v2 of Generic Encap/Decap (EXT 382) for Ethernet
*   Yi to respin NSH v2 series. Should we wait for merge of Generic 
Encap/Decap?
*   Ben to review NSH v2 series
*   Summer vacation: Jan: Jul 21 - Aug 4, Zoltan: Jul 31 - Aug 11.
As both of us are off 1st week of August, it would be great if we could 
finalize Generic encap/decap in July.

BR, Jan


  -Original Appointment-
  From: Jan Scheurich
  Sent: Sunday, 18 December, 2016 15:34
  To: Jan Scheurich; Zoltán Balogh; Yang, Yi Y (yi.y.y...@intel.com); Jiri 
Benc (jb...@redhat.com); Simon Horman (simon.hor...@netronome.com); 
'ja...@ovn.org'; 'Ben Pfaff'; 'ben.mackcr...@corsa.com'; d...@openvswitch.org; 
Georg Schmuecking
  Subject: Sync on PTAP, EXT-382 and NSH - Wed 2017-07-19 17:00 CET
  When: Wednesday, 19 July, 2017 17:00-18:00 (UTC+01:00) Amsterdam, Berlin, 
Bern, Rome, Stockholm, Vienna.
  Where: Skype Meeting


  Hi,

  Focus on getting the remaining series reviewed and merged for OVS 2.8:
  1. Generic Encap/Decap (EXT 382) for Ethernet (Ericsson)
  2. L3/PTAP tunnel config for kernel datapath (RedHat)
  3. Basic NSH MD1 including Encap/Decap for NSH (Intel)

  Minutes of previous meeting
  https://mail.openvswitch.org/pipermail/ovs-dev/2017-July/335373.html

  Thank you,
  Jan


  Link to the Google design doc:
  
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


  
.
  --> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
  Join by phone

  +492115343925 (Germany)English 
(United States)
  89925 (Germany)   English (United States)

  Find a local number

  Conference ID: 70849799
   Forgot your dial-in PIN? 
|Help


  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@ .ericsson.net, 
where =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

[ovs-dev] Sync on PTAP, EXT-382 and NSH - Wed 2017-07-19 17:00 CET

[Jan Scheurich]

Hi,

Focus on getting the remaining series reviewed and merged for OVS 2.8:
1. Generic Encap/Decap (EXT 382) for Ethernet (Ericsson)
2. L3/PTAP tunnel config for kernel datapath (RedHat)
3. Basic NSH MD1 including Encap/Decap for NSH (Intel)

Minutes of previous meeting
https://mail.openvswitch.org/pipermail/ovs-dev/2017-July/335373.html

Thank you,
Jan


Link to the Google design doc:
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


.
--> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
Join by phone

+492115343925 (Germany)  English (United 
States)
89925 (Germany) English (United States)

Find a local number

Conference ID: 70849799
 Forgot your dial-in PIN? 
|Help


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@ .ericsson.net, where 
=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

[ovs-dev] Sync on PTAP, EXT-382 and NSH - Minutes of Meeting Wed 2017-07-12 17:00 CET

[Jan Scheurich]

Participants: Ben P, Zoltan, Jan, Jiri, Thomas Morin

Patch series
*   Generic Encap/Decap (EXT 382) for Ethernet
o   Reviewed by Ben
o   One tunnel config bugfix commit merged
o   Zoltan will extract the PTAP bugfix and post separately
o   Zoltan to submit v2 series
*   collapse patches 1 and 2
*   change action codes to NX
*   Support for NSH MD1 including Encap/Decap for NSH (Yi)
o   Posted by Yi
o   Joe: NSH-related definitions in kernel header files need to be 
protected with "ifndef kernel" until NSH support are proposed upstream to 
net-next
o   No other review yet
*   Support layer3 VXLAN-GPE and GRE in kernel datapath (Eric)
o   Posted by Eric Garver on July 10
o   Minor changes except for a bugfix dealing with PTAP/Ethertype 
translation for kernel
o   Tested successfully by Thomas Morin for MPLSoGRE with different kernels 
and in-tree and out-of-tree module
o   No review yet
o   Actual Ben will ask Joe to review this

Overall Ben thinks that we can still include all parts in OVS 2.8 when we keep 
the pace up!

Next steps:
*   Joe(?) to review Support layer3 VXLAN-GPE and GRE in kernel datapath
*   Zoltan to post separate bugfix patch for PTAP (drop non-Ethernet packet 
sent to legacy_l2 ports)
*   Zoltan to post v2 of Generic Encap/Decap (EXT 382) for Ethernet
o   Ben to review v2 of Generic Encap/Decap (EXT 382) for Ethernet
*   Jan to provide his comments to NSH series
*   Yi to include Joe's and Jan's comments and respin NSH v2 series rebased 
to Generic Encap/Decap v2
*   Ben to review NSH series
*   Jan to call for follow-up meeting next week (Ben in Ireland, UTC+1)

BR, Jan


  -Original Appointment-
  From: Jan Scheurich
  Sent: Sunday, 18 December, 2016 15:34
  To: Jan Scheurich; Zoltán Balogh; Yang, Yi Y (yi.y.y...@intel.com); Jiri 
Benc (jb...@redhat.com); Simon Horman (simon.hor...@netronome.com); 
'ja...@ovn.org'; 'Ben Pfaff'; 'ben.mackcr...@corsa.com'; d...@openvswitch.org; 
Georg Schmuecking
  Subject: Sync on PTAP, EXT-382 and NSH - Wed 2017-07-12 17:00 CET
  When: Wednesday, 12 July, 2017 17:00-18:00 (UTC+01:00) Amsterdam, Berlin, 
Bern, Rome, Stockholm, Vienna.
  Where: Skype Meeting


  Hi,

  Focus on getting the remaining series reviewed and merged for OVS 2.8:
  1. Generic Encap/Decap (EXT 382) for Ethernet (Ericsson)
  2. Basic NSH MD1 including Encap/Decap for NSH (Intel)
  3. L3/PTAP tunnel config for kernel datapath (RedHat)

  Thank you,
  Jan

  Link to the Google design doc:
  
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


  
.
  --> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
  Join by phone

  +492115343925 (Germany)English 
(United States)
  89925 (Germany)   English (United States)

  Find a local number

  Conference ID: 70849799
   Forgot your dial-in PIN? 
|Help


  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@ .ericsson.net, 
where =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

[ovs-dev] Sync on PTAP, EXT-382 and NSH - Wed 2017-07-12 17:00 CET

[Jan Scheurich]

Hi,

Focus on getting the remaining series reviewed and merged for OVS 2.8:
1. Generic Encap/Decap (EXT 382) for Ethernet (Ericsson)
2. Basic NSH MD1 including Encap/Decap for NSH (Intel)
3. L3/PTAP tunnel config for kernel datapath (RedHat)

Thank you,
Jan

Link to the Google design doc:
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


.
--> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
Join by phone

+492115343925 (Germany)  English (United 
States)
89925 (Germany) English (United States)

Find a local number

Conference ID: 70849799
 Forgot your dial-in PIN? 
|Help


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@ .ericsson.net, where 
=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

[ovs-dev] Sync on PTAP, EXT-382 and NSH - Minutes of Meeting Wed 2017-06-28 14:00 CET

[Jan Scheurich]

Participants: Ben P, Zoltan, Jan, Thomas Morin

Patch series
*   PTAP v4
o   Merged by Ben last night. Thanks!
*   Generic Encap/Decap (EXT 382) for Ethernet
o   Rebased on PTAP v4 and refactored (refined CLI syntax)
o   Can be posted this week
*   Support for NSH MD1 including Encap/Decap for NSH
o   Refactoring and adaption to changes in PTAP v4 and Gen Encap/Decap 
ongoing
o   To be submitted until July 4
*   L3 tunnel config for kernel datapath (RedHat)
o   Missing piece in OVS 2.8 to be able to use L3 tunnels with kernel 
datapath
o   Status not known.
o   Note: OVSDB legacy L3 tunnel configuration changed in PTAP series 
compared to early L3 tunneling patch set from "options:layer_3=true|false" to  
"options:packet_type=legacy_l2|legacy_l3|ptap"

Next steps:
*   Ericsson to post Generic Encap/Decap (EXT 382) for Ethernet
*   Intel to post Support for NSH MD1 including Encap/Decap for NSH when 
ready
*   Ben to review both series next week
*   RedHat to submit patch for L3/PTAP tunnel config for kernel datapath.
o   Thomas M will contact RedHat (Jiri) regarding status of patch and offer 
help (e.g. testing MPLS over GRE).
*   Work on OVS documentation for L3 tunneling, PTAP and encap/decap, NSH.
*   Jan to call for follow-up meeting in two weeks

BR, Jan

  -Original Appointment-
  From: Jan Scheurich
  Sent: Sunday, 18 December, 2016 15:34
  To: Jan Scheurich; Zoltán Balogh; Yang, Yi Y (yi.y.y...@intel.com); Jiri 
Benc (jb...@redhat.com); Simon Horman (simon.hor...@netronome.com); 
'ja...@ovn.org'; 'Ben Pfaff'; 'ben.mackcr...@corsa.com'; d...@openvswitch.org; 
Georg Schmuecking
  Subject: Sync on PTAP, EXT-382 and NSH - Wed 2017-06-28 14:00 CET
  When: Wednesday, 28 June, 2017 14:30-15:30 (UTC+01:00) Amsterdam, Berlin, 
Bern, Rome, Stockholm, Vienna.
  Where: Skype Meeting


  Start postponed by 30 minutes due to collision with an internal meeting.

  Hi,

  Focus on getting PTAP series merged and attack the review of two 
remaining series
  1. Generic Encap/Decap (EXT 382) for Ethernet and
  2. Basic NSH MD1 including Encap/Decap for NSH

  Thank you,
  Jan

  Link to the Google design doc:
  
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


  
.
  --> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
  Join by phone

  +492115343925 (Germany)English 
(United States)
  89925 (Germany)   English (United States)

  Find a local number

  Conference ID: 70849799
   Forgot your dial-in PIN? 
|Help


  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@ .ericsson.net, 
where =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

[ovs-dev] Sync on PTAP, EXT-382 and NSH - Wed 2017-06-28 14:00 CET

[Jan Scheurich]

Start postponed by 30 minutes due to collision with an internal meeting.

Hi,

Focus on getting PTAP series merged and attack the review of two remaining 
series
1. Generic Encap/Decap (EXT 382) for Ethernet and
2. Basic NSH MD1 including Encap/Decap for NSH

Thank you,
Jan

Link to the Google design doc:
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


.
--> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
Join by phone

+492115343925 (Germany)  English (United 
States)
89925 (Germany) English (United States)

Find a local number

Conference ID: 70849799
 Forgot your dial-in PIN? 
|Help


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@ .ericsson.net, where 
=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

[ovs-dev] Sync on PTAP, EXT-382 and NSH - Wed 2017-06-28 14:00 CET

[Jan Scheurich]

Hi,

Focus on getting PTAP series merged and attack the review of two remaining 
series
1. Generic Encap/Decap (EXT 382) for Ethernet and
2. Basic NSH MD1 including Encap/Decap for NSH

Thank you,
Jan

Link to the Google design doc:
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


.
--> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
Join by phone

+492115343925 (Germany)  English (United 
States)
89925 (Germany) English (United States)

Find a local number

Conference ID: 70849799
 Forgot your dial-in PIN? 
|Help


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@ .ericsson.net, where 
=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

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH - Minutes of Meeting Fri 2017-06-16 17:00 CET

[Ben Pfaff]

On Fri, Jun 16, 2017 at 03:35:41PM +, Jan Scheurich wrote:
> *   Ben will update his patch series with the conclusions so far today 
> and repost. The fixups can be folded in.

I did not have enough time for this today, so it will probably happen
Saturday or Sunday.  I'm traveling, but during my flight I should have
some time to work on the series.
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[ovs-dev] Sync on PTAP, EXT-382 and NSH - Minutes of Meeting Fri 2017-06-16 17:00 CET

[Jan Scheurich]

Participants: Ben P, Jan, Simon

PTAP series:
*   Agreed that we need three tunnel modes: legacy-l2, legacy-l3 (for LISP 
and e.g. MPLSoGRE), and ptap. The default mode depends on tunnel type and is 
legacy-l3 for LISP and legacy-l2 for all other tunnel types.
*   Ben will update his patch series with the conclusions so far today and 
repost. The fixups can be folded in.

Next steps:
*   Jan and Zoltan to review and test Ben's next PTAP series.
*   Jan and Zoltan to rebase the basic encap/decap patches on Ben's latest 
PTAP and send to ML next week.
*   Next sync meeting: Tuesday/Wednesday June 27/28 (Ben in EST time zone).

BR, Jan

  -Original Appointment-
  From: Jan Scheurich
  Sent: Sunday, 18 December, 2016 15:34
  To: Jan Scheurich; Zoltán Balogh; Yang, Yi Y (yi.y.y...@intel.com); Jiri 
Benc (jb...@redhat.com); Simon Horman (simon.hor...@netronome.com); 
'ja...@ovn.org'; 'Ben Pfaff'; 'ben.mackcr...@corsa.com'; d...@openvswitch.org; 
Georg Schmuecking
  Cc: Maria Pilar Benito Diez
  Subject: Sync on PTAP, EXT-382 and NSH - Fri 2017-06-16 17:00 CET
  When: Friday, 16 June, 2017 17:00-18:30 (UTC+01:00) Amsterdam, Berlin, 
Bern, Rome, Stockholm, Vienna.
  Where: Skype Meeting


  Hi,

  Main purpose of this sync meeting is to agree on final technical solution 
for PTAP to allow merging of that patch series and to establish a stable base 
for Generic Encap/Decap and NSH patch series.

  Target is still to upstream these changes in time for OVS 2.8.

  Thank you,
  Jan

  Link to the Google design doc:
  
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


  
.
  --> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
  Join by phone

  +492115343925 (Germany)English 
(United States)
  89925 (Germany)   English (United States)

  Find a local number

  Conference ID: 70849799
   Forgot your dial-in PIN? 
|Help


  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@ .ericsson.net, 
where =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

[ovs-dev] Sync on PTAP, EXT-382 and NSH - Fri 2017-06-16 17:00 CET

[Jan Scheurich]

Hi,

Main purpose of this sync meeting is to agree on final technical solution for 
PTAP to allow merging of that patch series and to establish a stable base for 
Generic Encap/Decap and NSH patch series.

Target is still to upstream these changes in time for OVS 2.8.

Thank you,
Jan

Link to the Google design doc:
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


.
--> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
Join by phone

+492115343925 (Germany)  English (United 
States)
89925 (Germany) English (United States)

Find a local number

Conference ID: 70849799
 Forgot your dial-in PIN? 
|Help


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@ .ericsson.net, where 
=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

[ovs-dev] Sync on PTAP, EXT-382 and NSH - Minutes of meeting Tue 2017-06-07 17:00 CET

[Jan Scheurich]

Participants
*   Zoltan, Jan, Jiri, Ben P, Georg, Ben M

Review/Discussion of current patch sets
*   RTNETLINK tunnel configuration (RedHat)
  Done: Merged my Joe on May 18th

*   L3 Tunneling (Ericsson)
Done: remaining 3 patches merged by Ben on June 2nd

*   L3 tunnel config based on RTNETLINK patches (RedHat)
  Work can start. Aim for end of the month for OVS 2.8

*   PTAP (Ericsson)
v3 based on final (v9) of L3 Tunneling sent out June 2nd.
To be reviewed by Ben

   Gitlab integration branch with PTAP, Basic NSH MD1 fields, Generic 
Encap/Decap (EXT-382) for Ethernet and NSH is fully working for userspace 
datapath.
   We are working on folding the bugfixes into the various patch sets and 
submit them to ML this week:

*   PTAP - v4 (Ericsson)
  Rebased to master after merge of L3 tunneling. No other change compared 
to v3 yet.

*   Basic Gen Encap/Decap: OF control plane and support for Ethernet 
(Ericsson)
v1 (based on PTAP v4)

*   Basic NSH MD1 fields (Intel)
  v2 (based on PTAP v4). Completely revised since v1 posted April 20th

*   Generic Encap/Decap for NSH MD1 (Intel)
  v1 (based on Basic Gen Encap/Decap).

Outstanding work:
*   Test PTAP and Generic encap/decap(Ethernet) with Linux kernel datapath
  Should work without further changes, but bugfixes may be necessary.

*   To support NSH with kernel datapath we will also need the following:
  NSH MD1 support (fields and encap/decap) in net-next kernel datapath 
(Intel)
  Yi Yang to start. Jiri can assist with this.

Technical questions:
*   It is not safe to modify the "packet-type-aware" property of a bridge, 
as already installed packet_type match fields and encap()/decap() actions have 
undefined semantics in a non-PTAP bridge.
  Should we prevent changing this parameter after bridge creation?
o   The general concept of having a bridge property was re-discussed:
*   Ben P and M asked whether a "versatile" property per tunnel port would 
not be better to control the bridge behavior.
*   Jan referred to the discussion in the Google doc (link below) and 
argued that maintaining strict backward compatibility for non-PTAP aware 
controllers was an important design goal. A bridge-global parameter to turn on 
packet type-awareness is the only safe way to not expose a controller to 
packet_type effects (e.g. in Packet In).
*   Ben P raised the issue with a patch port connecting a PTAP and a 
non-PTAP bridge. We need to make sure that the decision in the Google doc, not 
to support such patch ports is implemented.
o   Ben P: Users are not accustomed that OVSDB is transactional and would 
be confused if "packet-type-aware" cannot be set after bridge creation. Rather 
explain in documentation that this property should not be changed if there is 
flow state already.
o   We way need to harden ofproto not to crash in situations where 
encap/decap actions are translated in a bridge that is no longer packet-type 
aware.

Planning:
*   Can we still somehow meet freeze date for OVS 2.8?
o   Ben P is aiming at merging these patches for 2.8, provided the review 
cycles are fast.
o   Ericsson and Intel will do what
*   Jan to call for a follow-up meeting next week.

Thanks,
Jan

  -Original Appointment-
  From: Jan Scheurich
  Sent: Sunday, 18 December, 2016 15:34
  To: Jan Scheurich; Zoltán Balogh; Yang, Yi Y (yi.y.y...@intel.com); Jiri 
Benc (jb...@redhat.com); Pravin Shelar; Simon Horman 
(simon.hor...@netronome.com); 'ja...@ovn.org'; 'Ben Pfaff'; 
'ben.mackcr...@corsa.com'; d...@openvswitch.org; Georg Schmuecking
  Cc: Maria Pilar Benito Diez
  Subject: Sync on PTAP, EXT-382 and NSH - Tue 2017-06-07 17:00 CET
  When: Wednesday, 07 June, 2017 17:00-18:30 (UTC+01:00) Amsterdam, Berlin, 
Bern, Rome, Stockholm, Vienna.
  Where: Skype Meeting


  Hi,

  Let's have a look at the progress of the different patch series with 
respect to submission, review and merging.
  Target is still to upstream these changes in time for OVS 2.8.

  Thank you,
  Jan

  Link to the Google design doc:
  
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


  
.
  --> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
  Join by phone

  +492115343925 (Germany)English 
(United States)
  89925 (Germany)   English (United States)

  Find a local number

  Conference ID: 70849799
   Forgot your dial-in PIN? 
|Help

[ovs-dev] Sync on PTAP, EXT-382 and NSH - Tue 2017-06-07 17:00 CET

[Jan Scheurich]

Hi,

Let's have a look at the progress of the different patch series with respect to 
submission, review and merging.
Target is still to upstream these changes in time for OVS 2.8.

Thank you,
Jan

Link to the Google design doc:
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


.
--> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
Join by phone

+492115343925 (Germany)  English (United 
States)
89925 (Germany) English (United States)

Find a local number

Conference ID: 70849799
 Forgot your dial-in PIN? 
|Help


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@ .ericsson.net, where 
=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

[ovs-dev] Sync on PTAP, EXT-382 and NSH: Minutes of meeting Wed 2017-05-09, 14:00 CET

[Jan Scheurich]

Participants
*   Ben M, Zoltan, Georg, Jan, Simon

Review/Discussion of current patch packages
1.  RTNETLINK tunnel configuration - v3 still under review by Joe S (no 
update)
2.  L3 Tunneling
a.  v4: Ben P has merged 1st patch. Comment on 2nd patch fixed in v5
b.  v5: out on mailing list. Waiting for review by Ben
3.  PTAP - v2 (based on L3 Tunneling v5 and fully updated) to be sent this 
week
a.  To be reviewed by Simon and/or Ben P
4.  Basic NSH MD1 fields (according to google doc)
a.  v2 (rebased to PTAP v2) to be sent this week. To be reviewed by ???
5.  Gen encap/decap for Ethernet & NSH
a.  First working gitlab version internally reviewed
b.  Currently being refactored. Ready for mailing list perhaps 2 weeks from 
now
6.  L3 config based on RTNETLINK - not started. Jiri to talk to Eric if it 
can be started (no update)

Status/Planning
*   Lead time is getting an issue for 2.8 (branch date around July 1st)
  We need to focus on review and merge. Start with L3 tunneling v5 and 
RTNETLINK v3 then PTAP v2 and Basic NSH v2 when they are out.
*   Simon has some more bandwidth now and agreed to support Ben P with 
reviews. THANKS!
  We will send notifications to Simon/Ben when we push things for review.

Other
*   Ben Mackcrane explained slow progress in ONF due to ONF/ON.lab merger. 
Can possibly first document the assigned point codes outside formal ONF spec.
*   Discussed again the problem of Encap/Decap actions in Action Sets: 
execution order undefined, support for multiple encap/decap actions? In OVS we 
will not support encap/decap in Write Actions, but we would really like to have 
support for encap in groups. What to do?
*   Jan to provide access to private gitlab repo to Simon and Ben M.
  https://gitlab.com/JScheurich/ovs
*   Jan to call for next meeting in two weeks

BR, Jan

  -Original Appointment-
  From: Jan Scheurich
  Sent: Sunday, 18 December, 2016 15:34
  To: Jan Scheurich; Zoltán Balogh; Yang, Yi Y (yi.y.y...@intel.com); Jiri 
Benc (jb...@redhat.com); Pravin Shelar; Simon Horman 
(simon.hor...@netronome.com); 'ja...@ovn.org'; 'Ben Pfaff'; 
'ben.mackcr...@corsa.com'; d...@openvswitch.org; Georg Schmuecking
  Cc: Maria Pilar Benito Diez
  Subject: Sync on PTAP, EXT-382 and NSH - Tue 2017-05-09 17:00 CET
  When: Tuesday, 09 May, 2017 14:00-15:30 (UTC+01:00) Amsterdam, Berlin, 
Bern, Rome, Stockholm, Vienna.
  Where: Skype Meeting


  Moved to 2pm CET to accommodate Ben, who is in Boston that week.
  Perhaps also Yi can join at that time slot.


  Hi,

  Let's have a look at the status and work out a plan how to accelerate the 
review and merging in order to achieve the agreed target to upstream these 
changes in time for OVS 2.8.

  Thank you,
  Jan

  Link to the Google design doc:
  
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


  
.
  --> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
  Join by phone

  +492115343925 (Germany)English 
(United States)
  89925 (Germany)   English (United States)

  Find a local number

  Conference ID: 70849799
   Forgot your dial-in PIN? 
|Help


  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@ .ericsson.net, 
where =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

[ovs-dev] Sync on PTAP, EXT-382 and NSH - Tue 2017-05-09 17:00 CET

[Jan Scheurich]

Moved to 2pm CET to accommodate Ben, who is in Boston that week.
Perhaps also Yi can join at that time slot.


Hi,

Let's have a look at the status and work out a plan how to accelerate the 
review and merging in order to achieve the agreed target to upstream these 
changes in time for OVS 2.8.

Thank you,
Jan

Link to the Google design doc:
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


.
--> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
Join by phone

+492115343925 (Germany)  English (United 
States)
89925 (Germany) English (United States)

Find a local number

Conference ID: 70849799
 Forgot your dial-in PIN? 
|Help


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@ .ericsson.net, where 
=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

[ovs-dev] Sync on PTAP, EXT-382 and NSH - Tue 2017-05-09 17:00 CET

[Jan Scheurich]

Hi,

Let's have a look at the status and work out a plan how to accelerate the 
review and merging in order to achieve the agreed target to upstream these 
changes in time for OVS 2.8.

Thank you,
Jan

Link to the Google design doc:
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


.
--> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
Join by phone

+492115343925 (Germany)  English (United 
States)
89925 (Germany) English (United States)

Find a local number

Conference ID: 70849799
 Forgot your dial-in PIN? 
|Help


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@ .ericsson.net, where 
=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

[ovs-dev] Sync on PTAP, EXT-382 and NSH: Minutes of meeting Wed 2017-04-26, 17:00 CET

[Jan Scheurich]

Participants
*   Ben P, Zoltan, Georg, Jan, Jiri

Review/Discussion of current patch packages
1.  RTNETLINK tunnel configuration - v3 still under review by Joe S
2.  L3 Tunneling - v4 out fixing sparse errors. Ben to continue review
3.  PTAP - v1 out for review. Will need rebase to v4
4.  Basic NSH MD1 fields (according to google doc) - v1 out of review
5.  Gen encap/decap for NSH - v1 out, needs rework before review
6.  Gen encap/decap for Ethernet - ongoing (Zoltan)
7.  L3 config based on RTNETLINK - not started. Jiri to talk to Eric if it 
can be started

Status/Planning
*   Lead time is getting an issue for 2.8 (branch date around July 1st)
  We need to focus on review and merge. Start with L3 tunneling v4 and 
RTNETLINK v3 then Basic NSH
*   Ben to try to find an additional committer to help review
*   Jan, Zoltan and Yi to sort out open implementation issues with respect 
to generic encap/decap for NSH. Wait with pushing v2 for review until it is 
agreed in the team and functionally tested in accordance with the google doc.
*   Jan to call for next meeting in two weeks

BR, Jan

  -Original Appointment-
  From: Jan Scheurich
  Sent: Sunday, 18 December, 2016 15:34
  To: Jan Scheurich; Zoltán Balogh; Yang, Yi Y (yi.y.y...@intel.com); Jiri 
Benc (jb...@redhat.com); Pravin Shelar; Simon Horman 
(simon.hor...@netronome.com); 'ja...@ovn.org'; 'Ben Pfaff'; 
'ben.mackcr...@corsa.com'; d...@openvswitch.org; Georg Schmuecking
  Subject: Sync on PTAP, EXT-382 and NSH
  When: Wednesday, 26 April, 2017 17:00-18:30 (UTC+01:00) Amsterdam, 
Berlin, Bern, Rome, Stockholm, Vienna.
  Where: Skype Meeting


  Hi,

  The team is making good progress in preparing the various patch packages. 
We have a lot of things working in our gitlab repo 
(https://gitlab.com/JScheurich/ovs). v3 of the L3 tunneling patches are out on 
the mailing list since a week 
(https://mail.openvswitch.org/pipermail/ovs-dev/2017-April/330488.html) and are 
waiting for review.

  The PTAP series will follow next week. Also the NSH MD1 fields and 
generic encap/decap actions for Ethernet and NSH MD1 are mostly done.

  Let's have a look at the status and work out a plan how to accelerate the 
review and merging in order to achieve the agreed target to upstream these 
changes in time for OVS 2.8.

  Thank you,
  Jan

  Link to the Google design doc:
  
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


  
.
  --> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
  Join by phone

  +492115343925 (Germany)English 
(United States)
  89925 (Germany)   English (United States)

  Find a local number

  Conference ID: 70849799
   Forgot your dial-in PIN? 
|Help


  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@ .ericsson.net, 
where =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

[ovs-dev] Sync on PTAP, EXT-382 and NSH

[Jan Scheurich]

Hi,

The team is making good progress in preparing the various patch packages. We 
have a lot of things working in our gitlab repo 
(https://gitlab.com/JScheurich/ovs). v3 of the L3 tunneling patches are out on 
the mailing list since a week 
(https://mail.openvswitch.org/pipermail/ovs-dev/2017-April/330488.html) and are 
waiting for review.

The PTAP series will follow next week. Also the NSH MD1 fields and generic 
encap/decap actions for Ethernet and NSH MD1 are mostly done.

Let's have a look at the status and work out a plan how to accelerate the 
review and merging in order to achieve the agreed target to upstream these 
changes in time for OVS 2.8.

Thank you,
Jan

Link to the Google design doc:
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


.
--> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
Join by phone

+492115343925 (Germany)  English (United 
States)
89925 (Germany) English (United States)

Find a local number

Conference ID: 70849799
 Forgot your dial-in PIN? 
|Help


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@ .ericsson.net, where 
=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

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH: Minutes of meeting Mon 2017-03-13, 17:00 CET

[Ben Mack-Crane]

Hi Jan,

I do not understand the concept of masked packet type.  The note below from
the call is:


   - For masked packet_types use “/mask” or “*” notation ,
   e.g. packet_type=(1,*) to match any packet with name space ethertype.


Is this intended to relate to the canonical packet type ID or to any packet
type ID?  That is, would the indicated match include any protocol with an
EtherType identifier or only those that have their EtherType as the lowest
numbered namespace for which a protocol ID is defined (i.e., in the example
given not including Ethernet which has an ONF namespace ID)?

I'm still not sure how this masked match is useful.

Regards,
Ben

On Mon, Mar 13, 2017 at 12:23 PM, Jan Scheurich 
wrote:

> *Participants*
>
>- Ben P, Jiri, Simon, Thomas Morin, Zoltan, Georg, Jan
>
>
> *Review/Discussion of current patch packages*
>
>1. patch series on L3 tunneling user space (Ericsson)
>
>
>- Agreed on display format for packet_type field in match and flow keys
>
>
>- Matches: packet_type=(0,0), packet_type=(1,0x800), …
>- Flow keys:   packet_type(ns=0,id=0), packet_type(ns=1,id=0x800),
>….
>- For masked packet_types use “/mask” or “*” notation ,
>e.g. packet_type=(1,*) to match any packet with name space ethertype.
>
>
>- Keep packet_type field in struct dp_packet
>- Rename of dp_packet_l2() to dp_packet_eth()
>
>
>
>1. Kernel datapath backport L3 tunneling (Yi Yang)
>
>
>- Merged by Joe
>
>
>
>1. Kernel datapath tunnel configuration (RedHat, Eric Garver)
>
>
>- Still no comment yet
>- Resend as non-RFC patch to trigger new comments. *Please review**!*
>- Jan to include the new patch in Gitlab repo (see below).
>
>
> *Status/Planning of next work packages*
>
>- L3 tunneling user space - v2 this week, including vxlan-gpe.
>- PTAP patch set (Ericsson) - rebase to L3 tunneling v2
>- EXT-382 patch set (Ericsson) - not started
>- Basic NSH MD1 fields (Yi Yang) - started
>- Design of Generic TLV mapping (Jarno/Jan) - not started
>
>
> *AOB*
>
>- Thomas Morin joined out of interest in MPLSoGRE and MPLSoUDP.
>May contribute to testing if time allows.
>- Jan to provide info on how to access the gitlab.com repo for easy
>access
>
>
>- *https://gitlab.com/JScheurich/ovs*
>
>- Create free account at gitlab.com and send me your user id. I’ll add
>you to the project
>- I’ll distribute relevant branch names.
>
>
>- UDP as tunnel vport in user space to support things like MPLSoUDP
>
>
>- Kernel already supports arbitrary payload types in UDP tunnels with
>configurable mapping of destination port no to payload type.
>- Could be mimicked in OVS by providing the packet Ethertype as
>other_config parameter to the udp tunnel vport.
>
>
> BR, Jan
>
> -Original Appointment-
> *From:* Jan Scheurich
> *Sent:* Sunday, 18 December, 2016 15:34
> *To:* Jan Scheurich; Zoltán Balogh; Yang, Yi Y (yi.y.y...@intel.com);
> Jiri Benc (jb...@redhat.com); Pravin Shelar; Simon Horman (
> simon.hor...@netronome.com); 'ja...@ovn.org'; 'Ben Pfaff'; '
> ben.mackcr...@corsa.com'; d...@openvswitch.org; Georg Schmuecking
> *Subject:* Sync on PTAP, EXT-382 and NSH: Mon 2017-03-13, 17:00 CET
> *When:* Monday, 13 March, 2017 17:00-18:00 (UTC+01:00) Amsterdam, Berlin,
> Bern, Rome, Stockholm, Vienna.
> *Where:* Skype Meeting
>
>
> Hi,
>
> Please be invited to our next sync meeting: Mon 13 March, 5pm CET.
>
> Agenda:
>
>- Review/Discussion of current patch packages, e.g.
>
>
>- Display format for packet_type field in match and flow keys
>- packet_type in struct dp_packet or struct pkt_metadata
>
>
>- Status/Planning of next work packages
>- AOB
>
>
> Thank you,
> Jan
>
> Link to the Google design doc:
>
> *https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit*
> 
>
>
> 
> 
> .
> à *Join Skype Meeting* 
>
> This is an online meeting for Skype for Business, the professional
> meetings and communications app formerly known as Lync.
> Join by phone
>
> *+492115343925* <+492115343925,70849799%23> (Germany)  English
> (United States)
> *89925* <+89925,70849799%23> (Germany)  English (United States)
>
> *Find a local number* 
>
> Conference ID: 70849799
> *Forgot your dial-in PIN?*  |*Help*
> 
>
>
>
> 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 vide

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH: Minutes of meeting Mon 2017-03-13, 17:00 CET

[Ben Pfaff]

On Mon, Mar 13, 2017 at 05:23:26PM +, Jan Scheurich wrote:
> 2.  Kernel datapath tunnel configuration (RedHat, Eric Garver)
> *   Still no comment yet
> *   Resend as non-RFC patch to trigger new comments. Please review!
> *   Jan to include the new patch in Gitlab repo (see below).

I sent an email to Joe Stringer asking him to review this series or to
suggest someone to review it:
https://mail.openvswitch.org/pipermail/ovs-dev/2017-March/329737.html
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[ovs-dev] Sync on PTAP, EXT-382 and NSH: Minutes of meeting Mon 2017-03-13, 17:00 CET

[Jan Scheurich]

Participants
*   Ben P, Jiri, Simon, Thomas Morin, Zoltan, Georg, Jan

Review/Discussion of current patch packages
1.  patch series on L3 tunneling user space (Ericsson)
*   Agreed on display format for packet_type field in match and flow keys
*   Matches:packet_type=(0,0), packet_type=(1,0x800), ...
*   Flow keys:  packet_type(ns=0,id=0), packet_type(ns=1,id=0x800), 
*   For masked packet_types use "/mask" or "*" notation ,
e.g. packet_type=(1,*) to match any packet with name space ethertype.
*   Keep packet_type field in struct dp_packet
*   Rename of dp_packet_l2() to dp_packet_eth()

1.  Kernel datapath backport L3 tunneling (Yi Yang)
*   Merged by Joe

2.  Kernel datapath tunnel configuration (RedHat, Eric Garver)
*   Still no comment yet
*   Resend as non-RFC patch to trigger new comments. Please review!
*   Jan to include the new patch in Gitlab repo (see below).

Status/Planning of next work packages
*   L3 tunneling user space - v2 this week, including vxlan-gpe.
*   PTAP patch set (Ericsson) - rebase to L3 tunneling v2
*   EXT-382 patch set (Ericsson) - not started
*   Basic NSH MD1 fields (Yi Yang) - started
*   Design of Generic TLV mapping (Jarno/Jan) - not started

AOB
*   Thomas Morin joined out of interest in MPLSoGRE and MPLSoUDP.
   May contribute to testing if time allows.
*   Jan to provide info on how to access the gitlab.com repo for easy access
o   https://gitlab.com/JScheurich/ovs
o   Create free account at gitlab.com and send me your user id. I'll add 
you to the project
o   I'll distribute relevant branch names.
*   UDP as tunnel vport in user space to support things like MPLSoUDP
o   Kernel already supports arbitrary payload types in UDP tunnels with 
configurable mapping of destination port no to payload type.
o   Could be mimicked in OVS by providing the packet Ethertype as 
other_config parameter to the udp tunnel vport.

BR, Jan

  -Original Appointment-
  From: Jan Scheurich
  Sent: Sunday, 18 December, 2016 15:34
  To: Jan Scheurich; Zoltán Balogh; Yang, Yi Y (yi.y.y...@intel.com); Jiri 
Benc (jb...@redhat.com); Pravin Shelar; Simon Horman 
(simon.hor...@netronome.com); 'ja...@ovn.org'; 'Ben Pfaff'; 
'ben.mackcr...@corsa.com'; d...@openvswitch.org; Georg Schmuecking
  Subject: Sync on PTAP, EXT-382 and NSH: Mon 2017-03-13, 17:00 CET
  When: Monday, 13 March, 2017 17:00-18:00 (UTC+01:00) Amsterdam, Berlin, 
Bern, Rome, Stockholm, Vienna.
  Where: Skype Meeting


  Hi,

  Please be invited to our next sync meeting: Mon 13 March, 5pm CET.

  Agenda:
*   Review/Discussion of current patch packages, e.g.
o   Display format for packet_type field in match and flow keys
o   packet_type in struct dp_packet or struct pkt_metadata
*   Status/Planning of next work packages
*   AOB

  Thank you,
  Jan

  Link to the Google design doc:
  
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


  
.
  --> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
  Join by phone

  +492115343925 (Germany)English 
(United States)
  89925 (Germany)   English (United States)

  Find a local number

  Conference ID: 70849799
   Forgot your dial-in PIN? 
|Help


  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@ .ericsson.net, 
where =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

[ovs-dev] Sync on PTAP, EXT-382 and NSH: Mon 2017-03-13, 17:00 CET

[Jan Scheurich]

Hi,

Please be invited to our next sync meeting: Mon 13 March, 5pm CET.

Agenda:
*   Review/Discussion of current patch packages, e.g.
o   Display format for packet_type field in match and flow keys
o   packet_type in struct dp_packet or struct pkt_metadata
*   Status/Planning of next work packages
*   AOB

Thank you,
Jan

Link to the Google design doc:
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


.
--> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
Join by phone

+492115343925 (Germany)  English (United 
States)
89925 (Germany) English (United States)

Find a local number

Conference ID: 70849799
 Forgot your dial-in PIN? 
|Help


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@ .ericsson.net, where 
=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

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

[Simon Horman]

Hi,

Unfortunately I am unable to attend today's meeting due to illness.

2017/02/23 15:25 "Jan Scheurich" :

> Hi,
>
> It’s a while since we last had sync meeting. Now that OVS 2.7 is released,
> I would like to resume the calls.
>
> The first user space patch series to support L3 tunnels with a non-PTAP
> bridge was posted 3 weeks ago
> (
> *https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/328391.html*
> )
> but unfortunately hasn’t received any reviews yet.
>
> The next patch series adding support for PTAP as an optional feature of a
> bridge is completed and could be posted but we are waiting for the first
> patch set to be reviewed.
>
> In the meantime there has also been some progress with back-porting Jiri’s
> kernel datapath patches for L3 tunnels (and some earlier required kernel
> patches) to the OVS tree and have them configurable from user space through
> rtnetlink API.
>
> Let’s have a look at the status and work out a plan how to proceed in
> order to achieve the agreed target to upstream these changes in time for
> OVS 2.8.
>
> Thank you,
> Jan
>
> Link to the Google design doc:
>
> *https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit*
> 
>
>
> 
> 
> .
> à *Join Skype Meeting* 
>
> This is an online meeting for Skype for Business, the professional
> meetings and communications app formerly known as Lync.
> Join by phone
>
> *+492115343925* <+492115343925,70849799%23> (Germany)  English
> (United States)
> *89925* <+89925,70849799%23> (Germany)  English (United States)
>
> *Find a local number* 
>
> Conference ID: 70849799
> *Forgot your dial-in PIN?*  |*Help*
> 
>
>
>
> 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@
> .ericsson.net, where =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

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

[Jarno Rajahalme]

Thanks for the invite. In general I’d prefer if the email title or body would 
also contain the proposed meeting date & time.

I started review of the L3 userspace patches 3 weeks ago, but unfortunately 
have been swamped by urgent release tasks ever since. This should ease a bit 
next week.

  Jarno

> On Feb 23, 2017, at 6:24 AM, Jan Scheurich  wrote:
> 
> Hi,
>  
> It’s a while since we last had sync meeting. Now that OVS 2.7 is released, I 
> would like to resume the calls.
>  
> The first user space patch series to support L3 tunnels with a non-PTAP 
> bridge was posted 3 weeks ago
> (https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/328391.html 
> ) 
> but unfortunately hasn’t received any reviews yet. 
>  
> The next patch series adding support for PTAP as an optional feature of a 
> bridge is completed and could be posted but we are waiting for the first 
> patch set to be reviewed.
>  
> In the meantime there has also been some progress with back-porting Jiri’s 
> kernel datapath patches for L3 tunnels (and some earlier required kernel 
> patches) to the OVS tree and have them configurable from user space through 
> rtnetlink API.
>  
> Let’s have a look at the status and work out a plan how to proceed in order 
> to achieve the agreed target to upstream these changes in time for OVS 2.8.
>  
> Thank you,
> Jan
>  
> Link to the Google design doc:
> https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit
>  
> 
>  
>  
> .
>  <>à Join Skype Meeting    
> <><>
> This is an online meeting for Skype for Business, the professional meetings 
> and communications app formerly known as Lync.
> Join by phone
>  
> +492115343925  (Germany)  English 
> (United States)
> 89925  (Germany)  English (United States) 
>  
> Find a local number 
>  
> Conference ID: 70849799
> Forgot your dial-in PIN?  |Help 
>   
>  
>  
> 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@ .ericsson.net 
> , where =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

[ovs-dev] Sync on PTAP, EXT-382 and NSH

[Jan Scheurich]

Hi,

It's a while since we last had sync meeting. Now that OVS 2.7 is released, I 
would like to resume the calls.

The first user space patch series to support L3 tunnels with a non-PTAP bridge 
was posted 3 weeks ago
(https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/328391.html) but 
unfortunately hasn't received any reviews yet.

The next patch series adding support for PTAP as an optional feature of a 
bridge is completed and could be posted but we are waiting for the first patch 
set to be reviewed.

In the meantime there has also been some progress with back-porting Jiri's 
kernel datapath patches for L3 tunnels (and some earlier required kernel 
patches) to the OVS tree and have them configurable from user space through 
rtnetlink API.

Let's have a look at the status and work out a plan how to proceed in order to 
achieve the agreed target to upstream these changes in time for OVS 2.8.

Thank you,
Jan

Link to the Google design doc:
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit


.
--> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
Join by phone

+492115343925 (Germany)  English (United 
States)
89925 (Germany) English (United States)

Find a local number

Conference ID: 70849799
 Forgot your dial-in PIN? 
|Help


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@ .ericsson.net, where 
=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

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

[Jarno Rajahalme]

I also missed the meeting, did not have it my calendar, sorry.

  Jarno

> On Jan 24, 2017, at 5:52 AM, Jiri Benc  wrote:
> 
> On Wed, 18 Jan 2017 09:53:18 +, Jan Scheurich wrote:
>> Please be invited to the next sync meeting.
> 
> Sorry, won't make the meeting today. Too busy with DevConf.cz
> preparations.
> 
>> Actions Points:
>> AP-1 (Jarno): Coordinate review of Yi's backported net-next patches
>> AP-2 (Jiri) Check the ability of the kernel datapath to match on the
>> presence of Ethernet header w/o matching on Ethernet addresses.
>> Formating of such DP flows?
> 
> The OVS_KEY_ATTR_ETHERNET netlink attribute contains source and
> destination MAC address. It can be masked.
> 
> If the OVS_KEY_ATTR_ETHERNET attribute is present, only Ethernet frames
> will match. The MAC addresses may be masked (wildcarded). The
> OVS_KEY_ATTR_ETHERTYPE attribute indicates the ethertype to match and
> cannot be masked (it's always an exact match). If it's not present,
> ETH_P_802_2 is assumed.
> 
> If the OVS_KEY_ATTR_ETHERNET in not present, the OVS_KEY_ATTR_ETHERTYPE
> attribute is mandatory and indicates the ethertype to match. Again, it
> cannot be masked.
> 
> To answer the question, it's currently possible to match on Ethernet
> header without matching on Ethernet addresses but not without matching
> on ethertype. I think it can be relaxed with some work if needed.
> 
>> AP-3 (Jiri) Provide an update on the status and ETA of the RTNETLINK API 
>> patches
> 
> RFC patchset posted last week:
> https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/327749.html
> 
> Jiri

___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

[Jiri Benc]

On Wed, 18 Jan 2017 09:53:18 +, Jan Scheurich wrote:
> Please be invited to the next sync meeting.

Sorry, won't make the meeting today. Too busy with DevConf.cz
preparations.

> Actions Points:
> AP-1 (Jarno): Coordinate review of Yi's backported net-next patches
> AP-2 (Jiri) Check the ability of the kernel datapath to match on the
> presence of Ethernet header w/o matching on Ethernet addresses.
> Formating of such DP flows?

The OVS_KEY_ATTR_ETHERNET netlink attribute contains source and
destination MAC address. It can be masked.

If the OVS_KEY_ATTR_ETHERNET attribute is present, only Ethernet frames
will match. The MAC addresses may be masked (wildcarded). The
OVS_KEY_ATTR_ETHERTYPE attribute indicates the ethertype to match and
cannot be masked (it's always an exact match). If it's not present,
ETH_P_802_2 is assumed.

If the OVS_KEY_ATTR_ETHERNET in not present, the OVS_KEY_ATTR_ETHERTYPE
attribute is mandatory and indicates the ethertype to match. Again, it
cannot be masked.

To answer the question, it's currently possible to match on Ethernet
header without matching on Ethernet addresses but not without matching
on ethertype. I think it can be relaxed with some work if needed.

> AP-3 (Jiri) Provide an update on the status and ETA of the RTNETLINK API 
> patches

RFC patchset posted last week:
https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/327749.html

 Jiri
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[ovs-dev] Sync on PTAP, EXT-382 and NSH

[Jan Scheurich]

Hi,

Please be invited to the next sync meeting.

Minutes of the previous meeting:
https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/327738.html

Actions Points:
AP-1 (Jarno): Coordinate review of Yi's backported net-next patches
AP-2 (Jiri) Check the ability of the kernel datapath to match on the presence 
of Ethernet header w/o matching on Ethernet addresses. Formating of such DP 
flows?
AP-3 (Jiri) Provide an update on the status and ETA of the RTNETLINK API patches

Link to the Google design doc:
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit

Regards, Jan

.
--> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
Join by phone

+492115343925 (Germany)  English (United 
States)
89925 (Germany) English (United States)

Find a local number

Conference ID: 70849799
 Forgot your dial-in PIN? 
|Help


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@ .ericsson.net, where 
=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

[ovs-dev] Sync on PTAP, EXT-382 and NSH

[Jan Scheurich]

Hi,

Please be invited to the first sync meeting in the new year.

Agenda:
*   Status/progress/coordination of work packages:
  1 - L3 packets in kernel datapath (net-next)
  2 - Layer 3 tunnel configuration
  3 - L3 ports in non-PTAP bridge
  6 - VXLAN-GPE tunnel
  4 - PTAP bridge
  5 - Basic EXT-382
  7 - NSH MD1 Match Fields
  8 - Encap/Decap NSH MD1
  9 - GEN_TLV registers
  10 - NSH MD2 Support
*   ONF specification drafts for NSH and Generic TLV Mapping
*   Any other issue

Link to the Google design doc:
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit

Regards, Jan

.
--> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
Join by phone

+492115343925 (Germany)  English (United 
States)
89925 (Germany) English (United States)

Find a local number

Conference ID: 70849799
 Forgot your dial-in PIN? 
|Help


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@ .ericsson.net, where 
=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

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

[Jarno Rajahalme]

> On Jan 9, 2017, at 3:15 AM, Yang, Yi Y  wrote:
> 
> Jan, do you think when your proposal can be merged into ovs? The old NSH 
> implementation and new proposal aren’t contradictory, they can coexist, your 
> new proposal isn’t just for NSH, new proposal won’t have push_nsh & pop_nsh, 
> so we can let them coexist, let users decide which one is better.
>  
> We need to let users have one NSH version available before your proposal is 
> implemented. I support your proposal, but I have no way to do anything 
> helpful before your implementation for generic encap/decap and packet_type 
> are available.


OVS 2.7 is already feature frozen, and will release in February. Our intent is 
to have generic uncap/decap based NSH support in the OVS 2.8 release, so as far 
as OVS release cycle is concerned that is as soon as it can be.

  Jarno

>  
> I don’t know what other guys are thinking about this, it seems only you and I 
> are caring this J
>   <>
> From: Jan Scheurich [mailto:jan.scheur...@web.de] 
> Sent: Monday, January 9, 2017 8:23 AM
> To: Yang, Yi Y ; Jan Scheurich 
> ; Zoltán Balogh ; 
> Jiri Benc (jb...@redhat.com) ; Pravin Shelar 
> ; Simon Horman (simon.hor...@netronome.com) 
> ; 'jpet...@ovn.org' ; 
> 'ja...@ovn.org' ; 'Ben Pfaff' ; 
> 'ben.mackcr...@corsa.com' ; d...@openvswitch.org; 
> Zhou, Danny 
> Subject: Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH
>  
> Hi Yi,
> 
> I fully agree that support for NSH has been dragging along for to long. The 
> prime reason for this (in addition to the dependency on the L3 tunneling) 
> have been the mentioned conceptual problems with the current patches. Our 
> initiative is the attempt to put NSH on a solid basis in OF/OVS and make 
> faster progress by bundling all forces that agree on the solution documented 
> in the Google doc.
> 
> We wouldn't pursue this if we saw a chance of upstreaming the NSH patches as 
> they are now. We still hope that you can agree on the proposed approach and 
> help making NSH happen soon.
> 
> Please find some more answers below.
> 
> BR, Jan
> 
>  
> On 2017-01-03 01:59, Yang, Yi Y wrote:
> Jan, we can’t always be waiting endlessly, L3 patchset has been in Linux 
> kernel no matter you like it or not, we’re just to make sure ovs can work 
> with it, VxLAN-gpe is not only for NSH.
>  
> If you think L3 patchset in Linux kernel has any issue, please send out your 
> fix patches as soon as possible, it can be ported to ovs, this isn’t an 
> excuse we wait endlessly. I don’t think we need to wait it.
>  
> About several NSH-related issues you mentioned, I don’t think they are big 
> issues,   
>  
> Jan: “The NXM fields for NSH are used both as packet match fields and as 
> packet metadata fields (after decap). This ambiguity leads to problems, 
> latest when dealing with NSH in NSH packets.”
>  
> Yi: VxLAN tunnel metadata used the same way, isn’t it? What problems do you 
> mean? I believe we can fix them even if they are really so-called “problems”.
> Tunnel metadata do not have that issue. They are only valid after the tunnel 
> packet has been decapsulated or before it is encapsulated, but never when it 
> is encapsulated. However, if you use OXM fields both for matching present 
> packet headers and for keeping their content as packet metadata after 
> decapsulation, both the meaning of matching on them and manipulating them is 
> essentially undefined. This is most obvious for a packet with two NSH headers 
> in a row (hierarchical SFC).
> 
> Jan: “They introduce push/pop_nsh OpenFlow actions without dealing with the 
> resulting non-Ethernet packets in the pipeline. The behavior is not at all 
> well defined.”
> Yi: L3 patchset is just for this, isn’t it? Your new proposal will also 
> depend on L3 patchset, right?
> No, the L3 patch set merely allows to connect L3 ports to an Ethernet only 
> (non-PTAP) OF pipeline. The packets in the OF pipeline are logically always 
> L2 packets, even though the representation inside ofproto-dpif may 
> temporarily omit the Ethernet header from the packet. But the L2 fields 
> dl_src, dl_dst and dl_type can be matched on and manipulated by the OF 
> controller at any time. When a packet is sent to an Ethernet port, the L2 
> header containing these fields is always present.
> 
> There is nothing in the L3 tunneling patch set that would allow an OF 
> controller to modify the packet type in the pipeline. For this we need the 
> concept of packet-type aware pipeline and the packet_type match field.
> 
> The new proposal based on PTAP does indeed depend on "versatile" tunnel 
> ports, as e.g. already implemented in the kernel datapath. Zoltan and I are 
>

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

[Jiri Benc]

On Mon, 9 Jan 2017 11:15:22 +, Yang, Yi Y wrote:
> We need to let users have one NSH version available before your
> proposal is implemented. I support your proposal, but I have no way
> to do anything helpful before your implementation for generic
> encap/decap and packet_type are available.

Implementing something that we know will be obsolete in a relatively
short time does not make much sense. It's painful but the focus here is
long term maintainability, not short time gain.

> I don't know what other guys are thinking about this, it seems only
> you and I are caring this :)

The truth is very few people care about NSH in ovs. There is a lot of
people who *claim* they care and that they need it implemented ASAP but
when it comes to doing real work, it's only you, Ericsson and partially
Red Hat. Which, in my opinion, pretty much reflects the urgency. If
people did really care, they would invest into this. Hopefully this
will change now with Jan taking lead in this.

I like Jan's proposal.

 Jiri
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

[Yang, Yi Y]

Jan, do you think when your proposal can be merged into ovs? The old NSH 
implementation and new proposal aren't contradictory, they can coexist, your 
new proposal isn't just for NSH, new proposal won't have push_nsh & pop_nsh, so 
we can let them coexist, let users decide which one is better.

We need to let users have one NSH version available before your proposal is 
implemented. I support your proposal, but I have no way to do anything helpful 
before your implementation for generic encap/decap and packet_type are 
available.

I don't know what other guys are thinking about this, it seems only you and I 
are caring this :)

From: Jan Scheurich [mailto:jan.scheur...@web.de]
Sent: Monday, January 9, 2017 8:23 AM
To: Yang, Yi Y ; Jan Scheurich 
; Zoltán Balogh ; Jiri 
Benc (jb...@redhat.com) ; Pravin Shelar ; 
Simon Horman (simon.hor...@netronome.com) ; 
'jpet...@ovn.org' ; 'ja...@ovn.org' ; 'Ben 
Pfaff' ; 'ben.mackcr...@corsa.com' 
; d...@openvswitch.org; Zhou, Danny 

Subject: Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH


Hi Yi,

I fully agree that support for NSH has been dragging along for to long. The 
prime reason for this (in addition to the dependency on the L3 tunneling) have 
been the mentioned conceptual problems with the current patches. Our initiative 
is the attempt to put NSH on a solid basis in OF/OVS and make faster progress 
by bundling all forces that agree on the solution documented in the Google doc.

We wouldn't pursue this if we saw a chance of upstreaming the NSH patches as 
they are now. We still hope that you can agree on the proposed approach and 
help making NSH happen soon.

Please find some more answers below.

BR, Jan

On 2017-01-03 01:59, Yang, Yi Y wrote:
Jan, we can't always be waiting endlessly, L3 patchset has been in Linux kernel 
no matter you like it or not, we're just to make sure ovs can work with it, 
VxLAN-gpe is not only for NSH.

If you think L3 patchset in Linux kernel has any issue, please send out your 
fix patches as soon as possible, it can be ported to ovs, this isn't an excuse 
we wait endlessly. I don't think we need to wait it.

About several NSH-related issues you mentioned, I don't think they are big 
issues,

Jan: "The NXM fields for NSH are used both as packet match fields and as packet 
metadata fields (after decap). This ambiguity leads to problems, latest when 
dealing with NSH in NSH packets."

Yi: VxLAN tunnel metadata used the same way, isn't it? What problems do you 
mean? I believe we can fix them even if they are really so-called "problems".
Tunnel metadata do not have that issue. They are only valid after the tunnel 
packet has been decapsulated or before it is encapsulated, but never when it is 
encapsulated. However, if you use OXM fields both for matching present packet 
headers and for keeping their content as packet metadata after decapsulation, 
both the meaning of matching on them and manipulating them is essentially 
undefined. This is most obvious for a packet with two NSH headers in a row 
(hierarchical SFC).

Jan: "They introduce push/pop_nsh OpenFlow actions without dealing with the 
resulting non-Ethernet packets in the pipeline. The behavior is not at all well 
defined."
Yi: L3 patchset is just for this, isn't it? Your new proposal will also depend 
on L3 patchset, right?
No, the L3 patch set merely allows to connect L3 ports to an Ethernet only 
(non-PTAP) OF pipeline. The packets in the OF pipeline are logically always L2 
packets, even though the representation inside ofproto-dpif may temporarily 
omit the Ethernet header from the packet. But the L2 fields dl_src, dl_dst and 
dl_type can be matched on and manipulated by the OF controller at any time. 
When a packet is sent to an Ethernet port, the L2 header containing these 
fields is always present.

There is nothing in the L3 tunneling patch set that would allow an OF 
controller to modify the packet type in the pipeline. For this we need the 
concept of packet-type aware pipeline and the packet_type match field.

The new proposal based on PTAP does indeed depend on "versatile" tunnel ports, 
as e.g. already implemented in the kernel datapath. Zoltan and I are very close 
to having the user-space parts of the L3 tunneling patch sets adapted to the 
packet_type concept. These replace the user-space patches in your latest L3 
tunneling patch set. Then we'd have work packages 1,2,3 and 6 of the document 
in place and we could focus in parallel on 4 (PTAP), 5 (EXT-382) and NSH MD1 (7 
and 8).


Jan: "The re-use of the Geneve tunnel metada fields for NSH MD2 TLVs is 
problematic because
a) it again mixes packet metadata and header fields and
b) it couldn't handle NSH MD2 in Geneve tunnels."
Yi: You have to admit this is the existing best solution for MD type 2, it is 
not perfect, but it is ready for use. 

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

[Jan Scheurich]

7;ja...@ovn.org' ; 
'Ben Pfaff' ; 'ben.mackcr...@corsa.com' 
; d...@openvswitch.org; Zhou, Danny 


*Subject:* Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

Hi Yi,

Thanks for the confirmation and for rebasing the existing L3 tunneling 
patches to include VXLAN-GPE.


Unfortunately, Simon's original user-space implementation in patches 
9/17 through 11/17 using base_layer and offset fields in dp_packet is 
not compatible to our ongoing implementation of versatile tunnel ports 
in PTAP and non-PTAP bridges, which is based on an explicit 
packet_type field.


To avoid extensive rework, I would rather not merge these changes into 
master now but substitute them with the final implementation. This is 
work-package "3 - L3 ports in non-PTAP pipeline" in our Google doc and 
Zoltan and I will have that ready soon.


Regarding the implementation of NSH support, we should work together 
to implement what is described in the Google doc: 
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit#heading=h.wp4o2op1lp9z


In our opinion the earlier NSH patches cannot be upstreamed because of 
a couple of fundamental conceptual problems:


 1. The NXM fields for NSH are used both as packet match fields and as
packet metadata fields (after decap).
This ambiguity leads to problems, latest when dealing with NSH in
NSH packets.
 2. They introduce push/pop_nsh OpenFlow actions without dealing with
the resulting non-Ethernet packets in the pipeline. The behavior
is not at all well defined.
 3. The re-use of the Geneve tunnel metada fields for NSH MD2 TLVs is
problematic because
a) it again mixes packet metadata and header fields and
b) it couldn't handle NSH MD2 in Geneve tunnels.

All these issues are addressed in the proposed new solution built on 
PTAP and EXT-382. The fundamentals are aligned with ONF (OXM classes 
already assigned), so that there is a good chance that we can feed the 
OVS implementation of NSH into the next OpenFlow standard. The first 
phase covering the fixed MD1 NSH header should also be possible to 
upstream in Q1/17, quite soon after the basic patches for PTAP and 
EXT-382.


Let's have a direct talk when I'm back in office after New Year.

Regards, Jan

On 2016-12-23 01:51, Yang, Yi Y wrote:

Hi, Jan

I confirm I can take VxLAN-gpe and NSH  related work, now I'm pushing 
Jiri's L3 patches ot ovs in order that it can be ported into ovs as early as 
possible, Pravin, Joe and Jarno found some vlan-related issues in Jiri's L3 
patches in net-next and worked out several patches for net-next, but they are 
not merged yet.

But I have had  a workable local ovs version with Jiri's l3 patches and 
Jarno's fix patches merged, I have worked out several patches to make sure 
VxLAN-gpe can work in layer3 and layer 2 mode, now they are ready except DPDK 
userspace has some issues which I'm debugging.

So I think L3 patches and VxLAN-gpe will be ready very soon.

I remember every guys agreed our old NSH implementation with MD type 2 
support, I think that will be the fastest path we can take for NSH support, I 
dare to guarantee it can be ready to merge about one month after (including 
kernel patches and ovs patches)

I'm wondering if you guys can make a form to list pros and cons for the old 
implementation way and this new one in order that every people can clearly know 
what the advantages and disadvantages for them are.

From: Jan Scheurich [mailto:jan.scheur...@ericsson.com]

Sent: Thursday, December 22, 2016 6:51 PM

To: Zoltán Balogh <mailto:zoltan.bal...@ericsson.com>; Yang, Yi Y <mailto:yi.y.y...@intel.com>; Jiri Benc (jb...@redhat.com 
<mailto:jb...@redhat.com>) <mailto:jb...@redhat.com>; Pravin Shelar <mailto:pshe...@ovn.org>; Simon Horman (simon.hor...@netronome.com 
<mailto:simon.hor...@netronome.com>) <mailto:simon.hor...@netronome.com>; 'jpet...@ovn.org <mailto:jpet...@ovn.org>' <mailto:jpet...@ovn.org>; 
'ja...@ovn.org <mailto:ja...@ovn.org>' <mailto:ja...@ovn.org>; 'Ben Pfaff' <mailto:bpf...@vmware.com>; 'ben.mackcr...@corsa.com 
<mailto:ben.mackcr...@corsa.com>' <mailto:ben.mackcr...@corsa.com>;d...@openvswitch.org <mailto:d...@openvswitch.org>

Subject: RE: Sync on PTAP, EXT-382 and NSH

Thanks for the good meeting. Here are my notes:

Date: 2016-12-21, 17-18:30 CET

Participants: Jarno R, Ben P, Ben M-C, Jiri B, Simon H, Zoltan B, Jan S

Summary:

·Discussed making PTAP, EXT-382 and NSH available as extensions to 
OF 1.3.

·No big deal for the match fields and the encap/decap actions

·Potential problem could be the missing packet_type information in 
OF 1.3 Packet In, Packet Out and Table Features (Note: Closer inspection of OF 

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

[Yang, Yi Y]

Jan, we can't always be waiting endlessly, L3 patchset has been in Linux kernel 
no matter you like it or not, we're just to make sure ovs can work with it, 
VxLAN-gpe is not only for NSH.

If you think L3 patchset in Linux kernel has any issue, please send out your 
fix patches as soon as possible, it can be ported to ovs, this isn't an excuse 
we wait endlessly. I don't think we need to wait it.

About several NSH-related issues you mentioned, I don't think they are big 
issues,


Jan: "The NXM fields for NSH are used both as packet match fields and as packet 
metadata fields (after decap). This ambiguity leads to problems, latest when 
dealing with NSH in NSH packets."

Yi: VxLAN tunnel metadata used the same way, isn't it? What problems do you 
mean? I believe we can fix them even if they are really so-called "problems".
Jan: "They introduce push/pop_nsh OpenFlow actions without dealing with the 
resulting non-Ethernet packets in the pipeline. The behavior is not at all well 
defined."
Yi: L3 patchset is just for this, isn't it? Your new proposal will also depend 
on L3 patchset, right?
Jan: "The re-use of the Geneve tunnel metada fields for NSH MD2 TLVs is 
problematic because
a) it again mixes packet metadata and header fields and
b) it couldn't handle NSH MD2 in Geneve tunnels."
Yi: You have to admit this is the existing best solution for MD type 2, it is 
not perfect, but it is ready for use. I don't think people will use GENEVE for 
NSH now, we can modify it to adapt to such use case if people really would like 
to do that way.

Jan, I don't think the new proposal fixed the above issues you mentioned, on 
the contrary, it will make things more complicated. Why don't we go fats path 
instead take a from-a-scratch way?



From: Jan Scheurich [mailto:jan.scheur...@web.de]
Sent: Friday, December 30, 2016 6:34 PM
To: Yang, Yi Y ; Jan Scheurich 
; Zoltán Balogh ; Jiri 
Benc (jb...@redhat.com) ; Pravin Shelar ; 
Simon Horman (simon.hor...@netronome.com) ; 
'jpet...@ovn.org' ; 'ja...@ovn.org' ; 'Ben 
Pfaff' ; 'ben.mackcr...@corsa.com' 
; d...@openvswitch.org; Zhou, Danny 

Subject: Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH


Hi Yi,

Thanks for the confirmation and for rebasing the existing L3 tunneling patches 
to include VXLAN-GPE.

Unfortunately, Simon's original user-space implementation in patches 9/17 
through 11/17 using base_layer and offset fields in dp_packet is not compatible 
to our ongoing implementation of versatile tunnel ports in PTAP and non-PTAP 
bridges, which is based on an explicit packet_type field.

To avoid extensive rework, I would rather not merge these changes into master 
now but substitute them with the final implementation. This is work-package "3 
- L3 ports in non-PTAP pipeline" in our Google doc and Zoltan and I will have 
that ready soon.

Regarding the implementation of NSH support, we should work together to 
implement what is described in the Google doc: 
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit#heading=h.wp4o2op1lp9z

In our opinion the earlier NSH patches cannot be upstreamed because of a couple 
of fundamental conceptual problems:

  1.  The NXM fields for NSH are used both as packet match fields and as packet 
metadata fields (after decap).
This ambiguity leads to problems, latest when dealing with NSH in NSH packets.
  2.  They introduce push/pop_nsh OpenFlow actions without dealing with the 
resulting non-Ethernet packets in the pipeline. The behavior is not at all well 
defined.
  3.  The re-use of the Geneve tunnel metada fields for NSH MD2 TLVs is 
problematic because
a) it again mixes packet metadata and header fields and
b) it couldn't handle NSH MD2 in Geneve tunnels.
All these issues are addressed in the proposed new solution built on PTAP and 
EXT-382. The fundamentals are aligned with ONF (OXM classes already assigned), 
so that there is a good chance that we can feed the OVS implementation of NSH 
into the next OpenFlow standard. The first phase covering the fixed MD1 NSH 
header should also be possible to upstream in Q1/17, quite soon after the basic 
patches for PTAP and EXT-382.

Let's have a direct talk when I'm back in office after New Year.

Regards, Jan

On 2016-12-23 01:51, Yang, Yi Y wrote:

Hi, Jan



I confirm I can take VxLAN-gpe and NSH  related work, now I'm pushing Jiri's L3 
patches ot ovs in order that it can be ported into ovs as early as possible, 
Pravin, Joe and Jarno found some vlan-related issues in Jiri's L3 patches in 
net-next and worked out several patches for net-next, but they are not merged 
yet.



But I have had  a workable local ovs version with Jiri's l3 patches and Jarno's 
fix patches merged, I have worked out several patches to make sure VxLAN-gpe 
can work in layer3 and layer 2 mo

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

[Jan Scheurich]

Hi Yi,

Thanks for the confirmation and for rebasing the existing L3 tunneling 
patches to include VXLAN-GPE.


Unfortunately, Simon's original user-space implementation in patches 
9/17 through 11/17 using base_layer and offset fields in dp_packet is 
not compatible to our ongoing implementation of versatile tunnel ports 
in PTAP and non-PTAP bridges, which is based on an explicit packet_type 
field.


To avoid extensive rework, I would rather not merge these changes into 
master now but substitute them with the final implementation. This is 
work-package "3 - L3 ports in non-PTAP pipeline" in our Google doc and 
Zoltan and I will have that ready soon.


Regarding the implementation of NSH support, we should work together to 
implement what is described in the Google doc: 
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit#heading=h.wp4o2op1lp9z


In our opinion the earlier NSH patches cannot be upstreamed because of a 
couple of fundamental conceptual problems:


 * The NXM fields for NSH are used both as packet match fields and as
   packet metadata fields (after decap).
   This ambiguity leads to problems, latest when dealing with NSH in
   NSH packets.
 * They introduce push/pop_nsh OpenFlow actions without dealing with
   the resulting non-Ethernet packets in the pipeline. The behavior is
   not at all well defined.
 * The re-use of the Geneve tunnel metada fields for NSH MD2 TLVs is
   problematic because
   a) it again mixes packet metadata and header fields and
   b) it couldn't handle NSH MD2 in Geneve tunnels.

All these issues are addressed in the proposed new solution built on 
PTAP and EXT-382. The fundamentals are aligned with ONF (OXM classes 
already assigned), so that there is a good chance that we can feed the 
OVS implementation of NSH into the next OpenFlow standard. The first 
phase covering the fixed MD1 NSH header should also be possible to 
upstream in Q1/17, quite soon after the basic patches for PTAP and EXT-382.


Let's have a direct talk when I'm back in office after New Year.

Regards, Jan


On 2016-12-23 01:51, Yang, Yi Y wrote:

Hi, Jan

I confirm I can take VxLAN-gpe and NSH  related work, now I'm pushing Jiri's L3 
patches ot ovs in order that it can be ported into ovs as early as possible, 
Pravin, Joe and Jarno found some vlan-related issues in Jiri's L3 patches in 
net-next and worked out several patches for net-next, but they are not merged 
yet.

But I have had  a workable local ovs version with Jiri's l3 patches and Jarno's 
fix patches merged, I have worked out several patches to make sure VxLAN-gpe 
can work in layer3 and layer 2 mode, now they are ready except DPDK userspace 
has some issues which I'm debugging.

So I think L3 patches and VxLAN-gpe will be ready very soon.

I remember every guys agreed our old NSH implementation with MD type 2 support, 
I think that will be the fastest path we can take for NSH support, I dare to 
guarantee it can be ready to merge about one month after (including kernel 
patches and ovs patches)

I'm wondering if you guys can make a form to list pros and cons for the old 
implementation way and this new one in order that every people can clearly know 
what the advantages and disadvantages for them are.

From: Jan Scheurich [mailto:jan.scheur...@ericsson.com]
Sent: Thursday, December 22, 2016 6:51 PM
To: Zoltán Balogh ; Yang, Yi Y ; Jiri Benc (jb...@redhat.com) 
; Pravin Shelar ; Simon Horman (simon.hor...@netronome.com) 
; 'jpet...@ovn.org' ; 'ja...@ovn.org' ; 'Ben Pfaff' 
; 'ben.mackcr...@corsa.com' ; d...@openvswitch.org
Subject: RE: Sync on PTAP, EXT-382 and NSH

Thanks for the good meeting. Here are my notes:

Date: 2016-12-21, 17-18:30 CET
Participants: Jarno R, Ben P, Ben M-C, Jiri B, Simon H, Zoltan B, Jan S

Summary:
·Discussed making PTAP, EXT-382 and NSH available as extensions to OF 
1.3.
·No big deal for the match fields and the encap/decap actions
·Potential problem could be the missing packet_type information in OF 
1.3 Packet In, Packet Out and Table Features (Note: Closer inspection of OF 
1.5.1 spec reveals that OXM packet_type is part of struct ofp_match in Packet 
In and Packet Out. It should be OK for an OF 1.3 controller extended with PTAP 
support)
·Is it simpler for the controllers to upgrade to OF 1.5?
·Deferred the decision
·Agreed to use the (to be assigned) OXM field code points for 
packet_type and NSH in OVS for all OF versions
·Agreed to allow all NS=1 packet types received from/sent to a tunnel 
port that uses the Ethertype name space in its protocol field (like GRE). Other 
versatile tunnel ports (like VXLAN-GPE) which have their own code points 
require explicit mapping and must drop packets for which no such mapping exists.
·Discussed introduction of a new OXM class for the proposed GEN_TLV 
fields
·No problem to reserve an OXM class even before those fields are 
standardized
·For sta

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

[Ben Mack-Crane]

Re: Discussed introduction of a new OXM class for the proposed GEN_TLV
fields

   - No problem to reserve an OXM class even before those fields are
   standardized


We have allocated OXM class 0x8005 for TLV value mapping (experimental for
now) in the ONF Registry
.

Regards,
Ben

On Thu, Dec 22, 2016 at 4:51 AM, Jan Scheurich 
wrote:

> Thanks for the good meeting. Here are my notes:
>
> Date: 2016-12-21, 17-18:30 CET
> Participants: Jarno R, Ben P, Ben M-C, Jiri B, Simon H, Zoltan B, Jan S
>
> Summary:
>
>- Discussed making PTAP, EXT-382 and NSH available as extensions to OF
>1.3.
>
>
>- No big deal for the match fields and the encap/decap actions
>- Potential problem could be the missing packet_type information in OF
>1.3 Packet In, Packet Out and Table Features (Note: Closer inspection of OF
>1.5.1 spec reveals that OXM packet_type is part of struct ofp_match in
>Packet In and Packet Out. It should be OK for an OF 1.3 controller extended
>with PTAP support)
>- Is it simpler for the controllers to upgrade to OF 1.5?
>- Deferred the decision
>
>
>- Agreed to use the (to be assigned) OXM field code points for
>packet_type and NSH in OVS for all OF versions
>- Agreed to allow all NS=1 packet types received from/sent to a tunnel
>port that uses the Ethertype name space in its protocol field (like GRE).
>Other versatile tunnel ports (like VXLAN-GPE) which have their own code
>points require explicit mapping and must drop packets for which no such
>mapping exists.
>- Discussed introduction of a new OXM class for the proposed GEN_TLV
>fields
>
>
>- No problem to reserve an OXM class even before those fields are
>standardized
>- For standardization we also need to specify a dynamic binding
>mechanism between protocol TLVs and GEN_TLV fields. We can submit the
>mechanism to be developed in OVS for standardization when its stable.
>
>
>- Walk-through of division into work packages:
>
>
>- Some follow up needed for the L3 packet support kernel datapath
>patches
>- Rest OK
>- Technical discussion around GEN_TLV and use for NSH MD2 in
>conjunction with encap(NSH) to be continued in the Google doc.
>
>
>- Time line:
>
>
>- The entire work should be targeting OVS 2.8 with feature freeze
>around July
>
>
>- OVS 2.7 is having feature freeze already in early January
>
>
>- Work packages can be upstreamed individually. NSH MD1 support
>doesn’t have to wait for MD2
>
>
>- Basically agreed to the work split proposed in the document:
>
>
>- RedHat is taking the patches for L3 tunnel configuration (including
>use of RTNETLINK for config)
>- Ericsson take the infrastructure components (L3-tunnels, PTAP, Basic
>EXT-382)
>- Jarno (VMware) will handle the GEN_TLV infrastructure
>- Confirm with Yi Yang (Intel): Can they take VXLAN-GPE and the
>NSH-specific WPs? Or do they need help?
>
>
>- Way of working
>
>
>- Continue the meeting series for coordination of effort
>- Can use a feature integration branch to ease the joint development
>and test
>- Review of patches mainly through the ovs-dev mailing list
>- Use tools like git citool to break up larger patches into a series
>of smaller patches for review
>
>
>
>
> -Original Appointment-
> *From:* Jan Scheurich
> *Sent:* Sunday, 18 December, 2016 15:34
> *To:* Jan Scheurich; Zoltán Balogh; Yang, Yi Y (yi.y.y...@intel.com);
> Jiri Benc (jb...@redhat.com); Pravin Shelar; Simon Horman (
> simon.hor...@netronome.com); jpet...@ovn.org; ja...@ovn.org; Ben Pfaff; '
> ben.mackcr...@corsa.com'; d...@openvswitch.org
> *Subject:* Sync on PTAP, EXT-382 and NSH
> *When:* Wednesday, 21 December, 2016 17:00-18:30 (UTC+01:00) Amsterdam,
> Berlin, Bern, Rome, Stockholm, Vienna.
> *Where:* Skype Meeting
>
>
> Moved to Wednesday same time to accommodate Jiri.
> Hope this is still OK for the others.
>
>
> Hello all,
>
> I would like to call for a final sync meeting before the Christmas break.
>
> Now that we have gone through the main aspects of the design, I would like
> to focus on how to divide the entire function into manageable pieces,
> discuss the potential work split, an integration anatomy and a rough time
> plane for upstreaming. I will try to prepare input in our Google doc for
> this.
>
>
> *https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit*
> 
>
> If there are questions left regarding the design, please bring them up as
> well. You can also comment on the document at any time.
>
> Regards, Jan
>
> 
> 
> .
> à *Join Skype Meeting* 

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

[Yang, Yi Y]

Hi, Jan

I confirm I can take VxLAN-gpe and NSH  related work, now I'm pushing Jiri's L3 
patches ot ovs in order that it can be ported into ovs as early as possible, 
Pravin, Joe and Jarno found some vlan-related issues in Jiri's L3 patches in 
net-next and worked out several patches for net-next, but they are not merged 
yet.

But I have had  a workable local ovs version with Jiri's l3 patches and Jarno's 
fix patches merged, I have worked out several patches to make sure VxLAN-gpe 
can work in layer3 and layer 2 mode, now they are ready except DPDK userspace 
has some issues which I'm debugging.

So I think L3 patches and VxLAN-gpe will be ready very soon.

I remember every guys agreed our old NSH implementation with MD type 2 support, 
I think that will be the fastest path we can take for NSH support, I dare to 
guarantee it can be ready to merge about one month after (including kernel 
patches and ovs patches)

I'm wondering if you guys can make a form to list pros and cons for the old 
implementation way and this new one in order that every people can clearly know 
what the advantages and disadvantages for them are.

From: Jan Scheurich [mailto:jan.scheur...@ericsson.com]
Sent: Thursday, December 22, 2016 6:51 PM
To: Zoltán Balogh ; Yang, Yi Y 
; Jiri Benc (jb...@redhat.com) ; Pravin 
Shelar ; Simon Horman (simon.hor...@netronome.com) 
; 'jpet...@ovn.org' ; 
'ja...@ovn.org' ; 'Ben Pfaff' ; 
'ben.mackcr...@corsa.com' ; d...@openvswitch.org
Subject: RE: Sync on PTAP, EXT-382 and NSH

Thanks for the good meeting. Here are my notes:

Date: 2016-12-21, 17-18:30 CET
Participants: Jarno R, Ben P, Ben M-C, Jiri B, Simon H, Zoltan B, Jan S

Summary:
·Discussed making PTAP, EXT-382 and NSH available as extensions to OF 
1.3.
·No big deal for the match fields and the encap/decap actions
·Potential problem could be the missing packet_type information in OF 
1.3 Packet In, Packet Out and Table Features (Note: Closer inspection of OF 
1.5.1 spec reveals that OXM packet_type is part of struct ofp_match in Packet 
In and Packet Out. It should be OK for an OF 1.3 controller extended with PTAP 
support)
·Is it simpler for the controllers to upgrade to OF 1.5?
·Deferred the decision
·Agreed to use the (to be assigned) OXM field code points for 
packet_type and NSH in OVS for all OF versions
·Agreed to allow all NS=1 packet types received from/sent to a tunnel 
port that uses the Ethertype name space in its protocol field (like GRE). Other 
versatile tunnel ports (like VXLAN-GPE) which have their own code points 
require explicit mapping and must drop packets for which no such mapping exists.
·Discussed introduction of a new OXM class for the proposed GEN_TLV 
fields
·No problem to reserve an OXM class even before those fields are 
standardized
·For standardization we also need to specify a dynamic binding 
mechanism between protocol TLVs and GEN_TLV fields. We can submit the mechanism 
to be developed in OVS for standardization when its stable.
·Walk-through of division into work packages:
·Some follow up needed for the L3 packet support kernel datapath patches
·Rest OK
·Technical discussion around GEN_TLV and use for NSH MD2 in conjunction 
with encap(NSH) to be continued in the Google doc.
·Time line:
·The entire work should be targeting OVS 2.8 with feature freeze around 
July
·OVS 2.7 is having feature freeze already in early January
·Work packages can be upstreamed individually. NSH MD1 support doesn't 
have to wait for MD2
·Basically agreed to the work split proposed in the document:
·RedHat is taking the patches for L3 tunnel configuration (including 
use of RTNETLINK for config)
·Ericsson take the infrastructure components (L3-tunnels, PTAP, Basic 
EXT-382)
·Jarno (VMware) will handle the GEN_TLV infrastructure
·Confirm with Yi Yang (Intel): Can they take VXLAN-GPE and the 
NSH-specific WPs? Or do they need help?
·Way of working
·Continue the meeting series for coordination of effort
·Can use a feature integration branch to ease the joint development and 
test
·Review of patches mainly through the ovs-dev mailing list
·Use tools like git citool to break up larger patches into a series of 
smaller patches for review



-Original Appointment-
From: Jan Scheurich
Sent: Sunday, 18 December, 2016 15:34
To: Jan Scheurich; Zoltán Balogh; Yang, Yi Y 
(yi.y.y...@intel.com); Jiri Benc 
(jb...@redhat.com); Pravin Shelar; Simon Horman 
(simon.hor...@netronome.com); 
jpet...@ovn.org; ja...@ovn.org; 
Ben Pfaff; 'ben.mackcr...@corsa.com'; 
d...@openvswitch.org
Subject: Sync on PTAP, EXT-382 and NSH
When: Wednesday, 21 December, 2016 17:00

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

[Jan Scheurich]

Thanks for the good meeting. Here are my notes:

Date: 2016-12-21, 17-18:30 CET
Participants: Jarno R, Ben P, Ben M-C, Jiri B, Simon H, Zoltan B, Jan S

Summary:
*   Discussed making PTAP, EXT-382 and NSH available as extensions to OF 
1.3.
o   No big deal for the match fields and the encap/decap actions
o   Potential problem could be the missing packet_type information in OF 
1.3 Packet In, Packet Out and Table Features (Note: Closer inspection of OF 
1.5.1 spec reveals that OXM packet_type is part of struct ofp_match in Packet 
In and Packet Out. It should be OK for an OF 1.3 controller extended with PTAP 
support)
o   Is it simpler for the controllers to upgrade to OF 1.5?
o   Deferred the decision
*   Agreed to use the (to be assigned) OXM field code points for 
packet_type and NSH in OVS for all OF versions
*   Agreed to allow all NS=1 packet types received from/sent to a tunnel 
port that uses the Ethertype name space in its protocol field (like GRE). Other 
versatile tunnel ports (like VXLAN-GPE) which have their own code points 
require explicit mapping and must drop packets for which no such mapping exists.
*   Discussed introduction of a new OXM class for the proposed GEN_TLV 
fields
o   No problem to reserve an OXM class even before those fields are 
standardized
o   For standardization we also need to specify a dynamic binding mechanism 
between protocol TLVs and GEN_TLV fields. We can submit the mechanism to be 
developed in OVS for standardization when its stable.
*   Walk-through of division into work packages:
o   Some follow up needed for the L3 packet support kernel datapath patches
o   Rest OK
o   Technical discussion around GEN_TLV and use for NSH MD2 in conjunction 
with encap(NSH) to be continued in the Google doc.
*   Time line:
o   The entire work should be targeting OVS 2.8 with feature freeze around 
July
*   OVS 2.7 is having feature freeze already in early January
o   Work packages can be upstreamed individually. NSH MD1 support doesn't 
have to wait for MD2
*   Basically agreed to the work split proposed in the document:
o   RedHat is taking the patches for L3 tunnel configuration (including use 
of RTNETLINK for config)
o   Ericsson take the infrastructure components (L3-tunnels, PTAP, Basic 
EXT-382)
o   Jarno (VMware) will handle the GEN_TLV infrastructure
o   Confirm with Yi Yang (Intel): Can they take VXLAN-GPE and the 
NSH-specific WPs? Or do they need help?
*   Way of working
o   Continue the meeting series for coordination of effort
o   Can use a feature integration branch to ease the joint development and 
test
o   Review of patches mainly through the ovs-dev mailing list
o   Use tools like git citool to break up larger patches into a series of 
smaller patches for review



  -Original Appointment-
  From: Jan Scheurich
  Sent: Sunday, 18 December, 2016 15:34
  To: Jan Scheurich; Zoltán Balogh; Yang, Yi Y (yi.y.y...@intel.com); Jiri 
Benc (jb...@redhat.com); Pravin Shelar; Simon Horman 
(simon.hor...@netronome.com); jpet...@ovn.org; ja...@ovn.org; Ben Pfaff; 
'ben.mackcr...@corsa.com'; d...@openvswitch.org
  Subject: Sync on PTAP, EXT-382 and NSH
  When: Wednesday, 21 December, 2016 17:00-18:30 (UTC+01:00) Amsterdam, 
Berlin, Bern, Rome, Stockholm, Vienna.
  Where: Skype Meeting


  Moved to Wednesday same time to accommodate Jiri.
  Hope this is still OK for the others.


  Hello all,

  I would like to call for a final sync meeting before the Christmas break.

  Now that we have gone through the main aspects of the design, I would 
like to focus on how to divide the entire function into manageable pieces, 
discuss the potential work split, an integration anatomy and a rough time plane 
for upstreaming. I will try to prepare input in our Google doc for this.

  
https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit

  If there are questions left regarding the design, please bring them up as 
well. You can also comment on the document at any time.

  Regards, Jan

  
.
  --> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
  Join by phone

  +492115343925 (Germany)English 
(United States)
  89925 (Germany)   English (United States)

  Find a local number

  Conference ID: 70849799
   Forgot your dial-in PIN? 
|Help


  To join a Lync / Skype for Business meeting from an Ericsson standard 

[ovs-dev] Sync on PTAP, EXT-382 and NSH

[Jan Scheurich]

Moved to Wednesday same time to accommodate Jiri.
Hope this is still OK for the others.


Hello all,

I would like to call for a final sync meeting before the Christmas break.

Now that we have gone through the main aspects of the design, I would like to 
focus on how to divide the entire function into manageable pieces, discuss the 
potential work split, an integration anatomy and a rough time plane for 
upstreaming. I will try to prepare input in our Google doc for this.

https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit

If there are questions left regarding the design, please bring them up as well. 
You can also comment on the document at any time.

Regards, Jan

.
--> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
Join by phone

+492115343925 (Germany)  English (United 
States)
89925 (Germany) English (United States)

Find a local number

Conference ID: 70849799
 Forgot your dial-in PIN? 
|Help


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@ .ericsson.net, where 
=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

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

[Jiri Benc]

Hi Jan,

On Sun, 18 Dec 2016 14:44:03 +, Jan Scheurich wrote:
> I would like to call for a final sync meeting before the Christmas break.

you managed to hit almost the only slot in this week when I have a
conflict with another meeting. I'm not available on Tuesday starting at
the time you chose.

Moving the meeting to an earlier time slot or to a different day
(except for today) would work for me.

Thanks,

 Jiri
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[ovs-dev] Sync on PTAP, EXT-382 and NSH

[Jan Scheurich]

Hello all,

I would like to call for a final sync meeting before the Christmas break.

Now that we have gone through the main aspects of the design, I would like to 
focus on how to divide the entire function into manageable pieces, discuss the 
potential work split, an integration anatomy and a rough time plane for 
upstreaming. I will try to prepare input in our Google doc for this.

https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit

If there are questions left regarding the design, please bring them up as well. 
You can also comment on the document at any time.

Regards, Jan

.
--> Join Skype Meeting
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
Join by phone

+492115343925 (Germany)  English (United 
States)
89925 (Germany) English (United States)

Find a local number

Conference ID: 70849799
 Forgot your dial-in PIN? 
|Help


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@ .ericsson.net, where 
=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

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

[Jan Scheurich]

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
  This is an online meeting for Skype for Business, the professional meetings 
and communications app formerly known as Lync.
  Join by phone

  +492115343925 (Germany)   English 
(United States)
  89925 (Germany)  English (United States)

  Find a local number

  Conference ID: 281130796
   Forgot your dial-in PIN? 
|Help


  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@ .ericsson.net, 
where =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