From: Dave Taht <dave.taht@gmail.com>
To: Dave Collier-Brown <dave.collier-brown@indexexchange.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] cloudflare consumer labels blog
Date: Fri, 15 Apr 2022 10:20:45 -0700 [thread overview]
Message-ID: <CAA93jw585RJM+tn6w0xp6g2om4VMtmAzkaFD8DJfJSRUpm2GvQ@mail.gmail.com> (raw)
In-Reply-To: <a261698b-59a7-ff46-5be3-49bab8b50d64@indexexchange.com>
thank you. I just ranted there also. Having tilted at that windmill
today, I am going to go do some real work....
https://news.ycombinator.com/item?id=31041494
On Fri, Apr 15, 2022 at 9:55 AM Dave Collier-Brown
<dave.collier-brown@indexexchange.com> wrote:
>
> I added this comment via Hacker News
>
> "Packet loss" is more interesting to nerds than consumers, who don't know what it means. Arguably it needs a better name.
> "Delays due to retransmission" is short enough to fit the label, and is what a packet loss means _to the reader of the label_, rather than to me.
>
> --dave
>
>
> On 4/15/22 10:47, Dave Taht wrote:
>
> "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
>
>
> --
> David Collier-Brown, | Always do right. This will gratify
> System Programmer and Author | some people and astonish the rest
> dave.collier-brown@indexexchange.com | -- Mark Twain
>
>
> CONFIDENTIALITY NOTICE AND DISCLAIMER : This telecommunication, including any and all attachments, contains confidential information intended only for the person(s) to whom it is addressed. Any dissemination, distribution, copying or disclosure is strictly prohibited and is not a waiver of confidentiality. If you have received this telecommunication in error, please notify the sender immediately by return electronic mail and delete the message from your inbox and deleted items folders. This telecommunication does not constitute an express or implied agreement to conduct transactions by electronic means, nor does it constitute a contract offer, a contract amendment or an acceptance of a contract offer. Contract terms contained in this telecommunication are subject to legal review and the completion of formal documentation and are not binding until same is confirmed in writing and has been signed by an authorized signatory.
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
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
prev parent reply other threads:[~2022-04-15 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 14:47 Dave Taht
2022-04-15 16:55 ` Dave Collier-Brown
2022-04-15 17:20 ` Dave Taht [this message]
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=CAA93jw585RJM+tn6w0xp6g2om4VMtmAzkaFD8DJfJSRUpm2GvQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.collier-brown@indexexchange.com \
/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