From: Robert McMahon <rjmcmahon@rjmcmahon.com>
To: Dave Taht via Nnagain <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] pet peeves and policy recommendations
Date: Mon, 09 Oct 2023 16:58:53 -0700 [thread overview]
Message-ID: <1568d6e4-7e03-42b1-b8b3-1fa0f3aa5380@rjmcmahon.com> (raw)
In-Reply-To: <CAA93jw7hvsR0ZbFtvJZ6OcCC6upodddK64ATzg5jqKqnU_5tKw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2473 bytes --]
There are large NRE spends and advancements in WiFi around spectral efficiency, multilink operatons, ofdma and RUs, wider channels, lower latency, ap/sta densities, obss concurency, etc.
The 802.11be standard is a good reference. https://en.wikipedia.org/wiki/IEEE_802.11be
WiFi hasn't been abandoned like DSL, ATM, tokenring, etc. I think 802.11 will survive and have continuous improvements per this mass investment by industry players.
Bob
On Oct 9, 2023, 1:45 PM, at 1:45 PM, Dave Taht via Nnagain <nnagain@lists.bufferbloat.net> wrote:
>I scribbled down a few things that I wish had more champions.
>
>1) The US government holds 10? 11? IPv4/8s. At the current market
>prices for these that is over 700m per range. To cross the digital
>divide new users and ISPs need IP addresses, the government itself
>update more to rfc1918 and/or ipv6, and selling these off seems like a
>way to fund other internet related projects.
>
>2) Obviously I care deeply about more QoE technologies being deployed.
>It makes an enormous difference in internet quality especially at low
>bandwidths. I have been pilloried for suggesting too often that 25/10
>with CAKE was actually all most american families need.
>
>3) The CTO of the whitehouse position remains unfilled since the start
>of the Biden administration. Perhaps with more clue at the top, and
>office space for it that is not in the basement floor, with a sign
>saying "Beware of the leopard", smarter policies will emerge.
>
>4) I wish the world could focus less on bandwidth in general, more on
>wifi and low latency at range, and less interference (e.g. smaller
>default channel widths) and jitter
>
>5) I really love the uIXP idea. IT has become very cheap to build a
>SDN router capable of bgp and 100Gbit throughput. Every town could
>have one or more open network interconnects, not just between the
>biggest providers but also enabling newer technologies to emerge.
>
>6) There is no 6!
>
>7) Similarly, Biden''s electrification program (every 50 miles, a
>charger) is a good place for a uIXP. Similarly, the postal service has
>a lot of space everywhere mostly standing idle.
>
> 8) IPv6, anyone?
>
>--
>Oct 30:
>https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
>Dave Täht CSO, LibreQos
>_______________________________________________
>Nnagain mailing list
>Nnagain@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/nnagain
[-- Attachment #2: Type: text/html, Size: 2719 bytes --]
prev parent reply other threads:[~2023-10-09 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 20:45 Dave Taht
2023-10-09 23:58 ` Robert McMahon [this message]
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=1568d6e4-7e03-42b1-b8b3-1fa0f3aa5380@rjmcmahon.com \
--to=rjmcmahon@rjmcmahon.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