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
same allocation id has another Allocation Block Duration Discussion: Allocation Block Duration field within TDD Slot Structure element TDD Slot Structure element is not necessarily sent together with Extended Schedule element since these two elements can be sent with different periodicity. Moreover, the main function of the Allocation Block Duration field within Extended Scehdule element is to notify legacy STAs that this period of time is for TDD devices. For TDD devices, this duration information in TDD Slot Structure elment can be shorter than or equal to the duration indicated in Extended Schedule element. As a result, we need to include the TDD SP duration information in TDD Slot Structure element in case a STA misses the Extended Schedule element and therefore not able to understand the timing structure included in TDD Slot Structure element. In order to avoid confusion, suggest to change the field name from “Allocation Block Duration” to “TDD SP Block Duration” Slot Structure Time field within TDD Slot Structure element This field is different with the Allocation Start field. The Slot Structure Start Time field indicates when the associated timing structure of a TDD SP takes effect. This time is not necessarily the same as the Alocation Start time. Allocation ID within TDD Slot Structure element The Allocation ID is needed here. When there are more than one TDD SPs allocated in the BI, the Allocation ID would be used to associate a TDD SP with its structure. Allocation Block Duration Validity field within TDD Slot Structure element Agree that this field can be removed. Proposed resolution: Revised. Change Figure 78 in D1.1 as follows: Element ID Length Element ID Extension Slot Structure Control Slot Structure Time Block Duraiton Slot Schedule Octets 1 1 1 4 4 2 M Change Figure 79 in D1.1 as follows: Number of TDD Slots per TDD Interval GT1 Duration GT2 Duration GT3 Duration Allocation ID Reserved Bits 4 5 5 5 Remove the definitions of the deleted field “Allocation Block Duratin Validity” Change P110L6 in D1.1 as follows: The Block Duration field indicates the duration, in microseconds, of the SP. CID Clause Comment Proposed change 1743 9.4.2.128.2 TDD Channel Access Supported subfield should be set to a value depending on a MIB variable, which is missing. Define a MIB variable controlling TDD Channel Access mode operation at the STA. Set TDD Channel Access Supported subfield and any other normative behaviors based on this MIB value.