Re: [STDS-802-11] Suggested P802.11-2020/Cor1 change

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

Hello Ben,

I’m not sure what you mean by “11ay inadvertently deviated from the base 802.11 standard”. That is exactly what all amendments are intended to do; modify and become part of the base standard.

The error here is that 11ay inadvertently used a value it should not have used - a value that had previously been allocated for use by an external standard. An error that became apparent only after publication and hence requiring a new project to correct it.

-Robert

From: Benjamin Rolfe <ben@xxxxxxxxxxxxxx>
Sent: Wednesday, May 11, 2022 1:46 PM
To: STDS-802-11@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11] Suggested P802.11-2020/Cor1 change

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

Jon,

Thank you for the explanation and background. I appreciate Robert's work and his explanation. The explanation caused me to doubt what I thought I had understood.

I had thought that 801.11-ay inadvertently deviated from the base 802.11 standard but the statement below suggests I was mistaken, suggesting that the inconsistency arose with an external specification which deviates from the 802.11 standard.

Which is it?

Thanks.

Thanks alsoto Robert for his excellent work BTW.

Ben

From: Jon Rosdahl <jrosdahl@xxxxxxxx>
Sent: Wednesday, May 11, 2022 11:54 AM
To: STDS-802-11@xxxxxxxxxxxxxxxxx <STDS-802-11@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11] Suggested P802.11-2020/Cor1 change

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

Ben,

The Corrigenda changes bit 6 to bit 11.

The debate is how to describe that in the document so that it makes sense.

The introductory paragraph is not part of the standard, but a description of how the change from 6 to 11 is displayed in the standard.

The roll-in of TGba which occurs after TGay is part of the "current baseline". The Corrigenda has to reflect that reality.

Hence on the very first page, it lists 802.11-2020, 802.11ax, 802.11ay, 802.11ba.

So the description explains how the change from bit 6 to 11 (the error that was the target of the corrigenda) is depicted.

Given the comments from the potential balloters, the update that Robert has made is reasonable and expected.

Jon

-----------------------------------------------------------------------------

Jon Rosdahl                         Engineer, Senior Staff
IEEE 802 Executive Secretary Qualcomm Technologies, Inc.
office: 801-492-4023                  10871 North 5750 West
cell:   801-376-6435       Highland, UT 84003

A Job is only necessary to eat!
A Family is necessary to be happy!!

On Tue, May 10, 2022 at 7:27 PM Benjamin Rolfe <ben@xxxxxxxxxxxxxx> wrote:

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

Hi Robert,

With that explanation, I would say the change is out of scope of a corrigendum. As described (inconsistency with an external spec) it is not an error in the standard, but a desired change.

If it had been consistent with the WFA specs prior to the revision and was inadvertently changed subsequently, then it might be within the definition of a corrigendum. That is not what the description below states, however, and taken as stated (which may not be what you meant?).

FWIW

Ben

From: Stacey, Robert <robert.stacey@xxxxxxxxx>
Sent: Tuesday, May 10, 2022 10:06 AM
To: STDS-802-11@xxxxxxxxxxxxxxxxx <STDS-802-11@xxxxxxxxxxxxxxxxx>
Subject: [STDS-802-11] Suggested P802.11-2020/Cor1 change

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

Hello Members,

On the Editors meeting yesterday, we reviewed the corrigendum. There was some concern that the origin of Table 9-321 onto which the changes are applied is not clear. In particularly, there was some confusion around why there are two rows with value 6.

One suggestion was to add more detail to the Introduction. I am proposing the following change (addition of the blue underline text):

This corrigendum to IEEE Std 802.11-2020 as amended by IEEE Std 802.11ax-2021, IEEE Std 802.11ay-
2021, and IEEE Std 802.11ba-2021 corrects an error in the position of the Protected Announce Support field
in the Extended RSN Capabilities field in the RSN Extension element. Bit position 6, as defined in

IEEE Std 802.11ay-2021, is in conflict with the allocation of bit position 6 to the Wi-Fi Alliance. This

corrigendum moves the Protected Announce Support field to position 11.

If you have any comments on this change, email me directly. I will compile the input and re distribute to the reflector.

Regards,

-Robert

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

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

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