From: Sebastian Moeller <moeller0@gmx.de>
To: Dave Taht <dave.taht@gmail.com>,
Dave Taht via Bloat <bloat@lists.bufferbloat.net>,
libreqos <libreqos@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] summarizing the bitag latency report?
Date: Sat, 12 Nov 2022 09:39:31 +0100 [thread overview]
Message-ID: <9FAAD498-E02B-4780-9324-FD8883C6320E@gmx.de> (raw)
In-Reply-To: <CAA93jw4MXxRnzchsETc7mgT0xdAkxs4vG0MoNu=GfQ4u8ALLqg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1429 bytes --]
My lightning round take:
Politically: it's complicated
Practically: this ain't rocket-science, just deploy competent traffic shaping, competent scheduling (preferably FQ) and competent AQM.
Then you are in a fine spot to wait until the political dust settles.
I admit only having browsed the report and that some time ago... but a single paragraph will always be far from the text.
On 12 November 2022 00:16:43 CET, Dave Taht via Bloat <bloat@lists.bufferbloat.net> wrote:
>If you were to try to summarize this *in a paragraph*, what would you say?
>
>https://www.bitag.org/documents/BITAG_latency_explained.pdf
>
>(yes, I helped write this, but squeezing it down to less than 3 pages
>is beyond my capabilities, much less a paragraph, and by the time we
>hit the recommendations section, things had got too political to make
>sane recommendations)
>
>Also QoS, vs QoE. Try to imagine explaining the need to a CFO, or
>congresscritter. Feel free to take more than a paragraph.
>
>
>--
>This song goes out to all the folk that thought Stadia would work:
>https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
>Dave Täht CEO, TekLibre, LLC
>_______________________________________________
>Bloat mailing list
>Bloat@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/bloat
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 2021 bytes --]
next prev parent reply other threads:[~2022-11-12 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 23:16 Dave Taht
2022-11-11 23:49 ` [Bloat] [LibreQoS] " dan
2022-11-12 8:39 ` Sebastian Moeller [this message]
2022-11-12 13:14 ` [Bloat] " Sebastian Moeller
2022-11-12 21:59 ` Dave Collier-Brown
2022-11-14 17:05 ` Jonathan Morton
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=9FAAD498-E02B-4780-9324-FD8883C6320E@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
/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