public inbox for wireless-regdb@lists.infradead.org
 help / color / mirror / Atom feed
From: Seth Forshee <sforshee@kernel.org>
To: "tavio.wong" <tavio.wong@proton.me>
Cc: "wireless-regdb@lists.infradead.org"
	<wireless-regdb@lists.infradead.org>
Subject: Re: [wireless-regdb] wireless-regdb: Regulatory rules for Hong Kong (HK)
Date: Tue, 21 Mar 2023 12:12:29 -0500	[thread overview]
Message-ID: <ZBnlfZXMxxhfxOSD@do-x1extreme> (raw)
In-Reply-To: <oiVeDD95tMcpWN4ynhZfWbX0idjaGq3ibft2obzq-RSMVptQ3TncwBf_kcekWctED_IGNRx3BmIACchzsrEcSwH1tcfr3jMRP2S1egcTCpY=@proton.me>

On Wed, Mar 15, 2023 at 02:37:16PM +0000, tavio.wong wrote:
> Hello,
> 
> According to section 2.1(b) of [1], the allowed peak output power in different bands is higher than currently defined in db.txt. I see that the rules for HK have not been updated since 2014. Since I don't understand sections 2.2 and 2.3, is there any reason for limiting the output power other than that the information is outdated?
> 
> If not, I propose the rules for HK be updated as follows [section 2.1(a) also requires that 5.15-5.35 GHz be restricted to indoor use]:

Thanks for the proposed updates. I have a few adjustments to suggest,
below.

> country HK: DFS-ETSI
> 	(2402 - 2482 @ 40), (36)

Here and in other rules I'd suggest adjusting the ranges based on the
regulations rather than aligning them based on wifi channels. So here
use 2400 - 2483.5 instead, etc.

> 	(5170 - 5250 @ 80), (23), AUTO-BW, NO-OUTDOOR
> 	(5250 - 5330 @ 80), (23), DFS, AUTO-BW, NO-OUTDOOR
> 	(5490 - 5710 @ 160), (30), DFS

This range actually extends to 5725 MHz. But since the subsequent range
has looser restrictions, we can do what we've done with some other
countries and extend the rule to 5730 MHz to allow use of channel 144.

The document references the technical requirements from the FCC rules
for 5150-5350 and 5470-5725 MHz, which requires TPC when the EIRP is
over 500 mW. The 5250-5350 MHz rule should be okay, but the 5470-5725
MHz rule needs to have the max EIRP lowered to 500 mW (27 dBm).

Thanks,
Seth

> 	(5735 - 5835 @ 80), (36)
> 
> Thank you for your consideration.
> 
> [1] https://www.ofca.gov.hk/filemanager/ofca/en/content_401/hkca1039.pdf
> 
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/tree/db.txt?id=7f7a9f7bc6011b072b5427eced1ff19261764e95#n751
> 
> Best regards,
> Tavio
> 
> _______________________________________________
> wireless-regdb mailing list
> wireless-regdb@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/wireless-regdb

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

  reply	other threads:[~2023-03-21 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 14:37 [wireless-regdb] wireless-regdb: Regulatory rules for Hong Kong (HK) tavio.wong
2023-03-21 17:12 ` Seth Forshee [this message]
2023-03-22 15:14   ` tavio.wong
2023-04-16  0:00     ` Seth Forshee
2023-04-16 16:14       ` tavio.wong
2023-05-03 14:17         ` 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=ZBnlfZXMxxhfxOSD@do-x1extreme \
    --to=sforshee@kernel.org \
    --cc=tavio.wong@proton.me \
    --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