Cross-layer cooperation to boost multipath TCP performance in cloud networks

Differential delay constrained multipath routing for SDN and optical networks

“…For the source S and destination T node pair in the network of Figure 1b the maximum number of link-disjoint paths is equal to 6, imposing the upper bound for the maximization of K. Although the gain obtained by allowing LIP is not so significant, Figure 2a shows how 3D-LIP improves the solution subset of Δ values. In particular, for Δ = [4,5,6], 3D-LIP always reaches the upper bound of K = 6 (while 3D-LF does not), with a small impact on L as compared with 3D-LF (see Figure 2b). …”

“…Another issue is related to routing: MP improvements in terms of throughput, load balancing, reliability and protection bandwidth are all fully achievable only provided that the paths of the MP are link disjoint. For example, it was proven that the TCP performance can be enhanced by MPTCP only if physical path-disjointness is enforced [4]. In a highly loaded network the throughput of the MP connection will increase as the number of paths K grows.…”

Transparent cloud access performance augmentation via an MPTCP-LISP connection proxy

“…In a previous work [2] it was investigated the usage of two novel protocols standardized by the Internet Engineering Task Force (IETF) in the recent years: the Multipath Transport Control Protocol (MPTCP) [3], an incrementally deployable extension of TCP that creates sub-connections (called MPTCP subflows), each identified by a different TCP portbased and IP address-based 4-tuple; the Locator/Identifier Separation Protocol (LISP) [4], an IP-to-IP encapsulation protocol architecture including a distributed control-plane (similar to the Domain Name System one) to map destination IP address to routing locator (RLOC) IP address. In [2], it is proposed to modify the MPTCP implementation at endpoints to allow user's terminal to query the LISP mapping system and get the number of RLOCs of the server, and hence to open as much subflows as the number of RLOCs, gambling on a high level of disjointness between the corresponding Internet paths and hence decreasing the risk of passing through bottleneck and traffic shaping middle-boxes.…”

An implementation of multipath TCP in ns3

“…Path management is also a problem -though less studied -since creating many subflows with the hope of exploiting path diversity can hurt the perfor-240 mance (due to competition between subflows [10]). The problem is two-fold:…”

“…It is worth noting 140 that several subflows can be created from the same IP address with different ports. This may prove worthwhile to exploit the network path diversity, in case the network runs load-balancing [10]. There is no standard procedure and the subflow opening/closing strategy depends on local policies.…”