1. Suggested TGu Down Selection
July 2005
doc.: IEEE /0522r0
July 2005
Suggested TGu Down Selection
Date:
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
Eleanor Hepworth, Siemens Roke Manor
Mike Moreton, STMicroelectronics

2. July 2005
doc.: IEEE /0522r0
July 2005
Abstract
This document provides some initial thoughts on the down selection procedure for TGu. It is based in part on the TGn selection process (03/665r9)
Eleanor Hepworth, Siemens Roke Manor
Mike Moreton, STMicroelectronics

3. July 2005
Background
TGu addresses a number of different technical areas in order to facilitate interworking with external networks
For example, some aspects may be protocol related, others are API issues
The complete functional requirements are being captured in 05/279rX. They are grouped according to technical area into “clusters”.
Eleanor Hepworth, Siemens Roke Manor

4. July 2005
Definitions
Functional Requirements: A list of mandatory features, performances and behaviors of the amendment.
Cluster: the set of functional requirements for a particular technical area.
Complete Proposal: A proposal that does not violate the PAR and meets all of the Functional Requirements associated with a Cluster. All complete proposals shall disclose how the Functional Requirements are met.
Partial Proposal: A proposal that does not violate the PAR but is not complete i.e. addresses a subset of the requirements in a Cluster. All partial proposals should disclose which Functional Requirements they meet and how they meet them.
Eleanor Hepworth, Siemens Roke Manor

5. Process (part I) July 2005 Procedure Start Step 1: Adopt Terms and
Definitions
Step 2:
Adopt Functional
Requirements
Step 3:
Issue Call
for Proposal
Eleanor Hepworth, Siemens Roke Manor

6. Process (part II) July 2005 July 2005 doc.: IEEE 802.11-05/0522r0
For each cluster:
Step 4:
Initial Presentation
of Proposal
Step 11:
Internal Review
Mergers? Y
Step 5:
Carry out mergers
etc. N
Step 12:
Vote on whether to
forward to WG
Step 6:
Discard Unmerged
Proposals (partial)
Step 10:
Combine Cluster
Proposals
>1
Proposal? Y
Step 7:
Elimination
Procedure
>75% N
Step 9: includes getting comments from no voters etc.
Step 10: can start once one or more clusters have been addressed (i.e. a single solution for a particular cluster has been selected and confirmed).
Step 11: includes checking all mandatory requirements have been met.
Start of each meeting it might be nice to confirm the latest draft document produced by editor, plus have a confirmation vote to approve the latest draft. N
Step 8:
Confirmation
Vote Y
Step 13:
Forward to WG
for LB N
>75%
Step 9:
No Vote
Resolution Y
Eleanor Hepworth, Siemens Roke Manor
Mike Moreton, STMicroelectronics