OpenFlow 1.1+ support in Open vSwitch
=====================================
-Open vSwitch support for OpenFlow 1.1, 1.2, and 1.3 is a work in
+Open vSwitch support for OpenFlow 1.1 and beyond is a work in
progress. This file describes the work still to be done.
The Plan
The list of remaining work items for OpenFlow 1.1 is below. It is
probably incomplete.
- * OFPT_TABLE_MOD message. This is new in OF1.1, so we need to
- implement it. It should be implemented so that the default OVS
- behavior does not change. Simon Horman has posted a patch.
- [required for OF1.1 and OF1.2]
-
- * MPLS. Simon Horman maintains a patch series that adds this
- feature. This is partially merged.
- [optional for OF1.1+]
-
* Match and set double-tagged VLANs (QinQ). This requires kernel
work for reasonable performance.
[optional for OF1.1+]
* Add OFPMP_TABLE_FEATURES statistics. Alexander Wu has posted a
patch series. [optional for OF1.3+]
- * More flexible table miss support.
- This requires the following.
- - Change the default table-miss action (in the absense of table-miss
- entry) from packet_in to drop for OF1.3+. Decide what to do if
- a switch is configured to support multiple OF versions.
- [required for OF1.3+]
-
* IPv6 extension header handling support. Fully implementing this
requires kernel support. This likely will take some careful and
probably time-consuming design work. The actual coding, once
* Flow entry notifications
This seems to be modelled after OVS's NXST_FLOW_MONITOR.
+ (Simon Horman is working on this.)
[EXT-187]
[required for OF1.4+]
[EXT-256]
[optional for OF1.4+]
- * Duplicate instruction error
- We already have ONFBIC_DUP_INSTRUCTION.
- [EXT-260]
- [required for OF1.4+]
-
* Multipart timeout error
[EXT-264]
[required for OF1.4+]
[EXT-154]
[optional for OF1.4+]
- * Flow-removed reason for meter delete
- Report flow removal due to meter deletion with OFPRR_METER_DELETE.
- [EXT-261]
- [optional for OF1.4+]
-
* Meter notifications
[EXT-235]
[optional for OF1.4+]
* Coding style (see the CodingStyle file at the top of the source
tree).
- * The patch submission guidelines (see SubmittingPatches). I
+ * The patch submission guidelines (see CONTRIBUTING). I
recommend using "git send-email", which automatically follows a
lot of those guidelines.