Changes between Version 30 and Version 31 of Internal/OpenFlow/Controllers/MultiCtl

Timestamp:

Nov 2, 2012, 10:46:10 PM (13 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Controllers/MultiCtl

@@ -285 +285 @@
 
 To keep things simple, of the Message category of events, focus will be placed on the Packet_In type (0x10), which is practically a catch-all for network host related messages. If more fine-tuned filtering is requires, a OFMatch structure may probably be used to describe the constraints on the types of Packet_Ins a subscriber may wish to hear about. 
- 
+
+==== (11/2) ==== #w8
+Concept work for the module front end to remote connections: [[BR]]
+1.3 types of message processing chain behaviors, according to application type at remote end.
+
+   1. Proxy : messages cannot be passed down chain until the remote module has processed things, and returned a decision. This includes firewalls and authentication. 
+   1. Concurrent : messages being processed by the remote module can also be processed by the others down the chain even while it is being remotely processed. 
+   1. Both : some modules may be required to wait for the results of the remote module, while others may work concurrently.   
+
+ In terms of communicating the specific type, there can be a field that specifies preferred processing options in the !ExportsReply messages. 
+
+2.Implementation wise, static modules makes dynamic connection additions difficult. In dynamic controllers, a module-per-connection may be added as connections are introduced, so tacking this problem is not considered to be a topic of interest. (However, it has to be done)
+
+3.Flow entry merging is a nontrivial topic that is not covered due to its extensiveness. Once a flow entry is added, it is assumed to:
+
+  1. aside from removal, never be modified
+  2. not conflict with any others. 
 ----
 [#home Home.]