From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp113.iad3a.emailsrvr.com (smtp113.iad3a.emailsrvr.com [173.203.187.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 9BA1F3B2A4 for ; Mon, 18 Jun 2018 12:26:34 -0400 (EDT) Received: from smtp15.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp15.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 6A9DE59FE; Mon, 18 Jun 2018 12:26:34 -0400 (EDT) X-SMTPDoctor-Processed: csmtpprox beta Received: from smtp15.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp15.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 64F675A02; Mon, 18 Jun 2018 12:26:34 -0400 (EDT) Received: from app39.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by smtp15.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 547BB59FE; Mon, 18 Jun 2018 12:26:34 -0400 (EDT) X-Sender-Id: MAILER-DAEMON Received: from app39.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by 0.0.0.0:25 (trex/5.7.12); Mon, 18 Jun 2018 12:26:34 -0400 Received: from deepplum.com (localhost.localdomain [127.0.0.1]) by app39.wa-webapps.iad3a (Postfix) with ESMTP id 4412C2009F; Mon, 18 Jun 2018 12:26:34 -0400 (EDT) Received: by apps.rackspace.com (Authenticated sender: dpreed@deepplum.com, from: dpreed@deepplum.com) with HTTP; Mon, 18 Jun 2018 12:26:34 -0400 (EDT) Date: Mon, 18 Jun 2018 12:26:34 -0400 (EDT) From: "dpreed@deepplum.com" To: "Dave Taht" Cc: cerowrt-devel@lists.bufferbloat.net, "bloat" MIME-Version: 1.0 Content-Type: text/plain;charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <1529339194.276412941@apps.rackspace.com> X-Mailer: mobile/6.0.2 Subject: [Cerowrt-devel] Invisibility of bufferbloat and its remedies X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2018 16:26:34 -0000 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 ge= ar 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 he= avier users, because it is a shared buffering pool with no fairness or bloa= t 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 k= nowing 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 iss= ues like this one.