RadioTap Archive on lore.kernel.org
 help / color / Atom feed
From: Simon Barber <simon-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
To: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Cc: radiotap-S783fYmB3Ccdnm+yROfE0A@public.gmane.org
Subject: Re: HE (11ax) extensions
Date: Mon, 13 Feb 2017 11:33:27 -0800
Message-ID: <D96F5F50-5B44-487C-8FF8-36A793960B7D@superduper.net> (raw)
In-Reply-To: <1486992211.19813.1.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1958 bytes --]

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

> 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


[-- Attachment #2: Type: text/html, Size: 3073 bytes --]

<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">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&nbsp;<a href="https://code.wireshark.org/review/#/c/20043/" class="">https://code.wireshark.org/review/#/c/20043/</a><div class=""><br class=""></div><div class="">Simon</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 13, 2017, at 5:23 AM, Johannes Berg &lt;<a href="mailto:johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org" class="">johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi,<br class=""><br class="">We're looking to add HE/11ax extensions to radiotap.<br class=""><br class="">Has anyone else already identified the data that would be necessary?<br class=""><br class="">So far I have - assuming 'presence bits' for each,<br class=""><br class="">for HE_SU:<br class=""> * beam change (1 bit)<br class=""> * UL/DL (1 bit)<br class=""> * MCS (4 bits)<br class=""> * DCM (1 bit)<br class=""> * BSS color (6 bits)<br class=""> * spatial reuse (TBD)<br class=""> * bandwidth<br class=""> * GI+LTF size (2 bits)<br class=""> * Nsts<br class=""> * TXOP duration (7 bits)<br class=""> * Coding (BCC/LDPC)<br class=""> * LDPC extra symbol flag<br class=""> * STBC flag<br class=""> * TX BF flag<br class=""> * pre-FEC padding factor<br class=""> * PE disambiguity<br class=""> * doppler mode<br class=""><br class="">for HE_MU:<br class=""> * UL/DL<br class=""> * MCS<br class=""> * DCM<br class=""> * BSS color<br class=""> * spatial reuse<br class=""> * TXOP Duration<br class=""> * bandwidth<br class=""> * # of HE SIGB symbols<br class=""> * SIG-B compression<br class=""> * GI+LTF size<br class=""> * # of HE-LTF symbols<br class=""> * LDPC extra symbol flag<br class=""> * STBC<br class=""> * pre-FEC padding factor<br class=""> * PE disambiguity<br class=""> * doppler mode<br class=""> * RU allocation<br class=""> * center 26 tone RU<br class=""> * per-user: STA-ID, Nsts, TX BF, MCS, DCM, Coding<br class=""><br class="">for HE_TRIG:<br class="">(similar to HE_SU but a little restricted)<br class=""><br class=""><br class="">Obviously a number of these fields are in all three formats, and I<br class="">haven't really done a full size analysis, but perhaps we should split<br class="">the extra MU fields into a separate bit so that they don't have to have<br class="">space allocated to them when not used, for SU/TRIG formats?<br class=""><br class="">johannes<br class=""></div></div></blockquote></div><br class=""></div></body></html>

  parent reply index

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 13:23 Johannes Berg
     [not found] ` <1486992211.19813.1.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-02-13 19:33   ` Simon Barber [this message]
     [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 publically 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=D96F5F50-5B44-487C-8FF8-36A793960B7D@superduper.net \
    --to=simon-vp0mx6+5gkqfx2apin6yfw@public.gmane.org \
    --cc=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

RadioTap Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/radiotap/0 radiotap/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 radiotap radiotap/ https://lore.kernel.org/radiotap \
		radiotap@radiotap.org
	public-inbox-index radiotap

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.netbsd.radiotap


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git