Search Linux Wireless

RE: [PATCH v4 1/5] cfg80211: Add indoor only and GO concurrent channel attributes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> -----Original Message-----
> From: linux-wireless-owner@xxxxxxxxxxxxxxx [mailto:linux-wireless-
> owner@xxxxxxxxxxxxxxx] On Behalf Of Luis R. Rodriguez
> Sent: Wednesday, February 19, 2014 19:56
> To: Arend van Spriel
> Cc: Peer, Ilan; linux-wireless; Spinadel, David
> Subject: Re: [PATCH v4 1/5] cfg80211: Add indoor only and GO concurrent
> channel attributes
> 

> > So apparently FCC has another understanding than the WiFi Alliance
> > (from section 2.3 in WFA P2P-TS):

I do not think that there is a contradiction here, as the WFA uses the 'may' notation and they are not really addressing regulatory limitations.

> >
> > """
> > A P2P Device can operate concurrently with a WLAN (infrastructure
> > network). Such a device is considered a P2P Concurrent Device. The
> > concurrent operation requires a device to support multiple MAC entities.
> >         :
> >         :
> > A P2P Group may operate in the same or different operating class and
> > channel as a concurrently operating WLAN BSS. For example, a WLAN BSS
> > may operate in channel 36 in the 5.2 GHz band, while the P2P Group may
> > operate in channel 6 in the 2.4 GHz band.
> > """

> 
> But can a WLAN BSS operate on channel 6 in the 2.4 GHz band and infer it can
> start GO on channel 36? This question seems not related to concurrent stuff
> but rather pure regulatory but I suppose that will depend on the definition
> that the FCC intended behind GO concurrency.

No. As mentioned in previously, the UNII bands are bundles of channels which share the same rules, so since channels 6 is not in the same UNII band as channel 36 it is not allowed to instantiate a GO on channel 36 based on the GO concurrent relaxation.

> Is the definition of concurrency GO thing supposed to *restrict* the number
> of interfaces a device can create (STA, GO), or simply define permissive rules
> which would have otherwise been blocked?
> 

The definitions to not limit/restrict the number of concurrent interface but allow permissive rules to allow certain operations which in other circumstances would be blocked. 

Regards,

Ilan.

��.n��������+%������w��{.n�����{���zW����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f





[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux