1. TGn Sync MAC Response to Reasons and Cures
Month Year
doc.: IEEE yy/xxxxr0
May 2005
TGn Sync MAC Response to Reasons and Cures
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
Adrian Stephens, Intel Corporation
John Doe, Some Company

2. Authors (continued): May 2005 Month Year doc.: IEEE 802.11-yy/xxxxr0
Adrian Stephens, Intel Corporation
John Doe, Some Company

3. Month Year
doc.: IEEE yy/xxxxr0
May 2005
Abstract
Summarises status of TGn Sync MAC team response to reasons and cures
Adrian Stephens, Intel Corporation
John Doe, Some Company

4. Month Year
doc.: IEEE yy/xxxxr0
May 2005
Responses Documents
n-tgnsync-mac-response-to-reasons-and-cures.xls
Detailed responses to MAC comments
No plan to present in detail
Can reference for Q & A
Presentations related to these responses
Purpose of this and following MAC presentations
Listed Later in this document
Adrian Stephens, Intel Corporation
John Doe, Some Company

5. Related Presentations – Responses
Month Year
doc.: IEEE yy/xxxxr0
May 2005
Related Presentations – Responses
Topic
Presenter
Doc No (pages)
General
Peter Loc
(12)
Aggregation
Huanchun Ye
(34)
Frame Formats
Sudheer Grandhi
Link Adaptation
Sanjiv Nanda
(14)
Pairwise Spoofing
Yuichi Morioka
(11)
Reverse Direction
Robert Stacey
(11)
40/20 Coexistence
Tomoko Adachi
(16)
Adrian Stephens, Intel Corporation
John Doe, Some Company

6. Summary of Reasons and Cures by Type
Month Year
doc.: IEEE yy/xxxxr0
May 2005
Summary of Reasons and Cures by Type
Category
Count
Aggregation 30 BA 1
Coexistence 5
Frame Formats 13
General 20
Handset 3
Link Adaptation 14
Multicast 2
Power Saving
Protection 10
Reverse Direction 6
TSF Synchronization
Adrian Stephens, Intel Corporation
John Doe, Some Company

7. Summary of Status May 2005 Status Number Description accepted 14
Month Year
doc.: IEEE yy/xxxxr0
May 2005
Summary of Status
Status
Number
Description
accepted 14
This is where we accepted the proposed cure
alternative 1
This is where we proposed an alternative solution
partial 18
This is where we have partly addressed the stated reason
possible accept
This is where we could accept it, but haven't done anything about it in our spec, because we haven't had enough time to consider it
possible alternative
This is where we have an alternative, but haven't had time to discuss
respectfully disagree 65
This is where we disagree with the comment
more input needed
This is where we have a solution to the comment, but we need more input from TGn to determine if the potential change has the support of TGn members
Adrian Stephens, Intel Corporation
John Doe, Some Company

8. Comments on the MAC Reasons and Cures
Month Year
doc.: IEEE yy/xxxxr0
May 2005
Comments on the MAC Reasons and Cures
Many of the reasons had no cures
We have worked towards addressing the reasons as best as we can
Many of the reasons are very general
“It’s too complex”
We are working towards reduction of complexity generally
Adrian Stephens, Intel Corporation
John Doe, Some Company

9. Month Year
doc.: IEEE yy/xxxxr0
May 2005
Comments on Process
If we were to accept all the comments, this would cause a reduction in support
We need a process to find the solution that gains the highest support in TGn, without resorting to multiple process “resets”
The “reasons and cures” is an inadequate tool to get feedback (only the “no” voters get to express themselves, and then only a subset of those)
Introduces substantial delay
Adrian Stephens, Intel Corporation
John Doe, Some Company

10. Month Year
doc.: IEEE yy/xxxxr0
May 2005
Summary of Changes
Improved handset support – power-saving through MRA multi-poll packet
Improved protection
Improved power-saving for handsets and 3rd-party STA
Reduced mandatory complexity for STA
Scheduled responses optional
The ability to receive MRA optional
The ability to perform calibration optional
Substantial reduction of technical spec (75  46 pages)
Removed redundant material, rewritten and simplified
Detail will be presented in detailed presentations listed on the next slide
Adrian Stephens, Intel Corporation
John Doe, Some Company

11. Month Year
doc.: IEEE yy/xxxxr0
May 2005
References
n-tgnsync-mac-response-to-reasons-and-cures.xls
Adrian Stephens, Intel Corporation
John Doe, Some Company