1. Requirements for TGT Proposals
December 2004
doc.: IEEE /1533r1
December 2004
Requirements for TGT Proposals
Corrected Doc# in headers
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
C. Wright, Azimuth Systems
C. Wright, Azimuth Systems

2. December 2004
doc.: IEEE /1533r1
December 2004
Abstract
This presentation is the starting point for a requirements document for TGT proposals. It contains some ideas discussed at the November 2004 meeting. It needs further discussion and refinement within the Task Group.
C. Wright, Azimuth Systems
C. Wright, Azimuth Systems

3. December 2004
Introduction
This document is a first crack at a list of requirements for proposals
Some of these ideas were discussed in the San Antonio meeting, but without firm closure
We should continue the discussion to come to agreement so proposal writers can receive the proper guidance
Ultimate goal: by end of January meeting, a document containing the explicit, written requirements that can be approved by vote in the TG
C. Wright, Azimuth Systems

4. Requirements for Proposals
December 2004
doc.: IEEE /1533r1
December 2004
Requirements for Proposals
The proposal will define a performance metric and a corresponding methodology for measuring the metric
A proposal will consist of
Draft text in the form of instructions to the editor
A presentation to be given by proposer that explains the proposal
Would like to define requirements for the form of the draft text and the presentation
The next few slides outline some ideas for this
C. Wright, Azimuth Systems
C. Wright, Azimuth Systems

5. Requirements of the Draft Text
December 2004
Requirements of the Draft Text
Definition of the metric
Methodology for measurement
Content should abide by the test template
Describes the bulk of requirements for a methodology
Doc #11-04/863r2 is most recent, but an ad hoc group worked on it further during the San Antonio meeting – where is this output?
Should be made available one week (TBR) before a motion to accept to allow for evaluation
C. Wright, Azimuth Systems

6. Requirements for the Proposal Presentation
December 2004
Requirements for the Proposal Presentation
A “viewer friendly” version of the metric definition and the methodology
Discussion of why this metric is important
Influence on user experience
Results of a demonstration of the proposed test methodology performed on real equipment
Results will be sanitized of vendor names
Discussion of repeatability of results
C. Wright, Azimuth Systems

7. Questions? Clarification based on a comment in the telecon:
December 2004
Questions?
Clarification based on a comment in the telecon:
The requirements document is not meant to stop presentations of any kind relevant to TGT from coming before the group. I hope that members continue to come forward with proposed metrics for discussion and collaboration with others in the group, if desired.
The requirements document is meant to define what consititutes a complete or full proposal – i.e., one that the proposers consider to be ready for incorporation into the draft
One parting thought from the author:
I’ve said that a proposal must define a metric, etc. But there are other parts of the draft that must be written as well. I referred to a background section describing test conditions and degree of compliance of the device with , etc. How do we want to handle inclusion of text that does not define a metric and methodology? What other kinds of text do we want in our draft?
C. Wright, Azimuth Systems

8. December 2004
References
11-04/863r2, “Wireless Performance (Task Group T) Test Plan Template (Version 3)”, Polanec, Mandeville, Goubert, Berry
C. Wright, Azimuth Systems