Hi Martin, Will the upcoming NOX release be OpenFlow 1.0 feature compatible and not just OpenFlow 1.0 candidate wire protocol compatible?
One more question: It seems that it is currently impossible to trace an event and a NOX generated OpenFlow message back to their originator events (e.g., a Packet_in_event may cause other events to be dispatched and some OpenFlow messages to be sent out). It would be useful to have an entry in the Event and OpenFlow Message classes to pinpoint their originators. It seems that this needs only a few changes to the code base and enables NOX (& third-party applications) to have a high level view of NOX operation. I am working on OpenFlow control plane distribution and this feature would be quite useful for that I believe. Thanks, Amin _______________________________________________ nox-dev mailing list [email protected] http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
