Tgax editor shall make the changes shown in 11-16-1266r2 under all headings that include CID 724 – note that empy slots are filled with NA as appropriate and similar to CID 1156, 1157, 1158, 1327 971 kaiying Lv 76.56 There is no CQI frame.CQI report is one of the modes of sounding feedback. Suggest to change to"Frames transmitted during a broadcast TWT SP are recommended to be limited to: PS-Poll, CQI, QoS Null with buffer status, Sounding Feedback, Management Action..." Revised – agree in principle with the proposed resolution – Tgax editor shall make the changes shown in 11-16-1266r2 under all headings that include CID 971 1156 Kwok Shum Au 29.29 The entry is left empty. Fill in the empty blanket with "N/A". Accept 1157 Kwok Shum Au 29.42 The entry is left empty. Fill in the blanket with "N/A". Accept 1158 Kwok Shum Au 30.24 The entry is left empty. Fill in the empty blanket with "N/A". Accept 1205 Liwen Chu 27.50 Sounding Feedback should be after NDPA, NDP. Removing sounding feedback. Revised – generally agree with commenter specifically that the language is ambiguous; propose to include a reference to sounding feedback subclause. Tgax editor shall make the changes shown in under all headings that include CID 1205 1206 Chu 29.13 Scheduled TWT is broadcasted by AP, no negotiation is required. As in comment. Reject while the scheduling STA makes the decisions about when to send Broadcast TWT, it can make the best decisions if it has input from the STAs that it wishes to serve – the cited entry provides a path for that input.
1325 Mark RISON 28.05 "beacon frames containing broadcast TWT," -- what does this mean? How does a beacon contain a broadcast TWT? Reword in terms of "with a TWT element that indicates a broadcast TWT" or similar Revised – Agree in principle with the comment – TGax editor to make the changes shown in under all headings that include CID 1324 1327 Mark RISON 29.04 are 3 blank cells in this table Put "N/A" in each Revised – Agree in principle with the comment – note that one entry is now filled with text that is not N/A – TGax editor to make the changes shown in 11-16/1266r2 under all headings that include CID 1327 1655 Matthew Fischer 26.38 The table of TWT command values is not clear. Clarify the relationships the various command options and provide more explanation as to how each one is to be used. Revised – Agree in principle with the comment – TGax editor to make the changes shown in under all headings that include CID 1655 1721 Osama 26.38 It is not clear to me why 11ax should TWT with no added value. The TWT will attract 100 of comments and waste lots of energy answering these comments. Delete TWT from the amendment and all related sections. The comment fails to identify a technical issue. Please refer to the contributions that have discussed this topic in IEEE for the added value: TargetWakeTime: Scheduled Trigger frames: 2276 Xiaofei Wang 26.43 The definition of Boradcast field is unnecessary because if TWT element is contained in a beacon frame, it is broadcast without ambiguity remove L43~L56 Revise – use of the Broadcast bit is extended to allow a broadcast TWT response to a request for an individual TWT agreement and to allow an explicit request for a broadcast TWT agreement as well as identifying the specific role of the transmitter of a TWT IE. TGax editor to make the changes shown in under all headings that include CID 2276
TWT SP(s) corresponding to the TWT flow identifier(s) of the TWT element will be protected by allocating RAW(s) that restrict access to the medium during the TWT SP(s) for that(those) TWT(s). An S1G TWT responding STA sets the TWT Protection subfield to 0 to indicate that the TWT SP(s) identified in the TWT element might not be protected from TIM STAs by allocating RAW(s)." 2830 Yusuke Tanaka 27.29 should this be a recommendation? remove "recommends on" Reject – yes it should be a recommendation. 2831 Yusuke Tanaka 27.48 should this be a recommendation? remove "recommended to be" Reject – yes it should be a recommendation. 2832 Yusuke Tanaka 27.55 should this be a recommendation? remove "recommended to be" Reject – yes it should be a recommendation. 116 Alfred 48.58 There are many features (PHY and MAC) which capabilities entry is missing in this HE Capabilities Informaiton field. Add the missing capabilities to the HE Capabilities information field. As in comment. Revised – Agree in principle with the comment – TGax editor to make the changes shown in under all headings that include CID 116 200 Alfred 49.57 Per 25.10.3, Multiple TIDs Capable is a capability that to be negotiated. Also the STA is supposed to indicate the maximum number of TIDs it supports (there is a motion on this). Hence this values should be the one added in the HE Caps. Add the Max Nr of TIDs field to HE Capabilities Element. Revised – in principle with the comment – TGax editor to make the changes shown in under all headings that include CID 200
201 Alfred 49.57 Add "HE Link Adaptation" subfield (Table 9-18a) in the HE Capabilities element to enable this mode. Add support for HE Link Adaptation field in HE Capabilities Element Revised – Agree in principle with the comment – TGax editor to make the changes shown in under all headings that include CID 201 263 Bin Tian 32.19 It is mentioned that the RU count sub-field has reserved values for 0 and 3. However, the table has defined those values. Remove the sentences that indicate that 0 and 3 for the RU count is reserved Revised – Agree in principle with the comment – TGax editor to make the changes shown in under all headings that include CID 263 264 Bin Tian 33.05 Table 9-ax14 is inconsistent and redundant. The titles to the columns are unnecessarily complicated and the second to last row is redundant. It is also not clear how the fields PPET8 and PPET16 can be absent when the bits are allocated to them according to the RU count and Nss Simplify the titles in the columns in the table. Clearly state the packet extension value when PPET8 and PPET16 are both NONE. This should be done in one place and not two. The PE values in the last two rows should have units added. Clarify the option when the fields PPET8 and PPET16 can be absent. This may require redefinign the number of bits allocated to the fields. Revised – in principle with the comment – TGax editor to make the changes shown in under all headings that include CID 264 – commenter to note that the headings do not change because while complicated, they are accurate and no simplification is suggested, nor is any simplification obvious. The second to last row is not redundant as there is a difference between none and not present and none is needed unless the encoding of the PPET8, PPET16 fields is to be changed to become more complex (e.g. a bitmap would have to be included for each NSS and RU combination in the thresholds field) 387 Brian Hart 31.16 PPE Expand this acronym / put it in section 3 Revised – Agree in principle with the comment – TGax editor to make the changes shown in under all headings that include CID 387
changes shown in under all headings that include CID 391 392 Hart 34.36 "shall also declare .. Class A/B" / how are these classes declared? Add Revised – Agree in principle with the comment – TGax editor to make the changes shown in under all headings that include CID 392 457 Daewon Lee 32.01 Combined minimum total duration of the post-FEC padding and packet extension requirement for an HE PPDU for 242 tone RU can be either for BCC encoded PPDU or LDPC encoded PPDU. However, the required total duration for different encoder types are different. The specification is not clear whether the same required duration capability applies for both BCC and LDPC or the required duration capability only applies for LDPC. Clarify that combined minimum duration of the padding and packet extension requirement for an HE PPDU is intended for LDPC encoded PPDUs. BCC encoded PDDUs do not have such requirement for STAs. Reject – discussion, PHY experts agree that the commenter is incorrect 571 32.32 It is not defined the exact NNS value for every PPET16 PPET8 field Replace "for NNSx" with "for NSS=x" Reject – the value NSS=1 is by definition present if the field is present. The value n represents the highest NSS value. The definition of the field does not allow for skipping of some NSS values. It is questionable whether the bit savings for this once-per association frame is enough justification to change the format to use a bitmask for the NSS values. 572 32.19 If the RU Count subfield has the reserved values of 0 and 3, why is it 2 bit long but not 1 bit long? Explain in the standard or change the size to 1 bit Revised – Agree in principle with the comment – TGax editor to make the changes shown in under all headings that include
1680 34.01 When QPSK DCM is used, it is not what is the modulation order (QPSK or BPSK) to be compared with the constellation index of PE threshold. The decoding time may be different for QPSK with DCM and without DCM for the same {Nss, BW} and may not necessarily need to have the same PE clarify the PE threshold rules for DCM Revise – agree in principle with the comment – TGax editor to make the changes shown in under all headings that include CID 1680 – commenter to note that in the lookup table, the value of m (RU allocation index) used to perform the lookup of the threshold values for DCM now corresponds to the RU allocation size that is one less than the actual allocation size used for the DCM PPDU – this change is inside of table 9-ax16 PPET8 and PPET16 encoding 1723 Osama 30.58 What is PPE? And its threshold? define PPE Revise – agree in principle with the comment – TGax editor to make the changes shown in under all headings that include CID 1723 1724 33.37 Table 9-ax15: RU Allocation Under encoding doesn't seem to be part of ant of the Figures shown in this clause. Something is missing but it is hard to find out what is missing. Clarify Revise – agree in principle with the comment – TGax editor to make the changes shown in under all headings that include CID 1724 1725 Osama 34.05 Table 9-ax 16: Same as the previous comment. Where is this field, "Constellation Index encoding"? Clarify Revise – agree in principle with the comment – TGax editor to make the changes shown in under all headings that include CID 1725
count, but in fact, the value in the field would not be the NSS count, but one less than the value of the NSS count, hence the current name of “NSS M1” 1885 Sigurd 32.19 Change "RU allocation values" to "RU "RU allocation" is used differently in other context Revise – format changed entirely to a bitmask, so the problem is resolved in a different manner TGax editor to make the changes shown in 11-16/1266r2 under all headings that include CID 1885 1886 Sigurd 32.20 Are two values enough for the field "RU Count"? Clarify Revise – there are now four values – TGax editor to make the changes shown in 11-16/1266r2 under all headings that include CID 1886 1887 Sigurd 32.30 Which values of NSS1 and Rum are to be included in the PPE Thresholds Info Field? Clarify Revise – TGax editor to make the changes in 11-16/1266r2 under all headings that include CID 1887 1888 Sigurd 32.39 is the format of "Constellation Index Value"? Add reference to Table 9-ax16 if appropriate. See also line 41 Revise – TGax editor to make the changes shown in 11-16/1266r2 under all headings that include CID 1888 1889 Sigurd 32.45 Elsewhere "minimum duration of the padding and packet extension for HE PPDUs" is refered to as "maximum PE duration" (see e.g. page 152) Replace "minimum duration of the padding and packet extension for HE PPDUs" with "maximum PE duration" Revise – TGax editor to make the changes shown in 11-16/1266r2 under all headings that include CID 1889 1890 Sigurd 32.45 "combined to encode" should be "combined to determine" See comment Accept – TGax editor to make the changes shown in 11-16/1266r2 under all headings that include CID 1890 1891 Sigurd 32.46 "implicitly, for values of NSS and RU not explicitly indicated in the field.". If there is an implicit assumption about how missing values are to be interpreted, this should be clarified. See comment Accept – TGax editor to make the changes in 11-16/1266r2 under all headings that include CID 1891
2392 Yongho Kim 31.05 The support of being TWT scheduling STA and TWT scheduled STA needs to be declared in HE Capabilities Use Reserved bit in HE Capabilities field format(Table 9-554b) to indicate the support of TWT scheduling STA and TWT scheduled STA: Change bit B5 to TWT scheduling STA support Change bit B6 to TWT scheduled STA support Insert the followings: "The TWT scheduling STA Support field indicates support by an HE STA for the role of TWT scheduling STA as described in 10.44.4 (Broadcast TWT operation). The TWT scheduled STA Support field indicates support by an HE STA for the role of TWT scheduled STA as described in 10.44.4 (Broadcast TWT operation)." Revise – a bit is added to the HE Cap IE for Broadcast TWT which serves both purposes, depending on STA functionality (i.e. AP or non-AP) - TGax editor to make the changes shown in 11-16/1266r2 under all headings that include CID 2392 2393 Yongho Kim 31.05 The support of HE triggered-based PPDU needs to be declared in HE Capabilities Use Reserved bit in HE Capabilities format(Table 9-554b) to indicate the support HE PPDU: Change bit B7 to HE trigger-based PPDU Capable Reject – the group has determined that this function is mandatory for HE STA and therefore, no bit is needed. 2394 Yongho Kim 31.05 The support of needs to be declared in HE Capabilities Use Reserved bit in HE Capabilities field format(Table 9-554b) to indicate the support of +HTC-HE: Change bit B8 to +HTC-HE Capable Insert the followings: "+HTC-HE Capable bit indicates whether the STA supports receiving a HE variant HT Control field." Revise – TGax editor to make the changes shown in 11-16/1266r2 under all headings that include CID 2394 based
2466 Yongho Seok 31.49 "Support for fragments that are contained within a VHT single MPDU, no support for fragments within an A VHT single MPDU is also a subset of an Change the corresponding sentence as the following: "Support for a fragment that is contained within an only" Because a terminology of a VHT single MPDU has been changed from 802.11ah draft. Also change "[a] VHT Single to "[an] S-MPDU" throughout the 802.11ax draft. As per comment Revise – TGax editor to make the changes shown in 11-16/1266r2 under all headings that include CID 2466 117 Alfred 53.07 Some information is missing here. E.g., is MCS and NSS Set going to be inherited from VHT or will it be different from VHT? If the second is the case then need to add it and its definition. Also BSS Color is 6 bits so replace TBD with 6 bits. And the AP can enable certain features (e.g., RTS transmisstions from its STAs). This needs a bit to activate it or not. Check if anyother feature needs dynamic signaling of its activation or not. As in comment Revise – TGax editor to make the changes in 11-16/1266r2 under all headings that include CID 117 202 Alfred 53.10 Change TBD for BSS bitmap size to 6 bits As in comment Revise – see CID 244
198 Alfred 23.44 Remove HE Operation from Association Request Remove HE Operation from Association Request Revise – TGax editor to make the changes shown in 11-16/1266r2 under all headings that include CID 198 2253 Weimin Xing 23.44 the "HE Operation element" should not be in Association request Reassociation request frame or Probe Request frame. delete the HE Operation row in table 9-29 P23, table 9-31 P24, table 9-33 P24 Revise – TGax editor to make the changes in 11-16/1266r2 under all headings that include CID 2253 2425 Yongho Seok 23.44 Because the HE Operation element is provided by the HE AP, the HE Operation element is not needed in the Association Request frame. Delete the HE Operation element from Table 9-29. As per comment Revise – TGax editor to make the changes shown in 11-16/1266r2 under all headings that include CID 2425 1152 Kwok Shum Au 24.16 In subclause 6.3.11.2.2, HE Operation element is present when both BSSType = INFRASTRUCTURE and is true". Change "The HE Operation element is present when the is true" with "The HE Operation element is present when both BSSType = INFRASTRUCTURE and is true". Revise – like the commenter has it reversed – the infrastructure condition is already present and does not need to be present - TGax editor to make the changes shown in 11-16/1266r2 under all headings that include CID 1152 197 Alfred 42.37 Remove HE Operation from Reassociation Request Remove HE Operation from Reassociation Request Revise – TGax editor to make the changes in 11-16/1266r2 under all headings that include CID 197 5 5 7
2426 Yongho Seok 24.37 Because the HE Operation element is provided by the HE AP, the HE Operation element is not needed in the Reassociation Request frame. Delete the HE Operation element from Table 9-31. As per comment Revise – TGax editor to make the changes shown in 11-16/1266r2 under all headings that include CID 2426 199 Alfred 43.45 Remove HE Operation from Probe Request Remove HE Operation from Probe Request Revise – TGax editor to make the changes shown in 11-16/1266r2 under all headings that include CID 198 1314 Mark RISON 25.17 HE Operation no sense in a probe request Delete this row Revise – TGax editor to make the changes shown in 11-16/1266r2 under all headings that include CID 1314 2427 Yongho Seok 25.17 Because the HE Operation element is provided by the HE AP, the HE Operation element is not needed in the Probe Request frame. Delete the HE Operation element from Table 9-33. As per comment Revise – TGax editor to make the changes shown in 11-16/1266r2 under all headings that include CID 2427 2277 Xiaofei Wang 27.16 It is unclear what the value should be set for the TWT command setup field for the TWT element sent in the beacon Suggest to add description for the quoted case and use 6 for TWT command setup field Revise – see which makes appropriate draft text changes to resolve the comment 393 Brian Hart 35.16 0 = no color but no clause 25 language that describes how "no color" is used Add Revise – CIDs also addressed this issue which was resolved with the following language found in 25.11 of D0.4: An HE STA transmitting an HE SU PPDU or an HE extended range SU PPDU for which one or more intended recipient STAs is not a member of a transmitting STA's BSS shall set the TXVECTOR parameter BSS_COLOR of the HE PPDU to 0. An HE STA 9