From: "Livingood, Jason" <jason_livingood@comcast.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:53:20 +0000 [thread overview]
Message-ID: <8B19A758-D0A7-49C9-AB17-72CFF18D945C@comcast.com> (raw)
In-Reply-To: <2FC4966A-530C-4E5B-B82B-544299CB4194@gmx.de>
>w/a 100ms baseline. Hilarious. Sad.
[SM] This is not all that terrible for minimal RTT measurements, it does however do zilch for latency under load. The 100ms is also not that terrible, given that the US is large, think test point in Anchorage reflector in Miami...
[JL] The 100ms was initially put there to exclude satellite internet from being eligible (prior to LEO operators coming onto the scene).
[JL] Some concerns I noticed in the document:
1. They want 10% of homes tested in Sec. 3.2, which seems to be an extremely large percentage - well above typical statistical significance - the FCC MBA only needed >30 to be valid nationally. Amusingly, the example they cite in Sec. 3.3 works out to 5% - so they are not internally consistent.
2. In Sec. 3.4, expecting the ISP to temporarily upgrade subs to the highest tier to run tests and then downgrade them again does not make practical sense – for example they suggest that rather than randomly selecting from users in the highest tier that instead you must select from all tiers and then upgrade those not on the highest tier.
3. In Sec. 3.9, it seems a bit too proscriptive on the (IXP) server locations – could be simplified to a regional peering location of the ISP network to allow for flexibility.
4. In Sec. 3.10, similarly proscriptive for example by defining the duration of a test as 10-15 seconds – what if they test can be completed just as accurately in 9 seconds? ISPs should have latitude to configure these tests & the state of the art is moving fast.
next prev parent reply other threads:[~2024-12-09 18:53 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
2024-12-09 21:22 ` Eugene Chang
2024-12-09 18:29 ` Sebastian Moeller
2024-12-09 18:53 ` Livingood, Jason [this message]
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=8B19A758-D0A7-49C9-AB17-72CFF18D945C@comcast.com \
--to=jason_livingood@comcast.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