From: Richard Sharpe <realrichardsharpe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org
Subject: Re: Allocation of new presence bits, eg for HE, etc
Date: Thu, 14 Dec 2017 10:05:23 -0800 [thread overview]
Message-ID: <CACyXjPzQ8Qc6xqwhjUXggASkG8QVTHGad-4E56iUyjyYAk0jjQ@mail.gmail.com> (raw)
In-Reply-To: <CAF7Mx6oZbpHebL7dO-jB0ngCZoqjRO2O=a456QJfQr1PRQ3-vw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, Dec 14, 2017 at 9:55 AM, Arend Van Spriel
<arend.vanspriel-dY08KVG/lbpWk0Htik3J/w@public.gmane.org> wrote:
> Op 14 dec. 2017 18:51 schreef "Arend Van Spriel"
> <arend.vanspriel-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>:
>>
>> Johannes already posted some proposals.
>>
>> See:
>>
>> http://www.radiotap.org/fields/HE
>> http://www.radiotap.org/fields/HE-MU
>> http://www.radiotap.org/fields/HE-MU-other-user
Yes, I noticed those, but no bit assignments have been made. At least
one organization is interested in this.
Is it a case of ANA (Add Next Available?)
It will mean making sure that the tools doing captures add the bits
and that things like Wireshark are backward compatible.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
next prev parent reply other threads:[~2017-12-14 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 17:34 Allocation of new presence bits, eg for HE, etc Richard Sharpe
[not found] ` <CACyXjPwCj1nmGyh-EDHOVn1aT30WEKdEQrRpOTnQqaV7mV0C0Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-14 17:43 ` David Young
[not found] ` <20171214174316.GL12698-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2017-12-14 17:51 ` Arend Van Spriel
[not found] ` <CAF7Mx6pY+zjr9b9iL4B0O2Lqy2-EdvPZ9Uok4DYHN1ns4-GGMQ@mail.gmail.com>
[not found] ` <CAF7Mx6pY+zjr9b9iL4B0O2Lqy2-EdvPZ9Uok4DYHN1ns4-GGMQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-14 17:55 ` Arend Van Spriel
[not found] ` <CAF7Mx6oZbpHebL7dO-jB0ngCZoqjRO2O=a456QJfQr1PRQ3-vw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-14 18:05 ` Richard Sharpe [this message]
[not found] ` <CACyXjPzQ8Qc6xqwhjUXggASkG8QVTHGad-4E56iUyjyYAk0jjQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-15 8:21 ` 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=CACyXjPzQ8Qc6xqwhjUXggASkG8QVTHGad-4E56iUyjyYAk0jjQ@mail.gmail.com \
--to=realrichardsharpe-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=radiotap-sUITvd46vNxg9hUCZPvPmw@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).