General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Collier-Brown <dave.collier-Brown@indexexchange.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] FCC requires broadband "Nutritional Label"
Date: Fri, 18 Nov 2022 08:15:19 -0500	[thread overview]
Message-ID: <34be6a8d-a246-3415-c1a5-734e63601ce6@indexexchange.com> (raw)
In-Reply-To: <7F6137DB-DB43-4073-9140-27E875BF1A6B@gmail.com>


On 11/18/22 07:36, Rich Brown via Bloat wrote:
> Forwarded from NANOG list:
>
>> The effective date will be determined later, after publication in the
>> Federal Register and OMB review under PRA.
>>
>> November 17, 2022?The Federal Communications Commission today
>> unveiled new rules that will for the first time require broadband
>> providers to display easy-tounderstand labels to allow consumers to
>> comparison shop for broadband services. The Report and Order approved by
>> the Commission creates rules that require broadband providers to
>> display, at the point of sale, labels that show key information consumers
>> want?prices, speeds,fees, data allowances, and other critical
>> information. The labels resemble the well-known nutrition labels that
>> appear on food products.
>>
>> https://www.fcc.gov/document/fcc-requires-broadband-providers-display-labels-help-consumers-0
> 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?
>
> At what point does the expense of handling all the tech support calls outweigh the expense of actually making (and deploying) good routers?

For small ISPs, pretty quickly (eg, the late UUNET Canada, where we all
fit in one room)

For the duopolists, not until the legal department says "We've just had
a class-action suit filed against us, is it cheaper to fight it or to
fix whatever they're talking about?"

--dave c-b (;-))

--
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.

  reply	other threads:[~2022-11-18 13:15 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 [this message]
2022-11-19  8:28 ` Jan Ceuleers
2022-11-28 13:45 ` Livingood, Jason

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=34be6a8d-a246-3415-c1a5-734e63601ce6@indexexchange.com \
    --to=dave.collier-brown@indexexchange.com \
    --cc=bloat@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