| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Minyoung,
Thanks for preparing the submission 1434r0
I have some comments on the following proposed changes.
“(#12814)During the frame exchanges, the PPDU format of a Data frame or a Management frame that is transmitted by the AP affiliated with the AP MLD that initiated the frame exchanges shall be the EHT MU PPDU format or the HE MU PPDU format.”
The justification provided is that the switch back to listen operation for an EMLSR non-AP is based on determining PPDUs not addressed to itself and it may be difficult to decode these PPDUs (say the PPDU addressed to another non-AP can be at a higher MCS than what can be decoded by the given EMLSR non-AP due to differences in the SINR). However, the spec does not say that an EMLSR non-AP has to decode a frame not addressed to itself in order to switch back to listen operation. (If you remember, this was arrived at after a lot of discussion) It rather says that if it does not detect any of the following class of frames it shall switch back to listen. So, if the AP transmits a PPDU to another non-AP and the given EMLSR non-AP does not decode it, the EMLSR non-AP shall switch back to listen.
"...the STA affiliated with the non-AP MLD does not detect, within the PPDU corresponding to the PHY-RXSTART.indication any of the following frames:
-an individually addressed frame with the RA equal to the MAC address of the STA affili-ated with the non-AP MLD
-a Trigger frame that has one of the User Info fields addressed to the STA affiliated with the non-AP MLD
-a CTS-to-self frame with the RA equal to the MAC address of the AP affiliated with the AP MLD
-a Multi-STA BlockAck frame that has one of the Per AID TID Info fields addressed to the STA affiliated with the non-AP MLD
-a NDP Announcement frame that has one of the STA Info fields addressed to the STA affil-iated with the non-AP MLD"
So, the premise of the proposal and the corresponding change are not needed.
The resolution to CID 10155 states that “the EMLSR operation in TGbe D2.1.1 is defined between an AP MLD and a non-AP MLD and is not defined for a NSTR mobile AP” I have a concern with this resolution. What kind of non-APs does an NSTR mobile AP support? Only single-link or STR? Because even NSTR is only defined between an AP MLD and a non-AP MLD. As per my interpretation, since an NSTR mobile AP MLD is a kind of AP MLD (as mentioned in its definition), it can support all the AP MLD features other than the ones that are explicitly ruled out in the specification.
Some editorial comments: Page 5 “One of the otherA STAs operating on the corresponding one of the other links of the EMLSR links” should be “Any of the other…”. Same comment for a similar change in page 6.
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