From: Ping-Ke Shih <pkshih@realtek.com>
To: <wens@kernel.org>
Cc: <linux-wireless@vger.kernel.org>, <wireless-regdb@lists.infradead.org>
Subject: [PATCH v2 4/4] wireless-regdb: Update regulatory info for Mexico (MX) on 6GHz
Date: Wed, 5 Jun 2024 15:14:53 +0800 [thread overview]
Message-ID: <20240605071453.8091-4-pkshih@realtek.com> (raw)
In-Reply-To: <20240605071453.8091-1-pkshih@realtek.com>
The Plenary Session of the Federal Telecommunications Institute (IFT)
determined, in its IV ordinary session of 2023, to classify the
5925 - 6425 MHz frequency segment as free spectrum and issued the
technical operating conditions that allow coexistence with the existing
services in the country [2], which [1] is the entry page.
Within the operating conditions of this band as free spectrum, its use was
determined for low power indoor and very low power indoor and outdoor
systems.
In the agreement [3] of section Single Annex 2. Low power systems operating
indoor is
30 dBm (5 dBm over any 1 MHz bandwidth) for Access points
and
24 dBm (-1 dBm over any 1 MHz bandwidth) for Client computer
Very low power systems operating indoors and outdoors is
14 dBm (1 dBm over any 1 MHz bandwidth) for User terminal
Considering -1 dBm/MHz for Client computer and smallest channel is 20 MHz,
limit 12 dBm is adopted.
[1] https://www.ift.org.mx/comunicacion-y-medios/comunicados-ift/es/el-pleno-del-ift-clasifica-la-banda-de-5925-6425-mhz-como-espectro-libre-comunicado-132023-16-de
[2] https://www.ift.org.mx/sites/default/files/comunicacion-y-medios/comunicados-ift/comunicado13ift_1.pdf
[3] https://www.dof.gob.mx/nota_detalle.php?codigo=5681829&fecha=07/03/2023#gsc.tab=0
Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
---
v2: update reference [3] to have power limit values, and consider -1 dBm/MHz
to set 12 dBm.
---
db.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/db.txt b/db.txt
index d3b106526252..c4f5e995e422 100644
--- a/db.txt
+++ b/db.txt
@@ -1293,12 +1293,16 @@ country MW: DFS-ETSI
(5250 - 5330 @ 80), (20), DFS, AUTO-BW
(5490 - 5710 @ 160), (27), DFS
+# Source:
+# https://www.ift.org.mx/sites/default/files/comunicacion-y-medios/comunicados-ift/comunicado13ift_1.pdf
+# https://www.ift.org.mx/sites/default/files/industria/temasrelevantes/consultaspublicas/documentos/20210119-cpi6ghz2020-162.pdf
country MX: DFS-FCC
(2402 - 2482 @ 40), (20)
(5170 - 5250 @ 80), (17), AUTO-BW
(5250 - 5330 @ 80), (24), DFS, AUTO-BW
(5490 - 5730 @ 160), (24), DFS
(5735 - 5835 @ 80), (30)
+ (5925 - 6425 @ 320), (12), NO-OUTDOOR
# Source:
# https://www.mcmc.gov.my/skmmgovmy/media/General/CA-No-1-of-2022_-signed_19012022.pdf
--
2.25.1
next prev parent reply other threads:[~2024-06-05 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 7:14 [PATCH v2 1/4] wireless-regdb: Update regulatory info for Malaysia (MY) for 2022 Ping-Ke Shih
2024-06-05 7:14 ` [PATCH v2 2/4] wireless-regdb: Update regulatory info for Morocco (MA) on 6GHz Ping-Ke Shih
2024-06-05 7:14 ` [PATCH v2 3/4] wireless-regdb: Update regulatory info for Chile (CL) " Ping-Ke Shih
2024-06-05 7:14 ` Ping-Ke Shih [this message]
2024-06-05 7:44 ` [PATCH v2 4/4] wireless-regdb: Update regulatory info for Mexico (MX) " Ping-Ke Shih
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=20240605071453.8091-4-pkshih@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--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