From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: radiotap-S783fYmB3Ccdnm+yROfE0A@public.gmane.org
Cc: Richard Sharpe
<realrichardsharpe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [RFA] HE addition: TB PPDU bandwidth
Date: Mon, 03 Dec 2018 15:14:46 +0100 [thread overview]
Message-ID: <8f56ce73baa72725c01eecef8645595cfea71b2b.camel@sipsolutions.net> (raw)
Trigger-based PPDUs have an additional bandwidth that determines the
spectral mask etc., I forgot those before but now we need to be able to
look at them in a sniffer.
Since we have a few (very few!) reserved bits, change the HE field as
follows:
data 6
0x00e0 (reserved)
to
0x0020 TB PPDU bandwidth known
0x00c0 TB PPDU bandwidth (bits 24/25 from HE-SIG-A1),
0: 20 MHz, 1: 40 MHz, 2: 80 MHz, 3: 160 MHz/80+80 MHz
The existing bandwidth field captures only the bandwidth/RU allocation
of the data, which in this case would be the RU allocation for the
captured transmitter, not the bandwidth of the overall transmission(s).
johannes
reply other threads:[~2018-12-03 14:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f56ce73baa72725c01eecef8645595cfea71b2b.camel@sipsolutions.net \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=radiotap-S783fYmB3Ccdnm+yROfE0A@public.gmane.org \
--cc=realrichardsharpe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).