* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download One-to-one m
Survey
Document related concepts
Point-to-Point Protocol over Ethernet wikipedia , lookup
Deep packet inspection wikipedia , lookup
Internet protocol suite wikipedia , lookup
Backpressure routing wikipedia , lookup
IEEE 802.1aq wikipedia , lookup
Wake-on-LAN wikipedia , lookup
Cracking of wireless networks wikipedia , lookup
Computer network wikipedia , lookup
Zero-configuration networking wikipedia , lookup
Airborne Networking wikipedia , lookup
Multiprotocol Label Switching wikipedia , lookup
Recursive InterNetwork Architecture (RINA) wikipedia , lookup
Transcript
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 Src 1 Destination Nexthop Dst Dst Src 2 TwoD-IP Routing Src 1 Source Destination Src1 Dst Src2 Dst Nexthop Dst Src 2 Add source address into the routing system 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 Use Cases1: Load Balancing 30Mbps Utilization=83.3% Utilization=50.0% 20Mbps E.g., cloud computing Utilization=50.0% Use Cases2: Multi-homing Provider Independent address causes routing table inflation Provider Aggregatable address is recommended However: Complicating configurations Address A Facing failure Ingress filtering presents additional difficulties Address B Use Cases3: Diagnosis & Measurement Reduce probing traffic Reduce number of monitors (e.g., link (c, d)) TwoD-IP Routing Framework Challenges Forwarding table design Source Destin ation Nexthop Table size: avoid explosion Lookup speed New source-related routing protocol design Efficient Minimum states on routers and minimum exchanged messages Consistent Worst Case: N2 Avoid loops and policy confliction FIB Structure for TwoD-IP(FIST) Lookup Action 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 Discussion in the mailing list Most routers can already be programmed to support multi-path/ECMP/TE… Adding source address can not solve anything There are many patch-like solutions TwoD-IP Routing intrinsically supports multi-path and can easily support load balancing, multi-homing… 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 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)