Proceedings of the 6th International Workshop on Hot Topics in Planet-Scale Measurement 2015
DOI: 10.1145/2798087.2798088
|View full text |Cite
|
Sign up to set email alerts
|

An Early Look at Multipath TCP Deployment in the Wild

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
17
0

Year Published

2016
2016
2021
2021

Publication Types

Select...
5
2
1

Relationship

1
7

Authors

Journals

citations
Cited by 17 publications
(17 citation statements)
references
References 7 publications
0
17
0
Order By: Relevance
“…MPTCP is a fully backward-compatible extension of TCP, published as an experimental standard in 2011 [25], [26], [176] and now widely deployed [177]. It allows applications to use multiple connections at the same time without any changes to the socket API.…”
Section: A Mptcpmentioning
confidence: 99%
“…MPTCP is a fully backward-compatible extension of TCP, published as an experimental standard in 2011 [25], [26], [176] and now widely deployed [177]. It allows applications to use multiple connections at the same time without any changes to the socket API.…”
Section: A Mptcpmentioning
confidence: 99%
“…The code for these modifications is available online 6 , as is that of our Ryu-based controller. 7 While layer-2 path capacity was estimated using port statistics, a dynamic layer-3 equivalent was not fully implementedthe controller currently needs manual configuration of path capacities. We expect the switches could use client traffic to implement methods such as packet dispersion [33].…”
Section: E Implementation Considerationsmentioning
confidence: 99%
“…Layer-2 multipath topologies [e.g., 6], have been successfully deployed and used within fully-controlled data-centre networks. End-to-end multipath support throughout the public Internet is however limited [7] due to the requirement to modify end-hosts. Heterogeneous network paths also worsen the issue of packet reordering, creating head-of-line blocking delays, and sometimes leading to worse performance than single-path transfers [8].…”
Section: Introductionmentioning
confidence: 99%
“…For example, in our testbed experiments presented in Section 6, 34% of source-destination pairs (the source playing the role of the gateway, the destination the role of the client) between which multiple paths exist would not support MPTCP, because the interface used by the client is common to the different paths. Finally, very few servers currently support MPTCP (less than 0.1% of the hosts in the Alexa top-1M list [26]). Contrary to MPTCP, EMPoWER acts at layer 2.5; it is therefore confined to the local network and transparent to other Internet hosts and protocols.…”
Section: Related Workmentioning
confidence: 99%