| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
There may be neighbor APs that is not UHR. They may also be reported by the AP MLD. The current procedure does not preclude the AP MLD reporting pre-UHR APs. 发件人: Duncan Ho <dho@xxxxxxxxxxxxxxxx>
+ Abhi Hi Chaoming, did you mean the “reporting AP may not be UHR AP”? Why the reported AP is not UHR? Thanks, Duncan From:
罗朝明(Chaoming Luo) <luochaoming@xxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. And one more: UHR Operation and UHR Capabilities elements may not be included in the Neighbor Report elements, since the reported AP may not be UHR AP. 发件人:
罗朝明(Chaoming Luo)
Hi Duncan, As discussed during the Ad hoc, the information in the Per-STA profile in the preparation phase should also be transferred to the target AP MLD. BR, Chaoming 发件人: Duncan Ho <00002b3e54cff3e2-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi all, I’ve updated the PDT Part 5 based on the comments I received during the MAC ad-hoc last week. The revision history in the doc gives a high level summary of the changes. https://mentor.ieee.org/802.11/dcn/25/11-25-1101-01-00bn-pdt-cr-mac-on-seamless-roaming-part-5.docx Could you please let me know if you have any questions or comments? Thanks, Duncan To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1 |