From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Jon Pike <jonpike54@gmail.com>, make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Upcoming WiFi standard to set per-flow DSCP values?
Date: Tue, 04 Jan 2022 22:49:56 +0100 [thread overview]
Message-ID: <87r19nb27v.fsf@toke.dk> (raw)
In-Reply-To: <CALukJKQeJKGsHVBh2GJU+BWP_Hf7j9evTa2avOfQp2qpEvb_Ag@mail.gmail.com>
Jon Pike <jonpike54@gmail.com> writes:
> Might it have to do with these RFC's?
>
> https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=a5e3def1822431ef6436cb493df77006dbacafd6
Don't think so; that's just the standard static mapping. Bob pointed me
to this:
https://www.wi-fi.org/downloads-registered-guest/Wi-Fi_CERTIFIED_QoS_Management_Technology_Overview_202110.pdf/37425
which seems to be the right thing (you can just input garbage into the
form to download the PDF). It is a mechanism where the AP and client can
request of each other to apply certain DSCP markings (and thus WiFi WMM
classes) to certain flows. The document has gems like:
> To deliver good quality of experience in these applications it is
> essential that Wi-Fi networks support a range of service categories
> that differentiate and prioritize data flows for such applications.
> Wi-Fi networks that give equal priority access to all connected
> devices and data flows cannot provide the throughput and stability
> required when traffic demands exceed the available bandwidth. This
> negatively impacts the user experience.
and:
> The efficient use of unlicensed spectrum used by Wi-Fi requires good
> faith use of mechanisms that enable prioritized access to that
> spectrum. Therefore, it is important that all entities that leverage
> Wi-Fi QoS Management features do so in a reasonable and responsible
> manner.
So yeah, that'll all end well...
Also, what is it with people wanting to provide AR in sports stadiums?
Crops up in all these "future of wireless" type marketing presos...
-Toke
next prev parent reply other threads:[~2022-01-04 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1641315601.32049.make-wifi-fast@lists.bufferbloat.net>
2022-01-04 18:31 ` Jon Pike
2022-01-04 21:49 ` Toke Høiland-Jørgensen [this message]
2022-01-04 23:57 ` Jon Pike
2022-01-05 12:02 ` Toke Høiland-Jørgensen
2022-01-05 12:28 ` Sebastian Moeller
2022-01-05 17:11 ` Aaron Wood
2022-01-05 18:33 ` Sebastian Moeller
2022-01-05 20:42 ` Bob McMahon
2022-01-09 22:51 ` Sebastian Moeller
2022-01-09 23:41 ` Dave Taht
2022-01-10 16:02 ` Bob McMahon
[not found] <mailman.1399.1641415377.1267.make-wifi-fast@lists.bufferbloat.net>
2022-01-07 5:48 ` Jon Pike
2022-01-03 21:06 Toke Høiland-Jørgensen
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=87r19nb27v.fsf@toke.dk \
--to=toke@toke.dk \
--cc=jonpike54@gmail.com \
--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