From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] is there no RED at level3?
Date: Wed, 30 Jul 2014 18:49:25 -0400 [thread overview]
Message-ID: <CAA93jw7w+7ukoidu4hDhCuJjz-1bDEvpPPmZ+umMb7TDm9MHOQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 569 bytes --]
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?
http://blog.level3.com/global-connectivity/verizons-accidental-mea-culpa/#comment-41993
--
Dave Täht
NSFW:
https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
[-- Attachment #2: Type: text/html, Size: 886 bytes --]
next reply other threads:[~2014-07-30 22:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 22:49 Dave Taht [this message]
2014-07-31 20:13 ` Wes Felter
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=CAA93jw7w+7ukoidu4hDhCuJjz-1bDEvpPPmZ+umMb7TDm9MHOQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--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