12035 9.4.2.200 130.43 The TWT interval should Change to:" ... STA Accept be the time between expects to elapse successive TWT SP between succesive start times. The time TWT SP start between successive times." TWT SPs may variate. 12036 9.4.2.200 131.17 The interval between Please clarify how Revise - TGax editor to broadcast TWT SPs may Broadcast TWT make changes as be longer than a beacon Persistent field is shown in 11-17/1893r6 interval. When a TWT set, if no TWT SP that are marked with SP interval is longer than will be present in CID 12036, which a beacon interval, no the coming/current generally indicate that broadcast TWT SP may beacon intervals. the the persistence field be present in the beacon Please add text to meaning depends on interval. explain that if TWT the comparison of the This may cause two persistent field is TWT SP interval issues: larger than 0, then against the beacon 1. The wording suggests there will be at interval. that there is a TWT SP least one TWT SP in a beacon interval and before the TWT there may not be any Persistent field TWT SP. reaches value 0. 2. If the TWT Persistent field is implemented poorly, the TWT Persistent field may indicate that TWT is ongoing, but because of hte timing parameters, the TWT may not have any TWT SP. 12037 9.4.2.200 128.44 The Table 9-262k shows Please add Accept that Reject TWT is N/A. description of However, this value is Reject TWT to present in other tables Table 9-262k. and the value is needed to signal the termination of the BC TWT. 12038 9.4.2.200 129.38 Please clarify whether As in comment. Reject even though – AP allocates RUs for two SPs might overlap, OFDMA random access the scheduling STA can if an AP has a TWT SP meet both conditions, with TWT Flow Identifier as each trigger value 1 tthat overlaps transmitted belongs to with TWT SP with other one or the other TWT value in TWT Flow then each trigger identifier value. therefore obeys the rules and parameters associated with its respective TWT.
12035 9.4.2.200 130.43 The TWT interval should be the time between successive TWT SP start times. The time between successive TWT SPs may variate. Change to:" ... STA expects to elapse between succesive TWT SP start times." Accept 12036 9.4.2.200 131.17 The interval between broadcast TWT SPs may be longer than a beacon interval. When a TWT SP interval is longer than a beacon interval, no broadcast TWT SP may be present in the beacon interval. This may cause two issues: 1. The wording suggests that there is a TWT SP in a beacon interval and there may not be any TWT SP. 2. If the TWT Persistent field is implemented poorly, the TWT Persistent field may indicate that TWT is ongoing, but because of hte timing parameters, the TWT may not have any TWT SP. Please clarify how Broadcast TWT Persistent field is set, if no TWT SP will be present in the coming/current beacon intervals. Please add text to explain that if TWT persistent field is larger than 0, then there will be at least one TWT SP before the TWT Persistent field reaches value 0. Revise - TGax editor to make changes as shown in 11-17/1893r6 that are marked with CID 12036, which generally indicate that the the persistence field meaning depends on the comparison of the TWT SP interval against the beacon interval. 12037 9.4.2.200 128.44 The Table 9-262k shows that Reject TWT is N/A. However, this value is present in other tables and the value is needed to signal the termination of the BC TWT. Please add description of Reject TWT to Table 9-262k. Accept 12038 9.4.2.200 129.38 Please clarify whether AP allocates RUs for OFDMA random access if an AP has a TWT SP with TWT Flow Identifier value 1 tthat overlaps with TWT SP with other value in TWT Flow identifier value. As in comment. Reject – even though two SPs might overlap, the scheduling STA can meet both conditions, as each trigger transmitted belongs to one or the other TWT then each trigger therefore obeys the rules and parameters associated with its respective TWT.