From: rjmcmahon <rjmcmahon@rjmcmahon.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>,
"Dave Taht via Starlink" <starlink@lists.bufferbloat.net>,
Rpm <rpm@lists.bufferbloat.net>,
discuss <discuss@measurementlab.net>,
"National Broadband Mapping Coalition"
<bbcoalition@marconisociety.org>
Subject: Re: [Starlink] [M-Lab-Discuss] The FCC 2024 Section 706 Report, GN Docket No. 22-270 is out!
Date: Mon, 26 Feb 2024 12:02:21 -0800 [thread overview]
Message-ID: <3d808d9df1a6929ecfba495e75b4fc1b@rjmcmahon.com> (raw)
In-Reply-To: <CAA93jw5vN73pH9VOfxN1n8ciAjExo+9nfOzGJpS1uK9G9mWyWQ@mail.gmail.com>
Thanks for sharing this. I'm trying to find out what are the key metrics
that will be used for this monitoring. I want to make sure iperf 2 can
cover the technical, traffic related ones that make sense to a skilled
network operator, including a WiFi BSS manager. I didn't read all 327
pages though, from what I did read, I didn't see anything obvious. I
assume these types of KPIs may be in reference docs or something.
Thanks in advance for any help on this.
Bob
> And...
>
> Our bufferbloat.net submittal was cited multiple times! Thank you all
> for participating in that process!
>
> https://docs.fcc.gov/public/attachments/DOC-400675A1.pdf
>
> It is a long read, and does still start off on the wrong feet (IMHO),
> in particular not understanding the difference between idle and
> working latency.
>
> It is my hope that by widening awareness of more of the real problems
> with latency under load to policymakers and other submitters
> downstream from this new FCC document, and more reading what we had to
> say, that we will begin to make serious progress towards finally
> fixing bufferbloat in the USA.
>
> I do keep hoping that somewhere along the way in the future, the costs
> of IPv4 address exhaustion and the IPv6 transition, will also get
> raised to the national level. [1]
>
> We are still collecting signatures for what the bufferbloat project
> members wrote, and have 1200 bucks in the kitty for further articles
> and/or publicity. Thoughts appreciated as to where we can go next with
> shifting the national debate about bandwidth in a better direction!
> Next up would be trying to get a meeting, and to do an ex-parte
> filing, I think, and I wish we could do a live demonstration on
> television about it as good as feynman did here:
>
> https://www.youtube.com/watch?v=raMmRKGkGD4
>
> Our original posting is here:
> https://docs.google.com/document/d/19ADByjakzQXCj9Re_pUvrb5Qe5OK-QmhlYRLMBY4vH4/edit
>
> Larry's wonderful post is here:
> https://circleid.com/posts/20231211-its-the-latency-fcc
>
> [1] How can we get more talking about IPv4 and IPv6, too? Will we have
> to wait another year?
>
> https://hackaday.com/2024/02/14/floss-weekly-episode-769-10-more-internet/
>
> --
> https://blog.cerowrt.org/post/2024_predictions/
> Dave Täht CSO, LibreQos
next prev parent reply other threads:[~2024-02-26 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 15:06 [Starlink] " Dave Taht
2024-02-26 20:02 ` rjmcmahon [this message]
2024-02-28 19:12 ` [Starlink] [M-Lab-Discuss] " Fenwick Mckelvey
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d808d9df1a6929ecfba495e75b4fc1b@rjmcmahon.com \
--to=rjmcmahon@rjmcmahon.com \
--cc=bbcoalition@marconisociety.org \
--cc=dave.taht@gmail.com \
--cc=discuss@measurementlab.net \
--cc=nnagain@lists.bufferbloat.net \
--cc=rpm@lists.bufferbloat.net \
--cc=starlink@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