Designing BGP-based outbound traffic engineering techniques for stub ASes

Abstract

Today, most multi-connected autonomous systems (AS) need to control the flow of their interdomain traffic for both performance and economical reasons. This is usually done by manually tweaking the BGP configurations of the routers on an error-prone trialand-error basis. In this paper, we demonstrate that designing systematic BGP-based traffic engineering techniques for stub ASes are possible. Our approach to solve this traffic engineering problem is to allow the network operator to define objective functions on the interdomain traffic. Those objective functions are used by an optimization box placed inside the AS that controls the interdomain traffic by tuning the iBGP messages distributed inside the AS. We show that the utilization of an efficient evolutionary algorithm allows to both optimize the objective function and limit the number of iBGP messages. By keeping a lifetime on the tweaked routes, we also show that providing stability to the interdomain path followed by the traffic is possible. We evaluate the performance of solution based on traffic traces from two stub ASes of different sizes. Our simulations show that the interdomain traffic can be efficiently engineered by using not more than a few iBGP advertisements per minute.Our contribution in this paper is to demonstrate that by carefully thinking the design of the interdomain traffic engineering technique, stub ASes can engineer their outbound traffic over relatively short timescales, by exclusively tweaking their BGP routes, and with a minimal burden on BGP. Systematic BGP-based traffic engineering for stub ASes is thus possible at a very limited cost in terms of iBGP messages.

Load balancing inbound traffic in multihomed stub autonomous systems

“…Transit ASes primarily interconnect networks and hence they are connected to more than one provider or peer. Interestingly this trend of multihoming has been observed in stub ASes too ( [26]). In multihomed networks, traffic on one path is congested, even when traffic on other links are under-utilised.…”

Quantifying the benefits of joint content and network routing

“…Lee et al [27] explore ways to scale active measurements for multi-homed enterprises. Uhlig et al [43] and Wang et al [44] propose formalizing upstream ISP selection as an optimization problem. Most of the efforts mentioned above focus on the enterprise setting and do not compare content routing with network routing.…”

An Integrated Network Management Framework for Inter-domain Outbound Traffic Engineering

“…The key idea of the framework is to continuously monitor 1 the network conditions and, if some optimization triggering poli-1 . In this paper, continuous monitoring can refer to 10 minutes interval according to [5,6]. However, there is a trade off between the accuracy of network conditions and monitoring overheads.…”

“…In fact, its FS worst case performance is respectively 44% and 20% better than the FS worst case performance of the NO-REOPT and the PEP-REOPT-ONLY. Note that in the IOTE FRAMEWORK the maximum EP utilization in FSs is proactively re-optimized for both TFs and NTFs, whereas in the PEP-REOPT-ONLY, there is no re-optimization for TFs due to their very short duration 6 but there are reactive re-optimizations for NTFs. As a result, the significant performance degradation shown in Figure 4(b) due to TFs and NTFs do not occur in Figure 4(c).…”