8406 Can be used in Rejected- Directly specify if multi-TID can be carried in A-MPDU carried in Currently, the multi-TID PPDU. From PPDU such as VHT A-MPDU can’t be commenter's point of view, PPDU, HT PPDU, and transmitted in an HT the answer is yes as long as non-HT PPDU? From the PPDU or a VHT PPDU. the recipient supports sentence, it may be A-MPDU. implied that the restriction I think that there is no exists. technical problem when the multi-TID A-MPDU is transmitted in an HT PPDU or a VHT PPDU. But, such flexibility can makes additional implementation complexity. 6484 Instead of "(all) HE Change "all HE trigger-based Revised- PPDUs addressed to the trigger-based PPDUs Agree in principal. same AP" to "HE addressed to the same PPDUs transmitted AP", it would be more Change to same HE “the simultaneously to the same precise to write "HE trigger-based PPDU” AP". trigger-based PPDUs transmitted TGax editor changes simultaneously to the as shown in the as same AP", or in response specified in 11-17/0226r. to the same HE trigger frame, or something. HE trigger-based PPDUs transmitted at different times do not have to carry the same value, even if they are addressed to the same AP. 9611 The TXVECTOR As per comment. Revised- parameter Agree in principal. TXOP_DURATION of an It is necessary to cleary HE PPDU is specify how the based on the Duration/ID Duration/ID field in the field in the MAC header. MAC header of an HE If the Duration/ID fields of trigger-based PPDU is one or more HE calculated. PPDUs addressed to same AP are not TGax editor changes identical, the TXVECTOR as shown in the as parameter specified in 11-17/0226r. TXOP_DURATIONs of those HE trigger-based PPDUs can be different. In such case, 3rd party HE STA can't obtain the TXOP_DURATION value from the HE-SIG-A of the received HE trigger-based PPDU. Please clearly specify how the Duration/ID field in the MAC header of an
8406 Can be used in A-MPDU carried in PPDU such as VHT PPDU, HT PPDU, and non-HT PPDU? From the sentence, it may be implied that the restriction exists. Directly specify if multi-TID can be carried in PPDU. From commenter's point of view, the answer is yes as long as the recipient supports A-MPDU. Rejected- Currently, the multi-TID A-MPDU can’t be transmitted in an HT PPDU or a VHT PPDU. I think that there is no technical problem when the multi-TID A-MPDU is transmitted in an HT PPDU or a VHT PPDU. But, such flexibility can makes additional implementation complexity. 6484 Instead of "(all) HE trigger-based PPDUs addressed to the same AP", it would be more precise to write "HE trigger-based PPDUs transmitted simultaneously to the same AP", or in response to the same HE trigger frame, or something. HE trigger-based PPDUs transmitted at different times do not have to carry the same value, even if they are addressed to the same AP. Change "all HE trigger-based PPDUs addressed to the same AP" to "HE PPDUs transmitted simultaneously to the same AP". Revised- Agree in principal. Change to “the same HE trigger-based PPDU” TGax editor changes as shown in the as specified in 11-17/0226r. 9611 The TXVECTOR parameter TXOP_DURATION of an HE PPDU is based on the Duration/ID field in the MAC header. If the Duration/ID fields of one or more HE PPDUs addressed to same AP are not identical, the TXVECTOR parameter TXOP_DURATIONs of those HE trigger-based PPDUs can be different. In such case, 3rd party HE STA can't obtain the TXOP_DURATION value from the HE-SIG-A of the received HE trigger-based PPDU. Please clearly specify how the Duration/ID field in the MAC header of an As per comment. Revised- Agree in principal. It is necessary to cleary specify how the Duration/ID field in the MAC header of an HE trigger-based PPDU is calculated. TGax editor changes as shown in the as specified in 11-17/0226r.
11-17-0226-03-00ax-lb225-cr-9-7-part1.docx