linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Zefir Kurtisi <zefir.kurtisi@neratec.com>, Wei Zhong <wzhong@google.com>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: wireless-regdb: update CA rules for 5600 - 5650 mHz
Date: Mon, 6 Jul 2015 08:27:07 -0500	[thread overview]
Message-ID: <20150706132707.GA22962@ubuntu-hedt> (raw)
In-Reply-To: <5596A3C0.6020303@neratec.com>

On Fri, Jul 03, 2015 at 05:01:20PM +0200, Zefir Kurtisi wrote:
> On 07/03/2015 04:20 PM, Wei Zhong wrote:
> > On Fri, Jul 3, 2015 at 4:08 AM, Zefir Kurtisi <zefir.kurtisi@neratec.com> wrote:
> >>
> >> On 07/02/2015 07:44 AM, Wei Zhong wrote:
> >>> commit 2fef4cad8a1bd9cbbf178e59a1b3ca672b057095
> >>> Author: Wei Zhong <wzhong@google.com>
> >>> Date:   Wed Jul 1 22:39:09 2015 -0700
> >>>
> >>>     wireless-regdb: update CA rules for 5600 - 5650 mHz
> >>>
> >>>     Related regulation:
> >>>     http://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf10971.html#s6.2.3
> >>>
> >>>     Frequency Bands 5470-5600 MHz and 5650-5725 MHz
> >>>     Until further notice, devices subject to this section [i.e. Wifi device
> >>>     supporting 5 GHz bands] shall not be capable of transmitting in the band
> >>>     5600-5650 MHz. This restriction is for the protection of Environment
> >>>     Canada’s weather radars operating in this band.
> >>>
> >>> diff --git a/db.txt b/db.txt
> >>> index 809cd3c..da0cfad 100644
> >>> --- a/db.txt
> >>> +++ b/db.txt
> >>> @@ -216,7 +216,8 @@ country CA: DFS-FCC
> >>>         (2402 - 2472 @ 40), (30)
> >>>         (5170 - 5250 @ 80), (17), AUTO-BW
> >>>         (5250 - 5330 @ 80), (24), DFS, AUTO-BW
> >>> -       (5490 - 5730 @ 160), (24), DFS
> >>> +       (5490 - 5600 @ 80), (24), DFS
> >>> +       (5650 - 5730 @ 40), (24), DFS
> >>>         (5735 - 5835 @ 80), (30)
> >>>
> >>>  # Source:
> >>> --
> >>
> >> I believe this could also be interpreted differently. If the change is only about
> >> removing the weather radar band (5600-5650), the change should be
> >>
> >>  -       (5490 - 5730 @ 160), (24), DFS
> >>  +       (5490 - 5570 @ 80), (24), DFS
> >>  +       (5570 - 5590 @ 20), (24), DFS
> >>  +       (5650 - 5730 @ 80), (24), DFS
> >>
> >> The second rule explicitly states that channel 116 remains available for HT20. If
> >> this level of strict correctness is not needed, rule 1 and 2 combined would be
> >>
> >>  -       (5490 - 5730 @ 160), (24), DFS
> >>  +       (5490 - 5590 @ 80), (24), DFS
> > 
> > I agree. 5590 is more strict than 5600.
> > 
> >>
> >>  +       (5650 - 5730 @ 80), (24), DFS
> > 
> > 5690 MHz is not a channel can be used, is it still necessary to mark
> > this band as 80MHz while in practice it is not possible to fully
> > unitize the entire band?
> > 
> 
> I must be missing something here, where does the restriction for 5690 come from?
> The document handles the band 5650-5725 as available, I don't see any further
> restrictions for 5690.

I've only looked briefly at the relevant documents, but I also am not
seeing where this restriction comes from. The regulatory document linked
to in the patch description doesn't seem to restrict it, nor does
anything I see in the discussion of VHT80 center frequencies in IEEE
802.11 (in fact channel 138 is explicitly listed as a possible VHT80
center frequency index in some of the tables).

> From your other post:
> >>     >
> >>     >  -       (5490 - 5730 @ 160), (24), DFS
> >>     >  +       (5490 - 5590 @ 80), (24), DFS
> >> 
> >>     I agree. 5590 is more strict than 5600.
> >> 
> >>  
> >> On a second thought,  5590 implies channel 116 can't have 40MHz. I think that is
> >> still allowed per regulation.
> >> 
> >> 
> 
> No, channel 116 is not usable for HT40 if weather radar channels are disabled,
> since it can only be combined with channel 120 and that one partially falls into
> the restricted range.

It's not necessary to restrict the band down to 5590 or break out the
rule for channel 116 separately, the software is smart enough to work
out what's allowed based on the original rule Wei supplied for 5490-5600
MHz. In fact that rule exactly matches what we used to have in db.txt
for the US prior to the TDWR restrictions being lifted.

Seth

  reply	other threads:[~2015-07-06 13:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02  5:44 wireless-regdb: update CA rules for 5600 - 5650 mHz Wei Zhong
2015-07-02 13:48 ` Seth Forshee
2015-07-02 14:21   ` Wei Zhong
2015-07-02 14:31     ` Seth Forshee
2015-07-03 11:08 ` Zefir Kurtisi
2015-07-03 14:20   ` Wei Zhong
2015-07-03 15:01     ` Zefir Kurtisi
2015-07-06 13:27       ` Seth Forshee [this message]
2015-07-06 14:40         ` Zefir Kurtisi
2015-07-06 17:13           ` Wei Zhong
2015-07-07 20:11           ` Seth Forshee
2015-07-08 10:19             ` Zefir Kurtisi
2015-07-09 14:04               ` Seth Forshee

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=20150706132707.GA22962@ubuntu-hedt \
    --to=seth.forshee@canonical.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wireless-regdb@lists.infradead.org \
    --cc=wzhong@google.com \
    --cc=zefir.kurtisi@neratec.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).