of subclause 9.19.4a.1 states Channel Indication field of RPS can specify the allowed subchannel in the BSS. If allowed subchannel in Channel Indication filed is not included primary channel of BSS, each STA assigned to the RAW slot may select different channel and start transmit on same time. Also, relation of Channel Indication field and SST is not clear.SST shall be used for limiting accessible channel for STAs, and no other mechanism shall not be provided. paragraph of subclause 9.19.4a.1 and the Channel Indication field from RPS element (8.4.2.170b). Inside RAW, any channel access procedures can be utilized. When the SST is used, the RPS element should indicate the operating The last paragraph is saying the behavior of the SST protocol inside the RAW. CID Page Clause Comment Proposed Change Resolution 705 The sentences below conflicts with each other: "When Relay STA uses the Explicit Clarify whether the SF exchange is done under Relay operation. Clarify whether Revised- TGah editor to make changes
heading for CID 705, 706, 707, 709, 710, 711, 712, 713 707 response from the wrong entity to non AP STA: "The relay STA shall" "The AP shall" Revised- TGah editor to make changes shown in under the heading for CID 705, 706, 707, 709, 710, 711, 712, 713 709 what are "S1G frames"?Searched entire 11ah/D0.1; only one occurrence in line 36 page 160, but no definition. Provide clarification to "S1G frames" in line 36 page 160. Revised- TGah editor to make changes shown in under the heading for CID 705, 706, 707, 709, 710, 711, 712, 713 710 The sentence in line 34 page 160 needs clarification. How could "the choice" beceom optional? Does it mean a Relay may not make a choice? If so, does it mean no ack? Change the sentence in line 34 page 160 to the following text:The Relay STA decides which acknowledgement procedure is used, Explicit ACK procedure or Implicit ACK procedure. Revised- TGah editor to make changes shown in under the heading for CID 705, 706, 707, 709, 710, 711, 712, 713 711 The description in the paragraph in line 50 page 160 is very confusing. Let's use the Make the following changes:1) In the paragraph in line 50 page 160, Revised- TGah editor to make changes
response frames. Transmitter use of ACK Timeout should be clearly specifeid per each of the frame exchange cases allowed by 11ah. indicaiton of the expected response frame for a >=2MHz eliciting frame. fixed this comment. Any spec changes are not needed. CID Page Clause Comment Proposed Change Resolution 876 Because the non-TIM STA operation is a power saving mechanism, Section 10.2.2.22 is more appropriate. Move Section 9.32g to Section 10.2.2.22. Accepted- The STA operation is a power saving mechanism. All power saving feature should be written in the same clause. CID Page Clause Comment Proposed Change Resolution 101 The A1 and A2 values in the RA and TA fields respectively of the TACK frame have not been defined. Define those values Rejected- The A1 and A2 values in TACK are clearly defined. Clause Comment Proposed Change Resolution 115 Even thought it is allowed Define the appropriate signaling Rejected- The TWT element is
CID Page that TWT values are periodic or aperiodic the the required signaling for the periodic case is missing. for periodic TWT providing the enough information to set up a periodic TWT. CID Page Clause Change Resolution 116 It is not clear how the Channel Activity Bitmap looks like Define the Channel Activity Bitmap Rejected- The current definition of the channel activity bitmap is clearly described. See the below description. “The Channel Activity Bitmap subfield contains a bitmap indicating on channels there is expected or permitted to be transmission activity at a given time. Each bit in the bitmap corresponds to one minimum width channel for the band of operation with the LSbit corresponding to the lowest numbered operating channel of the BSS.”
CID Page Clause Change Resolution 118 How can a station belong to multiple groups? Clarify how this is possible and what a group can mean. Rejected- This is an invalid comment. Question is not an appropriate comment. If you want to know an answer for your question, See 9.32m Sectorized beam operation for the detailed information. CID Page Clause Comment Proposed Change Resolution 134 How does the AP respond to Sector ID Feedback? Does it always accept the STA's choice or can it also reject it? Please explain Rejected- This is an invalid comment. Question is not an appropriate comment. If you want to know an answer for your question, See 9.32m Sectorized beam operation for the detailed information. Clause Comment Proposed Change Resolution 496 Following P802.11ah specific definitions are missing.- Insert the definitions of following STA: The STA Accepted- in principle. TGah editor will update the
CID Page non-TIM STA- Sensor type STA which does not require reception of TIM.Sensor type STA: The STA characterized as small data size, low traffic, limited available power, and large number of STA per AP. specific definitions. CID Page Clause Change Resolution 528 The last sentence of sixth paragraph of subclause 8.3.1.20a is not necessary as the Next TWT Present subfield in the FC field can control presence of Next TWT value. Remove the last sentence of sixth paragraph of subclause 8.3.1.20a. Accepted- Agree with the comment. But, TGah Draft 0.2 already fixed this comment. Any spec changes are not needed. CID Page Clause Comment Proposed Change Resolution 538 It is not clear why the is needed to select presence of Sector Operation element in the Beacon. Remove is true." from Notes of Table 8-24. Accepted- is not defined and not used in 11ah draft. TGah editor removes is true." from Notes of Table 8-24. CID Page Clause Comment Proposed Change Resolution 539 A Modify Revised-
is used to select presence of a TWT element in subclauses 8.3.3.5, 8.3.3.6, 8.3.3.7 and 8.3.3.8. Though, in subclause 9.32f.1, a is used for the same purpose. to "dot11TWTOptionActivated". Replace to "dot11TWTOptionActivate" in sub-clauses 8.3.3.5, 8.3.3.6, 8.3.3.7 and 8.3.3.8. CID Page Clause Comment Proposed Change Resolution 569 G In Annex G (normative) "Frame exchange sequences", S1G frame sequences shall be defined. Insert a new subclause G.5 "S1G sequence".Details are TBD. Rejected- Agree in principle. Annex G shall define the frame exchange sequence of NDP MAC frame defined in 802.11ah. But, it is better to wait until the 11ah MAC protocol is stabilized. Before going to a Sponsor Ballot, it will be updated. Clause Comment Proposed Change Resolution 603 8.2.4.1.8 The "More Data" field should be updated since now a STA may also use it to indicate that it has UL data to transmit in ACK, Data or other type of frames. Note that clause 8.2.4.1.8 is not in the but should be added.Clarify that the more data field may be used by a non-AP STA (currently only AP STA uses it):A STA may set More Data bit to "1" in frames such as ACK, Data in Speed Frame Exchange indicate that it has buffered UL Revised- TGah editor to make changes in under the heading for CID 603
MSDU header, however the MSDU header is not always in a MPDU, due to fragmentation; etc.If 11ah really needs MPDU level classification for convinceable reasons, then it can introduce an additional classification, i.e., MPDU classification, and leave the current MSDU classificaiton unchanged. 754 TCLAS was originally defined to classify "traffic" rather than individual Frame litrally in my understanding, hence it is not radical if TCLAS as Frame classification is defined only for S1G(11ah). Language such a way as in comment. Revised - IEEE 802.11mc Draft 1.6 already updated those change for supporting IEEE 802.11 MAC header parameters of frame classifier type. TGah editor removes a traffic classification (TCLAS) from 3.1. Clause Comment Proposed Change Resolution 617 "Frames transmitted over the first hop and second hop are separated by SIFS." It is not clear which SIFS is Rejected- This is an invalid comment. Question is not an appropriate comment. And, the commenter should say
CID Page referenced here. For example, in the DL, does the relay AP transmit SIFS after the Relay STA receives the transmission from the AP, or SIFS after transmitting an ACK from the Relay STA to the AP? the proposed change. CID Page Clause Change Resolution 629 What's the unit of the TWT Is it TU (Time Unit, i.e., 1024us)? Clarify the TWT value unit in the paragraph in line 28 page 33. Rejected- TWT is set to the lowest six bytes of the TSF time for the next TWT. And, the unit of TSF time is 1024us. There is no ambiguity. CID Page Clause Comment Proposed Change Resolution 659 The Dialog Token field is used to differentiate different transactions of the TWT request and the TWT response sequence. Although it does not add the following sentence at the end of the paragraph in line 14 page 114:The TWT requesting STA set different Rejected- The dialog is used to identify a request/response transaction. Additional rule for choosing the value of the dialog token is not needed.
CID Page geographical grouping. There is no reason to choose a different terminology. CID Page Clause Comment Proposed Change Resolution 768 TACK and BAT include 5 significant octets of TSF timer as partial timestamp while STACK, short beacon and short probe response carry only 4 least significant octets. This seems inconsistent. unify to 4 least significant octets for partial timestamp. Rejected - TACK, BAT, STACK, short beacon and short probe response are optimized for their specific use case. It is not necessary to unifying it with single format. 769 TACK and BAT include 5 least significant octets of TSF timer as partial timestamp while STACK, short beacon and short probe response carry only 4 least significant octets. This seems inconsistent. Equivalent 4 least significant octets for partial timestamp may be preferable. Rejected - TACK, BAT, STACK, short beacon and short probe response are optimized for their specific use case. It is not necessary to unifying it with single format. CID Page Clause Comment Proposed Change Resolution 772 Transmission power density limit entries Rejected –
density may be altered in case of total signal bandwidth is changed. But Subchannel Selective Transmission element can not discribe. according to selected taransmission bandwidth may be needed in channel activity schedule subfield. The spectrum density is a regulatory requirement. The STA shall satisfy this regulatory requirement. But, it is not a standardization issue. CID Page Clause Comment Proposed Change Resolution 792 Combinatory usage with Type 0 sectorization has to be defined. Type 0 sectorization has to be introdueced and appended. Rejected- This is an invalid comment. The commenter shall say how to do to satisfy the concern. The proposed change does not say how to resolve the comment. Clause Comment Proposed Change Resolution 807 TDLS/DLS can be a useful 11ah networking form with SST (and combined channel switching) and PU power saving (and combined usage with Include the possible set of scenerios interm of TDLS/DLS mechanism appropiate for S1G operation, including SST and PU and with PRAW/TWT protection. Rejected- TDLS supports an off-channel mechanism. Off-channel TDLS can provide the same benefit with the SST operation.