From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <toke@toke.dk>
Received: from mail.toke.dk (mail.toke.dk [52.28.52.200])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by lists.bufferbloat.net (Postfix) with ESMTPS id 4A7293CB35
 for <bloat@lists.bufferbloat.net>; Thu, 19 Jul 2018 12:44:40 -0400 (EDT)
From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= <toke@toke.dk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023;
 t=1532018678; bh=sobvTmk8F4ZQwByGJ8+/VLblRpfIMXreyuzLqPZ9h+U=;
 h=From:To:Subject:Date:From;
 b=iscFdXXMLZd8unGfXJF2Cq7ZBWWNQdDxuae7pux6WQ8S11EHVBdNof5UExMPd5zuA
 1oSA9+UVZ2boxCQoJrgKj7V6cdmg5jGFQ9Hpsq3RtF4db6tlP3MfZ7CNsNaDI/VPtC
 hXa+RYM2SCXNI0QOOAjXZ6jD3Uaw2TbcXKb8rNLwbvGCocmpYzGT4J2fedO3ENCOho
 VAUtuyAtEghh7NdFUVTXDyQJZ5sx3AlJe+CYbRaDtVMXgCAvuQHUVrwCaEZlt6mtMP
 P4Fee7ThMTujmM1r1IETv0Q+hcG3vJjm6I0r+R7aQsOUWuoyDhNDmaDI5LTblcbMA2
 664190/XRoIEg==
To: bloat@lists.bufferbloat.net
Date: Thu, 19 Jul 2018 18:44:24 +0200
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87va9b18gn.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Subject: [Bloat] Is bufferbloat a privacy issue?
X-BeenThere: bloat@lists.bufferbloat.net
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: General list for discussing Bufferbloat <bloat.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/bloat>,
 <mailto:bloat-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/bloat>
List-Post: <mailto:bloat@lists.bufferbloat.net>
List-Help: <mailto:bloat-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/bloat>,
 <mailto:bloat-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2018 16:44:40 -0000

This was presented at today's maprg session at the IETF:

https://datatracker.ietf.org/meeting/102/materials/slides-102-maprg-is-bufferbloat-a-privacy-issue-brian-trammell-00

-Toke