1 / 14

Two Dimensional IP Routing Architecture draft-xu-rtgwg-twod-ip-routing-00

Two Dimensional IP Routing Architecture draft-xu-rtgwg-twod-ip-routing-00. Mingwei Xu, Jianping Wu, Shu Yang CERNET Dan Wang Hong Kong Polytechnic University IETF83 Meeting, Paris, March 2012. Traditional Routing. Src1. Dst. Src2. TwoD-IP Routing. Src1. Dst. Src2.

ahmed-case
Download Presentation

Two Dimensional IP Routing Architecture draft-xu-rtgwg-twod-ip-routing-00

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. Two Dimensional IP Routing Architecture draft-xu-rtgwg-twod-ip-routing-00 Mingwei Xu, Jianping Wu, Shu Yang CERNET Dan Wang Hong Kong Polytechnic University IETF83 Meeting, Paris, March 2012

  2. Traditional Routing Src1 Dst Src2

  3. TwoD-IP Routing Src1 Dst Src2 Add source address into the routing system

  4. Related Work • Source Routing • Control handled by end hosts • Face security problems • MPLS • Additional packet/protocol overhead • Control overhead • The overhead increases with the number of LSPs • Some ISPs desire a pure-IP network • Others • one-hop source routing, policy-based routing, user-specific routing (e.g., NIRA), multi-topology routing, SAVI

  5. Use Cases1: Load Balancing 30Mbps Utilization=83.3% Utilization=50.0% Utilization=50.0% 20Mbps E.g., cloud computing

  6. Use Cases2: Multi-homing • Provider Independent address causes routing table inflation • Provider Aggregatableaddress is recommended • However: • Complicating configurations • Facing failure • Ingress filtering presents additional difficulties Address B Address A

  7. Use Cases3: Diagnosis & Measurement • Reduce probing traffic • Reduce number of monitors (e.g., link (c, d))

  8. TwoD-IP Routing Framework

  9. Challenges • Forwarding table design • Table size: avoid explosion • Lookup speed • New source-related routing protocol design • Efficient • Minimum states on routers and minimum exchanged messages • Consistent • Avoid loops and policy confliction Worst Case: N2

  10. FIB Structure for TwoD-IP(FIST)

  11. Lookup Action

  12. Implementation Status • We have implemented the TwoD-IP FIB on a hardware router with GE interfaces, which can achieve line speed • We are designing routing protocols based on TwoD-IP Routing

  13. Discussion in the mailing list • Most routers can already be programmed to support multi-path/ECMP/TE… • There are many patch-like solutions • TwoD-IP Routing intrinsically supports multi-path and can easily support load balancing, multi-homing… • Adding source address can not solve anything • We list some possible beneficial cases • TwoD-IP Routing provides a pure IP routing platform to design new routing functions and protocols • The FIB structure is interesting and valuable, but it is not much  applicable within an IETF draft • It is described just for completion. We may abstract this part

  14. Summary • Source address is included in every packet, but is used rarely • TwoD-IP Routing intrinsically supports multi-path and can easily support load balancing, multi-homing… • TwoD-IP Routing provides a pure IP routing platform to design new routing functions and protocols • Work in SAVI WG can guarantee source addresses are validated • We have implemented the TwoD-IP Routing on a hardware router with FPGA, TCAM and SRAM • We are planning to deploy several TwoD-IP routers in CERNET2 (a pure IPv6 backbone network)

More Related