<SNIP> > In Open vSwitch, we have already defined protocol extensions that > allow for extending the match. These extensions are, of course, > incompatible with switches and controllers that only speak OpenFlow > 1.0, but they provide a framework that makes adding more types of > matching easier. Port range matching could be easily added here. > > Here is the description of the extensible match protocol: > > http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob;f=include/openflow/nicira-ext.h;h=5cf02e7c58a1b4fe6dac19b18c14104f503cbeee;hb=HEAD#l762
What's the status with this protocol and the OpenFlow standard? Has it been proposed for inclusion? > > Given these changes, my initial feeling is that it shouldn't be too > > difficult to add the matching to the vSwitch itself. If the tp_*_end > > wasn't set, then we could safely ignore it matching time. > > The biggest question in my mind is not how to formulate range matches > but how to efficiently integrate them into the classifier. Do you > have thoughts on that? Could you give some more details, please? I'm not looked into this area much yet. Cheers, -Mike. -- Mike Bursell, Network Subsystem Architect Citrix Systems R&D. +44 7971 926937 _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
