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 <jan.scheur...@ericsson.com>
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*
>    <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*
> <https://docs.google.com/document/d/1oWMYUH8sjZJzWa72o2q9kU0N6pNE-rwZcLH3-kbbDR8/edit>
>
>
> ............................................................
> ............................................................
> .................
> à *Join Skype Meeting* <https://meet.ericsson.com/jan.scheurich/HJ2NTF23>
>
> 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* <https://dialin.ericsson.com?id=70849799>
>
> Conference ID: 70849799
> *Forgot your dial-in PIN?* <https://dialin.ericsson.com> |*Help*
> <http://o15.officeredir.microsoft.com/r/rlidLync15?clid=1033&p1=5&p2=2009>
>
>
>
> To join a Lync / Skype for Business meeting from an Ericsson standard
> video room, add 77 before the Conference ID (e.g. 771234567 where 1234567
> is the conference ID).    To join from a video room outside of Ericsson add
> one of the domains after 77 and Conference ID (e.g. 771234567@
> xxxx.ericsson.net, where xxxx=emea/apac/amcs).  For assistance contact
> the IT Service Desk.
> [!OC([1033])!]
> ............................................................
> ............................................................
> .................
>
>
>
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to