From: moeller0 <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] draft-szigeti-tsvwg-ieee-802.11
Date: Wed, 6 Apr 2016 21:42:59 +0200 [thread overview]
Message-ID: <446473DD-CA62-449D-B963-5F10083F2DA1@gmx.de> (raw)
In-Reply-To: <CAA93jw4rhiqUBSUeambci9d9rdkiRK48z818+S_yJ=uxp-ReXA@mail.gmail.com>
Hi Dave,
> On Apr 6, 2016, at 21:28 , Dave Taht <dave.taht@gmail.com> wrote:
>
> being discussed now in:
>
> https://buenayrea.conf.meetecho.com/q-meetecho/Index.jsp
>
> aside from not talking to multicast, and VO's inability to aggregate
> on 802.11n (making it a fairly poor choice for anything but voice),
> and recommending CS7 be dropped…
Dropping CS7 seems both overly cautious and careless at the same time. If the whole diffserve domain ends at an AP talk has any legs that would mean that the AP has strict rules which packets it let’s get access to CS7 in the first place and then sending them as VO seems fine (the burden is on the AP to remap “unauthorized” CS7 packets). So a re-map to AC_BE seems more rational in a home network that in all likelyhood does not remap DSCPs on ingress… Dropping only makes sense if one assumes a deliberately managed DSCP-domain in the first place, in which the admin got sloppy in regard to the APs, not very convincing.
Best Regards
Sebastian
>
> I'd liked it.
>
> --
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> https://www.gofundme.com/savewifi
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
prev parent reply other threads:[~2016-04-06 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 19:28 Dave Taht
2016-04-06 19:32 ` Dave Taht
2016-04-06 19:42 ` moeller0 [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/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=446473DD-CA62-449D-B963-5F10083F2DA1@gmx.de \
--to=moeller0@gmx.de \
--cc=dave.taht@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