2012 IEEE 26th International Conference on Advanced Information Networking and Applications 2012
DOI: 10.1109/aina.2012.103
|View full text |Cite
|
Sign up to set email alerts
|

Harsh RED: Improving RED for Limited Aggregate Traffic

Abstract: Abstract-A bottleneck router typically resides close to the edge of the network where the aggregate traffic is often limited to a single or a few users only. With such limited aggregate traffic Random Early Detection (RED) on the bottleneck router is not able to properly respond to TCP slow start that causes rapid increase in load of the bottleneck. This results in falling back to tail-drop behavior or, at worst, triggers the RED maximum threshold cutter that drops all packets causing undesired break for all t… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2013
2013
2019
2019

Publication Types

Select...
6
1
1

Relationship

1
7

Authors

Journals

citations
Cited by 11 publications
(6 citation statements)
references
References 23 publications
0
6
0
Order By: Relevance
“…Adaptive RED (ARED) [12], [15] is also likely to be too slow to respond resulting in similar behavior as with regular RED because state is only updated using relatively infrequent timer while the slow start keeps increasing the load constantly. Usually such a slow AQM response leads to fallback using tail-drop [26]. Instead of auto-tuning the dropping probability slowly such as with ARED, HRED immediately starts with aggressive dropping.…”
Section: Active Queue Managementmentioning
confidence: 98%
See 2 more Smart Citations
“…Adaptive RED (ARED) [12], [15] is also likely to be too slow to respond resulting in similar behavior as with regular RED because state is only updated using relatively infrequent timer while the slow start keeps increasing the load constantly. Usually such a slow AQM response leads to fallback using tail-drop [26]. Instead of auto-tuning the dropping probability slowly such as with ARED, HRED immediately starts with aggressive dropping.…”
Section: Active Queue Managementmentioning
confidence: 98%
“…HRED [26] is an aggressive RED variant that is designed TCP slow start in mind. The recommended RED parametrization [13] is not useful with load transients.…”
Section: Active Queue Managementmentioning
confidence: 99%
See 1 more Smart Citation
“…The difficulties associated with this approach are that the overload of data packets reveals in discontinuation and jitter. Jarvinen et al [20] addressed RED (Random Early Deduction) technique in which the authors proved that it has not more benefits as it is too moderate to tackle rapid change because of slow start TCP, particularly while the data traffic is inadequate. Each and every one of above methods changes the buffer size either by incrementing or decrementing the window size.…”
Section: Related Workmentioning
confidence: 99%
“…Random Early Detection (RED) [9] is one such AQM algorithm, but it has not been widely deployed in routers largely because of challenges to configure it correctly [32]. According to [23], RED does not work with the default settings as it is "too "gentle" to handle fast changes due to TCP slow start, when the aggregate traffic is limited." There may also be a lack of incentives to deploy AQM algorithms.…”
Section: Design Aspects Of Problems and Solutionsmentioning
confidence: 99%