Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Ahmed, Thanks for sharing, I have made some comments, please see attached. For ease of discussion, I have also copied the comment here: Not clear what is AP MLD’s action upon receiving the TDLS Channel Switch Notification frame? I think a simple “notification” is not enough, a two way “permission” frame exchange would be better, i.e., the non-AP seeks permission from
the AP-MLD prior to switching to an TDLS off-channel. This is especially true for the 6 GHz band, or even in 5 GHz DFS channels, in which the channel needs to be checked prior to using the channel (e.g., with AFC). Even for “regular” channels/links, it would
be good to check with AP prior to switching, e.g., the link may be part of a NSTR link pair, and non-AP STA may not be aware etc. Since AP would have such knowledge, it would make sense that the AP decides whether an off-channel may be used (rather than the
non-AP checking it self). For this reason, highly encourage to consider two way explicit “permission” exchange with the AP rather than a simple “notification”. Regards, Rojan From: Ahmed Ibrahim <0000162d12c1fcf3-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi Everyone, I have uploaded a CR for some TDLS CIDs (CIDs 4033, 4590, 4593). Would you please let me know if you have comments/suggestions/questions to make convergence faster? Thank you. Ahmed 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 |
Attachment:
11-22-0600-00-00be-some-tdls-cids-resolution_RC.docx
Description: 11-22-0600-00-00be-some-tdls-cids-resolution_RC.docx