from the scrambler initialization value in the Service field (as defined in 23.3.9.2 (SERVICE field)) prior to descrambling, and the FCS field of the PSDU that carries the soliciting frame. " According to the conventions FCS should be transmitted commencing with the coefficient of the highest-order term. Which is the highest bit of the FCS field? When generating the ACK ID field, should we take the received or transmitted order of the FCS? 11 9.8.4.2 A1 of the STACK frame Define version of Revise - TGmd editor to is defined as "The A1 is the STACK frame make changes as an SID field that that can address shown in 11-18/1724r3 contains the AID of the AP that are marked with intended recipient of the CR11, which prescribe frame in the AID a value of 0 to be used subfield. " which means for A1 for the frame that STACK frame when it is transmitted to cannot be transmitted to an AP. AP because it doesn’t have AID. 12 9.8.4.3 A1 of the BAT frame is Define version of Revise - TGmd editor to 17 defined as "The A1 is an the BAT frame that make changes as SID field that contains can address AP. shown in 11-18/1724r3 the AID of the intended Potential solution is that are marked with recipient of the frame in to follow address CR12, which prescribe the AID subfield. " which mechanism of PV1 a value of 0 to be used means that BAT frame management for A1 for the frame cannot be transmitted to frames. when it is transmitted to AP because it doesn’t an AP. have AID. 13 9.2.4.5.4 When ACK Policy bits in Describe behaviour Revise - TGmd editor to QoS Control field are set of the addressed make changes as to 00, both originator recipient in this shown in 11-18/1724r3 and addressed recipient scenario. that are marked with support fragment BA CR13, which modify procedure and table 9-13 by explicitly MPDU frame that naming the doesn’t contain fragment case and by is transmitted, behaviour explicitly naming of addressed recipient is STACK, TACK and not clear. It looks like BAT as response that this fits in Otherwise choices and by case and addressed including references to recipient should react 10.48.2 (TWT with BlockAck frame. acknowledgement procedure)
from the scrambler initialization value in the Service field (as defined in 23.3.9.2 (SERVICE field)) prior to descrambling, and the FCS field of the PSDU that carries the soliciting frame. " According to the conventions FCS should be transmitted commencing with the coefficient of the highest-order term. Which is the highest bit of the FCS field? When generating the ACK ID field, should we take the received or transmitted order of the FCS? 11 9.8.4.2 A1 of the STACK frame is defined as "The A1 is an SID field that contains the AID of the intended recipient of the frame in the AID subfield. " which means that STACK frame cannot be transmitted to AP because it doesn’t have AID. Define version of the STACK frame that can address AP Revise - TGmd editor to make changes as shown in 11-18/1724r3 that are marked with CR11, which prescribe a value of 0 to be used for A1 for the frame when it is transmitted to an AP. 12 9.8.4.3 A1 of the BAT frame is defined as "The A1 is an SID field that contains the AID of the intended recipient of the frame in the AID subfield. " which means that BAT frame cannot be transmitted to AP because it doesn’t have AID. Define version of the BAT frame that can address AP. Potential solution is to follow address mechanism of PV1 management frames. Revise - TGmd editor to make changes as shown in 11-18/1724r3 that are marked with CR12, which prescribe a value of 0 to be used for A1 for the frame when it is transmitted to an AP. 13 9.2.4.5.4 When ACK Policy bits in QoS Control field are set to 00, both originator and addressed recipient support fragment BA procedure and frame that doesn’t contain fragment is transmitted, behaviour of addressed recipient is not clear. It looks like that this fits in Otherwise case and addressed recipient should react with BlockAck frame. Describe behaviour of the addressed recipient in this scenario. Revise - TGmd editor to make changes as shown in 11-18/1724r3 that are marked with CR13, which modify table 9-13 by explicitly naming the case and by explicitly naming STACK, TACK and BAT as response choices and by including references to 10.48.2 (TWT acknowledgement procedure) 17 MPDU
11-18-1724-03-000m-response-to-d1p1-tgah-comments-from-1099.docx