public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <j@w1.fi>
Cc: Jouni Malinen <jouni.malinen@atheros.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] cfg80211/mac80211: Add TX/RX commands for Action frames
Date: Wed, 13 Jan 2010 15:53:12 +0100	[thread overview]
Message-ID: <1263394392.5515.272.camel@johannes.local> (raw)
In-Reply-To: <20100113113000.GA20835@jm.kir.nu>

[-- Attachment #1: Type: text/plain, Size: 716 bytes --]

On Wed, 2010-01-13 at 13:30 +0200, Jouni Malinen wrote:

> Assuming the later change in mac80211 is to start rejecting Action
> frames for which there is no known internal handler or register user
> space handler, the applications using this without the new
> registration mechanism would indeed need to be updated.

But we definitely want that, and it's trivial, so why not actually start
rejecting unknown frames?

<snip extensibility discussion>

So which ones do we need now? Could we start with code to reject unkonwn
ones, registering what we currently need (since there's a reason you
wrote this patch), and then extend as it becomes necessary, for instance
for vendor frames etc?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2010-01-13 14:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 10:11 [PATCH] cfg80211/mac80211: Add TX/RX commands for Action frames Jouni Malinen
2010-01-13 10:19 ` Johannes Berg
2010-01-13 11:30   ` Jouni Malinen
2010-01-13 14:53     ` Johannes Berg [this message]
2010-01-16 21:06     ` 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=1263394392.5515.272.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=j@w1.fi \
    --cc=jouni.malinen@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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