From: "dpreed@deepplum.com" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net,
"bloat" <bloat@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Invisibility of bufferbloat and its remedies
Date: Mon, 18 Jun 2018 12:26:34 -0400 (EDT) [thread overview]
Message-ID: <1529339194.276412941@apps.rackspace.com> (raw)
https://www.cordcuttersnews.com/3-easy-tips-to-fix-constant-buffering/
It's distressing how little the tech press understands the real problem.
Of course, cable companies like Charter and ATT who have mostly DOCSIS 2 gear deployed can't admit to their plant being bloat-causing.
In fact it protects their cable business against cord cutters.
And the solution is needed in the CMTS once neighbors all start becoming heavier users, because it is a shared buffering pool with no fairness or bloat protection.
Still, routers with queue management that reduce bloat would help a lot, if "buffering" is seen frequently under load.
So why isn't anyone talking about this problem after at least a decade of knowing it, and knowing how to fix it?
I blame IETF members, individually and collectively. If ietf exists for any reason other than as a boondoggle for world travel, it's for resolving issues like this one.
next reply other threads:[~2018-06-18 16:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 16:26 dpreed [this message]
2018-06-18 19:07 ` Dave Taht
2018-06-18 22:43 ` dpreed
2018-06-18 23:17 ` [Cerowrt-devel] [Bloat] " Jonathan Morton
2018-06-19 2:21 ` dpreed
2018-06-19 1:46 ` [Cerowrt-devel] " Dave Taht
2018-06-19 19:33 ` Dave Taht
2018-06-19 19:45 ` dpreed
2018-06-19 20:34 ` valdis.kletnieks
2018-06-19 23:32 ` Sebastian Moeller
2018-06-20 6:56 ` [Cerowrt-devel] (no subject) Sebastian Moeller
2018-06-19 23:41 ` [Cerowrt-devel] Invisibility of bufferbloat and its remedies Jonathan Morton
2018-06-19 23:47 ` [Cerowrt-devel] [Bloat] " Sebastian Moeller
2018-06-20 7:12 ` Kevin Darbyshire-Bryant
2018-06-20 8:07 ` Sebastian Moeller
2018-06-20 9:15 ` Kevin Darbyshire-Bryant
2018-06-20 9:34 ` Sebastian Moeller
2018-06-18 20:59 ` [Cerowrt-devel] " Michael Richardson
2018-06-18 21:14 ` Dave Taht
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1529339194.276412941@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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