From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] ntia explicitly excludes latency under load from bead measurements
Date: Mon, 9 Dec 2024 18:46:58 +0100 [thread overview]
Message-ID: <CAJUtOOhvVrsN-Vd3ChRPCwLvdauwwdsb23Rjnh-1856F17YqWQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5fxqq7K+YNabx8xUTqHOFAqZdB=i1L9ViHqZdx7S8zJw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
Are they retarded, or what? LOL
All the best,
Frank
Frantisek (Frank) Borsik
https://www.linkedin.com/in/frantisekborsik
Signal, Telegram, WhatsApp: +421919416714
iMessage, mobile: +420775230885
Skype: casioa5302ca
frantisek.borsik@gmail.com
On Mon, Dec 9, 2024 at 6:42 PM Dave Taht via Nnagain <
nnagain@lists.bufferbloat.net> wrote:
> from:
>
>
> https://www.ntia.gov/sites/default/files/2024-12/draft_performance_measures_for_bead_last-mile_networks_policy_notice.pdf
>
> "For latency testing, a provider must conduct a minimum of one test
> per minute — 60 tests per hour — for each testing hour. If the
> consumer load during a latency test exceeds 200,000 bits per second
> downstream,26 the provider may cancel the test and reevaluate whether
> the consumer load exceeds 200,000 bits per second downstream before
> retrying the test in the next minute."
>
> w/a 100ms baseline. Hilarious. Sad.
>
> --
> Dave Täht CSO, LibreQos
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>
[-- Attachment #2: Type: text/html, Size: 2991 bytes --]
next prev parent reply other threads:[~2024-12-09 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 17:42 Dave Taht
2024-12-09 17:46 ` Frantisek Borsik [this message]
2024-12-09 21:22 ` Eugene Chang
2024-12-09 18:29 ` Sebastian Moeller
2024-12-09 18:53 ` Livingood, Jason
2024-12-09 19:55 ` Robert McMahon
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/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJUtOOhvVrsN-Vd3ChRPCwLvdauwwdsb23Rjnh-1856F17YqWQ@mail.gmail.com \
--to=frantisek.borsik@gmail.com \
--cc=nnagain@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