2645 Young Hoon 25.5.2.3 In current spec. As mentioned in the [Text?] Kwon (REVmc_D5.2), after comment, clarify how to transmitting a frame that set retry count value in Revised requires an immediate case a transmissio that See presentation acknowledgement, the STA requires immediate 16/880 shall perform ack procedure, response is made as a and the retry counter value immediate response to a shall be incremented every Trigger frame, and time transmission of a frame modify subclause fails (see 10.22.2.11.1). 10.22.2.11.1 of However in case of UL MU REVmc_D5.2 transmission, as a transmission accordingly. is made as an immediate response to a Trigger frame, it is not clear how to handle the retry count. 2646 Hoon 25.5.2.3 With this condition, random Add a case that enables Revised Kwon access is not allowed. random access in the conditions list. Added See resolution in doc 16/929r1 2682 Yuhei Nagao 25.5.2.2.1 In the UL MU operation, Clarify Revised the of the User Identifier subfield of the Per-User Info Clarified field is undefined See resolution in for TF recipient STAs that are doc 16/929r1 not associated with the AP. We need to be clear what purpose of the User Identifier subfield for unassociated STAs with the AP. 2706 Yuichi Morioka 25.5.2.2.1 Is this restriction necessary? If Remove sentence Revised single MPDU Trigger can starting "If a Trigger be responded in SIFS, there is..." Control frames are should be no problem even if placd at the the Trigger frame is the last beginning of the frame in an A-MPDU. PPDU. 2707 Yuichi Morioka 25.5.2.2.3 What happens if the frame Define what the AP Revised exchange initiated by the should do if the trigger frame is "successful"? exchange is successful. Please modify section 25.5.2 as follows
2645 Young Hoon Kwon 25.5.2.3 In current spec. (REVmc_D5.2), after transmitting a frame that requires an immediate acknowledgement, the STA shall perform ack procedure, and the retry counter value shall be incremented every time transmission of a frame fails (see 10.22.2.11.1). However in case of UL MU transmission, as a transmission is made as an immediate response to a Trigger frame, it is not clear how to handle the retry count. As mentioned in the comment, clarify how to set retry count value in case a transmissio that requires immediate response is made as a immediate response to a Trigger frame, and modify subclause 10.22.2.11.1 of REVmc_D5.2 accordingly. [Text?] Revised See presentation 16/880 2646 Hoon Kwon 25.5.2.3 With this condition, random access is not allowed. Add a case that enables random access in the conditions list. Revised Added See resolution in doc 16/929r1 2682 Yuhei Nagao 25.5.2.2.1 In the UL MU operation, the of the User Identifier subfield of the Per-User Info field is undefined for TF recipient STAs that are not associated with the AP. We need to be clear what purpose of the User Identifier subfield for unassociated STAs with the AP. Clarify Revised Clarified See resolution in doc 16/929r1 2706 Yuichi Morioka 25.5.2.2.1 Is this restriction necessary? If single MPDU Trigger can be responded in SIFS, there should be no problem even if the Trigger frame is the last frame in an A-MPDU. Remove sentence starting "If a Trigger is..." Revised Control frames are placd at the beginning of the PPDU. 2707 Yuichi Morioka 25.5.2.2.3 What happens if the frame exchange initiated by the trigger frame is "successful"? Define what the AP should do if the exchange is successful. Revised Please modify section 25.5.2 as follows
11-16-0929-02-00ax-cr-ul-mu-operation.docx