linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Daniel Halperin <dhalperi@cs.washington.edu>
Cc: linux-wireless@vger.kernel.org
Subject: Re: vendor IEs?
Date: Tue, 21 Dec 2010 20:45:26 +0100	[thread overview]
Message-ID: <1292960726.3563.84.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTimGci-yzhbQwJSjFPGMq0vdQV=4iARb8DUZZZf_@mail.gmail.com>

On Tue, 2010-12-21 at 11:38 -0800, Daniel Halperin wrote:
> On Tue, Dec 21, 2010 at 2:41 AM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > On Sun, 2010-12-19 at 16:53 -0800, Daniel Halperin wrote:
> >> Is there a compiled list of vendor-specific IEs out there?  Googling
> >> didn't offer much help.
> >
> > I'm not aware of any list, nor can there really be one since everybody
> > who has an OUI is free to define their own IEs.
> >
> > That said, some of them are of course mostly standardised, like the WFA
> > ones for WPA, WSC/WPS and P2P for instance. I don't think there's a even
> > a comprehensive list of WFA ones though other than in what you get by
> > combining all those standards.
> 
> On that note, if you wanted to define a custom IE what would you do?

I'd work with a vendor to get to use their OUI :-)

> How did the WFA get an OUI?  Is there a Linux OUI?

http://standards.ieee.org/develop/regauth/oui/index.html

I'm not aware of a Linux OUI.

johannes


      reply	other threads:[~2010-12-21 19:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20  0:53 vendor IEs? Daniel Halperin
2010-12-20 15:44 ` Luis R. Rodriguez
2010-12-20 18:20   ` Daniel Halperin
2010-12-20 19:22     ` Luis R. Rodriguez
2010-12-20 19:25       ` Daniel Halperin
2010-12-21 10:41 ` Johannes Berg
2010-12-21 18:33   ` Henry Ptasinski
2010-12-21 19:38   ` Daniel Halperin
2010-12-21 19:45     ` 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=1292960726.3563.84.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=dhalperi@cs.washington.edu \
    --cc=linux-wireless@vger.kernel.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).