1. Proposed TGv Selection Process
September 2005
doc.: IEEE /0918r0
September 2005
Proposed TGv Selection Process
Date: 19 September 2005
Authors:
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 < 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 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
Emily Qi, et al
Emily Qi, et al

2. September 2005
doc.: IEEE /0918r0
September 2005
Motivation
As TG intends to call for substantive text in September 05, TG needs to put in place a process to evaluate various proposals for eventual inclusion in base draft.
The following process lays out a timeline and methods for considering all proposals, in order to achieve adoption of a unified proposal as the basis for the draft, and to avoid a draft that includes a quilt of mismatched methods
Emily Qi, et al
Emily Qi, et al

3. Process Overview Call for Substantive Text in September
doc.: IEEE /0918r0
September 2005
Process Overview
Call for Substantive Text in September
Substantive text selection for base draft
Step 1: Intent for proposing substantive text
Step 2: Preliminary Substantive Text
Step 3: Substantive Text Merge Update
Step 4: Completed Substantive Text for Base Draft
Subsequence additions and modifications can be submitted after the base draft adopted in TG
Emily Qi, et al
Emily Qi, et al

4. Step 1: Intent for proposing substantive text
September 2005
doc.: IEEE /0918r0
September 2005
Step 1: Intent for proposing substantive text
Submitter should send intent (to TGv Chair) for proposing substantive text
The intent to submit must indicate the specific objectives or requirements (refer to TGv Objectives) that proposed substantive text addresses
The intent to submit is due by midnight EST 30 days before the TGv meeting at which the proposal will be presented
Emily Qi, et al
Emily Qi, et al

5. Step 2: Preliminary Substantive Text
September 2005
doc.: IEEE /0918r0
September 2005
Step 2: Preliminary Substantive Text
Presentation: November 13-18, 2005
Due at IEEE: November 6, 2005 by midnight EST
The slot will only remain on the agenda if the material is on the server and an sent to the TG reflector announces this availability.  Otherwise, the item is removed from the agenda
Merge/No/Abstain vote after proposed substantive text presentation.
The vote shall consider “The substantive text is worthy of further consideration,” with choices being Merge/No/Abstain
Merge = The proposal is worthy of further consideration
No = The proposal is encouraged to merge with others
Abstain = No opinion expressed
Proposals must get a simple majority of “Merge” votes to continue
Emily Qi, et al
Emily Qi, et al

6. Step 3: Substantive Text Merge Update
September 2005
doc.: IEEE /0918r0
September 2005
Step 3: Substantive Text Merge Update
All remaining proposals merge to a single proposal
Remaining proposers addressing a common objective are expected to arrive at a common solution
E.g. a proposal for channel selection and for load balancing can be inserted into the same merged document, but the authors of two different load balancing proposals are expected to find a common load balancing solution for the merged document
Presentation: January 15-20, 2006
Due at IEEE: January 11, 2006 by midnight (EST)
Merge Update reports given at each subsequent meeting until a single proposal remains
If there is not a single merged document by July 2006, TGv will vote to rescind its PAR
Emily Qi, et al
Emily Qi, et al

7. Step 4: Completed Substantive Text
September 2005
Step 4: Completed Substantive Text
Presentation: The meeting after which the merger completes
Due at IEEE: midnight EST (EDT) 7 days prior to the meeting after which the merger completes
TGv will conduct a 75% Yes/No/Abstain vote of the merged proposal
The vote shall be “adopt this document as the base draft”.
The merged proposal must receive 75% or more to be adopted as the draft.
If vote is no, then TG votes to rescind its PAR
Proposals that have not merged into a single document by July 2006 will not be considered for the base TGv draft
But unmerged proposals may be subsequently considered for addition to the draft
Emily Qi, et al

8. Subsequent Additions and Modifications
September 2005
doc.: IEEE /0918r0
September 2005
Subsequent Additions and Modifications
Subsequence additions and modifications can be submitted after the base draft adopted in TG
Proposals must get 75% or more to be included in draft.
Must be compatible with the base draft and clearly instruct editor how to include it in the base draft
1 week intent to submit, including identification of the objectives satisfied, is required for all subsequent additions
Emily Qi, et al
Emily Qi, et al

9. September 2005
Motion
TGv shall use the process defined in the previous slides for the substantive text selection to produce TGv draft
Emily Qi, et al

10. September 2005
Backup
Emily Qi, et al

11. TGv Proposed Timeline (Report of TGv – July 2005 : Doc 0644r4)
September 2005
TGv Proposed Timeline (Report of TGv – July 2005 : Doc 0644r4)
The following time table will be used by TGv
Internal Call for Substantive text: September 05 (due Nov 05)
In November we expect normative text to be contributed and the amendment editorial task will begin
TG Ad-Hoc Draft Internal Review: November 06
This will be an internal review, with an additional meeting (January) to address internal comments
First WG Letter Ballot: March 07
Emily Qi, et al