Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Minyoung,
I wanted to ask you regarding the motivation behind the following proposed change in document 1756r6 (LB266 Comment Resolution Clause 35.3.17 EMLSR Part4) which has been added to both EMLSR enable and disable procedures:
“(#13413, 13414, 13811)The AP affiliated with the AP MLD that transmitted the EML Operating Mode Notification frame to the non-AP STA affiliated with the non-AP MLD in a TXOP shall not start another frame exchange sequence with the non-AP STA in the same TXOP.”
If the non-AP MLD is supposed to remain in active mode (following the EMLSR enable/disable) on the link that received the EML OMN frame from the AP MLD, it can receive any subsequent frames from the AP in the same TXOP. It is only if the non-AP MLD is supposed to transition to doze state on that link after transmitting the acknowledgement, that the non-AP MLD should not be expected to continue frame exchanges in that TXOP. Is this the reason the text has been added? If that is the case, the AP MLD is anyway not expected to continue any frame exchanges with the non-AP MLD on the link that is in the doze state as a part of the legacy PS mode behavior. So, the added sentence is not necessary even for the latter case.
Regards,
Sindhu
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