Re: [STDS-802-11-TGAX] Order of information in some management frames

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

Ganesh,

The standard says that the order is strict:

Fields and elements appear in the specified, relative order, skipping fields or elements that are not present.(#1500)(#185) STAs that encounter an
element ID they do not recognize in the frame body of a received Management frame ignore that element
and continue to parse the remainder of the management frame body (if any) for additional elements with
recognizable element IDs.

But it also says that receivers are supposed to examine the entire frame.

However,

I have heard of implementations in the past which discard everything after they see the highest ordered item of which they are familiar.

I guess that you could say that those implementations are not compliant with the language quoted above, even though that language is not exactly normative.

But you could also say that mis-ordered elements are not compliant.

Matthew Fischer

Nice Guy

Broadcom Inc.

+1 408 543 3370 office

On Wed, Oct 28, 2020 at 10:12 AM Venkatesan, Ganesh <ganesh.venkatesan@xxxxxxxxx> wrote:

Hello Youhan:

I think you comment on the order is strictly from a spec-consistency perspective (not to have contradictory order in REVmd versus .11ax). However, the order in which elements are included in a frame is generally not an issue – as implementation would be parsing elements based element id (and extended element id, if it applies) and not based on the order.

Cheers --

ganesh

“It is amazing what you can accomplish if you don’t care who gets the credit.” – Harry Truman

From: *** 802.11 TGax - HEW - High Efficiency WLAN *** <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx> On Behalf Of Youhan Kim
Sent: Wednesday, October 28, 2020 7:46 AM
To: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGAX] Order of information in some management frames

Hi, Osama, Robert,

11ax D7.0 is adding new information/elements to AssocReq frames, etc., whose order is overlapping w/ those in REVmd D5.0.

For example, 11ax D7.0 is adding the HE Capabilities element is at order #45, Channel Switch Timing is at order #46, etc to the AssocReq frame. But REVmd D5.0 already has MSCS Descriptor as order #45.

Similar issues exist in AssocResp, ReassocReq and ReassocResp.

While there aren’t any comments submitted on D7.0 for these, I would suggest the group to address these issues for a smooth publication of IEEE 802.11ax. Is this something the Editor (Robert) could address as an editorial update, or do you need someone to submit a formal text update request document?

Thanks.

Youhan

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

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