Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
--- This message came from the IEEE 802.11 Working Group Reflector ---
Hi Robert,
What I mean is that if in an amendment or the editing process during publication introduces a change that was not intended, that is clearly an error within scope of the corrigendum. If an amendment makes a change intentionally, which is balloted and approved,
then it is wrong to try and change that in a corrigendum because we now disagree with that properly vetted change. It should be made via a new amendment or during the revision process.
My understanding when reading the corrigendum draft is that the inconsistency being fixed was introduced unintentionally by an amendment. In that context it makes sense. Your discussion cast some doubt in my mind. Which is probably due to me misunderstanding
what you meant. But If the change is driven by an external organization that decided what was done in the standards process was "wrong" and wants to change it, then it is not appropriate to use the corrigendum process IMO to make such a technical change to
the standard. It should be done via amendment or revision. It seemed like that is what you were saying. If I misunderstood, I'm wrong and of course apologize for any confusion my misunderstanding might have created.
So either I was wrong when I reviewed the draft the first time or wrong now, I guess. Trying to understand which 😉.
Thanks
Ben
From: Stacey, Robert <robert.stacey@xxxxxxxxx>
Sent: Wednesday, May 11, 2022 2:54 PM 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 ---
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>
--- 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>
--- 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
On Tue, May 10, 2022 at 7:27 PM Benjamin Rolfe <ben@xxxxxxxxxxxxxx> wrote:
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 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 |