Clarify that the actions field is used only for reporting back the
standard actions defined in the Actions section of the document, not for
vendor-specific actions.
added a human readable string to ofp_stats_desc to describe
the datapath, e.g., "switch4 in closet 3b of Gates"
* updated openflow.h
* updated udatapath: defaults to "$HOSTNAME pid=$$"
* updated kernel datapath: defaults to "$HOSTNAME idx=$i"
* updated wireshark plugin
* added regression test for ofp_desc_stats
* addressed KK's review comments from:
https://mailman.stanford.edu/pipermail/openflow-dev/2009-December/000545.html
Improve precision of flow duration (time a flow has
been installed in a switch) from seconds to nanoseconds
to improve throughput measurement accuracy when using
flow stats messages. This implementation splits the
existing duration fields into duration_sec and
duration_nsec for both flow expiration and flow stats
messages. Passes included unit tests on Ubuntu 8.04.
Enable additional basic QoS support, without requiring a full QoS
framework. This commit defines a flow action to rewrite the DiffServ
CodePoint bits of the IP ToS field in the IP header.
Before this spec change, flow expiration messages included a duration
field for the time the flow was active. To find out the amount of time
the flow received traffic would have been much harder - the controller
would need to store a record of all flow mods it has sent, to know the
idle_timeout of this flow. Additionally, both phrases, 'time flow was
active' and 'time traffic was received' were used in the spec for the
duration field.
Now we return the idle timeout in the flow expiration message, and ensure
duration is the time the entry was present in the flow table. The hard
timeout will be obvious if it is the reason for the deletion, since the
reason field will be OFPER_HARD_TIMEOUT, and the duration will be the hard
timeout value. From the duration and the idle_timeout, we can also
compute the time the flow received traffic.
Add barrier request message, which ensures that all previously received
commands are complete before executing ones past the barrier message. A
barrier reply must be sent for each barrier request.
We expect this command to be useful for testing and wireless handover
purposes.
An OpenFlow hypervisor might choose to reject an OpenFlow request, but
currently has no message type defined for this error. It is not a
vendor-specific error, thus we define an _EPERM error code for each error
type.
Also remove unused, commented-out text.
The spec does not currently define how wildcard matching should behave for
flow modification (specifically DELETE and MODIFY commands) and stats.
This commit adds text to define behavior when some fields are wildcarded
and others are left exact.
Make flow expirations per-flow-entry, rather than per-switch.
This commit should give controllers extra flexibility to decide when they
want expirations, will simplify the job of an OpenFlow hypervisor, and may
reduce CPU load at the switch.
Clarified the wording in the Error Message section slightly:
- currently defined error types
- data field for OFPET_HELLO_FAILED
- codes for OFPET_BAD_REQUEST
Glen Gibb
Yiannis Yiakoumis
Brandon Heller
Justin Pettit
Rob Sherwood
David Erickson
Mikio Hara