5 research outputs found

    Two dimensional-ip routing

    No full text
    Abstract—Traditional IP networks use single-path routing, and make forwarding decisions based on destination address. Source address has always been ignored during routing. Lost of source address makes the traditional routing system inflexible and inefficient. The current network can not satisfy demands of both the network users and the ISP operators. Although many patch-like solutions have been proposed to bring the source address back to the routing system, the underlying problems of the traditional routing system can not be solved thoroughly. In this paper, we propose Two Dimension-IP Routing (TwoD-IP), which makes forwarding decisions based on both source and destination addresses. However, combining with source address, both the forwarding table and routing protocol have to be re-designed. To overcome the scalability problem, we devise a new forwarding table structure, which achieves wire-speeds and consumes less TCAM storage space. To satisfy demands of users and ISPs, we also design a simple TwoD-IP policy routing protocol. At last, we discuss the deployment problem of TwoD-IP. I

    Efficient Two Dimensional-IP Routing: An Incremental Deployment Design

    No full text
    That is, the forwarding decision of each router is not only based on the destination address, but also on the source address. One driving force is that the network needs the ability to divert traffic flows (identified by their source and destination IPs and we call them the VIP flows) to pre-defined paths (we call them the VIP paths). There are also increasing demands on load balancing, security issues, etc. A pure IP based solution is favored over MPLS. An important research issue towards TwoD-IP routing is the deployment of the TwoD-IP routing scheme. It is widely known that making changes to the network layer is notoriously difficult. The proposed scheme should have least impact on the current Internet protocols and infrastructure. A node-by-node incremental deployment scheme is highly preferred. Obviously, without full deployment, the resulting paths for traffic diversio
    corecore