From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: libreqos <libreqos@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [LibreQoS] [Bloat] summarizing the bitag latency report?
Date: Sat, 12 Nov 2022 14:14:57 +0100 [thread overview]
Message-ID: <E66A61AE-0C63-4A80-AA4E-3779E268C002@gmx.de> (raw)
In-Reply-To: <CAA93jw4MXxRnzchsETc7mgT0xdAkxs4vG0MoNu=GfQ4u8ALLqg@mail.gmail.com>
Hi Dave,
so I think you have three audiences that should learn about this:
a) end-users (my hot-take was tailored for end-users)
b) politicians
c) industry people (C-suite members of ISPs*)
I think you need three different one paragraph summaries tailored to each groups focus.
a) end users
I would stress the "you can improve your link today with little work" to make it fit for video conferencing "under working conditions".
I would not wade into the swamp that is "gaming" any deeper than necessary (so have a sentence along the lines of "these described methods will obviously also help other
latency-sensitive applications like gaming"). Why avoid gaming? Gamers are quite opinionated and take promises often literally, hence are easy to disappoint so better under-promise, but over-deliver.
b) politicians
Here I would emphasize that while fiber-to-everyone is the ultimate goal getting latency under control will result in a noticeable "better" (because subjectively more responsive) internet experience for those that will have to wait longer for fiber. I simply assume that fiber-everywhere is the goal across the aisle in the US, at least over here all major parties agree about the ultimate goal and just disagree how to get there, with the party in opposition magically always seeing more urgency ;).
So push this as a relative low-effort/low-cost method to noticeably improve the internet experience for the electorate...
c) industry people
This has two groups, those that run large internal networks and ISPs. I think for the first group the arguments for a) and b) could be re-used (b) reframed as low-cost ways to get more mileage out of the existing network infrastructure with a few targeted replacements/upgrades/configuration changes).
For the second group I am a bit at a loss, as the arguments a) and b) MIGHT not be all that attractive for someone selling internet-access priced by "top-speed", making lower speeds more enjoyable/usable seems a bit counter productive... One pitch could be a marketable advantage over the competition, but that requires actual competition.
Not sure how to give the enlightened ones arguments to convince their peers.
Regards
Sebastian
*) some are enlightened already
P.S.: QoS, vs QoE
Cause and effect, means and end... What the users will evaluate are their experiences; traditional QoS can be a means to improve that experience, with a hitherto often neglected aspect being latency-under-load which above a bare minimum access rate seems to correlate stronger with user experience than top-speeds.
To convince CFO, or congresscritters I would think the best would be a simple mobile demonstration platform... together with argument b) above
> On Nov 12, 2022, at 00:16, 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
next prev parent reply other threads:[~2022-11-12 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 23:16 [LibreQoS] " Dave Taht
2022-11-11 23:48 ` dan
2022-11-12 8:39 ` [LibreQoS] [Bloat] " Sebastian Moeller
2022-11-12 13:14 ` Sebastian Moeller [this message]
2022-11-12 14:38 ` Herbert Wolverson
2022-11-12 15:00 ` Dave Taht
2022-11-12 15:03 ` Herbert Wolverson
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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E66A61AE-0C63-4A80-AA4E-3779E268C002@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