From: Dave Taht <dave.taht@gmail.com>
To: Rpm <rpm@lists.bufferbloat.net>, bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] cloudflare consumer labels blog
Date: Fri, 15 Apr 2022 07:47:13 -0700 [thread overview]
Message-ID: <CAA93jw5xiKFbRMpk+yNd0egBOqPrLF8Qhgjj=VtF_f5x3oVrDw@mail.gmail.com> (raw)
"We believe that metrics beyond bandwidth such as latency and jitter
(the variance in latency) have grown appreciably in importance and
that should be reflected in policy going forward."
- https://blog.cloudflare.com/breaking-down-broadband-nutrition-labels/
It also includes a number for "typical packet loss": .08%
I miss when we could do a discussion in line with a blog, or via
email, in this case, they post urls to reddit, etc, at the end.
Follow on Twitter
David Tuber |@tubes__
Mike Conlow |@mikeconlow
Cloudflare |Cloudflare
--
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
next reply other threads:[~2022-04-15 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 14:47 Dave Taht [this message]
2022-04-15 16:55 ` Dave Collier-Brown
2022-04-15 17:20 ` Dave Taht
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='CAA93jw5xiKFbRMpk+yNd0egBOqPrLF8Qhgjj=VtF_f5x3oVrDw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=rpm@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