Hi all, Currently, NOX implements the OpenFlow message (command) dispatching functionality in a couple of functions builtin/nox.cc (e.g., send_openflow_command). I am wondering if it is possible to move this functionality to an application: i.e., to send OpenFlow commands to switches, applications fire events defined by the dispatcher application instead of calling the functions found in builtin/nox.cc instead. The dispatcher application handles such events and sends out OpenFlow messages to switches. I understand that it is a radical change, but it seems to be really beneficial:
* A policy enforcement application can be designed to discard the commands which violate network policies. * OpenFlow commands/messages can be prioritized. * This enables transparent proxying/routing of OpenFlow commands among multiple controllers. * The overhead seems to be negligible. - In particular, I need this feature for HyperFlow (http://www.usenix.org/event/inmwren10/tech/full_papers/Tootoonchian.pdf). I will ask about event serialization later :-) What do you think? Thanks, Amin _______________________________________________ nox-dev mailing list [email protected] http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
