1 / 11

ForCES Forwarding Element Functional Model

ForCES Forwarding Element Functional Model. Lily Yang, Joel Halpern, Ram Gopal, Ram Dantu < draft-yang-forces-model-02.txt> . Overview. FE Model Open Issues & Next Steps. Motivation. FE capability : what FE can be. FE. CE. FE state : what FE is now.

tracey
Download Presentation

ForCES Forwarding Element Functional Model

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. ForCES Forwarding Element Functional Model Lily Yang, Joel Halpern, Ram Gopal, Ram Dantu <draft-yang-forces-model-02.txt>

  2. Overview • FE Model • Open Issues & Next Steps

  3. Motivation FE capability: what FE can be FE CE FE state: what FE is now FE configuration: what FE should be FE Functional Model

  4. FE Block • FE Block = Abstract Base Class for FE logical functions • An FE block specifies: • Block ID or name (functional type) • Textual description of the function • Need a namespace: • Extensible (to allow new functions later)

  5. Block Library • Requirements to support 8 categories of FE functions: • Forwarding • QoS • Filtering • Port • Security • High touch • Off-loaded • Vendor specific

  6. FE stage & Directed Graph • FE Stage: an instance of an FE block in a data path • Stage id (unique within the FE) • Block Name or ID • Number of downstream stages • List of downstream stage Ids • FE Directed Graph: • Interconnection of the FE stages • Can support logical loops by configuring FE Block(s)

  7. Issues List – FE/CE Topology control • FE graph • Topology discovery should be out of scope (during initial stage of design) • No restriction of FE Block layout • Smart CE should be able to figure out and allow/disallow functions. (Current draft addresses this) • Control of Topology • FE has full control , less flexibility • CE has full control, flexibility, but FE may not like all possible configuration on graph elements • Balance approach will be better • Provide bunch of handles and don’t represent topology • Most of the interconnection are hard wired

  8. Issue List – Topology vs. Configuration (1) • Graph representation • CE get bigger picture and important for behavior of NE • It’s a constrained graph (pointers to existing work) • Difficulty in representation • CE don’t have capability for any network, any FE , any protocol • Logical loops and physical Loops representation • CE interpreting any graph is complicated • Element configuration • Focus on configuration and control • Converting FE’s Topology to represent NE

  9. Issue List – Topology vs. Configuration (2) • Resolution • Complete dynamic is out of scope. • Semi-dynamic - Configurablity by manipulating properties of FE Blocks(s) (eg., QoS, IPsec, L5 switching ) • Describe list of function blocks for the model

  10. TO DO List • TO DO List • Data modeling language: representation • Candidates : SMI/SPPI/ASN.1/XML/UML • Describe list of function blocks for the model • WG Document?

  11. Questions

More Related