X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=OPENFLOW-1.1%2B;h=eaf2ee99e5efe1fd618aeee506b554544a6d05ab;hb=4b0424809b823101c969a0691fc1db0c880ae64a;hp=f419803816afce2b2f629d332e35b21554ae3680;hpb=2431be1b68d386bd616378d2c528242775c4d54a;p=sliver-openvswitch.git diff --git a/OPENFLOW-1.1+ b/OPENFLOW-1.1+ index f41980381..eaf2ee99e 100644 --- a/OPENFLOW-1.1+ +++ b/OPENFLOW-1.1+ @@ -54,13 +54,6 @@ OpenFlow 1.1 The list of remaining work items for OpenFlow 1.1 is below. It is probably incomplete. - * The new in_phy_port field in OFPT_PACKET_IN needs some kind of - implementation. It has a sensible interpretation for tunnels - but in general the physical port is not in the datapath for OVS - so the value is not necessarily meaningful. We might have to - just fix it as the same as in_port. - [required for OF1.1; optional for OF1.2+] - * OFPT_TABLE_MOD message. 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. @@ -78,23 +71,6 @@ probably incomplete. reasonable performance. [required for OF1.1+] - * Groups. - - * Type all - [required for OF1.1+] - - * Type select - [optional for OF1.1+] - - * Type indirect - [required for OF1.1+] - - * Type fast failover - [optional for OF1.1+] - - * Statistics - [optional for OF1.1+] - OpenFlow 1.2 ------------ @@ -103,11 +79,6 @@ additional work specific to Openflow 1.2 are complete. (This is based on the change log at the end of the OF1.2 spec. I didn't compare the specs carefully yet.) - * Action translation needs some work to transform OpenFlow 1.1 - field modification actions into OpenFlow 1.2+ "set-field" - actions, because OpenFlow 1.2 dropped support for the OF1.1 - actions. - OpenFlow 1.3 ------------ @@ -136,18 +107,11 @@ didn't compare the specs carefully yet.) that is all done, is probably 2 or 3 days work. [optional for OF1.3+] - * Per-flow meters. Similar to IPv6 extension headers in kernel - 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. + * Per-flow meters. OpenFlow protocol support is now implemented. + Support for the special OFPM_SLOWPATH and OFPM_CONTROLLER meters + is missing. Support for the software switch is under review. [optional for OF1.3+] - * Per-connection event filtering. OF1.3 adopted Open vSwitch's - existing design for this feature so implementation should be - easy. - [required for OF1.3+] - * Auxiliary connections. An implementation in 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 @@ -157,15 +121,16 @@ didn't compare the specs carefully yet.) some kind of "hardware" support, if we judged it useful enough.) [optional for OF1.3+] - * MPLS BoS matching. (Included in Simon's MPLS series?) + * MPLS BoS matching. + Part of MPLS patchset by Simon Horman. [optional for OF1.3+] * Provider Backbone Bridge tagging. I don't plan to implement this (but we'd accept an implementation). [optional for OF1.3+] - * Rework tag order. I'm not sure whether we need to do anything - for this. Part of MPLS patchset by Simon Horman. + * Rework tag order. + Part of MPLS patchset by Simon Horman. [required for v1.3+] * On-demand flow counters. I think this might be a real @@ -262,6 +227,12 @@ OpenFlow 1.4 [EXT-235] [optional for OF1.4+] +General +----- + + * ovs-ofctl(8) often lists as Nicira extensions features that + later OpenFlow versions support in standard ways. + How to contribute -----------------