trigger frame as a TXOP a PIFS recovery shall not initiator cause useless be used in such case. NAV duration causing channel inefficiency. 13055 "Use of RTS/CTS clarify the statement Revised- exchange to obtain the highlighted in the comment Agree in principle. TXOP" needs to be explained. As far as I am Initiating a TXOP with the concerned HE STA still RTS/CTS is more uses CSMA/CA to obtain reasonable wording. access and TXOP. How does the RTS/CTS TGax editor makes exchange obtain a changes as shown in the TXOP? as specified in 13188 Clarify that when TXOP Add a sentence to the end Revised- Duration RTS of this paragraph as follows: Agree in principle. field is set to 1023, the "The AP may set the TXOP STA defaults to baseline Duration RTS Threshold When TXOP behavior as specified in field to 1023 to not require RTS/CTS 10.3.1 the use of exchange is disabled, the associated STAs follow by its associated the rules defined in STAs for enabling RTS/CTS 10.3.1. exchanges. In such case, the associated STAs follow TGax editor makes the rules defined in 10.3.1 changes as shown in the (General)" as specified in 14228 Features described in this Delete "The Accepted subclause are for HE devises, so it is not is not present at a needed to mention that non-HE non-AP STA." legacy devises do not support them. 14326 TXOP duration-based as in the comment Rejected- RTS/CTS is not a well The commenter is failed designed mechanism. to indetify the issue. The threshhold should be There is no sufficient in PSDU length rather reason why the unit of than the TXOP duration. the threshold has to be changed from the TXOP duration to the PSDU length. 11483 The commenter will submit Revised- contribution to propose a See the discussion part is sent to solution. of 11-18/0455r2. associated STAs in HE operation element either TGax editor makes individually or to all changes as shown in the associated STAs. There as specified in should be a option to sent to a group of associated STAs, for example type of STAs.
trigger frame as a TXOP initiator cause useless NAV duration causing channel inefficiency. a PIFS recovery shall not be used in such case. 13055 "Use of RTS/CTS exchange to obtain the TXOP" needs to be explained. As far as I am concerned HE STA still uses CSMA/CA to obtain access and TXOP. How does the RTS/CTS exchange obtain a TXOP? clarify the statement highlighted in the comment Revised- Agree in principle. Initiating a TXOP with the RTS/CTS is more reasonable wording. TGax editor makes changes as shown in the as specified in 13188 Clarify that when TXOP Duration RTS field is set to 1023, the STA defaults to baseline behavior as specified in 10.3.1 Add a sentence to the end of this paragraph as follows: "The AP may set the TXOP Duration RTS Threshold field to 1023 to not require the use of by its associated STAs for enabling RTS/CTS exchanges. In such case, the associated STAs follow the rules defined in 10.3.1 (General)" Revised- Agree in principle. When TXOP RTS/CTS exchange is disabled, the associated STAs follow the rules defined in 10.3.1. TGax editor makes changes as shown in the as specified in 14228 Features described in this subclause are for HE devises, so it is not needed to mention that legacy devises do not support them. Delete "The is not present at a non-HE non-AP STA." Accepted 14326 TXOP duration-based RTS/CTS is not a well designed mechanism. The threshhold should be in PSDU length rather than the TXOP duration. as in the comment Rejected- The commenter is failed to indetify the issue. There is no sufficient reason why the unit of the threshold has to be changed from the TXOP duration to the PSDU length. 11483 The is sent to associated STAs in HE operation element either individually or to all associated STAs. There should be a option to sent to a group of associated STAs, for example type of STAs. commenter will submit contribution to propose a solution. Revised- See the discussion part of 11-18/0455r2. TGax editor makes changes as shown in the as specified in
11-18-0455-02-00ax-lb230-cr-txop-duration-based-rts-cts.docx