802.11n Gen AdHoc Operation Date: 2006-05-15 Authors: May 2006 doc.: IEEE 802.11-06/0734r0 May 2006 802.11n Gen AdHoc Operation Date: 2006-05-15 Authors: 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>. Jon Rosdahl, Samsung Jon Rosdahl, Samsung

May 2006 doc.: IEEE 802.11-06/0734r0 May 2006 Abstract This is a presentation describing how the 802.11n Gen AdHoc will conduct its business. Jon Rosdahl, Samsung Jon Rosdahl, Samsung

Gen AdHoc Mission Review and accept operating rules for Gen AdHoc May 2006 doc.: IEEE 802.11-06/0734r0 May 2006 Gen AdHoc Mission Review and accept operating rules for Gen AdHoc Overview of comment spreadsheet Start resolving Gen AdHoc comments in order On first Gen AdHoc meeting, review progress and approach (and perhaps make changes) During Final Gen AdHoc meeting, discuss how we’ll proceed after the WG session adjourns Jon Rosdahl, Samsung Jon Rosdahl, Samsung

Goals for the May Session doc.: IEEE 802.11-06/0734r0 May 2006 Goals for the May Session Our goal for this sessions is To recommend explicit resolution of as many comments as is practical If it is not possible to recommend a resolution, our goal is to assign volunteers to author submissions. We prefer that various authors work together to create one submission However, where this is a difference of opinion that we cannot expect to resolve, we will accept volunteers for multiple submissions Pass comments off to other ad hocs or to the editor if resolving it does not fit within the focus of the Gen AdHoc Jon Rosdahl, Samsung Jon Rosdahl, Samsung

What comments fall to the GEN AdHoc? May 2006 doc.: IEEE 802.11-06/0734r0 May 2006 What comments fall to the GEN AdHoc? Our ad hoc will address comments that primarily relate to definitions, acronyms and general overall issues. However, comments that relate to other ad hocs with specific interest should be passed to those ad hocs. These include: MAC PSMP Coexistance Includes 20/40 issues and channelization issues Beam Steering Includes channel sounding, rate adaptation, and antenna switching PHY Jon Rosdahl, Samsung Jon Rosdahl, Samsung

Conduct of Meetings within May Session doc.: IEEE 802.11-06/0734r0 May 2006 Conduct of Meetings within May Session Our first agenda item will agree on a Sort of the comments. At the start of each meeting we’ll examine our progress and decide whether to change our approach or continue where we left off. During the final meeting we’ll discuss what we’ll do after the WG session ends When we complete a walk-through of all the comments, we’ll devise a new agenda. This new agenda will depend on the status of solicited submissions and on whether TGn accepts are proposed comment resolutions. Jon Rosdahl, Samsung Jon Rosdahl, Samsung

Comment Resolution For each comment we will either May 2006 doc.: IEEE 802.11-06/0734r0 May 2006 Comment Resolution For each comment we will either Recommend a resolution Assign volunteer author(s) to create submission(s) Refer the comment to another ah hoc or the editor If we cannot accomplish any of these, we will skip to the next comment (but we should discourage this behavior) When we encounter a comment that is a similar to another comment, we will refer the resolution to the resolution of the first comment Any new comments that are referred to us by another ad hoc will be added to the end of the list. Jon Rosdahl, Samsung Jon Rosdahl, Samsung

Comment Resolution May 2006 doc.: IEEE 802.11-06/0734r0 May 2006 Comment Resolution We will attempt to reach a consensus on each resolution. However, if we have a division of option, we may present multiple options to TGn We will not spend a lot of time during the May session in getting consensus We propose a 5 minute limit on discussion of each comment We will allow one 5 minute extension on this time limit if there is a consensus that we can make progress, but we expect to grant only one extension per comment. If we encounter a comment similar to a previous comment we timed-out on, we will skip this comment. We do not expect to review any technical contributions during the May session unless we have completed the first pass through all the comments. As soon as a comment resolution has been accepted by the group, that comment will be ready and available for submission to TGn. Remember that no resolution is final until accepted by TGn. If you are unhappy with the resolution of a comment, you will have another chance in TGn to discuss it Jon Rosdahl, Samsung Jon Rosdahl, Samsung

May 2006 doc.: IEEE 802.11-06/0734r0 May 2006 Submissions We expect to assign volunteer authors to create technical submissions as a means of resolving comments. Many of these submissions will likely be uncontroversial but will not be practical to resolve in a meeting (for example, creating a figure, adding a descriptive paragraph, fixing an equation, re-wording to remove an ambiguity) For these submissions, it will likely be sufficient to supply the proposed alterations to the draft without any other explanation Some topics will be complex and/or controversial and the authors may wish to explain the motivation for their proposals We encourage such explanations to be place in a separate submission form the submission with the proposed disposition of the comment We encourage the authors of such supporting submissions to present them to the body of TGn and not to the ad hoc, though this can be decided in a case-by-case basis In addition to the assigned volunteer authors, others can also volunteer to create additional submissions on the same comments outside the meetings, as long as the topic is still open (waiting for the assigned submissions). Any new volunteers should notify the chair and the TGn body be email. Jon Rosdahl, Samsung Jon Rosdahl, Samsung

Meeting Rules We will not take attendance at these meetings May 2006 doc.: IEEE 802.11-06/0734r0 May 2006 Meeting Rules We will not take attendance at these meetings Meeting minutes will be almost entirely in the form of updates to the spreadsheet Any submissions should be in response to an assigned comment. Any independent submissions (not related to specific comments) will be referred to TGn. But the submission will be heard/reviewed at a latter session, or ad hoc telcon. Jon Rosdahl, Samsung Jon Rosdahl, Samsung

May 2006 doc.: IEEE 802.11-06/0734r0 May 2006 Use of Email All emailed messages should be sent on the TGn reflector. This ad hoc does not have its own reflector Please begin the email subject line with “[GEN AdHoc]” This will allow us to know that the email relates to our ad hoc and allows others to ignore unwanted emails Jon Rosdahl, Samsung Jon Rosdahl, Samsung

Comment Spreadsheet May 2006 doc.: IEEE 802.11-06/0734r0 May 2006 Comment Spreadsheet Please download the comment spreadsheet for the GEN AdHoc. We will update this spreadsheet during our meetings. At the end of each 2-hour meeting, the chair will attempt to load the update spreadsheet back to the server. Most of the columns in the spreadsheet are derived from the master spreadsheet (created by the editor) and are explained on the schema tab. The General tab of the spreadsheet contains General comments that we will be addressing. The GEN tab spreadsheet cells are color coded: Orange means that the ad hoc will not update these fields Green means the ad hoc may update these fields White means the ad hoc expects to update these fields Yellow applied to items where the editor has altered a derivative entry from what the voter indicated (such as an error in page number) Jon Rosdahl, Samsung Jon Rosdahl, Samsung

Comment Spreadsheet—General Tab May 2006 doc.: IEEE 802.11-06/0734r0 May 2006 Comment Spreadsheet—General Tab The type column (L) has been coded by the editorial committee T means technical comment This applies to comments that we expect to resolve quickly ST means submission required technical comment This applied to technical comments that we expect to require submissions DT means disputed technical This applies to technical comments where we expect some contention We will use the type column for non-binding guidance in how to resolve a comment T-try to resolve immediately ST-Solicit a submission DT-solicit multiple submissions, try to resolve, or kick back to TGn Jon Rosdahl, Samsung Jon Rosdahl, Samsung

General Tab Columns We Will Update May 2006 doc.: IEEE 802.11-06/0734r0 May 2006 General Tab Columns We Will Update Resn Status (resolution status) A - accepted R - rejected C - counter (provided in proposed change field) D - Deferred X - No consensus reached in the ad-hoc T - Pending Transfer to another ad-hoc N – New Duplicate found Assignee Name of volunteer(s) to create submission(s) Submission Indicate the IEEE document number holding the submission(s) Jon Rosdahl, Samsung Jon Rosdahl, Samsung

GEN Tab Columns We Expect to Update May 2006 doc.: IEEE 802.11-06/0734r0 May 2006 GEN Tab Columns We Expect to Update Related Comment CID of a related comment Indicated that a group of comments are related and likely to have a common resolution Where there are many related comments, will refer to master comment (the first one we reviewed) In master comment, field will be blank Purpose is to allow submissions to cover multiple comments Technical Area This field will indicate the technical area of a comment where that might be useful. This is for informational purposes only. Consensus of Resolution Indicates the level of consensus of the group on the resolution The following levels are approximate measures (useful when we want to avoid precise vote counting to save time) U-Unanimous S-Strong (approximately 75%-99% in favor) M-Majority (approximately 50+% to 75%) D-Divided (no clear consensus) P – Preloaded proposal, the group has not voted/agreed to proposed resolution. Jon Rosdahl, Samsung Jon Rosdahl, Samsung

References 11-06-0541-06-000n-tgn-d1-0-lb84.xls May 2006 doc.: IEEE 802.11-06/0734r0 May 2006 References 11-06-0541-06-000n-tgn-d1-0-lb84.xls (Initial Comment file that was referenced.) 11-06-0688-xx-000n-TGn-General-Comment-Adhoc-Group-LB84 (Gen AdHoc Comment Resolution File) Jon Rosdahl, Samsung Jon Rosdahl, Samsung