From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Barber Subject: Re: HE (11ax) extensions Date: Mon, 13 Feb 2017 11:33:27 -0800 Message-ID: References: <1486992211.19813.1.camel@sipsolutions.net> Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Content-Type: multipart/alternative; boundary="Apple-Mail=_4C08E0A6-4AF3-48B5-830A-99EE01D6E515" Return-path: In-Reply-To: <1486992211.19813.1.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> Sender: radiotap-owner-sUITvd46vNxg9hUCZPvPmw@public.gmane.org To: Johannes Berg Cc: radiotap-S783fYmB3Ccdnm+yROfE0A@public.gmane.org List-Id: radiotap@radiotap.org --Apple-Mail=_4C08E0A6-4AF3-48B5-830A-99EE01D6E515 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 For HT and VHT one of the things that is missing is the total length of = aggregates (including padding) - it=E2=80=99s in the L-SIG header, would = be nice to have it exposed (since most chipsets pass up everything = that=E2=80=99s in the header). I assume the same will be true for ax. = Also some standardized way to put aggregates back together. My latest = wireshark extension uses same TSF as that clue. See = https://code.wireshark.org/review/#/c/20043/ = Simon > On Feb 13, 2017, at 5:23 AM, Johannes Berg = wrote: >=20 > Hi, >=20 > We're looking to add HE/11ax extensions to radiotap. >=20 > Has anyone else already identified the data that would be necessary? >=20 > So far I have - assuming 'presence bits' for each, >=20 > 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 >=20 > 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 >=20 > for HE_TRIG: > (similar to HE_SU but a little restricted) >=20 >=20 > 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? >=20 > johannes --Apple-Mail=_4C08E0A6-4AF3-48B5-830A-99EE01D6E515 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 For HT and VHT one of the things that is missing is the total = length of aggregates (including padding) - it=E2=80=99s in the L-SIG = header, would be nice to have it exposed (since most chipsets pass up = everything that=E2=80=99s in the header). I assume the same will be true = for ax. Also some standardized way to put aggregates back together. My = latest wireshark extension uses same TSF as that clue. See https://code.wireshark.org/review/#/c/20043/

Simon

On Feb 13, 2017, at 5:23 AM, Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> wrote:

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

= --Apple-Mail=_4C08E0A6-4AF3-48B5-830A-99EE01D6E515--