RadioTap Archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Richard Sharpe
	<realrichardsharpe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org
Subject: Re: Have new bits been defined for the A-MPDU Status field in the radiotap header for HE?
Date: Thu, 25 Jan 2018 17:15:35 +0100	[thread overview]
Message-ID: <1516896935.2189.2.camel@sipsolutions.net> (raw)
In-Reply-To: <CACyXjPxfD2K_YdHJVU3gm3Ms90gqXV9YnDoQonMviN2y4qXk0Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Thu, 2018-01-25 at 07:14 -0800, Richard Sharpe wrote:
> Hi folks,
> 
> I have a capture that has the value 0x00c0 in the A-MPDU Flags section
> of the A-MPDU status field. These bits are currently listed as
> reserved.
> 
> The HE folks are also saying they need to see an EOF bit to identify
> S-MPDU packets.
> 
> Does anyone know anything about that?

Yeah this probably came from us - I sent a note about it about 10 days
ago, that we were planning to make that addition.

Since I haven't heard anything about that, I think I'll just propose it
as an official part of the standard.

johannes

      parent reply	other threads:[~2018-01-25 16:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 15:14 Have new bits been defined for the A-MPDU Status field in the radiotap header for HE? Richard Sharpe
     [not found] ` <CACyXjPxfD2K_YdHJVU3gm3Ms90gqXV9YnDoQonMviN2y4qXk0Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-25 16:15   ` Johannes Berg [this message]

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=1516896935.2189.2.camel@sipsolutions.net \
    --to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
    --cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org \
    --cc=realrichardsharpe-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 read-only IMAP folder(s) and NNTP newsgroup(s).