General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Is bufferbloat a privacy issue?
Date: Thu, 19 Jul 2018 09:51:48 -0700	[thread overview]
Message-ID: <CAA93jw7cofSgNie8wX9sNe3XWz3hNufw46m_GihNvCP3We3RjA@mail.gmail.com> (raw)
In-Reply-To: <87va9b18gn.fsf@toke.dk>

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øiland-Jørgensen <toke@toke.dk> wrote:
>
> 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
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat



-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

  reply	other threads:[~2018-07-19 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19 16:44 Toke Høiland-Jørgensen
2018-07-19 16:51 ` Dave Taht [this message]
2018-07-19 18:52   ` Luca Muscariello

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw7cofSgNie8wX9sNe3XWz3hNufw46m_GihNvCP3We3RjA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox