January 2006

Simon Barber, Devicescape Software Inc

Slide 1

doc.: IEEE 802.11-06/238r0

Submission

Process for simultaneous balloting

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>.

Date: 2006-01-27

Name Company Address Phone email Simon Barber Devicescape

Software, Inc 1000 Marina Blvd, #400, Brisbane, CA 94005

(650) 829-2618 simon@devicescape.com

Authors:

January 2006

Simon Barber, Devicescape Software Inc

Slide 2

doc.: IEEE 802.11-06/238r0

Submission

Abstract

This document describes a process for1. Preparing an Amendment when a Revision is in progress.2. 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-SAMike Kipness, Michael Fisher, Dave Ringle, Michelle Turner, Yvette

January 2006

Simon Barber, Devicescape Software Inc

Slide 3

doc.: IEEE 802.11-06/238r0

Submission

When a revision is in progress

• Amendments expected to be sent for approval after the approval of the revision:– Should be based on the latest draft of the revision text.– Should 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)

January 2006

Simon Barber, Devicescape Software Inc

Slide 4

doc.: IEEE 802.11-06/238r0

Submission

When an amendment anda revision are in progress

• A second amendment expected to be sent for approval after the approval of first amendment:

– Should be based on• the latest draft of the revision text AND• the latest draft of the first amendment text

– Should 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 latest draft of the first amendment AND

– Only included if the first amendment makes technical changes that are relevant to the second amendment.

• the second amendment being balloted.– If a technical change happens in a part of the revision text or part of the first

amendment text that is relevant to the second amendment then the second amendment should be re-circulated.

• Relevant technical change is decided by the ballot resolution group (the TG itself in 802.11’s case)

January 2006

Simon Barber, Devicescape Software Inc

Slide 5

doc.: IEEE 802.11-06/238r0

Submission

In general – handling an amendmentwith other drafts in progress:

• An amendment expected to be sent for approval after the approval of prior drafts:– Should be based on

• If there is a revision in progress:– the latest draft of any revision in progress

• Otherwise– the current complete approved base text (base + any approved amendments)

• the latest draft of any amendment expected to be approved first– Should be sent for sponsor balloting with:

• the current, complete approved base text (base + all approved amendments), AND• If a revision is in progress:

– the latest draft of the revision AND• The latest drafts of any amendments in progress that are expected to be approved prior first, and that make

technical changes that are relevant to the amendment.• the second amendment being balloted.

– If a technical change happens in a part of the revision text or part of the first amendment text that is relevant to the second amendment then the second amendment should be re-circulated.

• Relevant technical change is decided by the ballot resolution group (the TG itself in 802.11’s case)

January 2006

Simon Barber, Devicescape Software Inc

Slide 6

doc.: IEEE 802.11-06/238r0

Submission

References