X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=DESIGN;fp=DESIGN;h=7dd6efa23d59de2d2b8050abe871405d660996fd;hb=f25d0cf3c366d92042269a4f787f19c741c2530c;hp=a3a62b2eeb7f29c8ec4833d128621d28de39186a;hpb=690a61c50a4744603be2ee3de8e22c97f9140d94;p=sliver-openvswitch.git

diff --git a/DESIGN b/DESIGN
index a3a62b2ee..7dd6efa23 100644
--- a/DESIGN
+++ b/DESIGN
@@ -612,6 +612,26 @@ The following are explicitly *not* supported by in-band control:
      gateway.
 
 
+Action Reproduction
+===================
+
+It seems likely that many controllers, at least at startup, use the
+OpenFlow "flow statistics" request to obtain existing flows, then
+compare the flows' actions against the actions that they expect to
+find.  Before version 1.8.0, Open vSwitch always returned exact,
+byte-for-byte copies of the actions that had been added to the flow
+table.  The current version of Open vSwitch does not always do this in
+some exceptional cases.  This section lists the exceptions that
+controller authors must keep in mind if they compare actual actions
+against desired actions in a bytewise fashion:
+
+        - Open vSwitch zeros padding bytes in action structures,
+          regardless of their values when the flows were added.
+
+Please report other discrepancies, if you notice any, so that we can
+fix or document them.
+
+
 Suggestions
 ===========