From: Michael Welzl <michawe@ifi.uio.no>
To: Dave Taht <dave@taht.net>
Cc: tsvwg@ietf.org, g.white@cablelabs.com, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] quick review and rant of "Identifying and Handling Non Queue Building Flows in a Bottleneck Link"
Date: Thu, 1 Nov 2018 11:39:18 +0100 [thread overview]
Message-ID: <A114864B-8B5C-4099-B04E-2403C5CBE1E8@ifi.uio.no> (raw)
In-Reply-To: <878t2h1jtm.fsf@taht.net>
Hi,
> On 29 Oct 2018, at 05:02, Dave Taht <dave@taht.net> wrote:
>
>
> Dear Greg:
>
> I don't feel like commenting much on ietf matters these days
> but, jeeze,
(snip)
There seems to me to be a disconnect here, the core of which is this comment:
> Did I rant already that the vast majority of flows are non-saturating?
That's a bug, not a feature - and you seem to treat it as an unchangeable fact.
Despite the undebatable importance of bufferbloat and its impact on e2e packet latency, this is only one of the factors playing into the "latency" that I perceive when I click on the link as I surf the Internet.
Flow completion time has to do with saturation as well.
Cheers,
Michael
next prev parent reply other threads:[~2018-11-01 10:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 4:02 Dave Taht
2018-10-29 14:15 ` Toke Høiland-Jørgensen
2018-10-31 0:12 ` Greg White
2018-11-01 13:25 ` Toke Høiland-Jørgensen
2018-11-01 19:13 ` Dave Taht
2018-11-06 4:17 ` Greg White
2018-11-12 22:19 ` Dave Taht
2018-11-01 10:39 ` Michael Welzl [this message]
2018-11-01 14:20 ` Dave Taht
2018-11-04 18:16 ` [Bloat] [tsvwg] " Michael Welzl
[not found] ` <alpine.DEB.2.02.1811011030500.24927@nftneq.ynat.uz>
2018-11-01 18:15 ` [Bloat] " David Lang
2018-11-01 19:12 ` [Bloat] [tsvwg] " Michael Welzl
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=A114864B-8B5C-4099-B04E-2403C5CBE1E8@ifi.uio.no \
--to=michawe@ifi.uio.no \
--cc=bloat@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=g.white@cablelabs.com \
--cc=tsvwg@ietf.org \
/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