2005
DOI: 10.1016/j.comnet.2005.01.012
|View full text |Cite
|
Sign up to set email alerts
|

Analysis and performance evaluation of the EFCM common congestion controller for TCP connections

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
17
0

Year Published

2005
2005
2022
2022

Publication Types

Select...
5
2
1

Relationship

1
7

Authors

Journals

citations
Cited by 15 publications
(17 citation statements)
references
References 18 publications
0
17
0
Order By: Relevance
“…Fig. 3 shows the goodput values of two TFRC flows with FSE in the presence of background synthetic traffic 5 when the priority of the first flow is set to 1, while the other flows' 5…”
Section: A Coupled Congestion Control For Rtp Mediamentioning
confidence: 99%
See 1 more Smart Citation
“…Fig. 3 shows the goodput values of two TFRC flows with FSE in the presence of background synthetic traffic 5 when the priority of the first flow is set to 1, while the other flows' 5…”
Section: A Coupled Congestion Control For Rtp Mediamentioning
confidence: 99%
“…However, it was hard to implement: it requires revamping the entire transport layer implementation because the congestion control logic needs to be taken out of the transport protocols. Ensemble TCP (E-TCP) [4] and Ensemble Flow Congestion Management (EFCM) [5] are also two proposals along these lines; while E-TCP tried to be no more aggressive than one flow, EFCM 1 The IETF counterpart of the W3C WebRTC standard is called RTCWEB. For simplicity, we will use the term "WebRTC" for the whole set of standards.…”
Section: Introductionmentioning
confidence: 99%
“…Examples of the former include SPDY [1] and HTTP/2 [2], which multiplex multiple web sessions on top of a single TCP connection between client and server. Examples of the latter, often referred to as coupled congestion control (ccc), include the Congestion Manager (CM [3]), Ensemble TCP (E-TCP [4]) and Ensemble Flow Congestion Management (EFCM [5]).…”
Section: Introductionmentioning
confidence: 99%
“…In E-TCP, the aggregate of an ensemble is no more aggressive than one TCP Reno connection. Ensemble Flow Congestion Management (EFCM) [9] extended E-TCP by allowing the aggregate of an ensemble to be as aggressive as n TCP connections. These two mechanisms both realize a service of joint congestion control, somewhat similar to the Congestion Manager (CM) [2] or when using application stream multiplexing as in e.g.…”
Section: Introductionmentioning
confidence: 99%