public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Dmitry Tunin <hanipouspilot@gmail.com>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] wireless-regdb: update regulatory rules for Kazakhstan (KZ)
Date: Tue, 29 Oct 2019 09:48:15 -0500	[thread overview]
Message-ID: <20191029144815.GR30813@ubuntu-xps13> (raw)
In-Reply-To: <1567189484-27536-1-git-send-email-hanipouspilot@gmail.com>

On Fri, Aug 30, 2019 at 09:24:44PM +0300, Dmitry Tunin wrote:
> Update according to the regulatory rule of January 21, 2015
> 
> http://egov.kz/cms/ru/law/list/V1500010730
> https://tengrinews.kz/zakon/pravitelstvo_respubliki_kazahstan_premer_ministr_rk/svyaz/id-V1500010730/
> 
> No DFS or TPC is mentioned in the document. Neither is 80 MHz channel width.
> 
> Signed-off-by: Dmitry Tunin <hanipouspilot@gmail.com>

Thanks for the patch. I don't agree with all of your changes though,
please see details below.

> ---
>  db.txt | 14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/db.txt b/db.txt
> index 37393e6..491598e 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -717,13 +717,13 @@ country KY: DFS-FCC
>  	(5735 - 5835 @ 80), (30)
>  
>  # Source:
> -# http://mic.gov.kz/sites/default/files/pages/pravila_prisvoeniya_polos_chastot_no34.pdf
> -# http://adilet.zan.kz/rus/docs/P000001379_
> -country KZ: DFS-ETSI
> -	(2402 - 2482 @ 40), (20)
> -	(5150 - 5250 @ 80), (20), NO-OUTDOOR, AUTO-BW
> -	(5250 - 5350 @ 80), (20), NO-OUTDOOR, DFS, AUTO-BW
> -	(5470 - 5725 @ 80), (20), NO-OUTDOOR, DFS
> +# http://egov.kz/cms/ru/law/list/V1500010730
> +# https://tengrinews.kz/zakon/pravitelstvo_respubliki_kazahstan_premer_ministr_rk/svyaz/id-V1500010730/
> +country KZ:
> +	(2400 - 2483.5 @ 40), (20)
> +	(5150 - 5350 @ 160), (23), NO-OUTDOOR
> +	(5470 - 5850 @ 160), (20), NO-OUTDOOR

The documents you provided reference this document:

https://egov.kz/wps/poc?uri=mjnpa:document&language=ru&documentId=V1500010375#z7

Which says that bands 5150-5350 MHz and 5470-5725 MHz should conform to
WRC-12 resolution 229:

https://www.itu.int/dms_pub/itu-r/opb/act/R-ACT-WRC.9-2012-PDF-E.pdf

This indicates that 5250-5350 MHz and 5470-5725 MHz must either have TPC
or reduce the maximum EIRP by 3 dBm, which for this database means
reducing the maximum power by 3 dBm for these bands. It also states that
these bands must implement the mitigation measures from ITU-R M.1652-1
in these bands, i.e. DFS.

So it appears to me that the existing DFS requirements are correct.
I think 5150-5250 MHz can be raised to 23 dBm, and 5250-5350 MHz needs
to remain at 20 dBm due to the TPC requirement. WRC-12 does mandate TCP
for 5470-5725 MHz, but also a maximum EIRP of 1W, so since 100 mW is far
less than half of that I suspect we can leave that at 20 dBm.

> +	(57000 - 66000 @ 2160), (40), NO-OUTDOOR

This addition looks fine to me.

Thanks,
Seth

>  
>  country LB: DFS-FCC
>  	(2402 - 2482 @ 40), (20)
> -- 
> 2.7.4
> 

  reply	other threads:[~2019-10-29 14:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30 18:24 [PATCH v2] wireless-regdb: update regulatory rules for Kazakhstan (KZ) Dmitry Tunin
2019-10-29 14:48 ` Seth Forshee [this message]
2020-01-27  4:25   ` Seth Forshee
2020-01-27 12:29     ` Dmitry Tunin
2020-02-16 14:36     ` wireless regdb issue Sebastian Gottschall

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=20191029144815.GR30813@ubuntu-xps13 \
    --to=seth.forshee@canonical.com \
    --cc=hanipouspilot@gmail.com \
    --cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox