From: Jouni Malinen <jouni@qca.qualcomm.com>
To: Peng Xu <pxu@qti.qualcomm.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Sara Sharon" <sara.sharon@intel.com>
Subject: Re: [RFC] cfg80211: Implement Multiple BSSID capability in scanning
Date: Tue, 14 Nov 2017 16:31:34 +0000 [thread overview]
Message-ID: <20171114163127.GA24453@jouni.qca.qualcomm.com> (raw)
In-Reply-To: <e540b35f76a447cab35f7267c09ee8f5@NASANEXM01F.na.qualcomm.com>
On Tue, Nov 14, 2017 at 02:39:31PM +0000, Peng Xu wrote:
> > I'm not even sure why this is necessary anyway though, do we really thi=
nk
> > vendors will expect to be able to put vendor IEs inside the subelements=
and
> > override the ones outside?
> >=20
> > Is there even any point for the WFA ones? It seems WMM really ought to =
be
> > the same for all anyway, for example.
>=20
> I don't have any use case for such scenario. If vendor elements are unlik=
ely to
> be present in subelement, this logic can be removed.
As far as WMM element is concerned, I'd note that IEEE 802.11 standard
does not list EDCA Parameter Set element as one of the items that has to
be same for all the BSSs in a multiple BSSID set and as such, I'd
consider it to be allowed behavior for an AP to advertise different WMM
parameters for different nontransmitted BSSIDs.
As far as other vendor specific elements are concerned, there could
certainly be use cases for using different values for WPA element,
Hotspot 2.0 element, MBO/OCE element.
--=20
Jouni Malinen PGP id EFC895FA=
next prev parent reply other threads:[~2017-11-14 16:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 16:39 [RFC] cfg80211: Implement Multiple BSSID capability in scanning Jouni Malinen
2017-11-13 10:07 ` Johannes Berg
2017-11-14 12:58 ` Johannes Berg
2017-11-14 14:20 ` Peng Xu
2017-11-14 14:23 ` Johannes Berg
2017-11-14 14:29 ` Peng Xu
2017-11-14 14:33 ` Johannes Berg
2017-11-14 14:39 ` Peng Xu
2017-11-14 16:31 ` Jouni Malinen [this message]
2017-11-14 17:38 ` Peng Xu
2017-11-27 12:03 ` Johannes Berg
2017-11-27 19:14 ` Peng Xu
2017-11-27 21:46 ` 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=20171114163127.GA24453@jouni.qca.qualcomm.com \
--to=jouni@qca.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pxu@qti.qualcomm.com \
--cc=sara.sharon@intel.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).