HE (11ax) extensions
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
A message that is not in the archive (sent off-list or not yet received): [email protected]
For HT and VHT one of the things that is missing is the total length of aggregates (including padding) - it’s in the L-SIG header, would be nice to have it exposed (since most chipsets pass up everything that’s 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/ <https://code.wireshark.org/review/#/c/20043/>
Simon
Quoted 60 lines · Johannes Berg
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 modefor
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, Codingfor
HE_TRIG:
(similar toHE_SUbut 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
A message that is not in the archive (sent off-list or not yet received): D96F5F50-5B44-487C-8FF8-36A793960B7D-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org
Quoted 4 lines · Simon Barber
For HT and VHT one of the things that is missing is the total length of aggregates (including padding) - it’s in the L-SIG header, would be nice to have it exposed (since most chipsets pass up everything that’s in the header).
I don't know about "most", but I know ours doesn't :-)
Quoted 3 lines
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/
We already have that, in the A-MPDU status field there's a reference number that's supposed to be constant within the same A-MPDU and change between consecutive A-MPDUs.
johannes
A message that is not in the archive (sent off-list or not yet received): [email protected]
It’s not correctly implemented on captures from Macs - it increments for every MPDU. TSF is reliable on all platforms that I’ve seen, although has different reference points for different platforms.
One things that is very odd is the different parameters for MU - 4 sets, but I’ve only ever seen 1 MPDU reported. How is this supposed to be used?
Simon
Quoted 19 lines · Johannes Berg
Quoted 4 lines · Simon Barber
For HT and VHT one of the things that is missing is the total length of aggregates (including padding) - it’s in the L-SIG header, would be nice to have it exposed (since most chipsets pass up everything that’s in the header).
I don't know about "most", but I know ours doesn't :-)
Quoted 3 lines
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/We already have that, in the A-MPDU status field there's a reference number that's supposed to be constant within the same A-MPDU and change between consecutive A-MPDUs.
johannes
A message that is not in the archive (sent off-list or not yet received): 0FB8C34C-910C-404F-97BA-18BB7F8949C4-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org
Quoted 7 lines · Simon Barber
It’s not correctly implemented on captures from Macs - it increments for every MPDU. TSF is reliable on all platforms that I’ve seen, although has different reference points for different platforms.
One things that is very odd is the different parameters for MU - 4 sets, but I’ve only ever seen 1 MPDU reported. How is this supposed to be used?
I don't think it *can* be used by a real sniffer, unless it is somehow able to decode for multiple users at once?
johannes
A message that is not in the archive (sent off-list or not yet received): [email protected]
And even then, where would the multiple MPDUs go, and how would they be delimited? If this option is unused, and unusable, and it causes big issues with UI, then could it be deprecated? (say only the first set of parameters are valid, all others are unused?)
Simon
Quoted 15 lines · Johannes Berg
Quoted 7 lines · Simon Barber
It’s not correctly implemented on captures from Macs - it increments for every MPDU. TSF is reliable on all platforms that I’ve seen, although has different reference points for different platforms.
One things that is very odd is the different parameters for MU - 4 sets, but I’ve only ever seen 1 MPDU reported. How is this supposed to be used?
I don't think it *can* be used by a real sniffer, unless it is somehow able to decode for multiple users at once?
johannes
A message that is not in the archive (sent off-list or not yet received): 4443A151-EFD0-44A4-A892-C40218EE0291-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org
Quoted 2 lines · Simon Barber
And even then, where would the multiple MPDUs go, and how would they be delimited?
That's a good point. Perhaps it was intended to convey some sort of half-decoding? I frankly don't remember any discussions about this.
Quoted 3 lines
If this option is unused, and unusable, and it causes big issues with UI, then could it be deprecated? (say only the first set of parameters are valid, all others are unused?)
Does it cause problems in any UI? wireshark just displays all the fields, so it shouldn't really cause any problems.
Anyway, this has certainly never been generated on Linux, and probably not elsewhere, so I have no objection to deprecating it and marking those fields reserved or so.
johannes
Quoted 3 lines · Simon Barber
It’s not correctly implemented on captures from Macs - it increments for every MPDU. TSF is reliable on all platforms that I’ve seen, although has different reference points for different platforms.
On this point, btw, you should probably just tell somebody to fix it :)
We can add all the standard ways we want to, but if people don't use them correctly there's not much we can do about it. I don't want to add yet another standard way to do this, just to have the next guy use it wrong ...
johannes
Quoted 1 line · Simon Barber
It’s not correctly implemented on captures from Macs - it increments for every MPDU.
bugreport.apple.com is your friend (well, it'll be all of our friends again once they fix the damn redirect loop). You'll need to get an Apple developer account in order to file bugs. (Note: the more duplicates a bug has, the more attention is paid to it.)
The spec says
The reference number is generated by the capture device and is the same across each subframe of an A-MPDU. Since the capture device might be capable of capturing multiple channels or data from multiple (concurrent) captures could be merged, the reference number is not guaranteed to be unique across different channels. As a result, applications should use the channel information together with the reference number to identify the subframes belonging to the same A-MPDU.
So are you saying that it increments for each *subframe* in macOS?
Quoted 2 lines · Simon Barber
For HT and VHT one of the things that is missing is the total length of aggregates (including padding) - it’s in the L-SIG header
It is, btw, very tempting to define fields for the various headers like L-SIG, SIG-A, SIG-B etc, but most chipsets won't be able to report everything there so we'd have to support masks, and we generally don't support anything with variable length.
johannes
Quoted 4 lines · Simon Barber
For HT and VHT one of the things that is missing is the total length of aggregates (including padding) - it’s in the L-SIG header, would be nice to have it exposed (since most chipsets pass up everything that’s in the header).
Come to think of this - that really should have been part of the A-MPDU field, but I don't think it makes sense to put it into an HE extension either, so it'd probably be better as a separate field.
johannes
Quoted 3 lines · Johannes Berg
Hi,
We're looking to add HE/11ax extensions to radiotap.
I looked more, and decided that it didn't really make a lot of sense to parse it all and put it back together ... so instead, how about we just put SIG-A1/A2/B common/B multiuser in?
Something like
http://www.radiotap.org/fields/HE
but I'm not really sure
* if sig_B_user[1] should be in HE or in HE multiuser
* if 3 bits are really needed for the Center 26-tone RU field, I'm not sure how it could be non-present
Does this make sense?
johannes
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 8 lines
Something like
http://www.radiotap.org/fields/HE
but I'm not really sure
* if sig_B_user[1] should be in HE or in HE multiuser
* if 3 bits are really needed for the Center 26-tone RU field, I'm not sure how it could be non-present
It really can be non-present, obviously SIG-B common field is already variable length :)
Anyway, that proposal missed a number of things and didn't really make any sense, here's a new one:
http://www.radiotap.org/fields/HE
http://www.radiotap.org/fields/HE-MU-common
http://www.radiotap.org/fields/HE-MU-user
One thing I like less about this is that the bitrate of the MPDU will be recorded in the "HE" field for SU/trigger-based PPDUs, but in the "HE-MU-user" field for MU PPDUs. But since all the data is present, I guess that's actually fine.
johannes
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · Johannes Berg
Quoted 1 line
Anyway, that proposal missed a number of things and didn't really make any sense, here's a new one:
http://www.radiotap.org/fields/HE
http://www.radiotap.org/fields/HE-MU-common
http://www.radiotap.org/fields/HE-MU-user
FWIW, I've not pursued this further for now since the spec is still a moving target. I'm told HE-SIG-B is fairly stable, but HE-SIG-A is still a heavily contended topic (at least some parts of it)
johannes
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 6 lines · Johannes Berg
Quoted 5 lines · Johannes Berg
Quoted 1 line
Anyway, that proposal missed a number of things and didn't really make any sense, here's a new one:
Quoted 7 lines
Quoted 3 lines
http://www.radiotap.org/fields/HE
http://www.radiotap.org/fields/HE-MU-common
http://www.radiotap.org/fields/HE-MU-userFWIW, I've not pursued this further for now since the spec is still a moving target. I'm told HE-SIG-B is fairly stable, but HE-SIG-A is still a heavily contended topic (at least some parts of it)
In the meantime, I've come to the conclusion that it's a stupid idea to encode the data like in HE-SIG-A, for multiple reasons:
1) the encoding heavily depends on the PPDU type (SU, ER SU, MU, TB), and there's practically nothing common between them - this means decoding has lots of special cases
2) the encoding is really really tight on bits, doing tricks like DCM=STBC=1 to indicate a 5th possibility for the 2-bit LTF+GI field, this also makes it awkward to decode again in tools like wireshark
3) TB PPDUs don't even contain the necessary rate data, it's given by the trigger frame, so one would have to correlate that during encoding. For pure sniffer mode, that may be necessary, but for some "monitor while operating" modes, the real rate etc. would be available
(and there are probably more reasons)
I'm going on sabbatical soon, but I'll revisit this in September or later to come up with a better proposal.
johannes
Hi all,
I've updated my HE proposal:
http://www.radiotap.org/fields/HE
http://www.radiotap.org/fields/HE-MU
http://www.radiotap.org/fields/HE-MU-user
This now basically just requires the HE field even for MU transmissions, with the HE-MU field giving some more detail of those; the HE-MU-user is just for completeness so one can capture the SIG-B for multiple users even if the frame isn't captured.
I'll still wait for the spec to settle down more until formally proposing this, but feedback is very welcome.
johannes
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · Johannes Berg
Hi all,
I've updated my HE proposal:
http://www.radiotap.org/fields/HE
http://www.radiotap.org/fields/HE-MU
http://www.radiotap.org/fields/HE-MU-user
And again, for D2.0
johannes
A message that is not in the archive (sent off-list or not yet received): [email protected]
Op 25 okt. 2017 13:54 schreef "Johannes Berg" <[email protected]>:
Quoted 9 lines · Johannes Berg
Quoted 7 lines
Hi all,
I've updated my HE proposal:
http://www.radiotap.org/fields/HE
http://www.radiotap.org/fields/HE-MU
http://www.radiotap.org/fields/HE-MU-user
The last link doesn't work (for me?).
Regards,
Arend
Quoted 3 lines
And again, for D2.0
johannes
A message that is not in the archive (sent off-list or not yet received): CAF7Mx6qFmbyDex8VOV9sxbMXofQVk9dpzBQNK0S57GCTfbw_PA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org
Quoted 11 lines · Arend Van Spriel
Op 25 okt. 2017 13:54 schreef "Johannes Berg" <[email protected]>:
Quoted 9 lines · Johannes Berg
Quoted 7 lines
Hi all,
I've updated my HE proposal:
http://www.radiotap.org/fields/HE
http://www.radiotap.org/fields/HE-MU
http://www.radiotap.org/fields/HE-MU-userThe last link doesn't work (for me?).
Indeed, it should be
http://www.radiotap.org/fields/HE-MU-other-user
I also notice that github hasn't updated the HE page with the data6 part of the field yet.
johannes