Fixing OF Multipart messages

[openflowjava.git] / openflow-protocol-api / src / main / yang / openflow-protocol.yang

diff --git a/openflow-protocol-api/src/main/yang/openflow-protocol.yang b/openflow-protocol-api/src/main/yang/openflow-protocol.yang
index 518d1973d37fab30ddb1d40b826e4681233dd0ba..659cc1edb88b5b46d3fcc948a812830c1b4c1dd8 100644 (file)
--- a/openflow-protocol-api/src/main/yang/openflow-protocol.yang
+++ b/openflow-protocol-api/src/main/yang/openflow-protocol.yang
@@ -541,6 +541,11 @@ module openflow-protocol {
                     type oft:multipart-request-flags;\r
                 }      \r
                 choice multipart-request-body {\r
+                    case multipart-request-desc {\r
+                        leaf desc {\r
+                            type empty;\r
+                        }\r
+                    }\r
                     case multipart-request-flow {\r
                         leaf table-id {\r
                             type uint8;\r
@@ -1306,9 +1311,16 @@ module openflow-protocol {
         /* Multipart messages. */\r
             //FIXME: Arent this wire protocol specific?\r
 \r
+            rpc send-multipart-request-message {\r
+                input {\r
+                    uses multipart-request;\r
+                }\r
+            }\r
+\r
             notification multipart-request-message {\r
                 uses multipart-request;\r
                 // reference "OFPT_MULTIPART_REQUEST message in Openflow Switch 1.3 Spec"\r
+                // TODO: This should probably be deprecated as I think it should have been an rpc - eaw@cisco.com\r
                 \r
             } /* Controller/switch message */\r
             notification multipart-reply-message {\r