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

[STDS-802-11] REVme: resolution for CID 3000

--- This message came from the IEEE 802.11 Working Group Reflector ---

Hi All,

 

TGm had discussed the proposed resolution for CID 3000 (DCN: 11-22/2208) during the January meeting but could not come to an agreement. This email is a follow-up to continue with the discussion and make progress towards a suitable resolution.

 

CID

Commenter

Pg/Ln

Section

Comment

Proposed Change

3000

Abhishek Patil

574.35

9.2.2

What is the purpose of the paragraph starting line 36? Per the previous paragraph (line 30), a reserved field/subfield is set to 0 by the transmitter and is ignored by the receiving STA. In addition, the 2nd sentence of paragraph starting line 36 seems to conflict with the receiver side requirement on line 30 (i.e., ignore vs undefined).

Either delete the paragraph starting line 36 or harmonize it with that on line 30.

 

Brief summary of the discussion (during the Jan meeting):

The first paragraph is meant to cover the case of reserved (sub)­fields while the second paragraph (being modified) is intended to cover the case of reserved values. The proposal was to modify the second paragraph to clarify reserved values carried in non-reserved (sub)field. The group could not converge on a suitable text. Two alternatives were considered.

 

--------

9.2.2 Conventions[3000]

TGm editor: Please update the following paragraphs in this subclause as shown below:

Reserved fields and subfields defined in this clause are set to 0 upon transmission and are ignored upon reception.

NOTE 2—This applies to reserved fields and subfields in MAC headers. Reserved fields and subfields in PHY headers might be set to a nonzero value upon transmission, and might not be ignored upon reception.

Reserved field and subfield values are not used upon transmission. Upon reception of a reserved field or subfield value, the behavior is undefined. Proposed text: Reserved values are not used in non-reserved fields and subfields upon transmission. Upon reception of a reserved value in a non-reserved field or subfield, the behavior is undefined. Alternate text: In non-reserved fields and subfields, reserved values result in undefined behavior upon reception.

 

--------

 

Could you please review the proposed text and let me know if you have a preference or suggest an alternate?


Regards,
Abhi

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