Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-11-TGAX] Comment assignment



Reassigned as suggested

 

-Robert

 

From: sun.bo1@xxxxxxxxxx [mailto:sun.bo1@xxxxxxxxxx]
Sent: Tuesday, November 05, 2019 5:36 PM
To: Stacey, Robert <robert.stacey@xxxxxxxxx>
Cc: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: Re:[STDS-802-11-TGAX] Comment assignment

 

Hello, Robert,

 

Among all those CIDs, some adresses issues resolved in the past LB. I'd suggest to re-assign these CIDs to original assignees:

CID 22413/22414 -> Old CID 21012: Osama

CID 22392 -> Old CID 20760: Ross Yu Jian

 

3 CIDs could be re-assigned to Yan:

CID 22036: Yan Zhang

CID 22462: Yan Zhang

CID 22044: Yan Zhang

 

1 CID could be re-assigned to Sameer:

CID 22163: Sameer

 

1 CID could be re-assgined to Brian:

CID 22448: Brian Hart

 

And I will take the rest CIDs:

CID 22415 -> Old CID 21020: Bo

CID 22418 -> Old CID 20899: Bo

CID 22382 -> Old CID 20707: Bo

CID 22210 -> Old CID 20477: Bo

CID 22459: Bo

CID 22458: Bo

CID 22554: Bo

CID 22162: Bo

CID 22295: Bo

CID 22029: Bo

 

 

 

Best Regards,

Bo

 

原始邮件

发件人:Stacey,Robert <robert.stacey@xxxxxxxxx>

收件人:孙波10013985;

20191105 02:06

RE: Re:[STDS-802-11-TGAX] Comment assignment

Hi Bo,

 

Reassigned as suggested for Xiaogang, Yan, Sameer and Jianhan.

 

I have 22383 assigned to Po-Kai.

 

I have some additional ones assigned to you (some editorials that are technical or “big”). Can you look at these and let me know who should be the assignee:

 

comments

Selected

CID

Page

Clause

Resn Status

Comment

Proposed Change

Resolution

Owning Ad-hoc

-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

 

-Robert

 

 

From: sun.bo1@xxxxxxxxxx [mailto:sun.bo1@xxxxxxxxxx]
Sent: Wednesday, October 30, 2019 6:02 PM
To: Stacey, Robert <robert.stacey@xxxxxxxxx>
Cc: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: Re:[STDS-802-11-TGAX] Comment assignment

 

Hello, Robert, 

 

There're 26 PHY CIDs under my name. After checking each of them and confirming with people who are more familiar with those topics, some of these CIDs could be re-assigned as below:

 

Xiaogang: CID 22030/22031/22032

Yan Zhang: CID 22033/22034/22035/22037

Sameer: CID 22328/22329/22331/22344/22350/22393

Jianhan: CID 22411

 

And I will propose resolutions of the rest 12 CIDs, plus one more (CID 22383) re-assigned to me by Po-kai.

 

Best Regards,

Bo

 

原始邮件

发件人:Stacey,Robert <robert.stacey@xxxxxxxxx>

日期 20191030 05:00

[STDS-802-11-TGAX] Comment assignment

Hello All,

 

Following today’s telecon, all comments have an assignee. See spreadsheet here:https://mentor.ieee.org/802.11/dcn/19/11-19-1782-02-00ax-comments-on-d5-0.xlsx

 

Brian, I still have you listed for 6 GHz Band Security, but we will reassign when Alfred provides a name.

 

Following the call I assigned the remaining few comments we did not review. These were mostly Mark’s comments that referenced an old CID for which the topic was not clear.

 

Some of the assignees were not on the call or have not explicitly volunteered for their assignment. I will contact you separately to verify that you can provide resolutions.

 

The assignees are as follows:

Assignee

Count of CID

Abhishek Patil

50

Multi-BSS

14

UORA

14

BSS color

22

Alfred Asterjadhi

74

(blank)

16

TWT

32

Queue Size

3

Supported Channel Width

4

BSR

2

In-band discovery

17

Bin Tian

2

MCS Tables

2

Bo Sun

26

(blank)

4

HE PHY

22

Brian Hart

18

PHY HE-SIG-B

17

6 GHz Band Security

1

Editor

183

Editorials

181

per20bitmap

1

BW signaling DSSS/CCK

1

Eldad Perahia

42

CA Doc

42

George Cherian

12

Ack procedure

12

Jarkko Kneckt

5

OM Control

3

TSPEC

2

Jianhan Liu

6

HE-SIG-A

2

HE PHY

3

Partial AID

1

Kaiying Lv

5

QTP

5

Laurent Cariou

32

Spatial Reuse

1

OPS

10

MU EDCA

10

6 GHz channelization

3

6 GHz CCA threshold

1

Out of band discovery

7

Liwen Chu

29

Definitions

4

(blank)

8

A-MPDU operation

6

A-Control reserved

3

BSS transition

1

Beacons in 6 GHz band

3

Misc

4

Lochan Verma

2

(blank)

2

Mark Rison

1

AID 2045 in HE MU PPDU

1

Matt Fischer

3

Fragment Flush

1

Disable EDCA

1

Disallow Subchannels

1

Menzo Wentink

14

Sounding procedure

14

Ming Gan

4

Fragmentation

2

MU Cascading

2

Osama Aboul-Magd

2

(blank)

2

Po-Kai Huang

16

MU-RTS/CTS

2

NAV

4

Duration-based RTS/CTS

8

SM Power Save

2

Robert Stacey

1

per20bitmap

1

Srini Kandala

1

(blank)

1

Tianyu Wu

1

HE PHY

1

Yan Zhang

6

PHY Math

4

HE PHY

2

Yongho Seok

2

UL MU Power Capabilities

2

Youhan Kim

17

(blank)

2

Tx spectral mask

5

HE PHY

10

Zhou Lan

1

BQR

1

Pooya Monajemi

1

Reason Codes

1

Jonathan Segev

2

FTM

2

Grand Total

558

 

-Robert

 


To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1

 

 


To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1