Process for simultaneous balloting January 2006 doc.: IEEE 802.11-06/238r0 January 2006 Process for simultaneous balloting Date: 2006-01-27 Authors: Notice: This document has been prepared to assist IEEE 802.11. 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 802.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, 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 <stuart.kerry@philips.com> 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 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>. Simon Barber, Devicescape Software Inc Simon Barber, Devicescape Software Inc

Abstract This document describes a process for January 2006 doc.: IEEE 802.11-06/238r0 January 2006 Abstract This document describes a process for Preparing an Amendment when a Revision is in progress. Preparing an Amendment when another Amendment is in process and expected to be send for approval prior to it. These notes come from a conference call between the IEEE 802.11 WG CAC and the IEEE-SA on 27th Jan 2006. Present from IEEE 802.11 WG CAC Bruce Kramer, Clint Chaplin, Richard Paine, Bob O’Hara, Tom Siep (attending for Adrian Stephens), Donald Eastlake, Simon Barber Present from IEEE-SA Mike Kipness, Michael Fisher, Dave Ringle, Michelle Turner, Yvette Simon Barber, Devicescape Software Inc Simon Barber, Devicescape Software Inc

If your amendment is based on a revision that is in progress.. January 2006 doc.: IEEE 802.11-06/238r0 January 2006 If your amendment is based on a revision that is in progress.. Your document should be based on the latest draft of the revision text. Your document must then be sent for sponsor balloting with: the current, complete approved base text (prior to the revision), AND the latest draft of the revision AND the amendment being balloted. If a technical change happens in a part of the revision text that is relevant to the amendment then the amendment should be re-circulated. Relevant technical change is decided by the ballot resolution group (the TG itself in 802.11’s case) Simon Barber, Devicescape Software Inc Simon Barber, Devicescape Software Inc

When a revision and another amendment are in progress… January 2006 doc.: IEEE 802.11-06/238r0 January 2006 When a revision and another amendment are in progress… Your amendment should be based on the latest draft of the revision text AND the latest draft of all amendments expected to be approved prior to yours Your document must then be sent for sponsor balloting with all the below: the current, complete approved base text (prior to the revision) the latest draft of the revision the latest draft of all amendments expected to be approved before yours These amendments are only included if they make technical changes that are relevant to your amendment. your amendment. If a technical change happens in a part of the revision text or part of the amendment text expected to be approved prior to your amendment, and that change is technically relevant to your amendment then your amendment should be re-circulated. Relevant technical change is decided by the ballot resolution group (the TG itself in 802.11’s case) Simon Barber, Devicescape Software Inc Simon Barber, Devicescape Software Inc

When other amendments are in progress… January 2006 doc.: IEEE 802.11-06/238r0 January 2006 When other amendments are in progress… Your amendment should be based on the current, complete approved base text AND the latest draft of all amendments expected to be approved prior to yours Your document must then be sent for sponsor balloting with all the below: the current, complete approved base text the latest draft of all amendments expected to be approved before yours These amendments are only included if they make technical changes that are relevant to your amendment. your amendment. If a technical change happens in a part of the revision text or part of the amendment text expected to be approved prior to your amendment, and that change is technically relevant to your amendment then your amendment should be re-circulated. Relevant technical change is decided by the ballot resolution group (the TG itself in 802.11’s case) Simon Barber, Devicescape Software Inc Simon Barber, Devicescape Software Inc

Note: Approved means approved by REVCOM January 2006 doc.: IEEE 802.11-06/238r0 January 2006 Note: Approved means approved by REVCOM None of this process affects the need for drafts to be based ONLY on previously approved documents when they are finally presented to REVCOM. Simon Barber, Devicescape Software Inc Simon Barber, Devicescape Software Inc

References January 2006 January 2006 doc.: IEEE 802.11-06/238r0 Simon Barber, Devicescape Software Inc Simon Barber, Devicescape Software Inc