Content deleted Content added
start the cleanup: headings at least, and over-use of Capital Letters |
verify the 2009 paper |
||
Line 1:
{{primary sources|date=June 2011}}
'''Blue''' is an [[active queue management]] algorithm for a [[Router (computing)|router]] or other [[computer network]] device. Like [[random early detection]] (RED), it operates by randomly dropping or marking packet with [[explicit congestion notification]] packets in a router's queue before it overflows. Unlike RED, however, it requires little or no tuning on the part of the network administrator.<ref>{{Cite journal |title=BLUE: A New Class of Active Queue Management Algorithms |author1=Wu-chang Feng |author2=Dilip D. Kandlur |author3=Debanjan Saha |author4=Kang G. Shin |year=1999 |month=April |url=http://www.eecs.umich.edu/techreports/cse/99/CSE-TR-387-99.pdf |
==Operation==
Line 9:
Assuming the mix of traffic on the interface doesn't change, ''p'' will slowly converge to a value that keeps the queue within its bounds with full link utilisation.
===Stochastic fair Blue===
The main flaw of Blue, which it shares with most single-queue queueing disciplines, is that it does not distinguish between flows, and treats all flows as a single aggregate. Therefore, a single aggressive flow can push out of the queue packets belonging to other, better behaved, flows.
Line 19:
When a flow's drop/mark probability reaches 1, the flow has been shown to not react to congestion indications from the network. Such an inelastic flow is put in a "[[penalty box]]", and rate-limited.
===Resilient stochastic fair Blue===
Active queue management (AQM) algorithms, including the fairness-aimed ones, are notably vulnerable to spoofing [[distributed denial-of-service]] (DDoS) attacks. A
===Implementations===
An implementation of Blue is part of [[ALTQ]], the alternative AQM framework for BSD Unix.<ref>[http://www.thefengs.com/wuchang/blue/ BLUE]</ref>
Line 30:
==References==
<references />
[[Category:Packets (information technology)]]
|