Boosting Cloud Communications through a Crosslayer Multipath Protocol Architecture

Coudron, Matthieu; Secci, Stefano; Maier, Guido; Pujolle, Guy; Pattavina, Achille

doi:10.1109/sdn4fns.2013.6702535

Cited by 9 publications

(8 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Examples of such functions include support for IP multicast [35]- [37] and network virtualization within a data center environment [38] based on methods like NVGRE, VXLAN, GRE-in-UDP and GUE [39]. Li [40] surveys proposals to improve future scalability of the Internet, including the Locator/ID Separation Protocol (LISP) [41] which-besides helping with, e.g., route table scaling-can aid in overcoming ossification by, e.g., adding edge support for mobility and multicast [42] or enabling some form of multipath transport proxy [43], [44]. Network overlays have benefits (especially in transition to support new protocols), however, they hide the underlying network from the transport, impose homogeneity on a diverse network service and can be an obstacle to evolution of different network-transport interactions, which adds to ossification.…”

Section: B Scope and Structure Of The Papermentioning

confidence: 99%

De-Ossifying the Internet Transport Layer: A Survey and Future Perspectives

Παπαστεργίου

Fairhurst

Ros

et al. 2017

IEEE Commun. Surv. Tutorials

View full text Add to dashboard Cite

It is widely recognized that the Internet transport layer has become ossified, where further evolution has become hard or even impossible. This is a direct consequence of the ubiquitous deployment of middleboxes that hamper the deployment of new transports, aggravated further by the limited flexibility of the application programming interface (API) typically presented to applications. To tackle this problem, a wide range of solutions have been proposed in the literature, each aiming to address a particular aspect. Yet, no single proposal has emerged that is able to enable evolution of the transport layer. In this paper, after an overview of the main issues and reasons for transportlayer ossification, we survey proposed solutions and discuss their potential and limitations. The survey is divided into five parts, each covering a set of point solutions for a different facet of the problem space: 1) designing middlebox-proof transports; 2) signaling for facilitating middlebox traversal; 3) enhancing the API between the applications and the transport layer; 4) discovering and exploiting end-to-end capabilities; and 5) enabling user-space protocol stacks. Based on this analysis, we then identify further development needs toward an overall solution. We argue that the development of a comprehensive transport layer framework, able to facilitate the integration and cooperation of specialized solutions in an application-independent and flexible way, is a necessary step toward making the Internet transport architecture truly evolvable. To this end, we identify the requirements for such a framework and provide insights for its development.

show abstract

Section: B Scope and Structure Of The Papermentioning

confidence: 99%

De-Ossifying the Internet Transport Layer: A Survey and Future Perspectives

Παπαστεργίου

Fairhurst

Ros

et al. 2017

IEEE Commun. Surv. Tutorials

View full text Add to dashboard Cite

show abstract

“…In contrast to limiting the number of subflows [194], Coudron et al [33,35] exploited the path diversity in cloud networks from a different perspective, for example, creating more subflows over disjoint WAN paths (under the assumption that the WAN capacity is the throughput bottleneck). To achieve this goal, in [35] Coudron et al proposed a crosslayer approach which combines MPTCP and LISP [55].…”

Section: Path Diversity For Mptcpmentioning

confidence: 99%

“…MPTCP could use the path manager "ndiffports" to create additional LISP-enabled subflows which share the same source IP with different TCP ports. In their another work [33], apart from MPTCP and LISP, Coudron et al introduced one more protocol TRILL [50] to support Ethernet level multipath transmission. For example, MPTCP employs coordinated congestion control to achieve RP, LISP handles path diversity at the external data center packets between border nodes, and TRILL deals with multipath Ethernet-layer communications.…”

Section: Path Diversity For Mptcpmentioning

confidence: 99%

“…A-MPTCP [35] 2013 Transport Network Use LISP [55] to give better knowledge of the underlying IP topology to MPTCP enabled endpoints in cloud networks. Coudron et al [33] 2013 Transport Network, link Use LISP [55] and TRILL [50] respectively in different environments to calculate and select multiple paths for MPTCP in data centers. LISP [55] handles path diversity between border nodes and TRILL [50] deals with multipath on Ethernet layer.…”

Section: E Summarymentioning

confidence: 99%

“…The link layer and network layer can provide path diversity for cross-layer approaches. For example, OpenFlow and TRILL can provide Ethernet level path diversity [33,194], and LISP can provide routing level path diversity [33,35].…”

Section: E Summarymentioning

confidence: 99%

See 2 more Smart Citations

Multipath Transmission for the Internet: A Survey

Lukyanenko

et al. 2016

IEEE Commun. Surv. Tutorials

Self Cite

127

View full text Add to dashboard Cite

Smart devices equipped with multiple network interfaces are becoming commonplace. Nevertheless, even though multiple interfaces can be used to connect to the Internet, their capabilities have not been fully utilized yet because the default TCP/IP stack supports only a single interface for communication. This situation is now changing due to the emergence of multipath protocols on different network stack layers. For example, many IP level approaches have been proposed utilizing tunneling mechanisms for hiding multipath transmission from the transport protocols. Several working groups under IEEE and IETF are actively standardizing multipath transmission on the link layer and transport layer. Application level approaches enable multipath transmission capability by establishing multiple transport connections and distributing data over them. Given all these efforts, it is beneficial and timely to summarize the state-of-the-art, compare their pros and cons, and discuss about the future directions. To that end, we present a survey on multipath transmission and make several major contributions: (1) we present a complete taxonomy pertaining to multipath transmission, including link, network, transport, application and cross layers; (2) we survey the state-of-the-art for each layer, investigate the problems that each layer aims to address, and make comprehensive assessment of the solutions; (3) based on the comparison, we identify open issues and pinpoint future directions for multipath transmission research.

show abstract

Performance Evaluation of MPTCP Transmission of Large Data Objects in Computing Cloud

Chodorek

2016

Advances in Intelligent Systems and Computing

View full text Add to dashboard Cite

Boosting Cloud Communications through a Crosslayer Multipath Protocol Architecture

Cited by 9 publications

References 4 publications

De-Ossifying the Internet Transport Layer: A Survey and Future Perspectives

De-Ossifying the Internet Transport Layer: A Survey and Future Perspectives

Multipath Transmission for the Internet: A Survey

Performance Evaluation of MPTCP Transmission of Large Data Objects in Computing Cloud

Contact Info

Product

Resources

About