RadioTap Archive on lore.kernel.org
 help / color / Atom feed
* Conflicting definitions between the radiotap HE PPDU format field and 802.11axD2
@ 2018-01-25 15:32 Richard Sharpe
       [not found] ` <CACyXjPzSHgyBkpXBR7=eqsfiCmeKBOsQD=0dJtUMwqUk=yWxYQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
  0 siblings, 1 reply; 3+ messages in thread
From: Richard Sharpe @ 2018-01-25 15:32 UTC (permalink / raw)
  To: radiotap-sUITvd46vNxg9hUCZPvPmw

Hi folks,

It seems that 802.11ax D2 defines, in Table 28-18, in HE-SIG-A, a
1-bit format fields (B0) that takes the values 0 for HE TB PPDUs and 1
for HE SU PPDUs and that is reserved for others but must be set to 1.

However, what seems to be the equivalent radiotap he ppdu format field
is 2 bits and uses different values.

Have I misunderstood? What is the resolution of this?

-- 
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Conflicting definitions between the radiotap HE PPDU format field and 802.11axD2
       [not found] ` <CACyXjPzSHgyBkpXBR7=eqsfiCmeKBOsQD=0dJtUMwqUk=yWxYQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2018-01-26 10:42   ` Johannes Berg
       [not found]     ` <1516963320.2189.22.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
  0 siblings, 1 reply; 3+ messages in thread
From: Johannes Berg @ 2018-01-26 10:42 UTC (permalink / raw)
  To: Richard Sharpe, radiotap-sUITvd46vNxg9hUCZPvPmw

Hi Richard,

Sorry, it was too late last night to think clearly about this :-)

> It seems that 802.11ax D2 defines, in Table 28-18, in HE-SIG-A, a
> 1-bit format fields (B0) that takes the values 0 for HE TB PPDUs and 1
> for HE SU PPDUs and that is reserved for others but must be set to 1.

Correct. There are four PPDU types:
 * HE SU PPDU
 * HE ER SU PPDU
 * HE TB PPDU
 * HE MU PPDU

The format bit distinguishes between TB and SU PPDUs. You'll note that
this bit doesn't even exist in an MU PPDU.

The actual differentiation between the four types is done in another
way, I'm not entirely sure right now how, you can see it in 28.3.21, in
particular in Figure 28-59.

Basically what I decided to expose in radiotap is the HE sub-formats as
per the RXVECTOR (and maybe TXVECTOR, if we use it for TX) parameters.

> However, what seems to be the equivalent radiotap he ppdu format field
> is 2 bits and uses different values.
> 
> Have I misunderstood? What is the resolution of this?

Does the above resolve this for you?

johannes

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Conflicting definitions between the radiotap HE PPDU format field and 802.11axD2
       [not found]     ` <1516963320.2189.22.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
@ 2018-01-26 14:50       ` Richard Sharpe
  0 siblings, 0 replies; 3+ messages in thread
From: Richard Sharpe @ 2018-01-26 14:50 UTC (permalink / raw)
  To: Johannes Berg; +Cc: radiotap-sUITvd46vNxg9hUCZPvPmw

On Fri, Jan 26, 2018 at 2:42 AM, Johannes Berg
<johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> wrote:
> Hi Richard,
>
> Sorry, it was too late last night to think clearly about this :-)
>
>> It seems that 802.11ax D2 defines, in Table 28-18, in HE-SIG-A, a
>> 1-bit format fields (B0) that takes the values 0 for HE TB PPDUs and 1
>> for HE SU PPDUs and that is reserved for others but must be set to 1.
>
> Correct. There are four PPDU types:
>  * HE SU PPDU
>  * HE ER SU PPDU
>  * HE TB PPDU
>  * HE MU PPDU
>
> The format bit distinguishes between TB and SU PPDUs. You'll note that
> this bit doesn't even exist in an MU PPDU.
>
> The actual differentiation between the four types is done in another
> way, I'm not entirely sure right now how, you can see it in 28.3.21, in
> particular in Figure 28-59.
>
> Basically what I decided to expose in radiotap is the HE sub-formats as
> per the RXVECTOR (and maybe TXVECTOR, if we use it for TX) parameters.
>
>> However, what seems to be the equivalent radiotap he ppdu format field
>> is 2 bits and uses different values.
>>
>> Have I misunderstood? What is the resolution of this?
>
> Does the above resolve this for you?

I think so. Someone who is involved with the spec also pointed out
that some of those bits are generated based on other criteria.

-- 
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, back to index

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-01-25 15:32 Conflicting definitions between the radiotap HE PPDU format field and 802.11axD2 Richard Sharpe
     [not found] ` <CACyXjPzSHgyBkpXBR7=eqsfiCmeKBOsQD=0dJtUMwqUk=yWxYQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-26 10:42   ` Johannes Berg
     [not found]     ` <1516963320.2189.22.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2018-01-26 14:50       ` Richard Sharpe

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