From: Ping-Ke Shih <pkshih@realtek.com>
To: "wens@kernel.org" <wens@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"wireless-regdb@lists.infradead.org"
<wireless-regdb@lists.infradead.org>
Subject: RE: [PATCH 4/4] wireless-regdb: Update regulatory info for Mexico (MX) on 6GHz
Date: Wed, 5 Jun 2024 02:52:54 +0000 [thread overview]
Message-ID: <a97fcc8d9dfd4f9784dace38d0c01351@realtek.com> (raw)
In-Reply-To: <CAGb2v65j604KUiVDiXSAbpJQQetGagFj53E8zuk6JqwaDdBk3w@mail.gmail.com>
Chen-Yu Tsai <wens@kernel.org> wrote:
> On Mon, Jun 3, 2024 at 2:10 PM Ping-Ke Shih <pkshih@realtek.com> wrote:
> >
> > 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].
> >
> > 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.
> >
> > According to WBA Response to the Mexico IFT 6 GHz Consultation [3]. The
> > Low Power Indoor is
> > 33 dBm Max Tx Power (EIRP) & 8dBm/MHz PSD (EIRP) for Access Points
> > and
> > 27 dBm Max Tx Power (EIRP) & 2dBm/MHz PSD (EIRP) for Clients
> >
> > The Very Low Power is 4 dBm Max Tx Power (EIRP)
> >
> > [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
>
> Not sure what this reference is for?
This is entry page of [2]. I will remove it or add description about it.
>
> > [2]
> https://www.ift.org.mx/sites/default/files/comunicacion-y-medios/comunicados-ift/comunicado13ift_1.pdf
> > [3]
> https://www.ift.org.mx/sites/default/files/industria/temasrelevantes/consultaspublicas/documentos/2021
> 0119-cpi6ghz2020-162.pdf
>
> [2] does not say what limits were adopted, nor that the WBA's
> recommendations [3] were adopted in its entirety. Without such
> wording, [3] is just a recommendation, not the final rule. This
> needs some more information.
I will try to search for the adopted power limits. If I can't get that shortly,
I will only submit 3 patches by v2.
A question about TX power value. Is a special value existing to indicate the
value is uncertain?
Thanks
Ping-Ke
next prev parent reply other threads:[~2024-06-05 2:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 6:05 [PATCH 1/4] wireless-regdb: Update regulatory info for Malaysia (MY) on 6GHz Ping-Ke Shih
2024-06-03 6:09 ` [PATCH 2/4] wireless-regdb: Update regulatory info for Morocco (MA) " Ping-Ke Shih
2024-06-04 9:49 ` Chen-Yu Tsai
2024-06-03 6:09 ` [PATCH 3/4] wireless-regdb: Update regulatory info for Chile (CL) " Ping-Ke Shih
2024-06-04 10:09 ` Chen-Yu Tsai
2024-06-03 6:09 ` [PATCH 4/4] wireless-regdb: Update regulatory info for Mexico (MX) " Ping-Ke Shih
2024-06-04 10:34 ` Chen-Yu Tsai
2024-06-05 2:52 ` Ping-Ke Shih [this message]
2024-06-05 4:11 ` Chen-Yu Tsai
2024-06-04 9:45 ` [PATCH 1/4] wireless-regdb: Update regulatory info for Malaysia (MY) " Chen-Yu Tsai
2024-06-05 2:45 ` Ping-Ke Shih
2024-06-04 9:47 ` Chen-Yu Tsai
2024-06-06 14:49 ` Chen-Yu Tsai
2024-06-06 14:51 ` 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=a97fcc8d9dfd4f9784dace38d0c01351@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