On Fri, Oct 17, 2014 at 01:19:33PM -0400, Dave Benson wrote: > On Fri, Oct 10, 2014 at 6:43 PM, Ben Pfaff <b...@nicira.com> wrote: > > With this change, I think that an OpenFlow flow table entry that > > matches on a VLAN will now match both 0x88a8 and 0x8100 tags for that > > VLAN. I doubt that that is desirable behavior, because my > > understanding is that 0x88a8 and 0x8100 tags are generally in > > different namespaces and are not interchangeable. > > Definately Agree. I saw that the OF spec has the same problem. They > define the eth_type as 'Ethernet type of the OpenFlow packet payload, after > VLAN tags.' So there is nothing currently to match on VLAN tpid. Does OVS > go it's own way in a case like this, or discuss this with the OF crowd?
I think we should figure out what we want to do first, then propose it for OpenFlow afterward. I am involved enough in OpenFlow standardization that I have an idea what will go over well. My first thought is to define a new NXM_NX_VLAN_TPID that matches the TPID, and for backward compatibility to imply a match on 0x8100 if it is not given. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
