Hi all,
There were some discussions about
25/1847 and
25/2131 last week. Both CRs enable receiver to initiate BA renegotiation. The intention is to address in-device coexistence of receiver side and misalignment between transmitter and receiver.
For
25/1847 on DELBA Reason Code:
- The added texts only apply to the new DELBA reason code.
- The intention of this CRD is to “renegotiate BA” rather than “delete BA”.
- The reason for reusing DELBA is to have simple changes and low complexity.
- We could have other ways for the purpose of BA renegotiation, such as new frame/IE/BA Action field value, but these options require a lot of changes.
- The CRD has “the originator UHR STA
shall send an ADDBA Request …
as soon as practical”, and there were suggestions to change to “the originator UHR STA
should send an ADDBA Request …”. I think there is no major difference between the two options.
- Both options do not mandate the originator STA to immediately send an ADDBA Request after receiving the new DELBA reason code.
- In theory, the originator STA may not send the ADDBA Request, which means falling back to the baseline. Of course, this is not beneficial to both originator and recipient STA and is
not what we want for this new DELBA reason code.
- Other aspects, such as ADDBA Request/Response/TID/Buffer Size, follow the baseline BA procedure.
For
25/2131 on AOM:
- It enables an AOM STA to limit the number of MPDUs per A-MPDU and Buffer Size to address the issues of in-device coexistence and misalignment between AP and AOM STA.
- Other aspects are already covered in the CRD.
If you have any comments, please let me know. Thanks.
Regards
Yongsen
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
|