X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=OPENFLOW-1.1%2B;h=1789f179abafe88a16a15dd026be248b8ab521fe;hb=003ce655b7116d18c86a74c50391e54990346931;hp=b58fec93493da806d701b60b57f26478f4fdaf12;hpb=d2e190cd21e1c1f433f366d0c105bf56f6c97e13;p=sliver-openvswitch.git

diff --git a/OPENFLOW-1.1+ b/OPENFLOW-1.1+
index b58fec934..1789f179a 100644
--- 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
@@ -54,11 +54,6 @@ OpenFlow 1.1
 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.
-      [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+]
@@ -91,15 +86,8 @@ didn't compare the specs carefully yet.)
       Currently we always report OFPBRC_MULTIPART_BUFFER_OVERFLOW.
       [optional for OF1.3+]
 
-    * Add OFPMP_TABLE_FEATURES statistics.
-      [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+]
+    * Add OFPMP_TABLE_FEATURES statistics.  Alexander Wu has posted a
+      patch series.  [optional for OF1.3+]
 
     * IPv6 extension header handling support.  Fully implementing this
       requires kernel support.  This likely will take some careful and
@@ -249,7 +237,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.