From: Dave Taht <dave@taht.net>
To: Rich Brown <richb.hanover@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Wi-Fi 6 - how many of our assumptions does it violate?
Date: Thu, 30 Jan 2020 14:28:05 -0800 [thread overview]
Message-ID: <87a764ziiy.fsf@taht.net> (raw)
In-Reply-To: <0928D44A-4F3A-462D-854E-91B653E40B1C@gmail.com> (Rich Brown's message of "Mon, 27 Jan 2020 09:20:41 -0500")
Rich Brown <richb.hanover@gmail.com> writes:
>> On Jan 24, 2020, at 9:06 AM, Rich Brown <richb.hanover@gmail.com> wrote:
>>
>> I saw this overview of the now-in-testing Wi-Fi 6 at
>> https://www.howtogeek.com/368332/wi-fi-6-what%E2%80%99s-different-and-why-it-matters/
>>
>> Its multiple MIMO streams and maybe talking to multiple devices at a
>> time seem as if they might be outside the assumptions we use.
>
> It's worse than I thought. I just watched this explainer video from
> ExtremeNetworks: https://www.youtube.com/watch?v=owBrkFk9afM
>
> If I understand correctly, they want the AP to solve a hard
> (bin-packing) problem, in real-time, with unclear rules for maximizing
> client goals (should the VoIP packet go first?). And no mention of
> airtime fairness or latency...
>
> Or am I missing something? Thanks.
No, they punted on these things in the design.
>
> Rich
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
next prev parent reply other threads:[~2020-01-30 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 14:06 Rich Brown
2020-01-24 20:49 ` Bob McMahon
[not found] ` <mailman.389.1579898991.1241.make-wifi-fast@lists.bufferbloat.net>
2020-01-25 15:41 ` Dave Taht
2020-01-27 14:20 ` Rich Brown
2020-01-30 22:28 ` Dave Taht [this message]
2020-01-31 1:20 ` Bob McMahon
[not found] ` <mailman.414.1580433623.1241.make-wifi-fast@lists.bufferbloat.net>
2020-01-31 1:28 ` Dave Taht
2020-02-03 18:45 ` 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=87a764ziiy.fsf@taht.net \
--to=dave@taht.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--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