IEEE INFOCOM 2016 - The 35th Annual IEEE International Conference on Computer Communications 2016
DOI: 10.1109/infocom.2016.7524599
|View full text |Cite
|
Sign up to set email alerts
|

Revisiting congestion control for multipath TCP with shared bottleneck detection

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

1
53
0
2

Year Published

2018
2018
2023
2023

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 76 publications
(56 citation statements)
references
References 11 publications
1
53
0
2
Order By: Relevance
“…• The inter-dependency (and processing time) between web resources reduces web performance when using multistreaming. This behaviour is not limited to TCP, for instance, Control block sharing [39] with shared bottleneck detection [40] could also result in a similar behaviour. 2 Image spriting is a technique increasingly used in web design to send a group of separate images as a single cluster.…”
Section: Discussion Of Multistreaming Analysismentioning
confidence: 88%
“…• The inter-dependency (and processing time) between web resources reduces web performance when using multistreaming. This behaviour is not limited to TCP, for instance, Control block sharing [39] with shared bottleneck detection [40] could also result in a similar behaviour. 2 Image spriting is a technique increasingly used in web design to send a group of separate images as a single cluster.…”
Section: Discussion Of Multistreaming Analysismentioning
confidence: 88%
“…We evaluated two scenarios (Ferlin et al, 2016a;Hassayoun et al, 2011), namely, subflows with and without shared links, which are denoted as NL and NSL respectively for the sake of simplicity in the remainder of this article. Fig.…”
Section: Measurement Settingmentioning
confidence: 99%
“…Following the parameters in (Barre et al, 2011), the number of subflow N ranges from 1 to 8. For the NSL scenarios, the bandwidth is 100 Mbps and the RTTs of the subflows are set as 10 ms, 20 ms, 30 ms, 40 ms, 60 ms, 80 ms, 90 ms and 100 ms. For the SL scenario, the common link has 100 Mbps capacity and 20 ms RTT (Ferlin et al, 2016a) and the RTTs of each subflow are 20 ms, 30 ms, 40 ms, 50 ms, 60 ms, 70 ms, 80 ms and 90 ms. Unless specifically stated, the default setting of the packet loss rate is 0.…”
Section: Measurement Settingmentioning
confidence: 99%
See 2 more Smart Citations