> -----Original Message----- > From: Luis R. Rodriguez [mailto:mcgrof@xxxxxxxxx] On Behalf Of Luis R. > Rodriguez > Sent: Wednesday, February 19, 2014 18:24 > To: Peer, Ilan > Cc: linux-wireless@xxxxxxxxxxxxxxx > Subject: Re: [PATCH v4 3/5] cfg80211: Enable GO operation on additional > channels > > On Wed, Feb 19, 2014 at 05:39:35PM +0200, Ilan Peer wrote: > > Allow GO operation on a channel marked with > > IEEE80211_CHAN_GO_CONCURRENT iff there is an active station interface > > that is associated to an AP operating on the same channel in the 2 GHz > > band or the same UNII band (in the 5 GHz band). This relaxation is not > > allowed if the channel is marked with IEEE80211_CHAN_RADAR. > > > > Note that this is a permissive approach to the FCC definitions, that > > require a clear assessment that the device operating the AP is an > > authorized master, i.e., with radar detection and DFS capabilities. > > Come to think of it, do we want to make this an FCC specific thing only? If so > then the dfs_region could be checked prior to enablement. The direction is set by the FCC but other regulatory bodies take similar approach. For example see page 27 in this ETSI standard where the same frequency ranges are mentioned (without specifically calling them UNII) and the same concept of channel bundles is defined for testing. http://www.etsi.org/deliver/etsi_en/301800_301899/301893/01.07.01_60/en_301893v010701p.pdf > If the premise is that we'd trust to be associated to a non-GO type AP, that is > a real AP, then we could likely consider a requirement that this real AP would > be using a country IE as well. Please consider this. Not sure that is needed. As I mentioned earlier it is the responsibility of user space to verify that this is not a GO, so it does not really make a difference if it tests for the P2P IEs or the country IE. Regards, Ilan. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
