All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <j@w1.fi>
Cc: Mohammed Shafi <shafi.wireless@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211: reply to directed probes in IBSS
Date: Mon, 14 Feb 2011 13:31:34 +0100	[thread overview]
Message-ID: <1297686694.3785.40.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20110214122818.GA6712@jm.kir.nu>

On Mon, 2011-02-14 at 14:28 +0200, Jouni Malinen wrote:
> On Mon, Feb 14, 2011 at 11:12:37AM +0100, Johannes Berg wrote:
> > The real question though is -- do we want/need this? I can only find
> > reference to this behaviour in the WMM spec.
> 
> Yes, we do want and need it. Peer capability discovery in RSN IBSS
> depends on this (or a potentially long wait on receiving Beacon frame
> from the specific STA). IEEE 802.11REVmb clarifies the rules for IBSS in
> 10.4.4.3.2 which has the following statement on this: "A STA in an IBSS
> shall respond to Probe Request frames sent to the individual address of
> the STA." after the sentence that limits responding to just the STA
> that transmitted the last Beacon frame.

Ok, good. I submitted the patch, maybe I should resubmit with this
information, but I guess it doesn't matter much.

The next question ends up being under which circumstances we should
_send_ a unicast probe request. Currently, I don't think we ever do.

johannes


  reply	other threads:[~2011-02-14 12:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 12:49 [RFC] mac80211: reply to directed probes in IBSS Johannes Berg
2011-02-08 11:11 ` Mohammed Shafi
2011-02-14 10:12   ` Johannes Berg
2011-02-14 10:28     ` Mohammed Shafi
2011-02-14 10:48       ` Mohammed Shafi
2011-02-14 12:28     ` Jouni Malinen
2011-02-14 12:31       ` Johannes Berg [this message]
2011-02-14 13:38         ` Jouni Malinen

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=1297686694.3785.40.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=shafi.wireless@gmail.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 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.