From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id D4B153B2A2 for ; Wed, 23 Nov 2016 12:27:40 -0500 (EST) Received: by mail-lf0-x232.google.com with SMTP id t196so9401097lff.3 for ; Wed, 23 Nov 2016 09:27:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rSTQDfmp8cXDv7jR3fnGVDMUwOIelwGuqYXnSfI9btM=; b=abvqWlyXu4OulTt90dts7POex6WzFncACn5lnGgdu4bt5lwcVBacz4S1ZFf4wVNHgw B2+SuuOIvgOYJYHOevv4xaGDChuUPLmHrWCXG5YmfrL2Iguyu9Oe5tfoCpYMbn/jHW4L 8ZcbuEgMN/lDcFzKA3J9/0Y2caUiMvngfT5+qN25uuLI60AZIgsJroG4Cz/wYFc2YZzj Cbfg+5KwihE2fsHwlpSaPF4Hwj1l+pjXkfrjLO2NT0YBjAIPSmfdThN/7krADDspBEEj y8RIZj7gwUyhFQ3AgR7dGde2KzCNn0ZY/sxc+1uXqUAo+3WQKUedd3MkgirfbZtwGKE7 F34A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rSTQDfmp8cXDv7jR3fnGVDMUwOIelwGuqYXnSfI9btM=; b=L0zzKkr793Q3nQQ+Vd00PhLHUmFSxvWPnE6owsGMjepo/YwJrx5hzcfoKQ5IkxIhMw XxcrNoTE5Fn9wUg1Dtz7oisyAQwm/ft9IvP+ho14iz9Mld9FQ8BUQqzolUS+zEoxRx9B xXFEmhb+kEh6QZ4Oh5v559amWGkv0d60ElxIt3CMWpd+OKMfV5Kv11rRvyNdXEXdxMNI 5VnJrMM5omJcVxF+uGs81bUe3xm01zQsmbcMKX9hJRxdcpUAnOz0fsqLRqajLL52Pb9J m7f89MJ3dtY2TlkE4qU72i9JhDUzddqJclM2tTgvtBj+dyfg/7GzLlj2ppum2fvkXJqS MlJw== X-Gm-Message-State: AKaTC022g6H3n+ivUiztVOMsU8MpL5/JLX82wqra8CxUbB6hv5Ld++vhZgfA4cXl8bqvl3BwHQkqw3LarShcvA== X-Received: by 10.46.32.165 with SMTP id g37mr1776755lji.49.1479922059578; Wed, 23 Nov 2016 09:27:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.16.85 with HTTP; Wed, 23 Nov 2016 09:27:38 -0800 (PST) In-Reply-To: References: <8d72490d-551a-c58f-991a-1750e9af8df9@gmail.com> From: Benjamin Cronce Date: Wed, 23 Nov 2016 11:27:38 -0600 Message-ID: To: Mikael Abrahamsson Cc: bloat Content-Type: multipart/alternative; boundary=001a1142b4c2a8132e0541fb3484 Subject: Re: [Bloat] fixing bufferbloat in 2017 X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2016 17:27:41 -0000 --001a1142b4c2a8132e0541fb3484 Content-Type: text/plain; charset=UTF-8 On Wed, Nov 23, 2016 at 11:20 AM, Mikael Abrahamsson wrote: > On Wed, 23 Nov 2016, Pedro Tumusok wrote: > > If this something we should try, I can help out with the first point, but >> the second one probably needs local bufferbloat evangelists. >> > > I am not worried about getting these people on board to show a solution. > > I'm worried that we do not have a solution that is easily deployable for > "normal" people. If someone has X/Y megabit/s Comcast Internet connection, > what solution do we have to offer them? I can't think of one that actually > solves the problem for real. If there is a simple affordable solution, say Open/DD-WRT distro based bridge that all you do is configure your up/down bandwidth and it applies Codel/fq-Codel/Cake, then all you need to do is drive up awareness. A good channel for awareness would be getting in contact with popular Twitch or YouTube gaming streamers. But I wouldn't put much effort into driving up awareness until there is a device that people can easily acquire, use, and afford. At first I was thinking of telling people to use *-WRT supporting routers, but changing the firmware on your router requires too much research, and many people care about bleeding edge features. You need something that works in tangent with whatever they are using. > > > -- > Mikael Abrahamsson email: swmike@swm.pp.se > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat > --001a1142b4c2a8132e0541fb3484 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



--001a1142b4c2a8132e0541fb3484--