From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: [Bloat] FCC chair
Date: Wed, 27 Oct 2021 16:56:34 -0700 [thread overview]
Message-ID: <CAA93jw4pgTNkSKnsBRjZHvg4X8NtJ5KkkCsrUO_9P5V7_YMiKg@mail.gmail.com> (raw)
I'm pretty sure this is very good news:
https://arstechnica.com/tech-policy/2021/10/biden-finally-makes-fcc-picks-rosenworcel-as-chair-gigi-sohn-as-commissioner/
I'd had a very brief but positive interaction with gigi during the
fight[1] to allow us to keep flashing our own routers so we could
perfect fq_codel for wifi,
and a few with "public knowledge as well. I often have remorse as
after we knocked the FCC flat with that one shot
( https://arstechnica.com/information-technology/2015/11/fcc-we-arent-banning-dd-wrt-on-wi-fi-routers/
)
we didn't pursue the political arena harder... as instead, wifi 6
ended up with even more binary blobs and totally missing out on what
we'd made feasible only a few months later on the ath9k chip. I'd just
got up from that one meeting at the FCC, and went back to work on the
technology, and the energy we'd built, dissolved.
I worry of course about regulation holding back the deployment of
quality aqm/fq algorithms such as pie, fq_codel, fq_pie, and cake as
opposed to promoting them...
[1] http://www.taht.net/~d/fcc_saner_software_practices.pdf
--
Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
Dave Täht CEO, TekLibre, LLC
reply other threads:[~2021-10-27 23:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4pgTNkSKnsBRjZHvg4X8NtJ5KkkCsrUO_9P5V7_YMiKg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=make-wifi-fast@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