Re: [Make-wifi-fast] Upcoming WiFi standard to set per-flow DSCP values?

[Jon Pike <jonpike54@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]

And there I was, thinking it was some kind of improvement on things...

Sounds like I should go from insuring I have it,  to figuring out how to
disable it altogether?  An "Unmark them all and let Airtime Fairness sort
them out" situation would be better?  Or is there something sensible
inbetween?


> On Wed, Jan 5, 2022 at 4:28 AM Sebastian Moeller <moeller0@gmx.de> wrote:
>
>> Hi Toke, hi Jon,
>>
>> IMHO RFC8325 and the whole WMM scheme clearly lacks data showing that is
>> actually delivers on its promises. RFC8325 specifically seems obsessed in
>> changing mappings such that PHBs align with the 4 WMM queues, instead of
>> interpreting the fact that the apparent mismatch between what the IETF
>> thinks about specific PHBs/DSCPs and how they are treated for most users,
>> as clear sign, that reality does not care... (probably mostly driven by the
>> elephant in the room, of DSCPs not being end-to-end).
>>
>> I agree with Toke that allowing APs to steer specific DSCP use by
>> applications seems taking an proven non-working idea to the extreme... (APs
>> can already instruct stations on which DSCPs to map to which AC (see
>> Felix's patch), which is not used that much, no idea why anybody thinks
>> that allowing APs even more disruptive changes to end-point behavior is
>> going to work any better).
>>
>> Regards
>>         Sebastian
>>
>> P.S.: IMHO the biggest change might be the up-prioritisation of EF from
>> AC_VI to AC_VO, and I am not sure that is a good idea.
>>
>>
>> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast


>
>

[-- Attachment #2: Type: text/html, Size: 2752 bytes --]