[Ecn-sane] [tsvwg] per-flow scheduling

Kyle Rose krose at krose.org
Wed Jun 19 10:20:29 EDT 2019


On Wed, Jun 19, 2019 at 10:13 AM Bob Briscoe <ietf at bobbriscoe.net> wrote:

> Jake, all,
>
> You may not be aware of my long history of concern about how per-flow
> scheduling within endpoints and networks will limit the Internet in
> future. I find per-flow scheduling a violation of the e2e principle in
> such a profound way - the dynamic choice of the spacing between packets
> - that most people don't even associate it with the e2e principle.
>
> I detected that you were talking about FQ in a way that might have
> assumed my concern with it was just about implementation complexity. If
> you (or anyone watching) is not aware of the architectural concerns with
> per-flow scheduling, I can enumerate them.
>

I would certainly be interested in reading more about these concerns. Even
a reference that I can read out-of-band would be fine. Thanks, Bob.

Kyle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/ecn-sane/attachments/20190619/34b7694a/attachment.html>


More information about the Ecn-sane mailing list