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 _______________________________________________ Starlink mailing list Starlink@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/starlink
