From: Oliver Hohlfeld <oliver@net.t-labs.tu-berlin.de>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] AQM usage in current Internet routers
Date: Mon, 13 Aug 2012 16:18:40 +0200 [thread overview]
Message-ID: <50290CC0.7000304@net.t-labs.tu-berlin.de> (raw)
In-Reply-To: <CAO-4OdGKiU3YMMbqeyQe=VK0Juv2UVgaX4AeTagV6nRAUdyK4w@mail.gmail.com>
Hi,
> I read the blog from Getty, saying that RED or other variants of AQM
> actually are not ran in current Internet routers.
That's a myth. RED is /not widely/ used, as it's configuration is
unclear and subject to a debate that has never converged. But there
are large operators out there that do deploy RED in their backbone,
so saying that it's never used is simple incorrect.
However, I also would be interested in statistics on the deployment
of AQM.
> If not, do you know how to detect / evaluate the usage of RED?
There is related work out there. See for example the paper by
Dischinger et al.:
http://www.mpi-sws.org/~mdischin/papers/07_imc_bb.pdf
See for example Figure 16 and Section 4.2.2.
> Maybe it's a good work to revisit AQM deployment in the wild of the
> Internet? What's your opinion???
But what would be the message of this work? I guess providing some
number would be nice, but would they have any impact? What if you
figure out that RED is not widely deployed (which is known); would it
make a difference to know the exact number for a subset of ASes? To me,
the pros and cons of RED are known and so are the reasons why or why
not to deploy it.
However, it could be interesting to track the deployment of Coddle and
see if operators adapt due to its ease of use. But that would be a
longitudinal study.
Best,
Oliver
prev parent reply other threads:[~2012-08-13 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 3:47 Haiqing Jiang
2012-08-13 14:18 ` Oliver Hohlfeld [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50290CC0.7000304@net.t-labs.tu-berlin.de \
--to=oliver@net.t-labs.tu-berlin.de \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox