All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Young <dyoung-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: "Luis R. Rodriguez" <mcgrof-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Radiotap <radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org>,
	Joshua Zhao <Joshua.Zhao-DlyHzToyqoxBDgjK7y7TUQ@public.gmane.org>,
	Matt Smith <Matt.Smith-DlyHzToyqoxBDgjK7y7TUQ@public.gmane.org>,
	Jouni Malinen <j@w1.fi>
Subject: Re: Vendor extensions on radiotap for Atheros
Date: Wed, 26 Aug 2009 14:51:15 -0500	[thread overview]
Message-ID: <20090826195115.GF1260@ojctech.com> (raw)
In-Reply-To: <43e72e890908261052g237dd19cy18baa900721f245a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Wed, Aug 26, 2009 at 10:52:30AM -0700, Luis R. Rodriguez wrote:
> [ resending to the right new e-mail distribution list now ]
> 
> Atheros would like to start using Radiotap vendor extensions [1]. Do
> we just start using our OUI for this, extend the extension info on the
> wiki and perhaps contribute parsing of it to existing parsers?
> 
> Is that the procedure?

Yes, except we haven't adopted vendor extensions as a standard.  Step 1:
propose (and adopt) vendor extensions as a standard.  Step 2: the rest.

> [1] http://www.radiotap.org/Discussion/Vendor-Extensions

I think it is a good description, is it understood by everyone?

I should underscore that for backwards compatibility, an implementation
should not interpret bit 29 or bit 30 as an implicit extension of the
presence-bitmap, but you still have to use bit 31, the presence-bitmap
extension bit, to extend the bitmap.

Dave

-- 
David Young             OJC Technologies
dyoung-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org      Urbana, IL * (217) 278-3933

  parent reply	other threads:[~2009-08-26 19:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26 17:52 Vendor extensions on radiotap for Atheros Luis R. Rodriguez
     [not found] ` <43e72e890908261052g237dd19cy18baa900721f245a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-26 19:51   ` David Young [this message]
     [not found]     ` <20090826195115.GF1260-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
2009-08-26 20:00       ` 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=20090826195115.GF1260@ojctech.com \
    --to=dyoung-e+axbwqsrlaavxtiumwx3w@public.gmane.org \
    --cc=Joshua.Zhao-DlyHzToyqoxBDgjK7y7TUQ@public.gmane.org \
    --cc=Matt.Smith-DlyHzToyqoxBDgjK7y7TUQ@public.gmane.org \
    --cc=j@w1.fi \
    --cc=mcgrof-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.