On 11 Mar 2025, at 9:29, Denis Davidoglu via discuss wrote:
> Hello, I am developing a vendor extension that performs matching based on > some string metadata and the length requirement is up to 4096 bytes. However, > current specification of OpenFlow messages for experimenter fields allows > only 8 bits for length: > > type experimenter > <----------> <----------> > > 16 7 1 8 8 24 (length - 4) bytes > +------+-----+--+------+ +------+-----+ +------------------+ > |class |field|HM|length| | zero | OUI | | body | > +------+-----+--+------+ +------+-----+ +------------------+ > 0xffff 0x00 > > I am asking for suggestions on how to extend this limit appropriately. I > thought of the following: > > 1. Use the reserved 'zero' bits (between 'length' and 'OUI'). > 2. Divide the string into multiple entries, specifying fragments' intervals > in the body. Hi Denis, I’d say the zero should remain zero, unless you're planning to create a new version of the OpenFlow spec :) Your second option makes more sense. You should handle this in the vendor-specific section, i.e., the body. Cheers, Eelco _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
