Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B928FC433F5 for ; Sat, 18 Dec 2021 07:34:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232283AbhLRHe1 (ORCPT ); Sat, 18 Dec 2021 02:34:27 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46960 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230506AbhLRHe0 (ORCPT ); Sat, 18 Dec 2021 02:34:26 -0500 Received: from mout-p-102.mailbox.org (mout-p-102.mailbox.org [IPv6:2001:67c:2050::465:102]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 41DDBC061574 for ; Fri, 17 Dec 2021 23:34:26 -0800 (PST) Received: from smtp2.mailbox.org (smtp2.mailbox.org [IPv6:2001:67c:2050:105:465:1:2:0]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-102.mailbox.org (Postfix) with ESMTPS id 4JGHfl0lpFzQk3V; Sat, 18 Dec 2021 08:34:23 +0100 (CET) X-Virus-Scanned: amavisd-new at heinlein-support.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gorani.run; s=MBO0001; t=1639812860; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=wfLZMS+LFEAxDKFFvLVwSlDstNXL+1AMVKuB3bV0N04=; b=g4Bhm2fASkMQykq4JiiLfKHXxHJNf9PYylNyJAFQdw3rmwwwgVmnXotLXXRdYxFOmqwO3K ThDSzKKTl0tClxZnNcjDaHLhiUTl0Lkrgi9ILKU8WFVP/r1ja9MPcYHYeD0Ij38RscseK7 8rQiT737Xde8VkYEFsw3/C2fzgHG9zvFb6K7xqH3noc0pDuBHNtl7hULFcjIFu6eQZBeAj NyOn+/ftEWd7NzrLCc36iIK7PSMaXWUpbj3Gg2dZyxijMBqS1eo559Ps02YFmadNUNHZVI ZKsOijh219CBpnvMI6cT3XVBCckauuDNwxtJNlhK7ns7g59lrUpfyXCSSTkC5Q== Message-ID: <3e599e1a-29cd-5c86-1f43-c4ce869909b3@gorani.run> Date: Sat, 18 Dec 2021 16:34:13 +0900 MIME-Version: 1.0 Subject: Re: [wireless-regdb] wireless-regdb: Update regulatory rules for the US on 6 GHz band To: "sforshee@kernel.org" , "Asura Liu (asuliu)" Cc: "wireless-regdb@lists.infradead.org" , "linux-wireless@vger.kernel.org" References: From: Sungbo Eo In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On 2021-12-18 06:55, sforshee@kernel.org wrote: > On Mon, Dec 13, 2021 at 09:19:50AM +0000, Asura Liu (asuliu) wrote: >> From 3db25ea674232fea6a5efca292f6ed3fd8eba7a2 Mon Sep 17 00:00:00 2001 >> From: Asura Liu >> Date: Mon, 13 Dec 2021 16:46:28 +0800 >> Subject: [PATCH] wireless-regdb: Update regulatory rules for the US on 6 GHz >> band >> MIME-Version: 1.0 >> Content-Type: text/plain; charset=UTF-8 >> Content-Transfer-Encoding: 8bit >> >> According to FCC 20-51, FCC adopts rules to unlicensed use of the 6 GHz band: >> "59. Third, the Commission limits the low-power indoor access points to lower power levels than the standard-power access points that operate under the control of an AFC. Consistent with the Commission's approach for the existing U-NII bands, the Commission specifies both a maximum power spectral density and an absolute maximum transmit power, both in terms of EIRP. Specifically, the Commission allows a maximum radiated power spectral density of 5 dBm per 1 megahertz and an absolute maximum radiated channel power of 30 dBm for the maximum permitted 320-megahertz channel (or 27 dBm for a 160-megahertz channel). In addition, to ensure that client devices remain in close proximity to the indoor access points, the Commission limits their PSD and maximum transmit power to 6 dB below the power permitted for the access points." >> See https://www.federalregister.gov/documents/2020/05/26/2020-11236/unlicensed-use-of-the-6-ghz-band >> >> And 47 CFR § 15.407 describe this as following: >> (a) (5) For an indoor access point operating in the 5.925-7.125 GHz band, the maximum power spectral density must not exceed 5 dBm e.i.r.p. in any 1-megahertz band. In addition, the maximum e.i.r.p. over the frequency band of operation must not exceed 30 dBm. >> (a) (8) For client devices operating under the control of an indoor access point in the 5.925-7.125 GHz bands, the maximum power spectral density must not exceed −1 dBm e.i.r.p. in any 1-megahertz band, and the maximum e.i.r.p. over the frequency band of operation must not exceed 24 dBm. > > Thanks for the patch. A couple of quick notes about the patch > description. It's preferred to wrap lines in the body at around 75 > characters, and it's required that you include a Signed-off-by tag > indicating your agreement to the DCO for your contribution (see > CONTRIBUTING). > > Additional comments below. > >> --- >> db.txt | 6 ++++++ >> 1 file changed, 6 insertions(+) >> >> diff --git a/db.txt b/db.txt >> index b898799..c6ef9b6 100644 >> --- a/db.txt >> +++ b/db.txt >> @@ -1606,6 +1606,12 @@ country US: DFS-FCC >> # https://www.federalregister.gov/documents/2021/05/03/2021-08802/use-of-the-5850-5925-ghz-band >> # max. 33 dBm AP @ 20MHz, 36 dBm AP @ 40Mhz+, 6 dB less for clients >> (5850 - 5895 @ 40), (27), NO-OUTDOOR, AUTO-BW, NO-IR >> + # 6ghz band >> + # https://www.federalregister.gov/documents/2020/05/26/2020-11236/unlicensed-use-of-the-6-ghz-band >> + # https://docs.fcc.gov/public/attachments/FCC-20-51A1_Rcd.pdf >> + # max. 30 dBm AP @ 320MHz, 27 dBm AP @ 160MHz, 6 dB less for clients >> + (5925 - 7125 @ 320), (30), NO-OUTDOOR, AUTO-BW >> + (5925 - 7125 @ 320), (24), NO-OUTDOOR, AUTO-BW, NO-IR > > The kernel doesn't currently support multiple rules with different flags > for the same range. This is an issue that's come up several times, but > so far nothing has been done about it. > > Even ingoring that, I don't think these rules accomplish the intended > purpose. There's nothing that would require a client device to use the > NO-IR rule, so they could end up using the higher power limit and > transmitting before detecting transmission from an AP. > > I also suspect that we should be able to express the AFC requirement in > the database before permitting AP operation in this range. > > Currently I think the best we're able to do is to use the lowest common > denominator, which is the 24 dBm rule with NO-IR. > > Thanks, > Seth Hi, sorry for intruding. I thought max EIRP rule for larger bandwidth also applies to smaller bandwidth, that means we would use 24 dBm tx power with 20 MHz channel as well. But the regulation limits PSD to -1 dBm/MHz and it leads to 12 dBm for 20 MHz. Shouldn't we use 12 dBm rule to fit the smallest bandwidth? I still don't understand exactly how the rules work, my apologies if I am mistaken. Regards, Sungbo