1 / 5

Switch Capability Advertisement for OF1.1

Switch Capability Advertisement for OF1.1. Edward Crabbe. Motivation. Given the expansion in the set of mod types proposed thus far (group mods , mods targeted by table) and actions (push, pop, swap), there must be some way for the switch to both

hilda
Download Presentation

Switch Capability Advertisement for OF1.1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Switch Capability Advertisement for OF1.1 Edward Crabbe

  2. Motivation • Given the expansion in the set of mod types proposed thus far (group mods, mods targeted by table) and actions (push, pop, swap), there must be some way for the switch to both • Describe the top level capability set of the switch • Describe characteristics of the capabilities • More generally: • It is undesirable for force vendors for implement the complete capability set into order to be OF spec X.Y compliant • Doing so will likely reduce adoption of protocol significantly • we are introducing features that may never be supported by all switches

  3. Proposal • Add capability advertisement to the OF protocol • Occurs on session initialization • TLV structure in both capability advertisement and per capability descriptions • Enumerate capability types in spec iterations • Not necc. full description of per capability semantics? • Let market determine what is and is not required

  4. Use Case 1: Tags • Either list a pre enumerated tag set, with well known protocols fields described in the capability spec • 1 MPLS • 2 dot1q • 3 IP etc etc ad infinitum • Or describe generalized packet format • Mark format as rewrite or encaps • Mark fields as rewritable

  5. Use Case 2: Tables • Export pipeline • Table • Actions • Out-edges / Downstream Neighbors • Comparand Width or Specific Field for Match? • Table Size • Actions available etc

More Related