public inbox for wireless-regdb@lists.infradead.org
 help / color / mirror / Atom feed
From: Chen-Yu Tsai <wens@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>, Pavel Starosek <starosekpd@gmail.com>
Cc: Chen-Yu Tsai <wens@kernel.org>,
	wireless-regdb@lists.infradead.org,
	linux-wireless@vger.kernel.org
Subject: [PATCH] wireless-regdb: Permit lower 6 GHz band for Kazakhstan (KZ)
Date: Tue, 30 Sep 2025 12:29:46 +0800	[thread overview]
Message-ID: <20250930042948.427154-1-wens@kernel.org> (raw)

By Order of the Minister of Digital Development No. 564/NK dated
September 19, 2024 [1], an amendment was made to the assignment of
frequency bands, opening up the lower part of the 6 GHz band (5,945 MHz
to 6,425 MHz) was opened up to "SRD (wideband data transmission systems)
WAS/RLAN Data transmission systems/radio local area networks".

The power is limited to 200 mW e.i.r.p. with a spectral density of 10
mW/MHz. Only indoor use is permitted.

While at it, also change the power limits to use mW units to match the
official documents.

Initial information was provided by the Wi-Fi Alliance website, which
has a map [2] showing all countries that have enabled 6 GHz WiFi, and
links to official documents. This document was not sufficient as it did
not include power limits or other restrictions.

A subsequent search found a blog post [3] providing details and titles
of the official documents in English. An AI agent was used to search
for the original text of said order [1] after rummaging through
government websites in Russian and Kazakh failed to find anything.

[1] https://adilet.zan.kz/rus/docs/V2400035100
[2] https://www.wi-fi.org/regulations-enabling-6-ghz-wi-fi
[3] https://www.onewindow.pro/blog-posts/6-ghz-band-regulation-in-the-republic-of-kazakhstan

Signed-off-by: Chen-Yu Tsai <wens@kernel.org>
---
If you received this patch, please help review it. The changes are
based on translations of the original text / tables, so a second set
of eyes would be appreciated.

 db.txt | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/db.txt b/db.txt
index 6e1ad30..16bcb32 100644
--- a/db.txt
+++ b/db.txt
@@ -1136,11 +1136,12 @@ country KY: DFS-FCC
 # http://adilet.zan.kz/rus/docs/V1500010730
 # http://adilet.zan.kz/rus/docs/V1500010375
 country KZ: DFS-ETSI
-	(2400 - 2483.5 @ 40), (20)
-	(5150 - 5250 @ 80), (23), NO-OUTDOOR, AUTO-BW
+	(2400 - 2483.5 @ 40), (100 mW)
+	(5150 - 5250 @ 80), (200 mW), 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
+	(5470 - 5725 @ 160), (100 mW), NO-OUTDOOR, DFS
+	(5725 - 5850 @ 80), (100 mW), NO-OUTDOOR
+	(5925 - 6425 @ 320), (200 mW), NO-OUTDOOR
 	(57000 - 66000 @ 2160), (40)
 
 country LB: DFS-FCC
-- 
2.47.3



             reply	other threads:[~2025-09-30  4:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30  4:29 Chen-Yu Tsai [this message]
2025-09-30  7:25 ` [PATCH] wireless-regdb: Permit lower 6 GHz band for Kazakhstan (KZ) Ping-Ke Shih
2025-09-30  8:17   ` Chen-Yu Tsai
2025-09-30  8:26     ` Ping-Ke Shih
2025-09-30  8:29       ` Ping-Ke Shih
2025-10-07  6:36 ` 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=20250930042948.427154-1-wens@kernel.org \
    --to=wens@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --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