Re: [STDS-802-11-TGM] CID 2056

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

All,

I have no strong opinion about option 1 or 2. I can live with either.

If we go with option 2, I would change the changes marked in yellow below (the “MAC” ones), to:

Change “data stream” to “MSDUs” (and change “uses” to “use”) at REVme D1.1

P521L30

P522L30

The context here is that this is the description of the Direction parameter to the DELBA primitives. The current text says (highlighting the replacement spot):

Specifies if the MAC entity initiating the MLMEDELBA.

request primitive is the originator or the recipient of the data stream that uses the block ack agreement.

I do not want to introduce a new concept/term, “MSDU stream” as suggested below (which will be comment-bait for asking for a definition of this term). I think in this context simply saying the originator or recipient of the MSDUs that use the block ack agreement is sufficient and clear.

Mark

From: Youhan Kim <youhank@xxxxxxxxxxxxxxxx>
Sent: Tuesday, March 29, 2022 10:58 AM
To: STDS-802-11-TGM@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGM] CID 2056

--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---

Merging threads:

To expedite the discussion on the next call, here are two potential options.

I am fine with option 1
I am fine with the non-DMG non-S1G PHY related parts of option 2 (the ones w/o any color highlighted)

There are MAC related changes which MAC folks should confirm (I highlighted these with yellow)
There is a DMG PHY related change which DMG folks should confirm (I highlighted this with blue)
There is a S1G PHY related change which S1G folks should confirm (I highlighted this with green)

Thanks

Youhan

Option 1:

REJECTED

Data stream does not always mean PSDU.

Option 2 (Latest proposal from Mark Rison + minor updates from Youhan. Requires more work by others – the ones highlighted in colors):

REVISED

Change “data streams” to “PSDUs” at REVme D1.1

P199L61

P200L54

Change “data stream” to “PSDU” at REVme D1.1

P3514L54

P3624L2

Change “data stream” to “MSDU stream” at REVme D1.1

P521L30

P522L30

Change “data stream” to “bit stream” at REVme D1.1

P3677L5

Change “maximum duration of the data stream” to “duration of the PPDU” at REVme D1.1

P3794L60

P4487L43

Change “data stream” to “PPDU” at REVme D1.1

P3992L60

From: M Montemurro montemurro.michael@xxxxxxxxx
Sent: Monday, March 28, 2022 2:10 PM
To: Jon Rosdahl jrosdahl@xxxxxxxx
Cc: Youhan Kim youhank@xxxxxxxxxxxxxxxx; STDS-802-11-TGM@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGM] CID 2056

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Hi Jon,

Could you add Youhan's comments in the adhoc notes. Given that this is ready for motion already, we can revisit at the beginning of the next call.

Thanks,

Mike

From: Mark Rison <m.rison@xxxxxxxxxxx>
Sent: Monday, March 28, 2022 11:32 AM
To: Youhan Kim <youhank@xxxxxxxxxxxxxxxx>; STDS-802-11-TGM@xxxxxxxxxxxxxxxxx
Subject: RE: CID 2056

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Thanks for looking at these, Youhan.

So maybe the answer is to change "data stream" as follows (my D1.1 doesn't

have the same locations as Youhan's, though):

Location	Youhan’s Feedback	Change "data stream" to
P198L61 P199L53 P3512L54 P3622L2	“Data stream” is equivalent to PSDU here IMO	199.61, 200.54 PSDU
P203L25	“Data stream” means “spatial streams” here, not PSDU	204.24 <no change, it's OK here>
P520L57 P521L59	I don’t know what the is exact definition of “data stream” here is (context = DELBA)	521.30, 522.30 MSDU stream (or change "of the data stream that uses the block ack agreement" to "of the block ack agreement")
P3097L37	I don’t know what the is exact definition of “data stream” here is (context = WEP)	3099.37 <ignore, WEP is deprecated>
P3583L14	“Data stream” is not PSDU here. Rather, this is the LDPC encoder output.	3585.13 no change, it's OK here
P3675L5	“Data stream” is not PSDU here. Rather, this is the RS encoder output.	3677.5 bit stream (to match surrounding text)
P3711L20 (Figure 21-10)	“Data stream” is not PSDU here. Rather, this is the BCC encoder input or output (not clear which one on a quick glance), where there are N_ES parallel BCC encoders. Also, prior to BCC encoder, PHY has added PHY padding on top of PSDU.	3713.20 no change, it's OK here
P3551L58 P3711L16 (Figure 21-10)	“Data stream” is not PSDU here. Rather, this corresponds to PSDU + PHY padding.	3713.16 no change, it's OK here
P3792L59 P4485L43	PPDU seems to be the more correct interpretation of “Data stream” here rather than PSDU.	3794.59, 4487.43 PPDU
P3990L60	This is S1G, and I don’t know whether “data stream” here is equivalent to PSDU.	3992.60 PPDU

Also change "data stream" to "PPDU" at 3514.54, 3624.2

and change "data string" to "data stream" at 3479.8, 3553.53, 3554.9

but otherwise leave "data stream" a few lines down in each case.

Thanks,

Mark

Mark RISON, Standards Architect, WLAN English/Esperanto/Français

Samsung Cambridge Solution Centre Tel: +44 1223 434600

Innovation Park, Cambridge CB4 0DS Fax: +44 1223 434601

ROYAUME UNI WWW: http://www.samsung.com/uk

From: Youhan Kim <youhank@xxxxxxxxxxxxxxxx>
Sent: Monday, 28 March 2022 18:42
To: STDS-802-11-TGM@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGM] CID 2056

--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---

Hi, Mike, Mark Rison and all,

At the end of today’s TGme teleconference, I was asked whether I had any comments or objections on marking CID 2056 as ACCEPTED. I didn’t have any comments at the time as I was not familiar with the CID and was not following the discussion on the call (sorry).

I have subsequently reviewed CID 2056, and do not feel ACCEPTED is the appropriate resolution.

CID	Commenter	Clause Number(C)	Page(C)	Line(C)	Comment	Proposed Change
2056	Mark RISON	3.2			There are about a dozen "data stream"s, but this term is not defined	Add a definition "data stream: A physical layer (PHY) service data unit (PSDU)."

There are 16 occurrences of “data stream(s)” in REVmd D1.1.

Location	Youhan’s Feedback
P198L61 P199L53 P3512L54 P3622L2	“Data stream” is equivalent to PSDU here IMO
P203L25	“Data stream” means “spatial streams” here, not PSDU
P520L57 P521L59	I don’t know what the is exact definition of “data stream” here is (context = DELBA)
P3097L37	I don’t know what the is exact definition of “data stream” here is (context = WEP)
P3583L14	“Data stream” is not PSDU here. Rather, this is the LDPC encoder output.
P3675L5	“Data stream” is not PSDU here. Rather, this is the RS encoder output.
P3711L20 (Figure 21-10)	“Data stream” is not PSDU here. Rather, this is the BCC encoder input or output (not clear which one on a quick glance), where there are N_ES parallel BCC encoders. Also, prior to BCC encoder, PHY has added PHY padding on top of PSDU.
P3551L58 P3711L16 (Figure 21-10)	“Data stream” is not PSDU here. Rather, this corresponds to PSDU + PHY padding.
P3792L59 P4485L43	PPDU seems to be the more correct interpretation of “Data stream” here rather than PSDU.
P3990L60	This is S1G, and I don’t know whether “data stream” here is equivalent to PSDU.

So, my suggested resolution to CID 2056 is:

REJECTED

Data stream does not always mean PSDU.

Thanks.
Youhan

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