linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Moskowitz <rgm@htt-consult.com>
To: linux-wireless@vger.kernel.org
Subject: SAE support
Date: Fri, 16 Dec 2011 14:38:22 -0500	[thread overview]
Message-ID: <4EEB9E2E.9050004@htt-consult.com> (raw)
In-Reply-To: <S1760568Ab1LPTWy/20111216192254Z+423@vger.kernel.org>

I see in:

http://marc.info/?l=linux-wireless&m=130145440930760&w=2

That SAE support is in for mesh networking.  SAE is so defined that it 
can be used for STA authentication to an AP or in AdHoc mode.  It is NOT 
limited to mesh node authentication.  This was extensively discussed at 
the 802.11 meetings as a reason that specific support of SAE by STAs did 
not need to be defined; it was already in there.

so......

if an AP is advertising SAE in an IE in the BEACON, what will it take 
for the STA to respond?  Does this patch provide the necessary 
functionality?  See sec 8.2a in IEEE 802.11s-2011.

Thank you.



           reply	other threads:[~2011-12-16 19:44 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <S1760568Ab1LPTWy/20111216192254Z+423@vger.kernel.org>]

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=4EEB9E2E.9050004@htt-consult.com \
    --to=rgm@htt-consult.com \
    --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).