The ONF Registry is a database of vendor proprietary unique identifiers used for extending the OpenFlow protocol. Members can define their own extension of the OpenFlow protocol, however this require them to use some unique identifier. The specification defines two types of member IDs, Experimenter IDs and OXM classes
The experimenter field is a 32-bit value that uniquely identifies the experimenter. If the most significant byte is zero, the next three bytes are the experimenter's IEEE OUI. If the most significant byte is not zero, it is a value allocated by the Open Networking Foundation. If experimenter does not have (or wish to use) their OUI, they should contact the Open Networking Foundation to obtain a unique experimenter ID.
Those are the OUI of some of the ONF members used as experimenter IDs
Those are the Experimenter IDs which are not OUI. This space is managed by the ONF.
The match types are structured using OXM match classes. The OpenFlow specification distinguish two types of OXM match classes, ONF member classes and ONF reserved classes, diferentiated by their high order bit. Classes with the high order bit set to 1 are ONF reserved classes, they are used for the OpenFlow specifiation itself. Classes with the high order bit set to zero are ONF member classes, they are allocated by the ONF on an as needed basis, they uniquely identify an ONF member and can be used arbitrarily by that member. Support for ONF member classes is optional.
Those are the currently defined OXM classes
"onf" has been added to the Formal URN Namespace registry: https://www.iana.org/assignments/urn-namespaces
The ONF process for managing this URN can be found here: https://wiki.opennetworking.org/download/attachments/325386251/ONF%20URN%20Management.pdf
To request branches, please email email@example.com