On Sat, Jan 18, 2014 at 10:16:50AM -0800, Peter Phaal wrote: > There are a number of interesting use cases for using network traffic > analytics (derived from measurement protocols such as SNMP, IPFIX, > NetFlow and sFlow) to build traffic engineering solutions that push > control actions using OpenFlow. The challenge (which has come up on > this list) is mapping the SNMP ifIndex numbers used in measurement > protocols to OpenFlow datapath IDs and port numbers so that OpenFlow > rules can be constructed to target measured flows. > > I believe that a simple change to the ofp_port structure in the > OpenFlow protocol would be the cleanest way to address this issue.
OpenFlow 1.4 made the port description a set of TLVs, with the possibility to add version extensions. This means that adding an ifindex field should be much easier now, because you don't have to get everyone to agree on it, only to define your own field, publish it as an extension, and get some vendors to implement it. And then if it becomes popular or useful, you can propose it for standardixation. _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
