Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi, All cases are listed in the following table with the suggested word to be used.
I think that “shall” is suggested for the reported AP(s) with which the STA has enabled links and “should” is suggested for the reported AP(s) with which the STA has
no enabled links for the cases highlighted in
magenta. BR, Xiangxin Unisoc Technologies Co., Ltd. +86 21 20360600 3324 From: Jeongki Kim <jeongki.kim.ieee@xxxxxxxxx>
Hello all,
In the second paragraph, I think it's natural that the STA parses the change sequence fields of other APs in RNR
if the STA supports the critical update flag and the flag is set to 1. In this case, if the STA does not parse the change sequences, then the STA can not know whether the critical update of other APs happen until the STA receives the next Critical Update
Flag subfield set to 1. And then, the STA does not update the up to date BSS parameters of the other APs. In the third paragraph, 1) if a STA that does not support the critical update flag does not parse the change sequence fields of other APs in the beacon, the STA cannot know whether the critical updates of other APs happen. 2) A STA with the ReceiveDTIMs=false
may miss the beacon frame with the Critical Update Flag set to 1 and then the STA cannot also know whether the critical updates of other APs happen until the STA receives the next Critical Update flag set to1. Please let me know if you have comments or suggestions. Regards, Jeongki 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 |