[STDS-802-16] Proposed PAR: Corrigendum to IEEE Std 802.16-2004
Folks,
There has been a lot of discussion about how to do:
(a) Corrections to 802.16-2004
(b) Enhancements to 802.16-2004
Here are my views.
(a) Corrections to 802.16-2004
A Corrigendum is "a document that only contains substantive
corrections to an existing IEEE standard". It's a maintenance
document. Corrections would fix editorial errors, inconsistencies,
and ambiguities. A Corrigendum PAR would let us write and ballot
those corrections very quickly and get them over with. Back on June 23
<http://ieee802.org/16/arc/802-16list2/msg01649.html>, I opened up a
maintenance process and said I'd schedule time at the Opening Plenary
to vote on a Corrigendum PAR.
In order to move the process forward, I have drafted a PAR for a
Corrigendum to IEEE Std 802.16-2004:
<http://ieee802.org/16/docs//04/C80216-04_16.pdf>
I'd like us to consider this on 12 July.
(b) Enhancements to 802.16-2004
We do not have a project to do enhancements to 802.16-2004, except
for mobile enhancements within the scope of 802.16e. As I see it, if
you want to make other improvements to 802.16-2004, you will have to
wait. We do not work in continual improvement process. We complete a
project and move on to the next project. We have just completed
802.16-2004, and I don't know if the WG is ready to reopen it and
rewrite it again.
Roger
>While we are still awaiting final approval of P802.16-REVd/D5, we
>have heard suggestions that there may be some bugs in it.
>
>Is this surprising? No. We could have balloted up to D10, and I
>suspect we'd still have errors. That's what you get in a complex,
>915-page technical specification.
>
>To handle the inevitable errors, I suggest that we open a PAR for a
>Corrigendum ("a document that only contains substantive corrections
>to an existing IEEE standard"). I'll schedule time to vote on this
>issue of initiating this PAR at Session #32's Opening Plenary.
>
>At this point, I'd like to open up a maintenance process to start
>collecting reports of errors so that we get them recorded without
>losing them. I plan to schedule time at Session #32 to review these
>inputs.
>
>Please submit your report, in Commentary format, to:
>http://maint.wirelessman.org
>
>If you have associated contributions, please submit them to the same
>upload area using a TGd-style contribution number and following the
>TGd numerical sequence. Once we have a formal process going, we'll
>switch to a new numbering sequence.
>
>The deadline is 6 July AOE.
>
>Roger