radiotap.netbsd.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: radiotap-S783fYmB3Ccdnm+yROfE0A@public.gmane.org
Subject: HE (11ax) extensions
Date: Mon, 13 Feb 2017 14:23:31 +0100	[thread overview]
Message-ID: <1486992211.19813.1.camel@sipsolutions.net> (raw)

Hi,

We're looking to add HE/11ax extensions to radiotap.

Has anyone else already identified the data that would be necessary?

So far I have - assuming 'presence bits' for each,

for HE_SU:
 * beam change (1 bit)
 * UL/DL (1 bit)
 * MCS (4 bits)
 * DCM (1 bit)
 * BSS color (6 bits)
 * spatial reuse (TBD)
 * bandwidth
 * GI+LTF size (2 bits)
 * Nsts
 * TXOP duration (7 bits)
 * Coding (BCC/LDPC)
 * LDPC extra symbol flag
 * STBC flag
 * TX BF flag
 * pre-FEC padding factor
 * PE disambiguity
 * doppler mode

for HE_MU:
 * UL/DL
 * MCS
 * DCM
 * BSS color
 * spatial reuse
 * TXOP Duration
 * bandwidth
 * # of HE SIGB symbols
 * SIG-B compression
 * GI+LTF size
 * # of HE-LTF symbols
 * LDPC extra symbol flag
 * STBC
 * pre-FEC padding factor
 * PE disambiguity
 * doppler mode
 * RU allocation
 * center 26 tone RU
 * per-user: STA-ID, Nsts, TX BF, MCS, DCM, Coding

for HE_TRIG:
(similar to HE_SU but a little restricted)


Obviously a number of these fields are in all three formats, and I
haven't really done a full size analysis, but perhaps we should split
the extra MU fields into a separate bit so that they don't have to have
space allocated to them when not used, for SU/TRIG formats?

johannes

             reply	other threads:[~2017-02-13 13:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 13:23 Johannes Berg [this message]
     [not found] ` <1486992211.19813.1.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-02-13 19:33   ` HE (11ax) extensions Simon Barber
     [not found]     ` <D96F5F50-5B44-487C-8FF8-36A793960B7D-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2017-02-13 19:39       ` Johannes Berg
     [not found]         ` <1487014748.19813.5.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-02-13 19:42           ` Simon Barber
     [not found]             ` <0FB8C34C-910C-404F-97BA-18BB7F8949C4-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2017-02-13 19:49               ` Johannes Berg
     [not found]                 ` <1487015370.19813.7.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-02-13 20:08                   ` Simon Barber
     [not found]                     ` <4443A151-EFD0-44A4-A892-C40218EE0291-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2017-02-13 20:14                       ` Johannes Berg
2017-02-15  8:58               ` Johannes Berg
2017-02-15  9:08               ` Guy Harris
2017-02-13 19:40       ` Johannes Berg
2017-02-15  9:05       ` Johannes Berg
2017-02-15 12:48   ` Johannes Berg
     [not found]     ` <1487162908.31885.1.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-02-22 11:54       ` Johannes Berg
     [not found]         ` <1487764486.2215.5.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-02-28  7:28           ` Johannes Berg
     [not found]             ` <1488266885.2388.0.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-06-27 13:41               ` Johannes Berg
2017-09-08  8:35   ` Johannes Berg
     [not found]     ` <1504859711.6177.12.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-10-25 11:54       ` Johannes Berg
     [not found]         ` <1508932475.2421.34.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-10-25 12:17           ` Arend Van Spriel
     [not found]             ` <CAF7Mx6qFmbyDex8VOV9sxbMXofQVk9dpzBQNK0S57GCTfbw_PA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-25 12:18               ` Johannes Berg

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=1486992211.19813.1.camel@sipsolutions.net \
    --to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
    --cc=radiotap-S783fYmB3Ccdnm+yROfE0A@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).