2175 31.21 9.2.4.5.4 The term "Scheduled Ack" is not Unified the term used for used anywhere in normative "Scheduled Ack" with the term behaviors. Either the different used for normative behavior or terms should be unified or this delete this term if there is no term should be deleted if no associated normative behavior. normative behavior is associated with it. 1962 105.36 10.3.2.10 The existent definition does not An MU-MIMO initiator shall include pay attention if an immediate a Block Ack Schedule frame in each BlockAck policy is indicated or A-MPDU transmitted within an not, that makes substantial EDMG MU PPDU if Ack policy of difference to the normative MPDUs contained in the A-MPDU is behavior. equal to normal ACK or BlocAckReq is aggregated in the A-MPDU and shall not be included otherwise. 1860 31.21 9.2.4.5.4 The term "Scheduled Ack" is used Define Scheduled Ack and update in updates to Table 9-9. It's not Table 9-9 clearly defined. In some instances it's reference to as PSMP ACK/Scheduled Ack and others as Block Ack Schedule. Proposed resolution: Revised. Discussion: The normative behaviour associated with Ack” was added to clause 10.3.2.12 (MU “Scheduled acknowledgment procedure) and 10.29 (Reverse direction protocol). See proposed text below. CID Page Clause Comment Proposed Change 1411 10.3.2.10 If the reverse directon protocol for and analyze the is used (see 10.28.5), how does the impact of reverse AP estimate the BATT Start offset which direction protocol on determines the required time for the STA to MU acknowledgement transmit BA back. For example, if STA1 uses process and see if reverse direction and transmits additional changes are needed. data together with the BA, STA2 and STA3 may have to wait longer to transmit their BAs back to AP. Otherwise the BA would collide with the data transmitted by STA1.
2175 31.21 9.2.4.5.4 The term "Scheduled Ack" is not used anywhere in normative behaviors. Either the different terms should be unified or this term should be deleted if no normative behavior is associated with it. Unified the term used for "Scheduled Ack" with the term used for normative behavior or delete this term if there is no associated normative behavior. 1962 105.36 10.3.2.10 The existent definition does not pay attention if an immediate BlockAck policy is indicated or not, that makes substantial difference to the normative behavior. An MU-MIMO initiator shall include a Block Ack Schedule frame in each A-MPDU transmitted within an EDMG MU PPDU if Ack policy of MPDUs contained in the A-MPDU is equal to normal ACK or BlocAckReq is aggregated in the A-MPDU and shall not be included otherwise. 1860 31.21 9.2.4.5.4 The term "Scheduled Ack" is used in updates to Table 9-9. It's not clearly defined. In some instances it's reference to as PSMP ACK/Scheduled Ack and others as Block Ack Schedule. Define Scheduled Ack and update Table 9-9 Proposed resolution: Revised. Discussion: The normative behaviour associated with “Scheduled Ack” was added to clause 10.3.2.12 (MU acknowledgment procedure) and 10.29 (Reverse direction protocol). See proposed text below. CID Page Clause Comment Proposed Change 1411 10.3.2.10 If the reverse directon protocol for is used (see 10.28.5), how does the AP estimate the BATT Start offset which determines the required time for the STA to transmit BA back. For example, if STA1 uses reverse direction and transmits additional data together with the BA, STA2 and STA3 may have to wait longer to transmit their BAs back to AP. Otherwise the BA would collide with the data transmitted by STA1. and analyze the impact of reverse direction protocol on MU acknowledgement process and see if changes are needed.
11-18-0757-02-00ay-resolution-of-cids-related-to-mu-ba-and-rd.docx