From: Johannes Berg <johannes@sipsolutions.net>
To: Wen Gong <wgong@codeaurora.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 9/9] mac80211: save transmit power envelope element and power constraint
Date: Fri, 13 Aug 2021 12:11:52 +0200 [thread overview]
Message-ID: <569d85aec8fecc836b5a6f9d40b53dff6e41c1b1.camel@sipsolutions.net> (raw)
In-Reply-To: <465b6b8535fc17ae51ee2f3116af87bb@codeaurora.org>
On Fri, 2021-08-13 at 17:16 +0800, Wen Gong wrote:
>
> yes, it should have some flag/logic to check whether it is BIGTK.
> If you know it, you can tell me. :)
Uh, actually, we don't have a secure indication of BIGTK getting used
until after the 4-way-HS.
> >
> Yes, the lower driver also have the max power limit itself. If power
> calulated
> from the fake beacon is bigger than the max power limit, then it will be
> ignored.
Right.
> >
> The Transmit Power Envelope is not existed in the assoc response, it is
> existed
> in beacon. So it can not use assoc response.
Right.
Given this discussion, I think we should just leave it as is, and simply
not assume that the TPE is protected by beacon protection or such. There
are a number of other similar parameters, and doing some real protection
at this level would likely require further spec changes.
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Wen Gong <wgong@codeaurora.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 9/9] mac80211: save transmit power envelope element and power constraint
Date: Fri, 13 Aug 2021 12:11:52 +0200 [thread overview]
Message-ID: <569d85aec8fecc836b5a6f9d40b53dff6e41c1b1.camel@sipsolutions.net> (raw)
In-Reply-To: <465b6b8535fc17ae51ee2f3116af87bb@codeaurora.org>
On Fri, 2021-08-13 at 17:16 +0800, Wen Gong wrote:
>
> yes, it should have some flag/logic to check whether it is BIGTK.
> If you know it, you can tell me. :)
Uh, actually, we don't have a secure indication of BIGTK getting used
until after the 4-way-HS.
> >
> Yes, the lower driver also have the max power limit itself. If power
> calulated
> from the fake beacon is bigger than the max power limit, then it will be
> ignored.
Right.
> >
> The Transmit Power Envelope is not existed in the assoc response, it is
> existed
> in beacon. So it can not use assoc response.
Right.
Given this discussion, I think we should just leave it as is, and simply
not assume that the TPE is protected by beacon protection or such. There
are a number of other similar parameters, and doing some real protection
at this level would likely require further spec changes.
johannes
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2021-08-13 10:12 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 20:19 [PATCH 0/9] cfg80211/mac80211: Add support for 6GHZ STA for various modes : LPI, SP and VLP Wen Gong
2021-05-17 20:19 ` Wen Gong
2021-05-17 20:19 ` [PATCH 1/9] cfg80211: add power type definition for 6G Hz Wen Gong
2021-05-17 20:19 ` Wen Gong
2021-07-23 9:22 ` Johannes Berg
2021-07-23 9:22 ` Johannes Berg
2021-05-17 20:19 ` [PATCH 2/9] mac80211: add definition of regulatory info in 6G Hz operation information Wen Gong
2021-05-17 20:19 ` Wen Gong
2021-05-17 20:19 ` [PATCH 3/9] mac80211: add parse " Wen Gong
2021-05-17 20:19 ` Wen Gong
2021-07-23 9:23 ` Johannes Berg
2021-07-23 9:23 ` Johannes Berg
2021-05-17 20:19 ` [PATCH 4/9] cfg80211: add definition for 6G power spectral density(psd) Wen Gong
2021-05-17 20:19 ` Wen Gong
2021-07-23 9:24 ` Johannes Berg
2021-07-23 9:24 ` Johannes Berg
2021-07-30 10:00 ` Wen Gong
2021-07-30 10:00 ` Wen Gong
2021-05-17 20:19 ` [PATCH 5/9] cfg80211: save power spectral density(psd) of regulatory rule Wen Gong
2021-05-17 20:19 ` Wen Gong
2021-07-23 9:27 ` Johannes Berg
2021-07-23 9:27 ` Johannes Berg
2021-07-30 10:06 ` Wen Gong
2021-07-30 10:06 ` Wen Gong
2021-05-17 20:19 ` [PATCH 6/9] mac80211: add definition for transmit power envelope element Wen Gong
2021-05-17 20:19 ` Wen Gong
2021-07-23 9:29 ` Johannes Berg
2021-07-23 9:29 ` Johannes Berg
2021-07-23 9:31 ` Johannes Berg
2021-07-23 9:31 ` Johannes Berg
2021-07-30 10:27 ` Wen Gong
2021-07-30 10:27 ` Wen Gong
2021-05-17 20:19 ` [PATCH 7/9] mac80211: add parse " Wen Gong
2021-05-17 20:19 ` Wen Gong
2021-07-23 9:33 ` Johannes Berg
2021-07-23 9:33 ` Johannes Berg
2021-07-30 10:16 ` Wen Gong
2021-07-30 10:16 ` Wen Gong
2021-05-17 20:19 ` [PATCH 8/9] mac80211: add transmit power envelope element and power constraint in bss_conf Wen Gong
2021-05-17 20:19 ` Wen Gong
2021-07-23 9:33 ` Johannes Berg
2021-07-23 9:33 ` Johannes Berg
2021-05-17 20:19 ` [PATCH 9/9] mac80211: save transmit power envelope element and power constraint Wen Gong
2021-05-17 20:19 ` Wen Gong
2021-07-23 9:38 ` Johannes Berg
2021-07-23 9:38 ` Johannes Berg
2021-07-30 10:47 ` Wen Gong
2021-07-30 10:47 ` Wen Gong
2021-08-03 8:53 ` Wen Gong
2021-08-03 8:53 ` Wen Gong
2021-08-13 7:19 ` Johannes Berg
2021-08-13 7:19 ` Johannes Berg
2021-08-13 7:25 ` Johannes Berg
2021-08-13 7:25 ` Johannes Berg
2021-08-13 8:47 ` Wen Gong
2021-08-13 8:47 ` Wen Gong
2021-08-13 8:53 ` Johannes Berg
2021-08-13 8:53 ` Johannes Berg
2021-08-13 9:16 ` Wen Gong
2021-08-13 9:16 ` Wen Gong
2021-08-13 10:11 ` Johannes Berg [this message]
2021-08-13 10:11 ` Johannes Berg
2021-08-13 10:29 ` Wen Gong
2021-08-13 10:29 ` Wen Gong
2021-08-13 8:13 ` Wen Gong
2021-08-13 8:13 ` Wen Gong
2021-05-25 10:04 ` [PATCH 0/9] cfg80211/mac80211: Add support for 6GHZ STA for various modes : LPI, SP and VLP Wen Gong
2021-05-25 10:04 ` Wen Gong
2021-06-15 8:52 ` Wen Gong
2021-06-15 8:52 ` Wen Gong
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=569d85aec8fecc836b5a6f9d40b53dff6e41c1b1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wgong@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.