[ovs-discuss] mf_value and mf_subvalue size restrictions

Ben Pfaff blp at nicira.com
Thu Nov 6 22:51:51 UTC 2014


On Thu, Nov 06, 2014 at 02:49:55PM -0800, Ben Pfaff wrote:
> On Thu, Nov 06, 2014 at 02:37:01PM -0800, Jesse Gross wrote:
> > I'm curious how you ended up laying this out. The OpenFlow spec says
> > that the extra space should be used as an vendor ID in the form of an
> > OUI. How did you reconcile this?
> 
> You can probably get away with a lot if you make the most significant
> byte of the extra 32 bits nonzero, because OpenFlow only specifies the
> format of the other 24 bits if that byte is zero and leaves the rest of
> the space reserved for future standardization.
> 
> But that's kind of a nasty thing to do.
> 
> Have you considered allowing database configuration to specify what kind
> of attributes are expected and how to parse them?  The configuration
> could be P4-based, for example.

By the way, did you realize that you've been frozen?
https://lists.debian.org/debian-devel-announce/2014/11/msg00003.html



More information about the discuss mailing list