From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Rich Brown <richb.hanover@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] FCC requires broadband "Nutritional Label"
Date: Mon, 28 Nov 2022 13:45:56 +0000 [thread overview]
Message-ID: <8A46D22F-454F-420C-BC56-5A5191C8EB4A@cable.comcast.com> (raw)
In-Reply-To: <7F6137DB-DB43-4073-9140-27E875BF1A6B@gmail.com>
On 11/18/22, 07:36, "Bloat on behalf of Rich Brown via Bloat" <bloat-bounces@lists.bufferbloat.net on behalf of bloat@lists.bufferbloat.net> wrote:
> Even though the label only specifies "typical latency", I have a sense that this is a good step forward. If your ISP specifies 5 msec as "typical" and their crummy router is bloated, can you get a repair if you call them and say that it's averaging 150msec?
FWIW I think there's now a further comment period open on the label. I am sure comments around (working) latency would be welcome...
Jason
prev parent reply other threads:[~2022-11-28 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 12:36 Rich Brown
2022-11-18 13:15 ` Dave Collier-Brown
2022-11-19 8:28 ` Jan Ceuleers
2022-11-28 13:45 ` Livingood, Jason [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=8A46D22F-454F-420C-BC56-5A5191C8EB4A@cable.comcast.com \
--to=jason_livingood@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@gmail.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