From: Seth Forshee <seth.forshee@canonical.com>
To: Pavel Starosek <starosekpd@gmail.com>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: wireless-regdb: Update regulatory rules for Kazakhstan (KZ)
Date: Tue, 10 Nov 2020 15:40:18 -0600 [thread overview]
Message-ID: <20201110214018.GM6125@ubuntu-x1> (raw)
In-Reply-To: <CAPgWZqx-bHc5iEn-fWbzarrUNB5kbMnay_Pr5BKROznOAO0nWQ@mail.gmail.com>
On Mon, Nov 09, 2020 at 03:19:01AM +0600, Pavel Starosek wrote:
> Updates, based on [1] (search for word "RLAN" to jump to the desired
> part on the page):
Thanks for the updates. I think there are some questions though be
answered in the documents you linked to. I find that tables like these
often have incomplete information. Sometimes they refer to other
documents, but I'm not seeing any such references here. I've tried to
find more complete documents, but I haven't had any luck.
Overall these look okay, but if you are able to find any additional
information to clarify some of these points it would be helpful.
> * Extended range 2400-2483.5
> * 5150–5250 MHz range may be up to 200 mW
> * The same is about 5250 - 5350 MHz according to our local
> regulations, but looks like this is incorrect because of TPC?
> Therefore, I didn't change this value
It would be nice to know for sure, but without any additional
information keeping it at 20 dBm is the safe bet. Many countries do
require TPC in this range.
> * Add 5725-5850 MHz range for indoor usage
Here it would be nice to know if there are any additional restrictions
on use, e.g. TPC or DFS. That appears to be rare though, so it seems
unlikely.
> * Add 57-66 GHz range. It must be outdoors only, so we don't specify
> NO-OUTDOOR at all, right?
That is generally the case for this range. What you suggest looks fine.
> * In 5470-5725 changed the bandwidth from 80 to 160 (typo?)
Probably not a typo, if 160 MHz channels are allowed the entry probably
just hasn't been updated. But those documents don't really state whether
or not they are allowed.
> As I understand it, there is no DFS requirement for the 5725-5850
> range anywhere in the [2] document.
I don't it documenting any DFS requirement at all though, and severaly
entries in the db have a DFS requirement, so I'm not sure that really
clears up the question. I'm reading a translation of the document
though, so maybe I'm just not finding them.
Let me know if you're able to find any more information to clear up
these questions. Are you able to send the changes as a patch? If you
don't know how, that's fine, I can create a patch.
Thanks,
Seth
>
> I can suggest this change. Please check if everything is correct?
> ---
> # [1] http://adilet.zan.kz/rus/docs/V1500010730
> # [2] http://adilet.zan.kz/rus/docs/V1500010375
> country KZ: DFS-ETSI
> (2400 - 2483.5 @ 40), (20)
> (5150 - 5250 @ 80), (23), NO-OUTDOOR, AUTO-BW
> (5250 - 5350 @ 80), (20), NO-OUTDOOR, DFS, AUTO-BW
> (5470 - 5725 @ 160), (20), NO-OUTDOOR, DFS
> (5725 - 5850 @ 80), (20), NO-OUTDOOR
> (57000 - 66000 @ 2160), (40)
>
> ---
> Thanks,
> Pavel
>
>
> On Mon, Nov 9, 2020 at 3:16 AM Pavel Starosek <starosekpd@gmail.com> wrote:
> >
> > Updates, based on [1] (search for word "RLAN" to jump to the desired part on the page):
> >
> > * Extended range 2400-2483.5
> > * 5150–5250 MHz range may be up to 200 mW
> > * The same is about 5250 - 5350 MHz according to our local regulations, but looks like this is incorrect because of TPC? Therefore, I didn't change this value
> > * Add 5725-5850 MHz range for indoor usage
> > * Add 57-66 GHz range. It must be outdoors only, so we don't specify NO-OUTDOOR at all, right?
> > * In 5470-5725 changed the bandwidth from 80 to 160 (typo?)
> > As I understand it, there is no DFS requirement for the 5725-5850 range anywhere in the [2] document.
> >
> > I can suggest this change. Please check if everything is correct?
> > ---
> > # [1] http://adilet.zan.kz/rus/docs/V1500010730
> > # [2] http://adilet.zan.kz/rus/docs/V1500010375
> > country KZ: DFS-ETSI
> > (2400 - 2483.5 @ 40), (20)
> > (5150 - 5250 @ 80), (23), NO-OUTDOOR, AUTO-BW
> > (5250 - 5350 @ 80), (20), NO-OUTDOOR, DFS, AUTO-BW
> > (5470 - 5725 @ 160), (20), NO-OUTDOOR, DFS
> > (5725 - 5850 @ 80), (20), NO-OUTDOOR
> > (57000 - 66000 @ 2160), (40)
> >
> > ---
> > Thanks,
> > Pavel
> >
next prev parent reply other threads:[~2020-11-10 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPgWZqzskMUOnmdBwh6TEh5yfrbdzg+4bZOUMQPkJffWizZweg@mail.gmail.com>
2020-11-08 21:19 ` wireless-regdb: Update regulatory rules for Kazakhstan (KZ) Pavel Starosek
2020-11-10 21:40 ` Seth Forshee [this message]
2020-11-11 18:36 ` Pavel Starosek
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=20201110214018.GM6125@ubuntu-x1 \
--to=seth.forshee@canonical.com \
--cc=linux-wireless@vger.kernel.org \
--cc=starosekpd@gmail.com \
--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