CIDs 3031 Patil 70.04 A TWT Scheduling STA that is responding to a TWT request to setup a wake TBTT will see the TBTT Negotiation subfield value to 1. Also see section 27.7.3.4 (pg 186, line 48) Change the sentence to say that a TWT scheduling STA that is responding to a TWT request to a wake TBTT shall set the value of TBTT Negotiated subfield to 1. Revise – deleting the sentence is logically equivalent, simpler and easier to understand, as the fields have the same meaning when the Wake TBTT Negotiation bit is set to 1, regardless of whether requesting, responding, scheduled or scheduling STA sets the bit. TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 3031. 3123 Adrian 69.28 802.11ah defines the TWT element as extensible. .11ax indicates that the body of the element can be repeated for Broadcast, and presumably relies on the Length field to determine the number of such repeats. These are incompatible. Change the element ID definition to indicate it is not extensible, or add a count subfield in the Control field. Revise – TGax editor to make changes as shown in 11-17/0777r5 that are marked with CID 3123 0 0
4765 Alfred 69.32 There are some issues in this Figure. First some parts are missing (TWR field is 8, 2, or 0 in length, Broadcast TWT ID needs to be underlined). Also in order to avoid confusion between a normal TWT element and a broadcast TWT element I suggest having two Figures, one for TWT element (with one TWT parameter set, as in baseline), and another one for broadcast TWT element (with one or more TWT parameter sets, this to be tied to the value broadcast = 1 and wake TBTT interval value 0). As in comment. Revise – TGax editor to make changes as shown in 11-17/0777r5 that are marked with CID 4765 4766 Alfred 69.55 The Broadcast TWT ID is present when the Broadcast field is 1, however the functionality of the Broadcast TWT ID depends on the value of the Wake TBTT interval value. If the value is 0 then this is a broadcast TWT element. If the value is 1 then this is a TWT request/response that is negotiating the broadcast TWT IDs of that (those) particular value(s). As in comment. Impacts also the paragraph that describes the definition of Wake TBTT Negotiation in the next paragraph as is refers only to when the Broacast is and need to add the case when broadcast is 1). Also to generalize call this field something else (as Wake TBTT is restrictive now). Also please make these changes to all those fields that depend on these settings in the remaining paragraphs of this subclause. Revise – TGax editor to make changes as shown in 11-17/0777r5 that are marked with CID 4766 0 0
already referenced here. 5833 Huizhao Wang 69.31 Target Wake Time field size should be either 8 or 2 octects Change "8 or 0" to "8 or 2" Revise – changes have caused a separate diagram to be created, so the change is effected in spirit, but differently than suggested - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 5833. 5834 Huizhao Wang 70.34 The description for TWT Setup command of Request TWT is not clear. It should just simply say that for Request TWT command, the Target Wake Time field should be set to zero. Replace the text: "The Target Wake Time field of the TWT element contains 0s as the TWT responding STA specifies the target wake time value for this case,". With following simple text: "Target Wake Time field shall set to zero." Reject – the group has this language in place because when the language was not present, there were questions about how there could be a request without providing a TWT Time value in the request and the language certainly does not make things more difficult to understand, but rather, provides an explanation that clears up the question of why 0s is appropriate. 0 0 zero
5835 Huizhao Wang 73.16 Deliver sounding feedback in TWT SP time may impact the performance of HE TxBF. The sounding feedback carries the channel matrix information of the moment of sounding NDP is received, need to timely delivered to the beamformer without delay, so using TWT SP time to deliver it will likely cause extra delays. Remove: "Frames that are sent as part of a sounding feedback exchange (see 27.6 (HE sounding protocol))" Reject – nothing in the statements here suggest that the sounding frames were sent at any significant time preceding the delivery of the feedback. It is much more probable that the TWT is for PS STA which are only waking at the TWT SP and therefore, the sounding PPDUs are transmitted in the same TWT SP as the feedback. Even if sounding were in one SP and FB in a later one, that is an implementation choice. 5836 Huizhao Wang 73.42 Deliver sounding feedback in TWT SP time may impact the performance of HE TxBF. The sounding feedback carries the channel matrix information of the moment of sounding NDP is received, need to timely delivered to the beamformer without delay, so using TWT remove: "Frames that are sent as part of a sounding feedback exchange (see 27.6 (HE sounding protocol))" Reject – nothing in the statements here suggest that the sounding frames were sent at any significant time preceding the delivery of the feedback. It is much more probable that the TWT is for PS STA which are only waking at the TWT SP and therefore, the sounding PPDUs are transmitted in the same TWT SP as the feedback. Even if sounding were in one SP and FB in a later one, that is an implementation choice. 5892 James Yee 69.69 Here and elsewhere, is 1" should be "field is set to 1" As suggested. Revise – generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 5892. 0 0 0
5959 Jarkko Kneckt 72.26 The Triggered TWT SP should define that AP shall transmit a Trigger frame or a frame with Reverse Direction Grant indication in the Triggered TWT SP. In both cases the AP schdules UL transmission resources for the STA. The transmission of the frame with Reverse Direction Grant is useful when data transmission is random or the AP does not have precise knowledge of the amount of UL data that a STA has or when few STAs wake up for the TWT SP. The Trigger frame and frame with RDG enables the AP to allocate transmission resource for the STA . When frame with RDG is transmitted, the transmission resources are not wasted, if the non-AP STA does not have traffic to transmit for the whole allocated resource. Please change the text p.72, l.26 to read:" includes Trigger frames or farmes with reverse direction The Trigger field is set to 1 to indicate that at least one Trigger frame or a frame with reverse direction grant is transmitted during the TWT SP." Reject – reverse direction does not promote efficient use of the medium that using a feature that is a fundamental enhancement offered by the TGax amendment. 6049 Jarkko Kneckt 73.03 How STAs that have established TWT Flow ID 1 or 2 transmit UL DATA? The recommendations do not allow UL data transmission. Please allow UL and DL data frames transmission at the end of the TWT SP. Thus, the first part of the TWT may be used to exchange short signaling packets and the last part could be used for the data transmissions. Transmitting data in the same TWT SP simplifies the TWT handling. Reject – see ID value 3, which already has no restrictions on what may be transmitted during the SP – this is all within the control of the AP and is therefore an implementation decision with all options available as per the current encodings in the draft specification. 0 0
6051 Jarkko Kneckt 69.17 The Trigger in the TWT currently controls whether the AP shall send a Trigger to a STA in TWT SP. The TWT should not force AP to send Trigger frames, the Triggering should be taken into use when EDCA is not performing well and AP should have flexibility to control this transition. Delete the Trigger field in the Request Type field of the TWT element. Reject – while there could be an alternative to the current description of triggered TWT behavior, the one that exists is the one that was agreed upon, and other variations of TWT SP operation also exist within the draft. The current triggered TWT rules do not allow the operation suggested by the commenter because the current rules also recommend that the requesting STA does not send frames outside of the SP. What is being suggested is really, a proposal for a new mode of operation and would need a more complete description to be considered. 6089 Jian Yu 74.52 The ax contains description for 11ah draft without an clarification. For example, there is description for channel width of 1MHz and 2MHz for a BSS, whch seems very strange Refine the paragraph and clarify which part is for ax and which part is for ah. Maybe should also add ah spec as a reference Revise – generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 6089. 6350 John Coffey 71.04 Unclear wording: "... contains 0s as the TWT ..." looks at first sight as if the TWT whatever contains 0s. In context it seems that the "as" means "because" here. The stray clause tacked on at the end by a comma doesn't help. Change "as" to "because". Revise – generally agree with comment but language is changed significantly - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 6350. 0 0
6351 John Coffey 71.04 The sentence in the fifth column has independent clasues linked by a comma without a coordinating conjunction. This is ungrammatical usage and it hurts clarity. Change the comma to a semicolon. Revise – generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 6351. 6352 John Coffey 73.09 Garbled text: "Feedback can be contained is the QoS Control field". Change "is" to "in". Revise – generally with comment - TGax editor shall make the changes shown in that are marked with CID 6352. 6353 John Coffey 73.34 Garbled text: "Feedback can be contained is the QoS Control field". Change "is" to "in". Revise – generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 6353. 6354 John Coffey 74.04 Anthropomorphism: "the TWT requesting STA expects". The STA is an object and does not "expect" anything. Reword to remove the Reject – if corporations are people, then it follows that STAs are people, see USA supreme court cases which established these facts almost 200 years ago: – 17 U.S. 518 (1819) and – 125 U.S. 181 (1888) – also note that neither the 802.11 style guide nor the IEEE SA style guide mentions whatever that means… and furthermore, the entity in question, perhaps best described as an algorithm, has definite expectations of 0 0 0 0
decent substitute for “expects” in this case 6363 John Coffey 75.50 The second case here is when the relevant STA is not an S1G STA, whereas earlier in the same section (P75 L20) the condition is "within an HE BSS". Is some distinction intended? Can TWT be used in non-S1G, non-HE BSSs? Change "is not an S1G STA" to "is an HE STA". Revise – generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 6363. 7170 kaiying Lv 70.27 The Wake TBTT Negotiation subfield is set to in TWT elements transmitted by a responding STA and by a scheduling STA. In table when transmitted by a TWT scheduling STA, Wake TBTT Negotiation subfield = 1", which is conflicted with the above statement. Please change to "Description when transmitted by a TWT scheduling STA, Wake TBTT Negotiation subfield =0." Revise – generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 7170. 7184 kaiying Lv 75.02 change"TWT broadcast field"to"broadcast field" As in comment Revise – generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 7184. 7208 kaiying Lv 71.04 the description about " Demand TWT" is incorrect. please clarify it Revise – generally agree with comment - TGax editor shall make the changes shown in 11-17/0296r2 that are marked with CID 8125. 9- 0
that are marked with CID 7361. 7362 Kwok Shum Au 74.25 For the sentence "When a TWT responding STA or a TWT scheduling STA with equal to transmits a TWT element to the TWT requesting STA ...", it means is required. However, cannot be found in this amendment (11ax D1.0), 11mc Draft 8.0 or 11ah Draft 10.0. Add in subclause C.3. Revise –generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 7362. 7551 Chu 74.04 Change to "In a TWT element transmitted by a TWT requesting or scheduled STA, the TWT wake interval is equal to the average time that the TWT requesting STA or TWT scheduled STA expects to elapse between successive TWT SPs." As in comment Revise –generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 7551. 7598 Liwen Chu 73.04 Add Ack/BA as the responding frame from scheduled STA. It makes no sense to only do sounding without data frame transmission. As in comment Revise –generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 7598. 7599 Liwen Chu 73.30 Add Ack/BA as the responding frame from scheduled STA. It makes no sense to only do sounding without data frame transmission. As in comment Revise –generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 7599.
7600 Liwen Chu 72.53 Add the following restriction "The AP transmit a TIM frame or a FILS discovery frame including a TIM element at the beginning of the TWT SP." As in comment Revise –generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 7600. 7922 Mark RISON 69.63 "The Wake TBTT Negotiation subfield indicates" -- how exactly does it indicate this? Add similar sentences to the "The Broadcast is 1 to indicate that the TWT SP(s) defined by the TWT element are associated with broadcast TWT(s). The Broadcast field is 0, otherwise." above Revise –generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 7922. 7923 Mark RISON 72.37 " the TWT Flow Identifier subfield contains a value that indicates recommendations on the types of frames that are transmitted by scheduled STAs during the broadcast TWT SP, encoded according to Table 262k1" -- but that table discusses both the scheduling STA and scheduled STA Delete "scheduled" Revise –generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 7923. 7924 Mark RISON 70.27 "Description when transmitted by a TWT scheduling STA, Wake TBTT Negotiation subfield = 1" is incompatible with " The Wake TBTT Negotiation subfield is set to in TWT elements transmitted by a responding STA and by a scheduling STA." at line 2 above Change "1" to "0" Revise – deleting the earlier sentence is logically equivalent, simpler and easier to understand, as the fields have the same meaning when the Wake TBTT Negotiation bit is set to 1, regardless of whether requesting, responding, scheduled or scheduling STA sets the bit. TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 7924.
7925 Mark RISON 70.27 Descriptions of the other four cases when Wake TBTT Negotiation Subfield = 1 and scheduling/scheduled when = 0) are missing Delete ", Wake TBTT Negotiation subfield = [0/1]" in each cell (4 deletions) Revise –generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 7925. 7926 Mark RISON 70.43 Spurious asterisk Delete the asterisk Revise –generally agree with comment but other instances changed the asterisk to the words “see NOTE”, so that is what is proposed here - TGax editor shall make the changes shown in that are marked with CID 7926. 7927 Mark RISON 71.30 There can be no TWT request to accept since a scheduled STA cannot make a request (see 70.35) Change the cell to "N/A" Reject – the accept outcome is also used to accept a suggest or demand. 7928 Mark RISON 71.33 It says "(See" in the 4th column Change to "(see" Accept – TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 7928. 7929 Mark RISON 73.22 are no restrictions on the frames transmitted by the schedul- ing STA of the broadcast TWT SP." -- but the scheduling STA is the AP, so the next para does introduce restrictions Delete the cited text; also at line 49. Also fix at line 56 to only refer to the scheduled STA Revise – generally with comment - TGax editor shall make the changes shown in that are marked with CID 7929. 7930 Mark RISON 73.09 "Feedback can be contained is the QoS Control field or in the HE variant HT Control field of the frame, " -- a PS-Poll cannot carry either At line 8 and line 33 change "PS-Poll and QoS Null frames" to "QoS Null frames and PS-Poll frames contained in Control Wrapper frames" Revise – generally with comment - TGax editor shall make the changes shown in that are marked with CID 7930.
8123 Matthew Fischer 70.03 The following text was not updated when the table of TWT commands and responses was updated for broadcast TWT negotiation: "The Wake TBTT Negotiation subfield is set to in TWT elements transmitted by a responding STA and by a scheduling STA." Missing definition for requesting and responding STA cases. Delete the cited line and change "The Wake TBTT Negotiation subfield indicates that the scheduled STA transmitting the TWT element is indicating a value for the next wake TBTT for a broadcast TWT" to "The Wake TBTT Negotiation subfield indicates that a scheduled STA transmitting the TWT element is indicating a requested value for the next wake TBTT for a broadcast TWT and a scheduling STA transmitting the element is indicating the next wake TBTT for the broadcast TWT. The Wake TBTT Negotiation subfield is set to by TWT Requesting and TWT Responding STAs." Revise – generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 8123. 8124 Matthew Fischer 69.36 figure was not correctly updated to reflect changes made during CR that created D1.0 - Broadcast TWT changes allow a value of 2 octets for the Target Wake Time field, and this is not reflected in the TWT element diagram octet count label for the field Change the number of octets in the figure for the Target Wake Time field to be 8 or 2 or 0. Revise – other changes have caused a separate diagram to be created, so the change is effected in spirit, but differently than suggested - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 8124. 8127 Matthew Fischer 70.34 The table entry for the first row for column wake tbtt negotiation is NA, but at P139 the text says that this box should not have NA value - also see P186L40 which does not mention REQUEST Make a decision - either do or do not request command by scheduled STA for Broadcast TWT - fix the different references so that they do not conflict. Revise – generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 8127.
8131 Matthew Fischer 70.34 Too many of the entries for column "Description when transmitted by a TWT scheduling STA, Wake TBTT Negotiation subfield = 1" have "NA" - according to Table 10-19a--TWT setup exchange command interpretation, there should be more entries with something other than NA here. Reconcile the table in 9.4.2.200 TWT element with Table 10-19a--TWT setup exchange command interpretation - noting that Table 10-19a is the more correct one. Revise – generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 8131. 8144 Matthew Fischer 69.36 The TWT Channel should be or 1 because for bTWT, the TWT channel is not present Change the TWT Channel count in figure 9-589av TWT element format to read "0 or 1" instead of "1" Revise – other changes have caused a separate diagram to be created, so the change is effected in spirit, but differently than suggested - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 8144. 8196 69.30 Comparing the IE in Figure 9-589av to the one in 11ah draft, it seems that this TWT element is a new element by adding Broadcast TWT ID. The question is; is this a new IE? If not then I don't understand what format is now used for ah clarify Reject – the text explains the difference, in that the Broadcast bit is reserved for S1G, and it explains how the format changes dependent on the value of the Broadcast subfield. Between these two facts, the format for each case should be clear. 8197 Osama 69.30 are sub-fields in the TWT IE having variable length. When repeating for each TWT parameter, how the information can be decoded given the variabe length of some of the sub-fields? Clarify Reject – the subfields are of different length for each field depends on the settings of other subfields, so that the size, format, length, etc of each repeated set of subfields is fully described by the bits within that set of subfields.
8200 Osama 72.47 Table 9-262k1 seems to be totally arbitrary and is not based on any rationale. Perhaps some explanation is in order. either provide a rationale for the different restrictions or simply delete the table. My preference is to delete the table. Revise – generally agree with comment, table modified significantly to simplify - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 8200. 8591 Sheng Sun 70.50 The terms Scheduling STA and Scheduled STA need to be defined as in comment Reject – definitions exist in 27.7.3.1 9843 Young Hoon Kwon 69.63 It is not clear the meaning when the Wake TBTT Negotiation subfield is set to or 1. Need further clarification. As in the comment. Revise – generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 9843. 9971 Yuchen Guo 70.04 The expression "The Wake TBTT Negotiation subfield is set to in TWT elements transmitted by a responding STA and by a scheduling STA." is not correct. When the TWT scheduling STA transmits a TWT response as a response to a TWT request frame in the negotiation procedure of wake TBTT and listen interval, The value of the Wake TBTT Negotiation subfield should be equal to 1. The Wake TBTT Negotiation subfield is set to 1 in TWT elements transmitted by a responding STA and by a scheduling STA in the negotiation procedure of wake TBTT and listen interval, and set to otherwise. Revise – generally agree with comment - TGax editor shall make the changes shown in 11-17/0777r5 that are marked with CID 9971. Discussion: TWT IE changes based on CIDs as shown above.
Proposed Changes to Text of TGax D1.3: TGax editor: modify subclause 9.4.2.200 TWT element as follows: TWT element The TWT element is shown in Figure 9-589av (TWT element format). TGax editor: please note that the change to the Broadcast TWT ID subfield in figure 9-589av (TWT element format) is that the text should be underlined to indicate that the presence of this subfield is an insertion to the the baseline. Change Figure 9-589av (TWT element format) as follows (add arrow and associated text): (#5833)(#7361)(#8124) Element ID Length Control Request Type Wake Time TWT Group Nominal Minimum TWT Wake Duration TWT Wake Interval TWT Channel NDP Paging (optional) Octets: 1 1 1 2 8 or 9 or 3 or 1 2 1 or 4 Figure – TWT element format (#4765)(#5765)(#5766)(#5833)(#8144) Repeat for each TWT parameter set Element ID Length Control Type Target Wake Time Nominal Minimum TWT Wake Duration TWT Wake Interval Mantissa Broadcast TWT Info Octets: 1 1 1 2 2 1 2 1
Bits: 1 3 1 1 1 3 5 1 Request Type field format Change Table 9-2 (TWT Setup Command field values) as follows: Command field values TWT field value Command name Request TWT 1 Suggest TWT TWT requesting STA