public inbox for wireless-regdb@lists.infradead.org
 help / color / mirror / Atom feed
From: Marcos Alano <marcoshalano@gmail.com>
To: wens@kernel.org
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org
Subject: Re: wireless-regdb: Update regulatory rules for Brazil (BR) on 6GHz
Date: Thu, 26 Jun 2025 07:13:17 -0300	[thread overview]
Message-ID: <af36819b-74a3-4fb1-9b4a-69d77dcec863@gmail.com> (raw)
In-Reply-To: <CAGb2v65BO=EV+HxwOV7it94q2wNQA5_8AtjuHkLdV_2R33T_NA@mail.gmail.com>

On 26/06/2025 07:05, Chen-Yu Tsai wrote:
> On Thu, Jun 26, 2025 at 5:56 PM Marcos Alano <marcoshalano@gmail.com> wrote:
>>
>>
>>
>> On 26/06/2025 06:23, Chen-Yu Tsai wrote:
>>> Hi,
>>>
>>> On Thu, Jun 26, 2025 at 4:37 PM Marcos Alano <marcoshalano@gmail.com> wrote:
>>>>
>>>> On 26/06/2025 05:15, Chen-Yu Tsai wrote:
>>>>> On Mon, Jun 2, 2025 at 9:23 AM Marcos Alano <marcoshalano@gmail.com> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> The rules for Brazil were based on this normative
>>>>>> https://informacoes.anatel.gov.br/legislacao/resolucoes/2017/936-resolucao-680,
>>>>>> as mentioned in the comments of the entry.
>>>>>>
>>>>>> This January came out a newer normative
>>>>>> https://informacoes.anatel.gov.br/legislacao/resolucoes/2025/2001-resolucao-772,
>>>>>>
>>>>>> It allows 6GHz frequencies, so the line:
>>>>>> (5925 - 7125 @ 320), (12), NO-OUTDOOR, NO-IR
>>>>>> Should change for, at least:
>>>>>> (5925 - 7125 @ 320), (12), NO-OUTDOOR
>>>>>> The removal of NO-IR is important, since routers Wi-Fi 6E and 7 don't
>>>>>> work because of this outdated rule based on an outdated normative.
>>>>>
>>>>> Those are very large documents. Could you help point out which sections
>>>>> or comments apply to your argument?
>>>>
>>>> https://informacoes.anatel.gov.br/legislacao/atos-de-requisitos-tecnicos-de-gestao-do-espectro/2024/1920-ato-915:
>>>> in the items IX.4 and IX.5 mentions the 6GHz frequency.
>>>
>>> This only covers point-to-point usage. You would need to modify the rules
>>> and add the PTP flag. Likely not what you actually want.
>>>
>>>> https://informacoes.anatel.gov.br/legislacao/resolucoes/2025/2001-resolucao-772:
>>>> You can search for "5925-6700" to check how the allocation is done.
>>>> It mentions satellites, so that's why I set indoors, but maybe you
>>>> understand that is not necessary.
>>>
>>> This only gives the band allocation, not the requirements for each use.
>>> Also, satellite communication is a different use category. We should look
>>> for WiFi or RLAN, or perhaps "comunicação multimídia".
>>>
>>> The requirements I were able to find are:
>>>
>>> https://informacoes.anatel.gov.br/legislacao/atos-de-certificacao-de-produtos/2021/1510-ato-1306
>>>
>>> ChenYu
>>
>> I created a v3 patch that updates the comments with the new normative
>> you found, removes the NO-IR so a AP can work correctly, and changed the
>> maximum power from 12 to 27, since for APs it seems to mention 30dBm,
>> but I considered TPC like the other frequencies.
> 
> You failed to consider the power spectral density requirement. As I
> mentioned in a previous reply, the requirement for clients is -1 dBm/MHz,
> which at the smallest channel width, translates to a power limit of around
> 12 dBm. The original value is correct.
> 
> The database in its current form simply does not have the capability to
> model things like PSD or AP vs client device specificity.
> 
> If the regulations require NO-IR for clients, then we cannot remove it
> just so that APs can work. See [1] for the same discussion for US 6 GHz.
> 
Where can I check if the regulation requires NO-IR? I couldn't find any 
mention to this.

> Sorry.
> 
> ChenYu
> 
> [1] https://lore.kernel.org/wireless-regdb/14ab2a58e7603047354a17b2c980c143992a6782.camel@sipsolutions.net/
> 
>>>
>>>> Marcos.
>>>>
>>>>
>>>>>
>>>>> Thanks
>>>>> ChenYu
>>>>>
>>>>>> I'm no lawyer, so please if you see something different, like more
>>>>>> granular control in the allowed frequencies, please let us know.
>>>>>>
>>>>>> Thanks,
>>>>>> --
>>>>>> Marcos Alano
>>>>>>
>>>>>>
>>>>
>>>> --
>>>> Marcos Alano
>>>>
>>
>> --
>> Marcos Alano
>>

-- 
Marcos Alano



      reply	other threads:[~2025-06-26 11:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-01 23:49 wireless-regdb: Update regulatory rules for Brazil (BR) on 6GHz Marcos Alano
2025-06-02 10:15 ` Marcos Alano
2025-06-26  8:15 ` Chen-Yu Tsai
2025-06-26  8:37   ` Marcos Alano
2025-06-26  9:23     ` Chen-Yu Tsai
2025-06-26  9:30       ` Marcos Alano
2025-06-26  9:35       ` Marcos Alano
2025-06-26  9:56       ` Marcos Alano
2025-06-26 10:05         ` Chen-Yu Tsai
2025-06-26 10:13           ` Marcos Alano [this message]

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=af36819b-74a3-4fb1-9b4a-69d77dcec863@gmail.com \
    --to=marcoshalano@gmail.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