Hi Pooya,
Thank you for the contribution. I agree the document in principle, with following suggestions.
1)
Association is at MLD level. So preserving MLD association is not needed for stopping a BSS of an AP affiliated with an MLD.
2)
It is enough for the Reason Code subfield to be per TID-To-Link Mapping. No needs to make it per link. The detail reason can be inferred from the change of the TID-To-Link
Mapping and the Reason code and the ML Load.
3)
The Priority subfield in TID-To-Link Mapping Control field is similar to TWT Setup Command subfield. Suggest to rename it to Command subfield. Value 0 for suggest TID-To-Link
Mapping and Value 1 for dictate TID-To-Link Mapping.
4)
Temporarily prohibiting frame exchange on a link is not applicable for legacy STAs. Maybe this can be implemented by removing affiliated AP procedure. If so, the Mapping
Switch Count subfield and the Duration are not needed because the information has been provided in adding or removing affiliated AP procedures.
BR,
Xiangxin Gu
Communication Standards Devision
From: Pooya Monajemi <00000ef0b9e0aff7-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Tuesday, April 19, 2022 8:17 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBE] Discussion on 1793 TID Mapping Enhancements
Hello all,
Opening this thread to discuss 1793, please reply with your comments
Many thanks
Pooya
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