X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=OPENFLOW-1.1%2B;h=b6a4222ae06bf5cb8018ecf410ae718588c66660;hb=a6ca7c672f6d5aaf24111d3414ea132ec36b40d6;hp=2c55cfed54fc8c933d64e1b42e78c966ce2d6102;hpb=85b20fd6ee585f462e012fbcc7f966a81edab2ed;p=sliver-openvswitch.git diff --git a/OPENFLOW-1.1+ b/OPENFLOW-1.1+ index 2c55cfed5..b6a4222ae 100644 --- a/OPENFLOW-1.1+ +++ b/OPENFLOW-1.1+ @@ -66,12 +66,6 @@ probably incomplete. specified. Check that OVS implements the new behavior, fix it if not. - * On OF1.1+ flow_mods, DELETE now ignores buffer_id. - - * OFPST_PORT and OFPST_QUEUE stats. These differ little from - OF1.0 to OF1.1 (just the size of the port number field) but do - require abstraction (Done?). - * OFPT_TABLE_MOD stats. This is new in OF1.1, so we need to implement it. It should be implemented so that the default OVS behavior does not change. @@ -79,8 +73,7 @@ probably incomplete. * Document how OVS does packet buffering. * MPLS. Simon Horman maintains a patch series that adds this - feature. It needs review and possible revision before it is - merged. + feature. This is partially merged. * SCTP. Joe Stringer maintains a patch series that adds this feature. It has received review comments that need to be @@ -99,7 +92,7 @@ OpenFlow 1.2 OpenFlow 1.2 support requires OpenFlow 1.1 as a prerequisite, plus the following additional work. (This is based on the change log at the -end of the OF1.2 spec. I didn’t compare the specs carefully yet.) +end of the OF1.2 spec. I didn't compare the specs carefully yet.) * Use new OpenFlow extensible error infrastructure, on OF1.2+ only, instead of the OVS-specific extension used until now. @@ -120,9 +113,6 @@ end of the OF1.2 spec. I didn’t compare the specs carefully yet.) * Update DESIGN to describe OF1.2 behavior also. - * Implement OFPT_ROLE_REQUEST. Patch submitted by Jarno - Rajahalme, currently under revision. - * Add ability to turn off packet buffering with OFPCML_NO_BUFFER. OpenFlow 1.3 @@ -131,7 +121,7 @@ OpenFlow 1.3 OpenFlow 1.3 support requires OpenFlow 1.2 as a prerequisite, plus the following additional work. (This is based on the change log at the end of the OF1.3 spec, reusing most of the section titles directly. I -didn’t compare the specs carefully yet.) +didn't compare the specs carefully yet.) * Add support for multipart requests. @@ -148,28 +138,28 @@ didn’t compare the specs carefully yet.) and design requirements. Might be politically difficult to add directly to the kernel module, since its functionality overlaps with tc. Ideally, therefore, we could implement these somehow - with tc, but I haven’t investigated whether that makes sense. + with tc, but I haven't investigated whether that makes sense. - * Per-connection event filtering. OF1.3 adopted Open vSwitch’s + * Per-connection event filtering. OF1.3 adopted Open vSwitch's existing design for this feature so implementation should be easy. * Auxiliary connections. These are optional, so a minimal implementation would not need them. An implementation in - generic code might be a week’s worth of work. The value of an + generic code might be a week's worth of work. The value of an implementation in generic code is questionable, though, since much of the benefit of axuiliary connections is supposed to be to take advantage of hardware support. (We could make the kernel module somehow send packets across the auxiliary - connections directly, for some kind of “hardware” support, if we + connections directly, for some kind of "hardware" support, if we judged it useful enough.) * MPLS BoS matching. (Included in Simon's MPLS series?) - * Provider Backbone Bridge tagging. I don’t plan to implement - this (but we’d accept an implementation). + * Provider Backbone Bridge tagging. I don't plan to implement + this (but we'd accept an implementation). - * Rework tag order. I’m not sure whether we need to do anything + * Rework tag order. I'm not sure whether we need to do anything for this. * Duration for stats. @@ -202,7 +192,7 @@ Please consider the following: tree). * The patch submission guidelines (see SubmittingPatches). I - recommend using “git send-email”, which automatically follows a + recommend using "git send-email", which automatically follows a lot of those guidelines. Bug Reporting