Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi. Thank you Morteza and Zinan for this. CID 17226 (on 35.15.3) is about channel switching, and 9.4.2.20.7 is about measurement report. Hence, they are not related to each other, and we should mix the two up. I find the current language in 35.15.3 to be fine, and do not see a need to change the text there. The current language is clear that it is up to the (non-AP) STA on whether it determines the EHT BSS operating channel bandwidth based on the Bandwidth Indication element or not. (“If” an EHT STA determines…) Alternative is for the non-AP STA to determine the BSS operating channel bandwidth from the Beacon frame after the channel switch has occurred. Both are valid under the current draft. The proposal discussed below in this email thread will now make it mandatory for non-AP STAs to determine the EHT BSS operation bandwidth based on the Bandwidth Indication element before the channel switch has occurred. I don’t see a need to make such technical change at this point. Regards, Youhan From: Zinan Lin <000019c80da359b9-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi Morteza, thanks for your response! CID 17226 is about 35.15.3. Do you suggest to replace the sentence you indicated below to replace the highlight part in35.15.3? Thanks, Zinan From: Morteza Mehrnoush <morteza.80211@xxxxxxxxx>
Hi Zinan, The "shall'' requirement is removed from the sublcuase 9, 11/23-733r3; as Mark pointed out too. And it reads as below now: How about adding below text to subclause "9.6.7.7 Extended Channel Switch Announcement frame format", "9.6.2.6 Channel Switch Announcement frame format",
and "9.4.2.162 Channel Switch Wrapper element" which covers the cases used in 35.15.3? "If a Bandwidth Indication subelement is received by an EHT STA, the EHT STA uses the Bandwidth Indication subelement for determining the EHT BSS operating channel bandwidth and ignores the Wide Bandwidth
Channel Switch subelement indication." Thanks, Morteza On Mon, May 15, 2023 at 10:16 AM Mark Rison <m.rison@xxxxxxxxxxx> wrote:
To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 |