From: <rmandrad@gmail.com>
To: "'Dennis Bland'" <dennis@dbperformance.com>,
"'Ping-Ke Shih'" <pkshih@realtek.com>, <wens@kernel.org>
Cc: <linux-wireless@vger.kernel.org>, <wireless-regdb@lists.infradead.org>
Subject: RE: wireless-regdb: Allow 6ghz in the US
Date: Wed, 5 Mar 2025 08:27:17 -0000 [thread overview]
Message-ID: <006301db8da8$686cbb20$39463160$@gmail.com> (raw)
In-Reply-To: <CAPRryQobXZe5OwR=F-X0KHYyfBwUpFsi=Y5pKnENcUXTN42xAA@mail.gmail.com>
Hi Dennis, et all
122. is not specifying NO-IR which basically is denying any 6Ghz in the US what it means in my opinion is
Client devices (like phones, tablets, laptops) need to find Wi-Fi networks before they can join them.
One-way devices do this is by sending out probe requests. These are little "Are you there?" signals that ask nearby access points (routers) to respond, so the device knows which networks are available. This is why drivers use the non 6Ghz for allowing clients to identify the router has 6ghz capabilities… I don’t think is for wireless-regdb to take over the HW router compliance and certification which is what 122. is about
Thank you
Best Regards,
Rudy
From: Dennis Bland <dennis@dbperformance.com>
Sent: 05 March 2025 05:49
To: Ping-Ke Shih <pkshih@realtek.com>; wens@kernel.org
Cc: rmandrad@gmail.com; linux-wireless@vger.kernel.org; wireless-regdb@lists.infradead.org
Subject: Re: wireless-regdb: Allow 6ghz in the US
Hi everyone:
Section 122 of Document 2020-11236 (Unlicensed Use of the 6 GHz Band) mentions the following, which formed the basis of the NO-IR requirement:
122. The Commission recognizes the utility of permitting probe requests to enable client devices to join an access point's network. However, these probe requests have the potential to cause harmful interference to licensed operations. The Commission therefore only permits a client device to send a probe request to an access point after it has detected a transmission from the access point.
Best regards,
Dennis
On Wed, Feb 26, 2025 at 2:09 AM Ping-Ke Shih <mailto:pkshih@realtek.com> wrote:
Chen-Yu Tsai <mailto:wens@kernel.org> wrote:
>
> > based on this remove NO-IR flag and allow 30 dBm max power
>
> The original submission mentioned NO-IR requirements, though I did not
> find such wording. Dennis, do you have any ideas?
>
FYI. The description below in [1]
In all cases, an exception exists for transmitting brief messages to an
access point when attempting to join its network after detecting a signal
that confirms that an access point is operating on a particular channel.
[1] https://www.federalregister.gov/documents/2020/05/26/2020-11236/unlicensed-use-of-the-6-ghz-band
next prev parent reply other threads:[~2025-03-05 8:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 7:46 wireless-regdb: Allow 6ghz in the US rmandrad
2025-02-26 8:58 ` Chen-Yu Tsai
2025-02-26 9:09 ` Ping-Ke Shih
[not found] ` <CAPRryQobXZe5OwR=F-X0KHYyfBwUpFsi=Y5pKnENcUXTN42xAA@mail.gmail.com>
2025-03-05 8:27 ` rmandrad [this message]
[not found] ` <002d01db8da7$daf2ed50$90d8c7f0$@gmail.com>
2025-03-05 8:58 ` Chen-Yu Tsai
2025-03-05 12:18 ` Nicolas Cavallari
2025-03-05 14:36 ` rmandrad
2025-03-05 15:11 ` Chen-Yu Tsai
2025-03-05 15:27 ` rmandrad
2025-03-06 8:02 ` Johannes Berg
2025-09-09 6:12 ` Chen-Yu Tsai
2025-09-09 12:03 ` Johannes Berg
[not found] ` <000901db882d$8cb13090$a61391b0$@gmail.com>
2025-02-26 9:16 ` Chen-Yu Tsai
2025-02-26 9:40 ` rmandrad
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='006301db8da8$686cbb20$39463160$@gmail.com' \
--to=rmandrad@gmail.com \
--cc=dennis@dbperformance.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.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