| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Yonggang, Regarding you suggestion highlighted in yellow – I’m OK with it Regarding point (2) . I provided it only to say that potentially it is better (as alternative to [#7430]with an associated AP that has enabled
P-EDCA in the BSS )
to solve this issue for _all_ modes as _all_ modes follow clause 37.31
If we add (my thinking, ) wording “_or_not_enabled” _ into that sentence:
If a UHR mode of operation is not supported “add: _or not enabled_” by an AP affiliated with an AP MLD, then the non-AP MLD shall not request.
It will solve the issues, isn’t it? STA will not be able to try to enable the mode if the mode is not enabled by the AP, even if AP supports it. I’m OK to defer this CID, but I’d like to hear other opinions as well. So far only you and Chaoming responded with comments. Dmitry From: Yonggang Fang <Yonggang.Fang@xxxxxxxxxxxx>
Hi Dmitry, Gaurang, Thanks for the update. I have some comments:
When a non-AP STA that supports P-EDCA mode (re)associates with an AP, P-EDCA mode is disabled by default for the non-AP STA. A UHR non-AP STA that supports P-EDCA mode and that intends
to enable or disable P-EDCA mode shall follow the procedure defined in 37.31 (Procedure for operating mode and parameter updates)
[#7430]with an associated AP that has enabled P-EDCA
in the BSS. The associated AP shall accept the request and follow the procedure defined in 37.31 (Procedure for operating mode and parameter updates).
“If a UHR mode of operation is not supported by the AP MLD, then the non-AP MLD shall not request to enable that mode for the non-AP MLD. If a UHR mode of opera-tion is not supported
by an AP affiliated with an AP MLD, then the non-AP MLD shall not request to enable that mode for the non-AP STA operating on the corresponding AP’s
link.” But there is no rule for a P-EDCA STA not to request to enable the P-EDCA if P-EDCA in the BSS is not enabled by the AP. In addition, if the AP changes the P-EDCA from the enabled to disabled, how would the
P-EDCA STAs react the state change? Would you please leave the CID 7430 open and use it to resolve those issues? Thanks Yonggang From: Akhmetov, Dmitry <Dmitry.Akhmetov@xxxxxxxxx>
Greetings everyone, I’ve uploaded revision 3 of 11-25/1819r3 document to the server: https://mentor.ieee.org/802.11/dcn/25/11-25-1819-03-00bn-lb291-cr-p-edca-part1.docx The document reflect comments that I’ve received during Monday MAC call:
For the CID 7430 – I removed the NOTE : NOTE[#6338] 1—[#7430]A non-AP STA can enable P-EDCA mode only if its associated AP supports P-EDCA
and has enabled P-EDCA for the BSS (see 37.31 (Procedure for operating mode and parameter updates)). As a potential resolution I’ve added corresponding text “
[#7430]with an associated AP that has enabled P-EDCA” to in the paragraph above: <cut>… A UHR non-AP STA that supports P-EDCA mode and that intends to enable or disable P-EDCA mode shall follow the procedure defined in 37.31 (Procedure for operating mode and parameter updates)
[#7430]with an associated AP that has enabled P-EDCA. </cut> Please let me know if you have issues with the proposed changes.
Alternatively, the requested change can be done directly in clause 37.31 where we have the following text:
Draft 1.1; page 278, lines 55-58 If a UHR mode of operation is not supported “add: _or not enabled_” by an AP affiliated with an AP MLD, then the non-AP MLD shall not request to enable that mode for the non-AP STA operating
on the corresponding AP’s link. Dmitry 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 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 |