5003 146.36 8.4.2.170j "The Zero Offset of Group subfield is optionally present in the TWT Group Assignment field and when a STA transmits multiple TWT requests for multiple TWT flows, the next TWT Group Assignment field might not include the Zero Offset of the Group subfield implying that the Zero Offset of the Group subfield is the same for each of the TWT flows." is not clear enough. Modify as "The Zero Offset of Group subfield is optionally present in the TWT Group Assignment field because a STA may transmit multiple TWT requests for multiple TWT flows expecting that the Zero Offset of Group subfield is same for each of the TWT flows. When a STA may transmit multiple TWT requests for multiple TWT flows, the TWT Group Assignment field in the responding frames other than responding to first requst, may not include the Zero Offset of Group subfield implying that the Zero Offset of Group subfield for each TWT flow is same as the latest value assigned in responding frames." Revise – generally with commenter, Tgah editor to execute proposed changes found in document under all headings that include CID 5003. 5023 286.38 9.42a1 "..., provided that the STA has indicated that it is in a power save mode and no other condition requires the STA to remain awake." need an example to clarify. Append an example as "..., provided that the STA has indicated that it is in a save mode and no other condition requires the STA to remain awake, e.g. no STACK is required to transmit, or no further requests for different TWT flows to send are existing even if the TWT requesting STA transmits S1G Capabilities element with the TWT Grouping Reject – there are many reasons for a STA to remain awake, some of which are included in subclauses scattered throughout the standard and its amendments and some of which are part of the TGah draft amendment and some of which are not requirements of the standard, but are choices on the part of an implementation. There is no value in attempting to provide a full or partial list of these reasons. The commenter has suggested a partial list containing only a few
Support subfield equal to 1." items which are relevant to this amendment, but the inclusion of such a partial list might give some readers the impression that other reasons that arise from other subclaues in the specification might therefore be exempt from the action described here. 5024 289.28 9.42a.3 "If the TWT responding STA has already transmitted a non-zero Next TWT Info/Suspend Duration field ....., the TWT responding STA may respond to the STA with a frame that contains a Next TWT Info/Suspend Duration field." is not clear enough. Append "Even" as "Even if the TWT responding STA has already transmitted a non-zero Next TWT Info/Suspend Duration field ..., the TWT responding STA may respond .... field." Reject – the commenter’s suggestion is to add an adverb which will change the language from being purely descriptive to a more editorial form by unnecessarily emphasizing the stipulated condition. E.g. why does “even” not appear in all instances of “if” that are followed by a clause that includes a normative verb? Which ones should include it and which should not? 5037 MARC 304.02 9.42f "(short) beacon interval" -- using this wording seems to require to introduce a new abbreviation which could easily be avoided by using "short beacon interval or beacon interval". This would alse prevent the use of parenthathes. Replace "(short) beacon interval" with "short beacon interval or beacon interval" Reject – the current form is more compact and satisfies the larger number of voters and there is nothing wrong with adding an abbreviation – we have a subclause dedicated for that very purpose. 5038 MARC 304.03 9.42f "(short) beacon interval" -- using this wording seems to require to introduce a new abbreviation which could easily be avoided by using "short beacon interval or beacon interval". This would alse prevent the use of parenthathes. Replace beacon interval" with "short beacon interval or beacon interval" Reject – the current form is more compact and satisfies the larger number of voters and is nothing wrong with adding an abbreviation – we have a subclause dedicated for that very purpose.
5073 MARC 160.01 8.4.2.170l "The Sounding Option subfield is set to 0 to indicate" -- value of field is important not the act of changing it to 0. Similar issue at 160.18 and 160.24 and 161.15 Change to "A Sounding Option subfield equal to 0 indicates" Reject – there are at least 120 instances of the cited phrasing in the baseline standard, so the group prefers that a centralized style authority makes a decision on the question to apply to all amendments before accepting the proposed change while also noting that in many instances in both the baseline and the draft amendment, the converse of a condition indicated by a particular value is easily contraindicated by the phrase “otherwise, the bit is set to x”, but there is no convenient, concise, equivalent phrase that can be used to express the converse condition if the suggested alternative phrasing is used. 5104 147.46 8.4.2.170j "Each bit in the bitmap corresponds to one minimum width channel (see 8.4.3.170y (SST Operation element)) for the band in which the TWT responding STA's associated BSS is currently operating, with the least significant bit corresponding to the lowest numbered channel of the operating channels of the BSS." is not clear enough unless the minimum channel width means 1MHz or 2MHz, i.e. SST Channel Unit information in SST Operating Eleent is required. Change to "Each bit in the bitmap corresponds (see 8.4.3.170y (SST Operation element)) to one minimum width channel (that is 1MHz or 2MHz as indicated in Primary Channel Number subfield of S1G Operating Element) for the band in which the TWT responding STA's associated BSS is currently operating, with the least significant bit corresponding to the lowest numbered channel of the operating channels of the BSS." Revise – generally agree with commenter, TGah editor to execute proposed changes found in document under all headings that include CID 5104. 5185 Liwen Chu 144.32 8.4.2.170j There is no TWT field in the element. Full name of the field should be used. As in comment Revise – generally agree with commenter, TGah editor to execute proposed changes found in document under all
headings that include CID 5185. 5186 Liwen Chu 144.44 8.4.2.170j "TWT group parameters that are different from ... TWT parameters" Which one is really talking about TWT group parameters or TWT parameters? Clarify it. Reject – requesting STA requests TWT group parameters, but response can use TWT group parameters. 5187 Liwen Chu 144.50 8.4.2.170j Why is the suggested/demanded parameter only TWT and the responder needs to accept a set of parameters? Make the of parameters same as the accepted parameters. Revise – generally agree with commenter, TGah editor to execute proposed changes found in document under all headings that include CID 5187. 5190 Liwen Chu 161.40 8.4.2.170l "...after the transmission of the Beacon frame containing the SST element." The decoding of element is higher MAC layer. STAs do not know SST element right after Beacon carrying SST element. Always use Start Time subfield. Reject – how long does it take to decode the element? There are many “correct” answers to this question and the commenter has not provided even one answer to the question, so it is impossible to know what minimum Start Time value should be mandated. Furthermore, it is possible for any STA interested in the sounding to simply stay awake immediately after the Beacon in case sounding starts and during the sounding, the element decoding can proceed. 5191 Liwen Chu 161.01 8.4.2.170l "...at the end of the transmission of the frame containing the SST element" The decoding of element is higher MAC layer. STAs do not know SST element right after the frame containing the SST element. Always use Start Time subfield. Reject – how long does it take to decode the element? are many “correct” answers to this question and the commenter has not provided even one answer to the question, so it is impossible to know what minimum Start Time value should be mandated. Furthermore, it is possible for any STA interested in the sounding to simply stay awake
immediately after the Beacon in case sounding starts and during the sounding, the element decoding can proceed. 5258 Alfred 145.36 8.4.2.170j Please replace STA" with "TWT requesting STA" throughout the draft to keep consistency. As in comment. Accept 5259 Alfred 146.10 8.4.2.170j The "Zero Offset of Group" subfield is optional. So replace "48" with "0 or 48". As in comment. Revise – generally agree with commenter, TGah editor to execute proposed changes found in document under all headings that include CID 5259. 5260 Alfred 147.33 8.4.2.170j Is the frame exchange expected to be completed during one TWT SP? Also I have noticed the use of "TWT ID", "Flow Identifier", "TWT Flow ID" and "TWT Flow Identifier", and TWT Identifier" likely for the same parameter. Possibly replace all of these terms with "TWT Flow Identifier" throughout the draft. Including when used in plural. As in comment. Accept – TGah editor to execute proposed changes provided by the commenter and the commeter is to note that the frame exchange is expected to be completed during one TWT SP, if not, then the flow will fall behind and fail. 5261 Alfred 147.49 8.4.2.170j The bit in the bitmap can correspond to one minimum width channel from the enabled SST subchannels in the SST BSS as well. Replace " BSS" with "BSS or SST BSS" here and in the next line. As in comment. Reject – an SST BSS is a BSS and therefore is already included in the term “BSS”. 5262 Alfred 148.01 8.4.2.170j Only an AP can schedule RAWs. But this condition that was present in D2.0 is not present in D3.0. Insert " that is an AP" immediately "TWT responding STA". As in comment. Accept – TGah editor to execute proposed changes found in document under all headings that include CID 5262.
5318 Alfred 304.02 9.42f The description of SST operation is quite sparse at this point and difficult to follow. In my understanding an SST AP can setup an SST BSS or use the existing BSS to identify the enabled SST channels. And then the SST AP can signal which are allowed to be accessed during a (short) beacon interval with the SST element (here) or with the RPS element when SST STA supports RAW (described in 9.22.5.1). The allowed SST channels can also be indicated via a TWT element (described in 9.42a) and can also be periodically setup using the RPS element (described in 9.42g.1). I think SST would really benefit from some organization and adding references to the subclauses when the signaling is provided via other elements. Suggest to have one subclause here that gives an Overview of the SST operation and SST BSS setup. Then describe that from the enabled SST channnels (picked either from the BSS operation or from the SST operation element) the AP signals the SST channels that are allowed to be used every (short) beacon interval by the SST STA via the SST element as described in (a subclause that follows this one: maybe calling it Basic SST operation?) or via the RPS element as described in 9.22.5.1. And refer to the signaling with TWT element when these STAs have negotiated TWT operation and to the Periodinc SST operation subclause for the periodic case. Also suggest keeping consistency between the language used in these subclauses. Revise – generally with commenter, TGah editor to execute proposed changes found in document under all headings that include CID 5318. 5319 Alfred 304.63 9.42f DL bit? I think this is DL Activity field. I noticed some similar inconistencies. Please check that the field names are inline with the elements descriptions. As in comment. Revise – generally agree with commenter, TGah editor to execute proposed changes found in document under all headings that include CID 5319.
5453 David Hunter 289.24 9.42a.3 The phrase "to be sent in response the TWT responding STA shall respond with" is confusing. Just what is associated with what here? Replace "to be sent in response the TWT responding STA shall" with "to be sent in response, then the TWT responding STA shall". Accept – TGah editor to execute proposed changes provided by the commenter. 5482 Joseph Levy 160.05 8.4.2.170I are two paragraphs describing the setting of Channel Activity Bitmap, one of page 160 and page 161. It is not very clear from the paragraphs directly why the descriptions are different. Add clarifying language such as "When Sounding Option is 0" to the first paragraph, and add "When Sounding Option is 1" to the second paragraph. Accept – TGah editor to execute proposed changes provided by the commenter. Discussion: xxxx Proposed changes The proposed changes are all referenced to draft P802.11ah_D3.1. CID 5002, 5003, 5071, 5072, 5104, 5185, 5187, 5259, 5262, 5263, 5264 TGah editor: modify the text and figures as 8.4.2.196 TWT element The TWT element is in Figure 8-575a20 (TWT element format).