radiotap.netbsd.org archive mirror
 help / color / mirror / Atom feed
From: Ray Wang <rwang-+OaQ/Okkt+3YtjvyW6yDsg@public.gmane.org>
To: "yodazhong-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
	<yodazhong-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	'Richard Sharpe'
	<realrichardsharpe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	'Johannes Berg'
	<johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Cc: "radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org"
	<radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org>,
	Tasheng Lin <tlin-+OaQ/Okkt+3YtjvyW6yDsg@public.gmane.org>
Subject: RE: Proposal for an S1G header for radiotap
Date: Fri, 1 Feb 2019 23:04:41 +0000	[thread overview]
Message-ID: <CY1PR07MB27160AEE154215058A2CA4F2FF920@CY1PR07MB2716.namprd07.prod.outlook.com> (raw)
In-Reply-To: <01da01d4ba7a$08824ac0$1986e040$@gmail.com>

Hi Johannes and Richard,

As to Aggregation related to A-MPDU, from 802.11ah -2016 spec it can be seen the field is defined in SIG-2 of SIG field of S1G_SHORT preamble, SIG-A2 of SIG-A field of S1G_LONG preamble, and SIG-2 of SIG field of S1G_1M preamble.

If looking at 802.11-2016 and Draft P802.11ax_D3.3 specs, the same field is defined only in HT-SIG, but not in VHT-SIG-A and VHT-SIG-B, and not in HE-SIG-A.

From the spec perspective regarding the Aggregation field, 802.11ah is different from 802.11n/ac/ax.

As you pointed out, Richard, if the existing field can be reused it might need some changes. If defining a new one, the existing one probably also needs to be handled. 

What would you suggest is the best way to tackle it?


Thanks,
Ray


-----Original Message-----
From: yodazhong@gmail.com [mailto:yodazhong@gmail.com] 
Sent: Friday, February 01, 2019 2:04 PM
To: 'Richard Sharpe' <realrichardsharpe@gmail.com>; 'Johannes Berg' <johannes@sipsolutions.net>
Cc: radiotap@radiotap.org; Ray Wang <rwang@wi-fi.org>; Tasheng Lin <tlin@wi-fi.org>
Subject: RE: Proposal for an S1G header for radiotap

Hi Johannes and Richard,

Thank you for your work and great comments.

For the S-MPDU issue, S-MPDU is same as VHT single MPDU in 802.11ac.
If there's pre-defined field for VHT single MPDU, we could use that.

For the S1G NDP issue, I found that there's PHDR_802_11_SOUNDING_PSDU for "0-length PSDU" field. That sounding PSDU means NDP sounding frame, I guess.
So I think we could add S1G NDP frames under "0-length PSDU" field.

--
Best,
Aaron J. Lee

-----Original Message-----
From: Richard Sharpe <realrichardsharpe@gmail.com>
Sent: Friday, February 1, 2019 10:35 AM
To: Johannes Berg <johannes@sipsolutions.net>
Cc: radiotap@radiotap.org; Aaron J. Lee <yodazhong@gmail.com>; Ray Wang <rwang@wi-fi.org>; tlin@wi-fi.org
Subject: Re: Proposal for an S1G header for radiotap

On Fri, Feb 1, 2019 at 3:33 AM Johannes Berg <johannes@sipsolutions.net> wrote:
>
> Hi Richard,
>
> > Attached is a git format-patch patch that contains a proposal for an S1G header.
> >
> > This proposal was created by Aaron Lee and underwent a couple of 
> > rounds of modifications among the WFA folks.
> >
> > All I have done here is to transcribe it to the format required by 
> > the documentation web site. Hopefully I have not changed any intent.
>
> Thanks for doing this! :)
>
> > Below is some feedback from Johannes about the proposal so he does 
> > not have to retype it along with some comments from me.
>
> :-)
>
> Some *additional* feedback below - please do check my previous note 
> about aggregation handling, this is very unclear to me.

I will look at the other comments separately, but I think Aggegration relates to A-MPDU if I am reading section 9.7 of 802.11ah-2016 correctly.

In which case, we already have an A-MPDU header but we might need some changes. Perhaps the WFA folks or Aaron can comment on this/

--
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)(传说杜康是酒的发明者)


  reply	other threads:[~2019-02-01 23:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01  0:02 Proposal for an S1G header for radiotap Richard Sharpe
     [not found] ` <CACyXjPwCydx6fumWdXdLvg-StsRcALBLc5+4fCsGDaC7tcZXCQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-02-01 11:33   ` Johannes Berg
     [not found]     ` <8d1bb1c53c670e7cfddfc0cf2f5e2447b2ee2ecb.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2019-02-01 18:35       ` Richard Sharpe
     [not found]         ` <CACyXjPzc--Deaecx9HuV5i0jyO5uUKFOqEeUaWWv3oYXqBqc8g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-02-01 22:03           ` yodazhong-Re5JQEeQqe8AvxtiuMwx3w
2019-02-01 23:04             ` Ray Wang [this message]
     [not found]               ` <CY1PR07MB27160AEE154215058A2CA4F2FF920-p80jK0/XGTb2cgXex6xO0uFPX92sqiQdvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2019-02-05  9:55                 ` Johannes Berg
     [not found]                   ` <885a63e846a5c08b111601dfd25bf352c3763538.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2019-02-05 19:19                     ` Ray Wang
2019-02-05  9:17             ` 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=CY1PR07MB27160AEE154215058A2CA4F2FF920@CY1PR07MB2716.namprd07.prod.outlook.com \
    --to=rwang-+oaq/okkt+3ytjvyw6ydsg@public.gmane.org \
    --cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
    --cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org \
    --cc=realrichardsharpe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=tlin-+OaQ/Okkt+3YtjvyW6yDsg@public.gmane.org \
    --cc=yodazhong-Re5JQEeQqe8AvxtiuMwx3w@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).