Good, point. I like to think of the original RED as more 1) noting that all
those full buffers weren't doing anyone any good and 2) noting that one
could perhaps be aware of creeping congestion and "gently" prevent it.
Those two items are still important it's just that making 2) work has more
"ahas" in it than was apparent at first blush. I think it is good for us as
a community to figure out what doesn't work and what directions we should
explore.
For example, as has been mentioned, creating better mixes of traffic shows
the issues of acks mixed with data real fast. Separate queues fixes those
issues very nicely. But we have to be standing on a stepping stone along the
path to see this stuff.
Kathie
On 2/24/15 8:13 AM, Matt Mathis wrote:
> RED doesn't work so well, by hindsight it has the wrong estimators and
> control functions. However every algorithm on the table today is in
> some sense derived from that ground breaking work.
>
> "Red in a different light" and others are the stepping stones between
> then and now.
>
> Thanks,
> --MM--
> The best way to predict the future is to create it. - Alan Kay
>
> Privacy matters! We know from recent events that people are using our
> services to speak in defiance of unjust governments. We treat privacy
> and security as matters of life and death, because for some users, they are.
>
> On Tue, Feb 24, 2015 at 7:43 AM, sahil grover <[email protected]
> <mailto:[email protected]>> wrote:
>
> (i) First of all,i want to know whether RED was implemented or not?
> if not then what were the reasons(major) ?
> anyone please tell me in simple words here only,because i don't want
> to read any paper like "RED in a different light".
>
> (ii)Second, as we all know RED controls the average queue size from
> growing.
> So it also controls delay in a way or we can say is a solution to
> bufferbloat problem. Then why it was not considered.
>
> _______________________________________________
> Bloat mailing list
> [email protected] <mailto:[email protected]>
> https://lists.bufferbloat.net/listinfo/bloat
>
>
>
>
> _______________________________________________
> Bloat mailing list
> [email protected]
> https://lists.bufferbloat.net/listinfo/bloat
>
_______________________________________________
Bloat mailing list
[email protected]
https://lists.bufferbloat.net/listinfo/bloat
