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

[STDS-802-11-TGM] Updated REVmd MAC ad hoc resolutions: MOTION for "Insufficient detail" rejections



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

All,

 

I’ve uploaded another update to the REVmd MAC ad hoc file, here: https://mentor.ieee.org/802.11/dcn/17/11-17-0927-62-000m-revmd-mac-comments.xls

 

This revision includes a tab with the CIDs listed below (“Motion MAC Insufficient detail”) as ready for motion with a rejection that the commenter fails to provide sufficient details to resolve the comment.  This is expected to be put to MOTION on this Friday’s REVmd CRC telecon (July 24).  If anyone has comments/concerns about this resolution for the comments, please let me know before the call.

 

Thanks.  Mark

 

CID

Commenter

Page

Line

Clause

Resn Status

Assignee

Comment

Proposed Change

Resolution

4078

Levy, Joseph

2176.00

14

11.2

J

Joseph Levy

The power save mode should describe the behavior of the AP, e.g. when it buffers frames, when it is allowed to transmit, and what it is allowed to transmit.  A STA that has activated PS mode is not required to be  any given state, as the STA can choose to transmit PPDUs at any time and can be in either awake or doze state as it chooses, independent of the agreed scheduled PS state (awake or doze).

As described in the comment. Detailed proposed changes will be supplied in a contribution.

REJECTED (MAC: 2020-07-21 17:56:04Z): The comment fails to identify changes in sufficient detail so that the specific wording of the changes that will satisfy the commenter can be determined.

4079

Levy, Joseph

2176.00

14

11.2

J

Joseph Levy

It is impossible to require a STA to receive a PPDU.  Hence, the STA behavior of "listening" or "receiving" should not be specified.  The specification should only specify: when the AP shall/may transmit to a STA, what the AP shall/may transmit, and what a STA does when it receives a transmission. Also the specification should define AP behavior regarding what the AP should do if a STA in PS mode does not respond to PPDUs transmitted by the AP during the STA's scheduled awake time.

As described in the comment. Detailed proposed changes will be supplied in a contribution.

REJECTED (MAC: 2020-07-21 17:56:23Z): The comment fails to identify changes in sufficient detail so that the specific wording of the changes that will satisfy the commenter can be determined.

4084

Levy, Joseph

2176.00

14

11.2

J

Joseph Levy

The specification currently uses PS mode to describe two concepts:  A STA that has activated PS mode requiring the AP to buffer PPDUs for the STA in accordance with the agreed Awake and Doze schedule and to define the type of PS that has been configured for the STA and AP pair during association/reassociation in a BSS or between STAs in an IBSS.  These two concepts are not the same and should not use the same term.  I suggest that the PS mode should be used to describe the particular PS setting negotiated between the STA and AP or between STAs and that a different term be used to describe a STA that has activated its PS mode and requires the AP or other STA to buffer PPDUs and only transmit them as defined by the agreed PS mode.  Statements such as setting the PS bit to 1 activates the PS mode and setting it to 0 de-activates the PS mode would make.  Hence the statement "a STA in PS mode"  should be replaced by "a STA with PS active" or something similar.

As described in the comment. Detailed proposed changes will be supplied in a contribution.

REJECTED (MAC: 2020-07-21 17:56:41Z): The comment fails to identify changes in sufficient detail so that the specific wording of the changes that will satisfy the commenter can be determined.

4264

RISON, Mark

1724.00

15

10.3.1

Mark Rison

Having stuff in DCF clauses that applies to EDCA (especially stuff that cannot apply to DCF, e.g. stuff related to HT/VHT) is very confusing

Move EDCA-only stuff to EDCA clauses.  Move stuff that is common to both DCF and EDCA to a common clause

REJECTED (MAC: 2020-01-31 16:36:04Z): The comment fails to identify changes in sufficient detail so that the specific wording of the changes that will satisfy the commenter can be determined.

4343

RISON, Mark

1052.00

49

9.4.2.21.6

J

Mark Rison

"The Antenna ID field(M101) is set to the identifying number for the antenna(s) used for this measurement.
The antenna ID(#1516) is defined in 9.4.2.39 (Antenna element)." but for things like 9.4.2.21.6 Noise Histogram report then (a) 9.4.2.39 only allows for a single DMG antenna ID but a noise histogram might involve multiple DMG antennas (b) 9.4.2.39 talks of the (DMG) antenna(s) used to receive an earlier frame" but no frame is being received during IPI measurement

As it says in the comment

REJECTED (MAC: 2020-07-20 19:05:39Z): The comment fails to identify changes in sufficient detail so that the specific wording of the changes that will satisfy the commenter can be determined.

4562

RISON, Mark

11

J

Mark Rison

Discussions of the Address 2 (or A2) or Address 3 (or A3) fields should not be in Clause 11 since already in 9.3.3.1

As it says in the comment

REJECTED (MAC: 2020-07-20 19:06:09Z): The comment fails to identify changes in sufficient detail so that the specific wording of the changes that will satisfy the commenter can be determined.

4754

RISON, Mark

10.6

J

Mark Rison

The multirate rules are an impenetrable mess.  It's impossible to determine whether they are complete, let alone whether they are correct

Rewrite as a flowchart or table, so that it can be seen that the rules are complete and correct

REJECTED (MAC: 2020-07-20 18:47:14Z): The comment fails to identify changes in sufficient detail so that the specific wording of the changes that will satisfy the commenter can be determined.

 


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