OPENFLOW-1.1+: OFPRR_METER_DELETE is used

[cascardo/ovs.git] / OPENFLOW-1.1+

diff --git a/OPENFLOW-1.1+ b/OPENFLOW-1.1+
index 4363d28..d337b8c 100644 (file)
--- a/OPENFLOW-1.1+
+++ b/OPENFLOW-1.1+
@@ -1,7 +1,7 @@
                 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
@@ -89,13 +89,6 @@ didn't compare the specs carefully yet.)
     * 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
@@ -178,11 +171,6 @@ Many of them are necessary for OpenFlow 1.4 as well.
       [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+]
@@ -205,11 +193,6 @@ OpenFlow 1.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+]
@@ -244,7 +227,7 @@ Please consider the following:
     * 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.