Internet routing diversity for stub networks with a Map-and-Encap scheme

Abstract

International audienceRouting diversity has been identified as essential for network robustness and traffic engineering. The Internet possesses by its very nature a large path diversity. However this diversity cannot be fully exploited due to BGP limitations, which only keeps one single route for each available prefix. Despite some previous works in the area, no operational and non-disruptive architecture have been proposed yet to allow the networks to better exploit Internet path diversity.This paper proposes one step in this direction, focusing on the interconnection between an Autonomous System (AS) and its Internet Service Provider (ISP). We propose the use of a so-called “Map-and-Encap” scheme to bypass current BGP limitations in order to use arbitrary paths. With this scheme, an ISP may propose its rich path diversity (at least partially) to its customers, in order to perform advanced traffic engineering (e.g. fast recovery, load balancing...) based on richer and more flexible path selection policies (e.g., considering price, performance or stability of routes). To assess the potential benefits of the proposed architecture, we evaluate the potential route diversity that a Tier 1 may offer to its stub clients, based on different possible route selection policies (i.e. which routes are offered to its customers). We also analyze the overhead that is created at the control-plane (routing updates received by the mapping database) and that may impact the data-plane (path changes that may be caused by some route withdrawals/updates). Our evaluation shows that the increase in diversity has a controllable and acceptable overhead. It also gives some insights into efficient deployment strategies

Can MPTCP secure Internet communications from man-in-the-middle attacks?

“…LISP primary scope is the edge provider one, hence results with the edge provider view readily apply to LISP traffic engineering. It is worth noting that, deployment of LISP as an intra-AS TE tool can also allow performing inter-AS multipath on the outbound direction as proposed in [43]. • MultiPath BGP: in BGP, when some higher BGP decision criteria are equivalent, even if the load might technically be balanced on the equivalent routes, only one route is retained using lower-level criteria (that can be inefficient ones in terms of global routing such as hot-potato or tie-breaking rules).…”

An Analytical Model for Loc/ID Mappings Caches

“…It has been long hinted at and today it is generally accepted that the origin of this architectural inflexibility can be tracked down to the semantic overloading of the IP addresses with both location and identity information [26]. Therefore, their separation, typically referred to as a loc/id split, has been proposed by many solution that aim to mitigate the routing problems [21] but also by those aiming to integrate new features [24]. Apart from infrastructure upgrades, these architectures also require the deployment of a mapping-system for linking the two new namespaces and often rely on caches to limit router memory requirements and improve forwarding speeds.…”

Managing resilience in carrier grade networks: Survey, open issues and trends

“…In a service-oriented communication model both routing and addressing features are not longer based on a particular destination address, rather multiple-destination addresses might be used according to the demanded service. This eases the deployment of Mobility and TE features, as well as it mitigates the interoperability issues in multi-addressing scenarios [106], [107], [108].…”