Abstract

The Border Gateway Protocol (BGP) is the current state-of-the-art inter-domain routing between Autonomous Systems (ASes). Although BGP has different mechanisms to manage outbound traffic in an AS domain, it lacks an efficient tool for inbound traffic control from transit ASes such as Internet Service Providers (ISPs). For inter-domain routing, the BGP’s destination-based forwarding paradigm limits the granularity of distributing the network traffic among the multiple paths of the current Internet topology. Thus, this work offered a new architecture to manage incoming traffic in the inter-domain using OpenFlow networks. The architecture explored direct inter-domain communication to exchange control information and the functionalities of the OpenFlow protocol. Based on the achieved results of the size of exchanging messages, the proposed architecture is not only scalable, but also capable of performing load balancing for inbound traffic using different strategies.

Highlights

  • The Internet is a collection of tens of thousands of independently operated networks

  • It is well known that Border Gateway Protocol (BGP) suffers from the process of “ossification”, where the architecture becomes very dependent on the protocol, and new features are inherently hard to introduce into the network

  • The BGP protocol does not provide an effective mechanism to control inbound traffic of advertised network prefixes. This work tackled this gap in the literature and proposed a new architecture to manage incoming traffic to multi-homed Autonomous Systems (ASes) where their Internet Service Providers (ISPs), using OpenFlow protocol (OF) networks, provide new services to allow customer ASes to apply network management tasks into the ISPs infrastructure

Read more

Summary

Introduction

The Internet is a collection of tens of thousands of independently operated networks. An AS can be an Internet Service Provider (ISP), a campus, a content provider, or any other independently operated network All these ASes can connect with each other as they execute an inter-domain routing protocol to exchange network reachability information. A new feature for the BGP protocol has to have a minimum integration within heterogeneous networks and interoperate through different administrative domains (e.g., the Internet) These requirements have frustrated new proposals to evolve BGP and the ecosystem of inter-domain routing [3]. This work applies SDN concepts and uses the OpenFlow capabilities to compose a new network architecture to evolve inter-domain routing systems.

Related Works
The Architecture Proposal
Network Architecture Overview
Architecture Components
Network Administrator
Policy Manager
Path Computer
Dynamic of the Proposed Architecture
Controlling Inbound Traffic
Proof of Concept
Topology Adopted
Prototype Environment
Workloads
Scenario I—Manage Incoming Traffic Using Different Strategies
Scenario II—External Link Failure
Signaling Overhead
Further Discussion
Number of Network Rules
Adopting a Routing Registry
The Proposed Architecture in the Internet
Findings
Future Works and Limitations
Conclusions
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.