Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
CID |
Clause |
Page |
Line |
Comment |
Proposed Change |
11071 |
12.7.6.1 |
355 |
45 |
The description implies that OCI KDE can be used for MLO. However, OCI KDE needs to be redesigned to include link ID and information for 320 MHz verification because 320 MHz may have 320 MHz-1 or 320 MHz-2. |
Define
MLO OCI KDE. Ideally, follow the format of OCI KDE to include link ID and
change "Frequency Segment 1 |
10678 |
12.7.6.3 |
358 |
46 |
For MLO, OCI verification should occur on all the links. Will need to make sure OCI works correctly for MLO. e.g., we should include the OCI KDE for each requested link in msg 2 for the AP MLD to verify the operating channels of the STAs corresponding to the requested links |
As in the comment |
10679 |
12.7.6.4 |
361 |
11 |
For MLO, OCI verification should occur on all the links. Will need to make sure OCI works correctly for MLO. e.g., we should include the OCI KDE for each requested link in msg 3 for the non-AP MLD to verify the operating channels of the APs corresponding to the requested links |
As in the comment |
14100 |
12.7.2 |
351 |
5 |
OCI KDE should have a corresponding MLO KDE defined because RNR in ML probe response is not protected |
As in comment |
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