All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Chen-Yu Tsai <wens@csie.org>
Cc: Jouni Malinen <jouni@qca.qualcomm.com>,
	wireless-regdb <wireless-regdb@lists.infradead.org>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 1/5] wireless-regdb: Update U-NII-2c (5470 ~ 5725 MHz) rules for Taiwan (TW)
Date: Tue, 4 Aug 2015 08:37:12 -0500	[thread overview]
Message-ID: <20150804133712.GA78399@ubuntu-hedt> (raw)
In-Reply-To: <CAGb2v667QvWzFvrYBWwZU8eGxMHfgh2LmsQUoYziD6UhEuQk3A@mail.gmail.com>

On Tue, Aug 04, 2015 at 09:55:06AM +0800, Chen-Yu Tsai wrote:
> On Tue, Aug 4, 2015 at 9:26 AM, Chen-Yu Tsai <wens@csie.org> wrote:
> > On Tue, Aug 4, 2015 at 2:27 AM, Seth Forshee <seth.forshee@canonical.com> wrote:
> >> On Thu, Jul 23, 2015 at 11:32:56AM +0800, Chen-Yu Tsai wrote:
> >>> Taiwan's Ministry of Transportation and Communications revised its
> >>> frequency allocation rules [1] on 2014/11/17, allowing usage of 5600 ~
> >>> 5650 MHz, previously allocated to weather radars, to U-NII applications
> >>> with DFS support.
> >>>
> >>> Also, the technical regulations [2] show that for 5470 ~ 5725 MHz U-NII
> >>> applications, the peak transmit power shall not exceed the lesser of
> >>> 250 mW (slightly less than 24 dBm) or 11 dBm + 10log B, where B is the
> >>> 26dB emission bandwidth in MHz. This is slightly more than 23 dBm for
> >>> 20 MHz channels.
> >>>
> >>> This patch updates both. Also add links to the two documents into the
> >>> database.
> >>>
> >>> [1] http://www.motc.gov.tw/websitedowndoc?file=post/201411171137330.doc&filedisplay=Table+of+radio+frequency+allocation.doc
> >>> [2] http://www.ncc.gov.tw/english/show_file.aspx?table_name=news&file_sn=681
> >>>
> >>> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> >>
> >> Sorry for the slow response to these patches.
> >>
> >>> ---
> >>>  db.txt | 10 ++++++++--
> >>>  1 file changed, 8 insertions(+), 2 deletions(-)
> >>>
> >>> diff --git a/db.txt b/db.txt
> >>> index 982db34..5114557 100644
> >>> --- a/db.txt
> >>> +++ b/db.txt
> >>> @@ -1118,11 +1118,17 @@ country TT: DFS-FCC
> >>>       (5490 - 5730 @ 160), (24), DFS
> >>>       (5735 - 5835 @ 80), (30)
> >>>
> >>> +# Source:
> >>> +# Table of Frequency Allocations of Republic of China (Taiwan) / Nov 2014:
> >>> +#   http://www.motc.gov.tw/websitedowndoc?file=post/201411171137330.doc& \
> >>> +#      filedisplay=Table+of+radio+frequency+allocation.doc
> >>> +# LP0002 Low-power Radio-frequency Devices Technical Regulations / 28 Jun 2011:
> >>> +#   http://www.ncc.gov.tw/english/show_file.aspx?table_name=news&file_sn=681
> >>> +#   (section 3.10.1, 4.7)
> >>>  country TW: DFS-JP
> >>>       (2402 - 2472 @ 40), (30)
> >>>       (5270 - 5330 @ 40), (17), DFS
> >>> -     (5490 - 5590 @ 80), (30), DFS
> >>> -     (5650 - 5710 @ 40), (30), DFS
> >>> +     (5470 - 5725 @ 160), (23), DFS
> >>
> >> Based on [2], it looks like this range requires TPC, in which case the
> >> power limit should be dropped by 3 dB on account of our not supporting
> >> TPC.
> >
> > Will fix.
> >
> > Is there any plan to support multiple rules per band? Such as different
> > power limits with vs without TPC, or something like DFS vs indoor only?

Not that I know of. Currently the binary database format is a constraint
on doing anything like that.

> BTW, this band has the exact same restrictions as the US, as specified
> by the FCC. The relevant rules were added in
> 
>     f894543 wireless-regdb: Add back regulatory rules for US
> 
> and expanded to cover the whole band in
> 
>     3c61549 wireless-regdb: Update 5GHz rules for US
> 
> These show the power limit at 23 dBm as well. Any comments on this?

Good question. Afaict this probably originates with commit 31dc1c5e
which defines the limit for 5250-5330 MHz in the US, then using the same
limit for the 5490-5730 MHz rule seemed logical. The 5250-5330 MHz rule
came from QCA then. Adding Jouni to the Cc to see if he can help clarify
how they arrived at 23 dBm.

Hmm, I see now that 15.407(h)(1) says that TPC is not required for
systems with an EIRP of less than 500 mW. In that case I guess maybe we
don't need to drop the power limit by 3 dB, so in light of that 23 dBm
does make sense. The documents you linked to say the same, seemingly
word-for-word, so in all likelihood 23 dBm is actually okay.

Thanks,
Seth

WARNING: multiple messages have this Message-ID (diff)
From: Seth Forshee <seth.forshee@canonical.com>
To: Chen-Yu Tsai <wens@csie.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	wireless-regdb <wireless-regdb@lists.infradead.org>,
	Jouni Malinen <jouni@qca.qualcomm.com>
Subject: Re: [wireless-regdb] [PATCH v2 1/5] wireless-regdb: Update U-NII-2c (5470 ~ 5725 MHz) rules for Taiwan (TW)
Date: Tue, 4 Aug 2015 08:37:12 -0500	[thread overview]
Message-ID: <20150804133712.GA78399@ubuntu-hedt> (raw)
In-Reply-To: <CAGb2v667QvWzFvrYBWwZU8eGxMHfgh2LmsQUoYziD6UhEuQk3A@mail.gmail.com>

On Tue, Aug 04, 2015 at 09:55:06AM +0800, Chen-Yu Tsai wrote:
> On Tue, Aug 4, 2015 at 9:26 AM, Chen-Yu Tsai <wens@csie.org> wrote:
> > On Tue, Aug 4, 2015 at 2:27 AM, Seth Forshee <seth.forshee@canonical.com> wrote:
> >> On Thu, Jul 23, 2015 at 11:32:56AM +0800, Chen-Yu Tsai wrote:
> >>> Taiwan's Ministry of Transportation and Communications revised its
> >>> frequency allocation rules [1] on 2014/11/17, allowing usage of 5600 ~
> >>> 5650 MHz, previously allocated to weather radars, to U-NII applications
> >>> with DFS support.
> >>>
> >>> Also, the technical regulations [2] show that for 5470 ~ 5725 MHz U-NII
> >>> applications, the peak transmit power shall not exceed the lesser of
> >>> 250 mW (slightly less than 24 dBm) or 11 dBm + 10log B, where B is the
> >>> 26dB emission bandwidth in MHz. This is slightly more than 23 dBm for
> >>> 20 MHz channels.
> >>>
> >>> This patch updates both. Also add links to the two documents into the
> >>> database.
> >>>
> >>> [1] http://www.motc.gov.tw/websitedowndoc?file=post/201411171137330.doc&filedisplay=Table+of+radio+frequency+allocation.doc
> >>> [2] http://www.ncc.gov.tw/english/show_file.aspx?table_name=news&file_sn=681
> >>>
> >>> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> >>
> >> Sorry for the slow response to these patches.
> >>
> >>> ---
> >>>  db.txt | 10 ++++++++--
> >>>  1 file changed, 8 insertions(+), 2 deletions(-)
> >>>
> >>> diff --git a/db.txt b/db.txt
> >>> index 982db34..5114557 100644
> >>> --- a/db.txt
> >>> +++ b/db.txt
> >>> @@ -1118,11 +1118,17 @@ country TT: DFS-FCC
> >>>       (5490 - 5730 @ 160), (24), DFS
> >>>       (5735 - 5835 @ 80), (30)
> >>>
> >>> +# Source:
> >>> +# Table of Frequency Allocations of Republic of China (Taiwan) / Nov 2014:
> >>> +#   http://www.motc.gov.tw/websitedowndoc?file=post/201411171137330.doc& \
> >>> +#      filedisplay=Table+of+radio+frequency+allocation.doc
> >>> +# LP0002 Low-power Radio-frequency Devices Technical Regulations / 28 Jun 2011:
> >>> +#   http://www.ncc.gov.tw/english/show_file.aspx?table_name=news&file_sn=681
> >>> +#   (section 3.10.1, 4.7)
> >>>  country TW: DFS-JP
> >>>       (2402 - 2472 @ 40), (30)
> >>>       (5270 - 5330 @ 40), (17), DFS
> >>> -     (5490 - 5590 @ 80), (30), DFS
> >>> -     (5650 - 5710 @ 40), (30), DFS
> >>> +     (5470 - 5725 @ 160), (23), DFS
> >>
> >> Based on [2], it looks like this range requires TPC, in which case the
> >> power limit should be dropped by 3 dB on account of our not supporting
> >> TPC.
> >
> > Will fix.
> >
> > Is there any plan to support multiple rules per band? Such as different
> > power limits with vs without TPC, or something like DFS vs indoor only?

Not that I know of. Currently the binary database format is a constraint
on doing anything like that.

> BTW, this band has the exact same restrictions as the US, as specified
> by the FCC. The relevant rules were added in
> 
>     f894543 wireless-regdb: Add back regulatory rules for US
> 
> and expanded to cover the whole band in
> 
>     3c61549 wireless-regdb: Update 5GHz rules for US
> 
> These show the power limit at 23 dBm as well. Any comments on this?

Good question. Afaict this probably originates with commit 31dc1c5e
which defines the limit for 5250-5330 MHz in the US, then using the same
limit for the 5490-5730 MHz rule seemed logical. The 5250-5330 MHz rule
came from QCA then. Adding Jouni to the Cc to see if he can help clarify
how they arrived at 23 dBm.

Hmm, I see now that 15.407(h)(1) says that TPC is not required for
systems with an EIRP of less than 500 mW. In that case I guess maybe we
don't need to drop the power limit by 3 dB, so in light of that 23 dBm
does make sense. The documents you linked to say the same, seemingly
word-for-word, so in all likelihood 23 dBm is actually okay.

Thanks,
Seth

_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb


  reply	other threads:[~2015-08-04 13:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23  3:32 [PATCH v2 0/5] wireless-regdb: Update TW and US rules to latest regulations Chen-Yu Tsai
2015-07-23  3:32 ` [wireless-regdb] " Chen-Yu Tsai
2015-07-23  3:32 ` [PATCH v2 1/5] wireless-regdb: Update U-NII-2c (5470 ~ 5725 MHz) rules for Taiwan (TW) Chen-Yu Tsai
2015-07-23  3:32   ` [wireless-regdb] " Chen-Yu Tsai
2015-08-03 18:27   ` Seth Forshee
2015-08-03 18:27     ` [wireless-regdb] " Seth Forshee
2015-08-04  1:26     ` Chen-Yu Tsai
2015-08-04  1:26       ` [wireless-regdb] " Chen-Yu Tsai
2015-08-04  1:55       ` Chen-Yu Tsai
2015-08-04  1:55         ` [wireless-regdb] " Chen-Yu Tsai
2015-08-04 13:37         ` Seth Forshee [this message]
2015-08-04 13:37           ` Seth Forshee
2015-07-23  3:32 ` [PATCH v2 2/5] wireless-regdb: Update regulatory rule boundary frequencies " Chen-Yu Tsai
2015-07-23  3:32   ` [wireless-regdb] " Chen-Yu Tsai
2015-07-23  3:32 ` [PATCH v2 3/5] wireless-regdb: Add U-NII-1 (5150 ~ 5250 MHz) band " Chen-Yu Tsai
2015-07-23  3:32   ` [wireless-regdb] " Chen-Yu Tsai
2015-08-03 18:40   ` Seth Forshee
2015-08-03 18:40     ` [wireless-regdb] " Seth Forshee
2015-07-23  3:32 ` [PATCH v2 4/5] wireless-regdb: Update 5GHz rules for US Chen-Yu Tsai
2015-07-23  3:32   ` [wireless-regdb] " Chen-Yu Tsai
2015-08-03 18:34   ` Seth Forshee
2015-08-03 18:34     ` [wireless-regdb] " Seth Forshee
2015-08-03 18:47     ` Seth Forshee
2015-08-03 18:47       ` [wireless-regdb] " Seth Forshee
2015-08-04  1:31     ` Chen-Yu Tsai
2015-08-04  1:31       ` [wireless-regdb] " Chen-Yu Tsai
2015-08-04 13:43       ` Seth Forshee
2015-08-04 13:43         ` [wireless-regdb] " Seth Forshee
2015-07-23  3:33 ` [PATCH v2 5/5] wireless-regdb: Update 5 GHz rules for Taiwan (TW) to follow US Chen-Yu Tsai
2015-07-23  3:33   ` [wireless-regdb] " Chen-Yu Tsai

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=20150804133712.GA78399@ubuntu-hedt \
    --to=seth.forshee@canonical.com \
    --cc=jouni@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wens@csie.org \
    --cc=wireless-regdb@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.