| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi All,
For 24/305, I received new comments from some members to say, as for the MAC address, the MLD MAC address rather than link MAC address is unique to identify each non-AP MLD. Based on that, in the latest revision 24/305r5, I change the place of IRM from TA field to ML element. Because some frames, like probe request, public action frame don't include ML element according to 11be baseline. I have to drop the relevent use cases in MLO subclause (Maybe these use case are not very strong in MLO senario) . That's, non-AP MLD may set IRM in MLD MAC address field in basic ML element in authentication and association frame.
Besides, I have some offline checked with 11bh group members and the Chair Mark, they confirmed that the Reassocation case is out of 11bh scope, and 11bh group intends to git rid of them after initial SA ballot. To keep this align with the on-going 11bh draft, I change (Re)association to Association in all occurrences in new subclause .
This is all the change compared with 305r4 that we are ageed with, Welcome futher comments or thought on this.
Hi Alfred,
Could you help put 24/305r5 (https://mentor.ieee.org/802.11/dcn/24/11-24-0305-05-00be-cr-for-rcm-relevant-cids.docx ) to the MAC queue in F2F meeting?
Thanks
Best Regards
Jay Yang (杨志杰)
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