|
-1
|
22163
|
|
|
|
Per the definition of an antenna connector there is only ever one for tx and one for rx
|
In 9.2.4.6a.1 TRS Control change "combined transmit power at the antenna connectors of all the transmit antennas" to "power at the transmit antenna connector". In
9.3.1.22.1 General change "combined transmitpower at the antenna connectors of all the transmit antennas used to transmit the Trigger frame" to "power at the transmit antenna connector"; "averagedover the AP's antenna connectors" to "averagedover the AP's
antennas". In 9.3.1.22.9 NDP Feedback Report Poll (NFRP) variant change "receiver's antenna connector(s)" to "receiver's receive antenna connector". In 3.2 (2x) and 9.4.2.248 HE Operation element and 26.17.7 Co-hosted BSSID set change "antenna connectors"
to "receive and transmit antenna connectors". In 11.10.14 Multiple BSSID set (5x) change "antenna connector" to "receive and transmit antenna connectors". In 26.10.2.4 Adjustment of OBSS PD and transmit power and 26.10.2.5 OBSS PD SR transmit power restriction
period (2x) and 26.10.3.3 SRP-based spatial reuse backoff procedure change "output of the antenna connector" to "transmit antenna connector". In 26.10.3.2 SRP-based spatial reuse initiation change "RSSI at the antenna connector(s)" to "RSSI at the receive
antenna connector". In 26.10.3.4 UL Spatial Reuse subfield of Trigger frame change "total power at the antenna connector(s)" to "total power at the transmit antenna connector". In 27.3.14.2 Power pre-correction change "target receive signal power of the HE
TB PPDU averaged over the AP's antennaconnectors" to "target receive signal power of the HE TB PPDU at the AP's receive antennaconnector" and "antenna connector(s)" to "receive antenna connector". In 27.3.14.3 Pre-correction accuracy requirements change "support
per chain max(P-32, -10) dBm as the minimum trans-mit power, where P is the maximum power, in dBm, that the STA can transmit at the antenna connector ofthat chain" to "support max(P-32, -10) dBm as the minimum transmit power, where P is the maximum power,
in dBm, that the STA can transmit at the transmit antenna connector" and "at the STA's antenna connector" to "at the STA's receive antenna connector". In 27.3.19.1 General change "the antenna connectors" to "the receive antenna connector"
|
|
EDITOR
|
|
-1
|
22414
|
|
|
|
CID 21012. The contradiction identified in this comment is not addressed by the resolution. Should state that a full-width transmission is an RU, at least
|
State that a full-width transmission is an RU
|
|
EDITOR
|
|
-1
|
22413
|
|
|
|
CID 21012. The contradiction identified in this comment is not addressed by the resolution
|
State that a full-width transmission is an RU, and then simplify things like "HE-MCSs for 242-tone RU and non-OFDMA 20 MHz, NSS = 1" to "HE-MCSs for 242-tone RU,
NSS = 1"
|
|
EDITOR
|
|
-1
|
22392
|
|
|
|
CID 20760. It needs to be specified (cf. "If the Beamformed field in HE-SIG-A of an HE sounding NDP is 1, then the receiver of the HE soundingNDP should not perform
channel smoothing when generating the compressed beamforming feedback report." in 27.3.16 HE sounding NDP)
|
At the end of the row for Beamformed in Table 27-18--HE-SIG-A field of an HE SU PPDU and HE ER SU PPDU and Table 27-28--User field format for a non-MU-MIMO allocation.
add "If this is set to 1, the receiver of the PPDU should skip three times and say yahoo."
|
|
EDITOR
|
|
-1
|
22415
|
|
27
|
|
CID 21020. Resolution claims that "The current note for parameter of "CH_BANDWIDTH" for HE_TB PPDU as in Table 27-1 has addressed the comment." but it hasn't, since
the comment was about adding to the NOTE!
|
In the NOTE for CH_BANDWIDTH in Table 27-1 append ", which is in the TXVECTOR parameter RU_ALLOCATION"
|
|
EDITOR
|
|
-1
|
22418
|
|
27
|
|
CID 20899. The resolution doesn't seem to address the comment
|
In Table 27-1, after "For an HE TB PPDU, [...] MU in the RXVECTOR column indicates the parameter is not present" append " (the receiver knows the values since they
were specified in the triggering PPDU)"
|
|
EDITOR
|
|
-1
|
22382
|
|
27.2.2
|
|
CID 20707. "SCRAMBLER_INITIAL_VALUE" would be clearer as "SCRAMBLER_INITIALIZATION_FIELD", since what the scrambler initial value is *not* what is being communicated;
what is being communicated is the (scrambled) value of the Scrambler Initialization field. The resolution said "The group had discussion as in 11-18/0754r0 and agreed to name the parameter as "SCRAMBLER_INITIAL_VALUE." but that document is not about the name
of the parameter, it's about what it contains in the TXVECTOR. Note that as Table 27-1 indicates, this parameter "In TXVECTOR, if present, indicates the value of the ***Scram-bler Initialization field*** in the SERVICE field, after scrambling.In RXVECTOR,
indicates the value of the ***Scrambler Initial-ization field*** in the SERVICE field, prior to descrambling." (my emphasis)
|
Change "SCRAMBLER_INITIAL_VALUE" to "SCRAMBLER_INITIALIZATION_FIELD" throughout
|
|
EDITOR
|
|
-1
|
22036
|
116.40
|
9.3.1.22.1
|
|
For TX of HETB, the logic on setting PE Disambiguity is incomplete. From P116L40, PE Disambiguity is set according to (27-118). From P629L63, (27-118), PE Disambiguity
= f(TXTIME) where it is indicated P630L5 that TXTIME is defined in 27.4.3. In 27.4.3, at P674L43, TXTIME = g(nSym). From P675L1, it is indicated that the calculation for nSym is found in 27.3.11.5.5. In 27.3.11.5.5, BUT this only defines how non-AP STAs may
obtain nSym, not APs. There is a NOTE that an AP is free to calculate any value for Pre-FEC Padding factor and LDPC Extra Symbol Segment fields, but this note is silent re nSym.
|
Perhaps include nSym in the note of the parameters that the AP is free to select? But does this ever create a situation where the client might calculate a 20us PE
(for instance?)
|
|
EDITOR
|
|
-1
|
22459
|
384.19
|
27.2.2
|
|
Line 10 states ".... the pre-HT modulated fields might be beamformed." Should it be a definite statement like " ... is beamformed?" If not, please add the conditions
that is not.
|
Please clarify as in the comment line if agreed.
|
|
EDITOR
|
|
-1
|
22458
|
476.22
|
27.2.2
|
|
What is "a higher frequency?"
|
Need to clarify what "a higher frequency" is with respect to.
|
|
EDITOR
|
|
-1
|
22554
|
477.10
|
27.2.2
|
|
There are two instances of INACTIVE_SUBCHANNELS in the TXVECTOR/RXVECTOR - P477L10 and P486L35.
|
Merge the two instances of INACTIVE_SUBCHANNELS into one.
|
|
EDITOR
|
|
-1
|
22210
|
482.43
|
27.2.2
|
|
CID 20477: again, the concept of "global" numbering of spatial streams is undefined
|
Delete "globally " in "spatial streams are globally numbered starting from 1" in the referenced subclause
|
|
EDITOR
|
|
-1
|
22162
|
487.10
|
27.2.3
|
|
Many of the parameters of Table 27-2--TRIGVECTOR parameters don't actually seem to have any behaviour associated with them (e.g. HE_MCS_LIST, UL_DCM_LIST)
|
Associate some behaviour to each of the parameters
|
|
EDITOR
|
|
-1
|
22295
|
488.19
|
27.2.3
|
|
The AID12 in the Trigger frame can only contain values up to 2007 when identifying one or more STAs, so the AID12_LIST actually is a list of AID11s
|
In Table 27-2--TRIGVECTOR parameters change AID12_LIST to AID11_LIST. At the end of the NOTE add "The MSB of the AID is always 0."
|
|
EDITOR
|
|
-1
|
22462
|
534.13
|
27.3.8
|
|
Is N_STS defined for an HE MU PPDU?
|
Please update as needed.
|
|
EDITOR
|
|
-1
|
22044
|
539.15
|
27.3.9
|
|
Kr is used in an equaton, and in the description of equaiton parameters below the equation, but is itself not defined below the equation.
|
To keep it simple, change to "|Kr| is the cardinality of the set of subcarriers Kr (defined in relation to Equations (27-3) and (27-4))"
|
|
EDITOR
|
|
-1
|
22029
|
545.05
|
27.3.10.5
|
|
aSignalExtension definition refers to Table 19-25, but that only defines aSignalExtension for 2.4 and 5 GHz (i.e. not 6 GHz)
|
Insert Table 19-25 into this draft and change "0 ┬╡s when operating in the 5 GHz band" to "0 ┬╡s when operating other than in the 2.4 GHz band"
|
|
EDITOR
|
|
-1
|
22448
|
579.19
|
27.3.10.8.5
|
|
N_SR is 28 for HE-SIG-B from the equation notation using Kshift(i_bw). Suggest keeping the same practice as HE-SIG-A (collectively Pre-HT modulated fields) to write
out the number 28 in the equation instead of pointing to Table 21-5.
|
Change N_SR to 28 if agreed.
|
|
EDITOR
|