doc.: IEEE /0828r0 Submission May 2007 Harry Worstell, AT&TSlide 1 Procedural Clarification Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at. ieee802.org/guides/bylaws/sb-bylaws.pdf Date: Authors:

doc.: IEEE /0828r0 Submission May 2007 Harry Worstell, AT&TSlide 2 Abstract This is a clarification of the procedural matter concerning passing output documentation to higher level groups and its impact on Task Groups and the Working Group.

doc.: IEEE /0828r0 Submission May 2007 Harry Worstell, AT&TSlide 3 1. Passing output documentation, such as Drafts, to higher level groups (i.e. Task Group to Working Group) requires the sending group to vote on the documents accuracy and content prior to passing the document forward. IEEE Policies and Procedures Section 2.9 Draft WG Balloting A draft must successfully pass a WG letter ballot before it can be forwarded to the 802 EC for approval for Sponsor Group voting. 2. If the Task Group can not vote on an output document during an Session, a 15 day procedural Working Group letter ballot must be conducted to pass the document forward for balloting on the draft. ( Draft Standard Balloting Requirements Before a draft is submitted to WG letter ballot, it shall meet all the following requirements: The TG must approve the draft by vote with at least 75% consensus, indicating the TG has conducted a technical review of the draft, and believes the draft is technically complete, and ready for WG approval e.g. no place holders or notes for future action, editing, or clarifications.) 3. Once the Draft has been passed to the Working Group, the Task Group has no further action on that draft as it is the property of the Working Group. 4. If the Draft fails to achieve the required 75% threshold for passing, the Working Group forwards the Draft back to the Task Group for further consideration.

doc.: IEEE /0828r0 Submission May 2007 Harry Worstell, AT&TSlide 4 5. Once the Draft passes the 75% threshold for approval, the Chair of the Working Group will continue to have recirculation ballots until no new “NO” votes with technical comments are received. During this period, the Working Group Chair will setup a Working Group Comment Resolution Committee to consider comments from the recirculation ballots. Typically this is the Task Group that generated the draft. 6. If the WG Comment Resolution Committee completes their work prior to the end of a Working Group session and the Working Group votes on and passes the comment resolution document but does not have time to complete the update of the Draft, the Draft may be updated after the close of the session and a letter ballot can be issued without a 15 day procedural ballot as the Draft is not being forwarded to a higher level organization until after the ballot has completed and the draft approved per the 802 Policies and Procedures.

doc.: IEEE /0828r0 Submission May 2007 Harry Worstell, AT&TSlide Template Instructions 3/4 PowerPoint Submission Preparation Summary: –Things to do:7 –Fields to fill in:12 5. Once the Draft passes the 75% threshold for approval, the Chair of the Working Group will continue to have recirculation ballots until no new “NO” votes with technical comments are received. During this period, the Working Group Chair will setup a Working Group Comment Resolution Committee to consider comments from the recirculation ballots. Typically this is the Task Group the generated the draft.

doc.: IEEE /0828r0 Submission May 2007 Harry Worstell, AT&TSlide Template Instructions 4/4 Recommendations –a) Always create a new presentation using the template, rather than using someone else's presentation. –b) For quick and easy creation of new submissions, place the template files in the template folder area on your computer. Typical locations are: c:\Program Files\Microsoft Office\Templates\802.11, or c:\Documents and Settings\User Name\Application Data\Microsoft\Templates\ –To create a new submission from within PowerPoint, menu select File, New, then select the appropriate template file. –c) When you update or revise your presentation, remember to check all 6 fields in steps 5 and 6 for the correct values. –rev: de

doc.: IEEE /0828r0 Submission May 2007 Harry Worstell, AT&TSlide 7 [begin placing presentation body text here]

doc.: IEEE /0828r0 Submission May 2007 Harry Worstell, AT&TSlide 8

doc.: IEEE /0828r0 Submission May 2007 Harry Worstell, AT&TSlide 9 References