Lets make wifi fast again!
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Rich Brown <richb.hanover@gmail.com>,
	 rjmcmahon via Make-wifi-fast
	<make-wifi-fast@lists.bufferbloat.net>,
	 bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] [Bloat]  Looking for a citation...
Date: Sun, 18 Aug 2024 11:52:42 -0700 (PDT)	[thread overview]
Message-ID: <s3n574s9-6qq5-q76s-9r7p-50o34rs130q9@ynat.uz> (raw)
In-Reply-To: <8D08AFCD-B80E-46B3-B18F-B0864E8095F3@gmx.de>

On Sun, 18 Aug 2024, Sebastian Moeller via Bloat wrote:

> *) I expect wildly different update schedules for routers/APs, notebooks, and 
> mobile devices. Smartphones might on the forefront with some folks replacing 
> them every 24 months, and laptops/APs on much slower schedules.... so even if 
> WiFi6/7 gear starts hitting some customer premises, I expect a looooong tail 
> of WiFi4/5 devices

IoT devices, video doorbells, set top boxes, etc probably have much slower 
upgrade cycles and usually have much older chipsets even on their chip date. 
Some of them don't use a lot of data, but because they are using older encoding 
they use a lot more airtime than you expect.

David Lang

  reply	other threads:[~2024-08-18 18:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-18  9:08 [Make-wifi-fast] " Rich Brown
2024-08-18 18:48 ` Sebastian Moeller
2024-08-18 18:52   ` David Lang [this message]
2024-08-19 13:29 ` [Make-wifi-fast] [Bloat] " Livingood, Jason
2024-08-19 22:12   ` Bob McMahon

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/make-wifi-fast.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s3n574s9-6qq5-q76s-9r7p-50o34rs130q9@ynat.uz \
    --to=david@lang.hm \
    --cc=bloat@lists.bufferbloat.net \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    --cc=richb.hanover@gmail.com \
    /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