From: Jouni Malinen <j@w1.fi>
To: Avinash Patil <patila@marvell.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Amitkumar Karwar <akarwar@marvell.com>,
Cathy Luo <cluo@marvell.com>, Xinming Hu <huxm@marvell.com>,
Li Long <longli@marvell.com>
Subject: Re: [PATCH 1/3] mwifiex: add cfg80211 set_default_mgmt_key handler
Date: Tue, 31 Mar 2015 17:59:10 +0300 [thread overview]
Message-ID: <20150331145910.GA8244@w1.fi> (raw)
In-Reply-To: <CBACCFA0AEB13A41977475BCF3E896FC689F4C7E9B@SC-VEXCH2.marvell.com>
On Tue, Mar 31, 2015 at 07:33:39AM -0700, Avinash Patil wrote:
> We feel set_default_key_mgmt handler is required for devices which supports 2 pair of GTKs.
Why would a device not support multiple GTKs/IGTKs? It does not sound
possible to implement RSN correctly without such support.. AP side could
kind of try to work with only a single GTK/IGTK, but non-AP STA would
not handle GTK/IGTK rekeying. In any case, IEEE Std 802.11-2012 seems to
be pretty clear on the assumption being that the device (including
AP-only cases) supports multiple GTK/IGTK. The authenticator state
machines use key index values 1 and 2 and swap between these when doing
rekeying.
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2015-03-31 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 18:15 [PATCH 1/3] mwifiex: add cfg80211 set_default_mgmt_key handler Avinash Patil
2015-02-12 18:15 ` [PATCH 2/3] mwifiex: WMM AC parameter configuration for AP mode Avinash Patil
2015-02-12 18:15 ` [PATCH 3/3] mwifiex: add cfg80211 set_mac_acl handler " Avinash Patil
2015-02-13 18:06 ` [PATCH 1/3] mwifiex: add cfg80211 set_default_mgmt_key handler Johannes Berg
2015-02-23 7:47 ` Avinash Patil
2015-03-17 11:25 ` Avinash Patil
2015-03-31 14:33 ` Avinash Patil
2015-03-31 14:59 ` Jouni Malinen [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=20150331145910.GA8244@w1.fi \
--to=j@w1.fi \
--cc=akarwar@marvell.com \
--cc=cluo@marvell.com \
--cc=huxm@marvell.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=longli@marvell.com \
--cc=patila@marvell.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;
as well as URLs for NNTP newsgroup(s).