From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-x243.google.com (mail-pf0-x243.google.com [IPv6:2607:f8b0:400e:c00::243]) (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 220393B260 for ; Tue, 22 Nov 2016 11:19:15 -0500 (EST) Received: by mail-pf0-x243.google.com with SMTP id c4so1654200pfb.3 for ; Tue, 22 Nov 2016 08:19:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=Fuk/TE+xyjS9lC/JYXPwme7A13ekeSIP7UYkWBEc0/I=; b=y2OP7prSFkY/wdABh5QkRwBwzpjVfyV6qy5zR+kjjZAHXZNOEb57LVnrOdOaKyUPj2 3XcIgvGJHlHsLRRpsQZ+S4g6nScX43iDZkX9kgGr+EZ8RY+QTbp6bmdbmH6TfJ4rcWQS gYXfq4w74AXqQzJWJx5+qNhQEpU0dtxX1AVEvUNRwVv4+6hAOqxYx8LpPHJ/0mxNlfPg OYsKqPP+fQGfILYUmWlfXB9p5bq8O9Ydh9ByDA4qRgbStcCx1VCISJ657eadGAzK70XP ikSuxIx5nK4HQX6uXm+MFzp5cNkh8lxERnnhcchdC022WcJQwootwE5+aMqufRrb3OpI zhug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Fuk/TE+xyjS9lC/JYXPwme7A13ekeSIP7UYkWBEc0/I=; b=RwVyR0d3a5U+ro5/NpQg507q+dMKMIwaLFTUtBGvKM/4/IK0fqgbvi1ll14FjiyIP3 MQBOix24vSsyz1UdA10+hUmKM8yripUf7BjE7mqH3je6R59W2oudaDLYujXk4WMez4xy 44rGLgALTuhgtp53uGZNsIGHvHPK425qSWQNaLyozWhqdWWsj88V+55hiH8Ojrd7pYYG nlUn7KMg8faCaeqzOuOAuOiXbup28erq8Czz49ycmZTY7QEc7O/Am3equA6goaG1LQFe KRhVWiIQANScpRkz6uN9wfVPFo9+j/4f9FaeWgpCXTOrFyf5hmCuvTKBXzVAMLbSQ282 OuFw== X-Gm-Message-State: AKaTC00EuxTbo9Fvi4K+xEcspgibkBHLDGQt13qYsanJ2aQphTUJKDNe3ezIbCiSOEgogg== X-Received: by 10.99.149.90 with SMTP id t26mr33051928pgn.156.1479831554155; Tue, 22 Nov 2016 08:19:14 -0800 (PST) Received: from zotac.xperim.be ([91.178.160.69]) by smtp.gmail.com with ESMTPSA id b71sm46315641pfj.62.2016.11.22.08.19.12 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 Nov 2016 08:19:13 -0800 (PST) Received: from [192.168.1.172] (mordor.xperim.be [192.168.1.172]) by zotac.xperim.be (Postfix) with ESMTPSA id C91D2486562; Tue, 22 Nov 2016 17:19:06 +0100 (CET) To: bloat@lists.bufferbloat.net References: From: Jan Ceuleers Message-ID: <8d72490d-551a-c58f-991a-1750e9af8df9@gmail.com> Date: Tue, 22 Nov 2016 17:19:06 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit 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: Tue, 22 Nov 2016 16:19:15 -0000 On 22/11/16 16:32, Dave Taht wrote: > What's left to do? Furthering adoption of the code that contains the bloat-related improvements. In my view, the single biggest potential contributor towards driving such adoption would be for Ookla to start measuring and reporting bufferbloat, thereby putting it on the agenda of both end users and carriers (who use Ookla's servers to qualify equipment in their labs). That would in turn put it on the agenda of equipment manufacturers.