Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Mark, Jose and other members,
The contribution, PASN ID for MLO(345r2), has presented during the March F2F meeting. I'd like to initiate this discussion based on the comments by Mark and Jose.
Mark: 1. no definition for ''the providing AP'' 2. association request frame should be from non-AP STA rather than non-AP MLD
Yan: Agree, the relevant text has modified in the 345r3. Please check it
Jose: MLD MAC address should be carried in protected info element. Therefore, no need to consider MLD recognition
Yan: Firstly, a non-AP MLD may randomly change its MLD MAC address while not associated. Secondly, the non-AP MLD may carry its MLD MAC address in the association request frame which is not protected according to 11be spec. From the perspective of non-AP MLD, it would like to change both of affiliated non-AP STA MAC address and MLD MAC address to avoid any track from third party.
However, this contribution focuses on the use case of transition from non-AP MLD to non-MLO STA instead of any pure MLD recognition, which has already merged into 11be spec.
Best Regards!
Yan Li
To unsubscribe from the STDS-802-11 list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11&A=1
To unsubscribe from the STDS-802-11 list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11&A=1