1 / 7

Forwarding and Control Element Separation (ForCES) Overview & Requirements Update

Forwarding and Control Element Separation (ForCES) Overview & Requirements Update. Todd A. Anderson. IP Forwarding & Control Separation. (Distributed) Network Element. CONTROL ELEMENT (Routing Protocols, Admission Control, Mgmt Agents, etc.). ForCES. FORWARDING ELEMENTS (ASIC, NP, etc.).

cleta
Download Presentation

Forwarding and Control Element Separation (ForCES) Overview & Requirements Update

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. Forwarding and Control Element Separation (ForCES) Overview & Requirements Update Todd A. Anderson

  2. IP Forwarding & Control Separation (Distributed) Network Element CONTROL ELEMENT (Routing Protocols, Admission Control, Mgmt Agents, etc.) ForCES FORWARDING ELEMENTS (ASIC, NP, etc.) FORWARDING ELEMENT (ASIC, NP, etc.) FORWARDING ELEMENT (ASIC, NP, etc.) • Standardize the interaction between IP control (slow path) and forwarding (fast path) elements • Control Element • CPU & memory intensiveprotocols and algorithms • Slow timescale – manypackets/operation • Forwarding Elements • Throughput oriented • Fast timescale –packet-by-packet operations • Provide a variety of functionality

  3. Why do it? • Rapid innovation – by allowing the control and forwarding planes to evolve independently. • Building blocks approach – by allowing network elements to be built from emerging network processors and third-party signaling, routing, and other software. • Scalability – by allowing additional forwarding capacity to be added to a network element w/o the addition of another point of management.

  4. Architectural Overview REQUIREMENTS 1.Variety of interconnects Which FEs do I control? Interconnect Which CE controls me? Which CE controls me? Network Element Control Element 2. Auto-membership & topology discovery 3. Inter-FE forwarding 4. Single “box” 5. Scalable: 1-10s of FEs 6. CE-FE protocol Forwarding Element 1 Forwarding Element 2

  5. Modeling Overview ? ? ? ? … Network Element • Given: • FEs have a variety of functionality • Problem: • How does the CE control the FE if it doesn’t know what it can do? • Requirement: • Define a functional model by which FEs can describe their functionality CE Interconnect FE

  6. Protocol Overview Ingress Filter Forwarder Egress Network Element REQUIREMENTS 1. Port configuration CE 1a. Packet redirection 2. Filter installation 3. Forward table install 4. QoS configuration 5. Secure communication Interconnect 6. Event notification 7. Statistics gathering FE

  7. Mailing List/Web site • Mailing list: • forces@peach.ease.lsoft.com • To subscribe: listserv@peach.ease.lsoft.com • In body of message “subscribe forces <your name>” • Web site • http://www.sstanamera.com/~forces • Drafts • draft-anderson-forces-req-01.txt

More Related