Wireless-regdb Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Louis Kotze <loukot@gmail.com>
To: wireless-regdb@lists.infradead.org
Cc: wens@kernel.org
Subject: [PATCH v2] wireless-regdb: Update 6 GHz rules for South Africa (ZA)
Date: Tue, 28 Apr 2026 09:28:44 +0200	[thread overview]
Message-ID: <20260428072844.482991-1-loukot@gmail.com> (raw)

ICASA Notice 1822 of 2023 (23 May 2023) amended Annexure B of the
Radio Frequency Spectrum Regulations, 2015, to allow licence-exempt
use of 5925-6425 MHz for WAS/RLAN.

The notice references ETSI EN 303 687 and defines two device
categories:

  LPI (Low Power Indoor): 23 dBm EIRP, indoor only
  VLP (Very Low Power):   14 dBm EIRP, no restriction

The current entry uses VLP power (14 dBm) with no indoor flag.
Update to LPI with the NO-OUTDOOR flag.

LPI is the appropriate choice because indoor WiFi is the primary
use case for 6 GHz. The VLP limit of 14 dBm is too low for
practical network operation with standard access points advertising
LPI power levels, causing repeated regulatory mismatch errors that
on MLO (Multi-Link Operation) setups disrupt the 6 GHz link.

Per maintainer guidance, only one rule per band is allowed, so this
replaces the VLP rule rather than adding the LPI rule alongside it.

Reference:
  ICASA Notice 1822 of 2023, Government Gazette No. 48643 (23 May 2023)
  Amendment to Annexure B, Radio Frequency Spectrum Regulations, 2015
  https://www.icasa.org.za/uploads/files/Notice-to-amend-Annexure-B-of-the-Radio-Frequency-Spectrum.pdf

Signed-off-by: Louis Kotze <loukot@gmail.com>
---
Changes since v1:
  - Replace VLP rule with LPI rule per "one rule per band" guidance
    (Chen-Yu Tsai), rather than adding both.
  - Resend as standalone top-level patch. The previous v2 was sent
    inline as a reply on 2026-04-10, which the b4-ty tooling cannot
    extract. No content change from that v2.

v1: https://lore.kernel.org/wireless-regdb/CAMcSecJ7nDo+-JqGri80m8yn_cp9UfajHqLQDPYup7Zh7QVj7Q@mail.gmail.com/

 db.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/db.txt b/db.txt
index e019bd0..c310b7f 100644
--- a/db.txt
+++ b/db.txt
@@ -2180,7 +2180,7 @@ country ZA: DFS-ETSI
 	(5170 - 5250 @ 80), (20), AUTO-BW
 	(5250 - 5330 @ 80), (20), DFS, AUTO-BW
 	(5490 - 5710 @ 160), (30)
-	(5925 - 6425 @ 320), (14)
+	(5925 - 6425 @ 320), (23), NO-OUTDOOR
 
 country ZW: DFS-ETSI
 	(2402 - 2482 @ 40), (20)

base-commit: d0781152c3349d64faffaaa28d1221eafe389346
-- 
2.54.0



             reply	other threads:[~2026-04-28  7:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28  7:28 Louis Kotze [this message]
2026-04-28  7:35 ` [PATCH v2] wireless-regdb: Update 6 GHz rules for South Africa (ZA) 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=20260428072844.482991-1-loukot@gmail.com \
    --to=loukot@gmail.com \
    --cc=wens@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