From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (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 82E283CB35 for ; Thu, 19 Jul 2018 14:52:45 -0400 (EDT) Received: by mail-yw0-x22b.google.com with SMTP id r184-v6so3457297ywg.6 for ; Thu, 19 Jul 2018 11:52:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jD61uzf4DXuJN4QlGseGU/fWL11tLDzg6NxioP+k5WE=; b=b3mYwSosDfM2J/GDGA8895VQ4gZx1wIHRrVKTEKSpjAH9Za92ge6GsUDjNb3p7yQGX pL3AW/QB19QPdglNmRxgWLa/UPN8xBCfkolcytbxtUkktjB3cVXYXKBH0OXXlYukRiFY sKzQUFzvibQOJMhoHBarlRALM7VA2PgVB55Jq8c+bWKmhF7LR1X8aKbbi2SHxwitvcXV wEX8YP6YymyqpKCPyb1fAa3d5D6BRTBkWgolhFrGd/c7S1LKeJoTnt8OpfdcRIGp6K/t kwonGMHsfKpqVDJ9xwHqZ2eedAeVt6j7geiuQ479jb8rtG7V4PLKF/GdzMwPAf217Wnl yhuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jD61uzf4DXuJN4QlGseGU/fWL11tLDzg6NxioP+k5WE=; b=kWwiP8W0XksG/6ryhXYsR0PCq2bFsc3577UeGGAglZDU4cHXw9FKfNAnkjjezpRbcc XFAhl0hR3VGPuQrCl2Sko5ojrFAT8U113JQqO5VCyiomv5EMmplSD+ahuBxIuPSXPbLs yhXS6MYzHi/D26oF2xLuT/OU6bdKHX01X+nVKZ3+R3ti1tuJrP3WKEVJgA0TUYbpcRWe 5KXkJCCFNqIMDwFm2UDHYpRFaZr25t0rdBUiGpQ6p8/K6vDH6oBdwfP0MvaBK18Qi0pQ 031B9LWgWPOYR0H1gvdZuG9MbGh/Kp82lPudOt87yLqa0aVVgXSXhaYBlbuKKz7FZGXY iH9A== X-Gm-Message-State: AOUpUlF29sqOWskMmSTtjTnJPcUAwiP+RPpzJCeF6iKSKDrSns1y+nfK O+rlVXTWXxtVsmbGj3QluwpMvuz8nnH+o7NcHEA= X-Google-Smtp-Source: AAOMgpdKBkuaUz253hSrwPm6bj+1sFzeUBkz1ROMkWNdK/VvbF7VX23OLEMXELApJsUiJf/MxJCrAEmrJ4JdmnMin7o= X-Received: by 2002:a81:1791:: with SMTP id 139-v6mr5714150ywx.354.1532026364955; Thu, 19 Jul 2018 11:52:44 -0700 (PDT) MIME-Version: 1.0 References: <87va9b18gn.fsf@toke.dk> In-Reply-To: From: Luca Muscariello Date: Thu, 19 Jul 2018 14:52:34 -0400 Message-ID: To: Dave Taht Cc: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= , bloat Content-Type: multipart/alternative; boundary="00000000000045124c05715eaf88" Subject: Re: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jul 2018 18:52:45 -0000 --00000000000045124c05715eaf88 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Good point. Flow isolation gives some kind of =E2=80=9Cprivacy=E2=80=9D. But I guess this is not the worse privacy violation one would be concerned about in today Internet. On Thu 19 Jul 2018 at 12:52, Dave Taht wrote: > hahaha. Aside from their last slide not recommending fq, that was an > enjoyable read. fq in this case (but I would deprioritize ping > responses slightly in the general case) makes the actual observed load > even more invisible. > > I think traceroute would have been a better tool for this study. > > and smokeping remains a very useful tool for those that can deploy it. > > On Thu, Jul 19, 2018 at 9:44 AM Toke H=C3=B8iland-J=C3=B8rgensen > wrote: > > > > This was presented at today's maprg session at the IETF: > > > > > https://datatracker.ietf.org/meeting/102/materials/slides-102-maprg-is-bu= fferbloat-a-privacy-issue-brian-trammell-00 > > > > -Toke > > _______________________________________________ > > Bloat mailing list > > Bloat@lists.bufferbloat.net > > https://lists.bufferbloat.net/listinfo/bloat > > > > -- > > Dave T=C3=A4ht > CEO, TekLibre, LLC > http://www.teklibre.com > Tel: 1-669-226-2619 > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat > --00000000000045124c05715eaf88 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Good point. Flow isolation gives some kind of =E2=80= =9Cprivacy=E2=80=9D.

But I guess this is not the worse privacy violation one would be concern= ed about in today Internet.=C2=A0

=
On Thu 19 Jul 2018 at 12:52, Dave Taht <dave.taht@gmail.com> wrote:
hahaha. Aside from their last slide not recommendin= g fq, that was an
enjoyable read. fq in this case (but I would deprioritize ping
responses slightly in the general case) makes the actual observed load
even more invisible.

I think traceroute would have been a better tool for this study.

and smokeping remains a very useful tool for those that can deploy it.

On Thu, Jul 19, 2018 at 9:44 AM Toke H=C3=B8iland-J=C3=B8rgensen <toke@toke.dk> wrote:
>
> This was presented at today's maprg session at the IETF:
>
> https://datatracker.ietf.org/meeting/102/materials/sli= des-102-maprg-is-bufferbloat-a-privacy-issue-brian-trammell-00
>
> -Toke
> _______________________________________________
> Bloat mailing list
> Bloat= @lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


--

Dave T=C3=A4ht
CEO, TekLibre, LLC
ht= tp://www.teklibre.com
Tel: 1-669-226-2619
_______________________________________________
Bloat mailing list
Bloat@list= s.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat
--00000000000045124c05715eaf88--