CID Clause Comment Proposed change 1384 9.4.2.130 "If the last received PPDU was not a Add a qualifier that the last PPDU BRP-TX PPDU, an EDMG BRP-TX packet from the same TX STA have been a or an EDMG BRP-RX/TX packet, this BRP-TX PPDU field is set to 0." - This is too limiting, may be a problem in TDD SP networks Proposed resolution: Revised Change P70L19-20 as follows: If the last received PPDU was not a BRP-TX PPDU, an EDMG BRP-TX packet or an EDMG packet from the same STA, this field is set to 0. CID Clause Comment Proposed change 1592 9.4.2.267 "... to indicate that the duration of the Please clarify/ revise. Add/ reference TDD SP is unlimited across consecutive constraints. BIs." Does this mean we have TDD SP with unlimited length? 1745 9.4.2.132 It is not what other fields in the Please clarify. Extended Schedule element indicate when TDD Applicable SP subfield is set to 1. When TDD Applicable SP subfield is 1, TDD Slot Structure element is used as well. There are duplicate fields in both elements and it is not clear fields in Extended Schedule element will indicate the allocation of the SP. 1754 9.4.2.267 The TDD Slot Structure element is used Remove Slot Structure Start Time together with the Extended Schedule field and Allocation Block Duration element. The Slot Structure Start Time field from the TDD Slot Structure field and Allocation Block Duration field element, and refer to these fields in are defined in Extended Schedule Extended Schedule element. element as well. They seems to be duplicated. 2002 9.4.2.267 It is not clear for "if the duration of the As in Comment SP is limited to the value of the Allocation Block Duration field". Because an SP may comprise multiple Allocation Blocks. Clarify what is the "duration of the SP". 2246 9.4.2.267 Not clear what is the use of Allocation Either remove this field or clarify the Block Duration field when the purpose of this field Extended Schedule Element with the
CID Clause Comment Proposed change 1384 9.4.2.130 "If the last received PPDU was not a BRP-TX PPDU, an EDMG BRP-TX packet or an EDMG BRP-RX/TX packet, this field is set to 0." - This is too limiting, may be a problem in TDD SP networks Add a qualifier that the last PPDU from the same TX STA have been a BRP-TX PPDU Proposed resolution: Revised Change P70L19-20 as follows: If the last received PPDU was not a BRP-TX PPDU, an EDMG BRP-TX packet or an EDMG packet from the same STA, this field is set to 0. CID Clause Comment Proposed change 1592 9.4.2.267 "... to indicate that the duration of the TDD SP is unlimited across consecutive BIs." Does this mean we have TDD SP with unlimited length? Please clarify/ revise. Add/ reference constraints. 1745 9.4.2.132 It is not what other fields in the Extended Schedule element indicate when TDD Applicable SP subfield is set to 1. When TDD Applicable SP subfield is 1, TDD Slot Structure element is used as well. There are duplicate fields in both elements and it is not clear fields in Extended Schedule element will indicate the allocation of the SP. Please clarify. 1754 9.4.2.267 The TDD Slot Structure element is used together with the Extended Schedule element. The Slot Structure Start Time field and Allocation Block Duration field are defined in Extended Schedule element as well. They seems to be duplicated. Remove Slot Structure Start Time field and Allocation Block Duration field from the TDD Slot Structure element, and refer to these fields in Extended Schedule element. 2002 9.4.2.267 It is not clear for "if the duration of the SP is limited to the value of the Allocation Block Duration field". Because an SP may comprise multiple Allocation Blocks. Clarify what is the "duration of the SP". As in Comment 2246 9.4.2.267 Not clear what is the use of Allocation Block Duration field when the Extended Schedule Element with the Either remove this field or clarify the purpose of this field
11-18-0721-00-00ay-resolution-to-cids-related-to-tdd-scheduling-part-2.docx