Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Liwen and all, I am re-forwarding my email regarding group-addressed frame reception for EMLMR (CID 19848) that was sent on Oct 10th. The issue is not about NSS or MCS of group-addressed frames, the issue is how to ensure the EMLMR STA is capable of frame reception and another EMLMR STA is not performing frame exchanges at that time (as Qi also pointed out). As in the
forwarded email, we can either say:
Any other suggested solutions are also welcome. Regards, Vishnu From: Vishnu Vardhan Ratnam Hi Liwen, This email is to initiate discussion regarding the 3CIDs I requested to defer in your document 1541r1. I am resending the email here on the reflector. CIDs 19846, 19847:
Discussion: When there is ongoing uplink frame exchange by an EMLMR STA with an AP affiliated with the AP MLD on a link (with the EMLMR STA as TXOP holder), the spec doesn't specify if another AP of the AP MLD can initiate a frame exchange as a TXOP
holder. This can cause failure of the frame exchange initiated by the other AP. So we need to either say:
The current spec text in the clause only covers the case where the frame exchange is initiated by the AP as a TXOP holder. CID 19848:
Discussion: During the time that an EMLMR STA of a non-AP MLD is involved in a frame exchange with the AP, it is possible that the other EMLMR STA(s) of the non-AP MLD are not capable of receiving any frames. If the group addressed frames on other
EMLMR links are delivered at this time, then the EMLMR non-AP MLD may not be able to receive the group addressed frames. Note that as per baseline, the group addressed frames can be delivered at any time if all the receiving STAs are in awake state, which
will make it difficult for an EMLMR non-AP MLD to receive group addressed frames reliably. So we need to either say:
The first option is probably simpler. Regards, Vishnu From: Liwen Chu <liwen.chu@xxxxxxx>
Hi Alfred, Please add the following contribution to the agenda: 11-23-1541-00-00be-lb275-11be-d4-0-comment-resolution-subclause 35.3.18 Best Regards, Liwen From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Hello all, I uploaded the latest version of the TGbe agenda for next week (here). Please consider sending the requests for adding CR documents to the agenda as soon as possible and no later than Sunday EVE. In addition, please upload the CR document at least 24 hours before the expected time slot for presentation. Regards,
-- Alfred Asterjadhi, PhD IEEE802.11 TGbe Chair, Qualcomm Technologies Inc. Cell #: +1 858 263 9445 Office #: +1 858 658 5302 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 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 |