Hi Saeed, Your confusing the spec with an implementation of the spec. The spec is finished and is ready to be used. But, to the best of my knowledge, there is yet no single switch that implements the entire OpenFlow 1.1 spec. ofps comes closest and its vlan push/pop functionality is completely implemented, but there are other parts of the spec that ofps does not implement (group tables, port stats, etc).
What you're reading from that webpage/table is that each feature has been implemented, but not all in the same place in the same working piece of code. The columns indicate where the feature was implemented, e.g., in OpenVSwitch or ofps. Note that none of the test code used to implement OF1.1 has been pushed back to the OVS folks. Hope this helps, - Rob . On Tue, Mar 8, 2011 at 11:34 PM, Saeed Attar <[email protected]> wrote: > On 03/09/2011 03:22 AM, Rob Sherwood wrote: > > I'm not sure I understand. As of now, there are no fully OF1.1 > compliant switches -- the spec has just been released. What did you > compile? The "most complete" 1.1 switch is the openflow python switch > ("ofps") that ships with oftest in the oft-1.1 branch, but even it is > missing significant functionality. Is this what you're using? > > As for simple description of how to use it, I can point you to the > QinQ test cases in oftest's vlan tests, but the short short > description is that the standard OpenFlow match structure only matches > the outer tag and there are push and pop vlan instructions, so you > would insert flow_mods that express: > > if dl_vlan_id = vlan1, then apply action push_vlan(ETHERTYPE_QinQ) > if dl_vlan_id = vlan2, then apply action pop_vlan() > > The tests in the vlanact.py oftest file work through this in gory detail. > > > - Rob > . > > > > On Tue, Mar 8, 2011 at 12:52 AM, Max Ott <[email protected]> wrote: > > Rob, > > Saeed has compiled the OF1.1 version and wants to experiment with QinQ. Is > there a simple description on how to do this for a simple case? > > Cheers, > -max > > On 08/03/2011, at 6:24 PM, Rob Sherwood wrote: > > In OpenFlow version 1.0, the SET_VLAN action implicitly adds a vlan > tag if none exists, but a limitation of 1.0 is that you cannot manage > multiple vlan tags (e.g., QinQ). You can remove the vlan tag with the > STRIP_VLAN action. > > Multiple vlan tags are better handled in the recently released > OpenFlow 1.1 specification, that has explicit push and pop vlan > actions. > > Both specifications are available at http://www.openflow.org/wp/documents/ > > Hope that helps, > > - Rob > . > > > > On Mon, Mar 7, 2011 at 5:35 PM, Saeed Attar <[email protected]> > wrote: > > Hi > > I couldn't find any examples on how to use push/pull labels in openflow, > Could any one point me to documentation or example code. in a simple > word how can we add a VLAN tag for a packet entering one port and > leaving through another. > > Thanks > Saeed > > The information in this e-mail may be confidential and subject to legal > professional privilege and/or copyright. National ICT Australia Limited > accepts no liability for any damage caused by this email or its attachments. > _______________________________________________ > openflow-discuss mailing list > [email protected] > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > > _______________________________________________ > openflow-discuss mailing list > [email protected] > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > > The information in this e-mail may be confidential and subject to legal > professional privilege and/or copyright. National ICT Australia Limited > accepts no liability for any damage caused by this email or its attachments. > > Rob, > > I am using ofp-1.1 branch, the feature that is important for us is push/pop > label and now based on the fact that you said currently it is missing > significant functionality I am confused whether it is part of completed > features or not. If I am right according to features table in > http://www.openflow.org/wk/index.php/OpenFlow_v1.1 it is done (OVS impl 1, > OVS impl 2, Python impl and test are in bold). could you please make it > clear for me that do we have push/pop label ready to use or it is not > complete yet. > > thanks > Saeed > _______________________________________________ openflow-discuss mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
