"Peter Phaal" <peter.ph...@inmon.com> writes: > Here is a new definition for the Extended OpenFlow structure that better > addresses your points:
This looks good to me. Since OpenFlow is not a final standard, it would be good to either specify a particular version of OpenFlow (in case the bit fields change in later versions) or to somehow include a version number in the packet.