7093 author The insertion here makes a special case out of the Extended NSS BW Support field and Supported Channel Width Set fields. All the other fields are fully defined the table 9-245. Move this text into Table 9-245 against definition of one or more of these fields. Revised – delete the cited text and note that changes introduced by resolution to CID 7674 clarify the text already present within the cited table. 7114 author R.7 The units of RSSI and P_adjust are not specified. Note, a separate comment has been submitted on the editorial style of these equations. Specify them. Revised – TGmc editor shall add “in units of dBm” to the end of the RSSI definition and add “in units of dBm” to the end of the P_adjust definition and add “dBm” to the term “10” of the denominator of the exponent of the equation for SNR_tone 7113 Author R.7 The equations starting at the location do not follow IEEE-SA equation style very closely. There is inconsistency between underscore and subscripting. The showing of units in equations is not done elsewhere in this standard. Rework equations to bring closer to style and to others in the Standard. Specifically: remove any units embedded in the equations, use "underscore" versus subscripts consistently, and certainly when referring to the same variable. Use shorter variable names, and put the explanation of what they represent into the variable list. Revised – TGmc editor shall make changes as indicated under all headings including CID 7113 within
7665 Author 1056.37 "the Extended NSS BW Support bits" -- what bits? Of what? Change to "the Extended NSS BW Support subfield in the <something>". Also change "bits" to "subfield" at 1053.42, 717.23 and 1056.39, and for the last two also add the missing "Support" before that Revised – TGmc editor shall change “capable of interpreting the Extended NSS BW Support bits” to “capable of interpreting the Extended NSS BW Support bits of the VHT Capabilities Information field of the VHT Capabilities Information element and the Dynamic Extended NSS BW Support field of the Operating Mode field” 7223 Mark 10.32.3 "An HT beamformer may use the following worst-case parameters to estimate the duration of the expected frame that contains the feedback response: Basic HT-MCS, Format, Supported Grouping." -- what about a VHT beamformer Add an equivalent statement to the VHT BF subclause (10.34.5) Revise – TGmc editor shall add “A VHT beamformer may use the following worst-case parameters to estimate the duration of the expected frame that contains the feedback response: lowest rate in basic VHT-MCS set, format, no grouping.” As a new paragraph to appear immediately after the paragraph that begins “A VHT beamformer that transmits a VHT NDP Announcement frame with more than one STA Info field should transmit any Beamforming Report Poll frames used to retrieve VHT Compressed Beamforming feedback from the intended VHT beamformees in the same TXOP.” In subclause 10.34.5.2 Rules for VHT sounding protocol sequences 9.4.2.158
7762 Mark 10.32.3 "The procedures in this subclause apply only to HT and non-HT PPDUs for which the HT Control field, if present, is the HT variant HT Control field." -- is this sufficiently clear that the subclause is only for non-VHT STAs? VHT STAs can sent HT variant HTCs, after all As it says in the comment Decline – the rules in the HT explicit beamforming subclause are applicable to operations initiated by either an HT STA or a VHT STA, i.e. a VHT STA may perform these operations, typically with an HT non-AP STA for example 7763 Mark 10.33.1 "The procedures in this subclause apply only to HT and non-HT PPDUs for which the HT Control field, if present, is the HT variant HT Control field." -- is this sufficiently clear that the subclause is only for non-VHT STAs? VHT STAs can sent HT variant HTCs, after all As it says in the comment Decline – the rules in the HT explicit beamforming subclause are applicable to operations initiated by either an HT STA or a VHT STA, i.e. a VHT STA may perform these operations, typically with an HT non-AP STA for example 7193 Mark R.7 "MPDU_pPPDU" is not defined Change to Revise - TGmc editor make changes as indicated under all headings including CID 7193 within 7197 Mark R.7 is not defined Change to "A_MSDU_B" Revise - TGmc editor shall make changes as indicated under all headings including CID 7197 within ?
7681 Mark This be clearer with the Meaning column split into 3, one for 20/40/80, one for 160 and one for 80+80, where the cell can say "not supported", "supported" or "supported at [half/twice] Max VHT NSS" As it says in the comment 7682 Mark 716.37 9.4.1.53 If Max VHT NSS is 5, is this combination allowed? If so, does it mean 8? Add a "NOTE Max NSS is equal to equal to double Max VHT NSS, limited to 8." at the end of the table Revise – TGmc editor shall add as a note at the end the table, the following text: “NOTE Max NSS is equal to double Max VHT NSS, limited to 8.” 7683 Mark If Max VHT NSS is 5, is this combination allowed? If so, does it mean 8? Add a "NOTE Max NSS is equal to equal to double Max VHT NSS, limited to 8." at the end of the table Revise – TGmc editor add as a note at the end the table, the following text: “NOTE Max NSS is equal to double Max VHT NSS, limited to 8.” 7684 Mark If Max VHT NSS is 5, is this combination allowed? If so, does it mean 8? Add a "NOTE Max NSS is equal to equal to double Max VHT NSS, limited to 8." at the end of the table Revise – TGmc editor add as a note at the end the table, the following text: “NOTE Max NSS is equal to double Max VHT NSS, limited to 8.” NEEDS TO BE RE-RESOLVED as shown: 7189 Rison R.7 It says "s/b" Change to "seconds/bit" for consistency with lines Revised – the are incorrect, tgmc editor shall change the description to “is dimensionless” Discussion:
None. Proposed changes As Shown: CID 7113, 7190, 7192, 7195, 7193, 7197, 7198, 7190, 7199 R.7 Calculating Estimated Throughput TGmc editor: within the equation for ESTAirtimeFraction change the term AMSDUB to A_MSDU_B TGmc editor: change the description of ESTAirtimeFraction to be “is dimensionless” TGmc editor: in the equation for MPDU_pA_MPDU, change the vertical bars to be ceiling symbols TGmc editor: in the equation for MPDU_pA_MPDU, change the term PPDUR to “PPDUR x DataRate” TGmc editor: change the definition of MPDU_pA_MPDU to “is dimesionless” TGmc editor: change the term MPDU_SS to MPDUSS throughout R.7 TGmc editor: change the definition of MPDUSS (formerly MPDU_SS) to “is in units of seconds” TGmc editor: change the definition of PPDUR to be “is the PPDU Payload duration and is in units of seconds” TGmc editor: change the definition of DataRate to include “and is in units of b/s” at the end of the definition TGmc editor: change the equation for PPDUDur to include “+ PHDUR” TGmc editor: within the equation for PPDUDur change the term MPDU_pPPDU to MPDUpPPDU TGmc editor: change all variable names that include _Dur to use subscript “Dur” instead of the non-subscripted “_Dur” TGmc editor: within the equation for MACHdr, remove the text “, e.g., 50” TGmc editor: throughout R.7, change A_MSDUB,TX to A_MSDU_BTX TGmc editor: throughout R.7, change A_MSDUB,RX to A_MSDU_BRX