1 / 8

Intra-NE Forwarding Mechanism for Efficient Routing

This draft proposes an Intra-NE routing mechanism to optimize data forwarding in networks with multiple Control Elements (CEs) and Forwarding Elements (FEs). By dividing routing tables and using selective forwarding, it enhances network efficiency without revealing full topology to individual elements. The document focuses on constructing routing tables and addresses considerations like security, single-hop forwarding, new Logical Forwarding Blocks (LFBs), and further improvements needed. Feedback is encouraged for refining this proposed mechanism.

kenda
Télécharger la présentation

Intra-NE Forwarding Mechanism for Efficient Routing

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. Intra-NE Routing Mechanismdraft-guo-forces-routing-01.txt Xiaoyi Guo(xiaotian@huawei.com) 64th IETF Meeting, Vancouver

  2. Forwarding mechanism Motivation • One NE may include many CEs and FEs, one of the forwarding path may cross many FEs ,not cross only one FE. • FEs should not know all the topology of the NE, so the routing table in FEs should not include all the NE routing information.

  3. CE Forwarding mechanism 2 routing tables in CE -- Edge FE Intra-FE Edge FE FE1 FE3 FE2 Intra-NE RT RT

  4. Forwarding mechanism Data forwarding • ----- Edge FE ----FE ---Edge FE -- • ( RT ) ( Intra-NE RT ) ( RT ) • We focus on Intra-NE forwarding mechanism

  5. Forwarding mechanism Routing table construction: • CE side: SPF algorithm Full topology --------- Intra-NE Routing Table routing protocols Routing information ----normal Routing table • FE side : CE send RT to each FE , not the full routing table

  6. Next .. • Consideration about the security? • Could one hop forwarding use this mechanism ? • Need the new LFBs construction? • More details of this mechanism need to considering and working out ….

  7. Other questions? • Interested in this work?

  8. Please send your comments to me and ForCES mailing list.

More Related