1 / 7

Evolving Traditional Routers to ForCES Architecture draft-ma-forces-proxy-framework-01.txt

Evolving Traditional Routers to ForCES Architecture draft-ma-forces-proxy-framework-01.txt. Huaiyuan,Ma (mahuaiyuan@huawei.com) ForCES WG, IETF #67. Problems during traditional router evolution. Problems

jwinters
Download Presentation

Evolving Traditional Routers to ForCES Architecture draft-ma-forces-proxy-framework-01.txt

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. Evolving Traditional Routers to ForCES Architecturedraft-ma-forces-proxy-framework-01.txt Huaiyuan,Ma (mahuaiyuan@huawei.com) ForCES WG, IETF #67

  2. Problems during traditional router evolution • Problems • proprietary communication protocols between physical control processor and physical forwarding processor. • Different forwarding models.

  3. Evolution Scenario I CE Physical Forwarding Processor Physical Forwarding Processor Physical Control Processor Physical Forwarding Processor Physical Forwarding Processor FE Adaptor FE FE

  4. Evolution Scenario II FE Proxy Physical Control Processor Physical Forwarding Processor Physical Forwarding Processor Physical Forwarding Processor Physical Forwarding Processor CE FE Adaptor FE FE

  5. Forwarding Element Adaptor • To implement ForCES protocol to communicate with its control element (s) and its forwarding element (s). • To convert the model-related information carried in cells/packets transferred across switch fabric.

  6. Next step • Is it necessary to evolve traditional router to ForCES architecture? • Is this proposal an appropriate solution?

  7. Any comments?

More Related