Re: [NNagain] ntia explicitly excludes latency under load from bead measurements

[Sebastian Moeller <moeller0@gmx.de>]

On 9 December 2024 18:42:01 CET, 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.

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

(I agree this could be more ambitious, but for reference the German regulator allows up to 150ms OWD or 300ms RTT, with reflectors mostly in the center (Frankfurt), and Germany is small, with largest distance ~1000km or 10ms RTT in fiber... I would take your 100ms every day ;) )


How about courteously applaud them for taking latency serious and advise them to include additional latency under load tests...



>
>-- 
>Dave Täht CSO, LibreQos
>_______________________________________________
>Nnagain mailing list
>Nnagain@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/nnagain

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.