Thanks for your comments.
On 10/18/14, 12:32 PM, Ben Pfaff wrote:
On Sat, Oct 18, 2014 at 09:55:57AM -0400, Thomas F Herbert wrote:
On 10/17/14, 4:54 PM, Ben Pfaff wrote:
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:
...
...
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.
I don't understand your proposal at all. It must be possible to
distinguish a match on an 0x88a8 tag from one on an 0x8100 tag. How do
you propose to do that?
802.1ad (double tagged 0x88a8) vlans and 802.1q(single tagged 0x8100)
vlans can co-exist and the name spaces can overlap so I absolutely agree
that it is a problem. Adding a match on the inner "customer" TCI, such
as NXM_NX_VLAN_CTCI would do it but matching on the TPID does have
clearer semantics.
--
Thomas F. Herbert
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
