Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>, starlink@lists.bufferbloat.net
Subject: [Starlink] BITAG report - "latency explained' - now published!
Date: Wed, 12 Jan 2022 16:46:36 -0800	[thread overview]
Message-ID: <CAA93jw5-4fq0M1JrnWT7=XA8pgpS3oWKt+dmw6wYZsdBqkgcCg@mail.gmail.com> (raw)

https://www.bitag.org/documents/BITAG_latency_explained.pdf

My hope is that this moves the needle this year, among policymakers
especially, towards a deeper understanding of the key factors that
would lead us all to a better internet,
in year three of the COVID crisis. And my thanks to everyone not just
that participated on this report, but for everyone that has made a
dent in the bufferbloat problem with us, in the last decade, or
longer. Let's cross this chasm in 2022!

The report starts off with;

"For over thirty years, industry has collectively missed a key factor
that drives end users’ Internet quality
of experience (QoE)! The industry has historically been focused on
increasing bandwidth, which has been
straightforward, easy to understand, and indisputably made dramatic
improvements to end-user QoE.

But we now recognize that it is not just greater throughput that
matters, but also consistently low latency.
Unfortunately, the way that we’ve historically understood and
characterized latency was flawed, and our
latency measurements and metrics were not aligned with end-user QoE."

and gets kind of detailed from there.


--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org

Dave Täht CEO, TekLibre, LLC

                 reply	other threads:[~2022-01-13  0:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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/starlink.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to='CAA93jw5-4fq0M1JrnWT7=XA8pgpS3oWKt+dmw6wYZsdBqkgcCg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=starlink@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