From: Wes Felter <wmf@felter.org>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] is there no RED at level3?
Date: Thu, 31 Jul 2014 15:13:25 -0500 [thread overview]
Message-ID: <lre816$uk5$1@ger.gmane.org> (raw)
In-Reply-To: <CAA93jw7w+7ukoidu4hDhCuJjz-1bDEvpPPmZ+umMb7TDm9MHOQ@mail.gmail.com>
On 7/30/14, 5:49 PM, Dave Taht wrote:
> I have been following the level3 vs verizon debate with some interest,
> trying to sort out fact from fiction. It does appear that once they
> saturate a core interconnect they end up with nearly 100ms of latency in
> it. Is RED not available on 10GigE interconnects or any other mediation
> means to increase packet loss in exchange for getting better latency?
Wasn't CoDel created because nobody understands how to configure RED?
If you've built a network under the assumption that congestion won't
happen, why enable RED?
If you're in an adversarial public pissing match, is your incentive to
make the situation look better or worse?
--
Wes Felter
next prev parent reply other threads:[~2014-07-31 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 22:49 Dave Taht
2014-07-31 20:13 ` Wes Felter [this message]
2014-07-31 20:44 ` Jim Gettys
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='lre816$uk5$1@ger.gmane.org' \
--to=wmf@felter.org \
--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