TGy March Report Date: 2008-03-16 Authors: March 2008 March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 TGy March Report Date: 2008-03-16 Authors: Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Abstract This submission summarizes the TGy agenda for IEEE 802.11 Orlando (March 2008) meeting Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

Opening Report March 2008 March 2008 doc.: IEEE 802.11-08/0318r2 Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

Attendance Recording -802.11 March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Attendance Recording -802.11 Sign-in at http://newton.events.ieee.org “newton” is a local server, not reachable via a VPN “newton” is active only during 802.11 sessions 172.16.0.10 ? First “sign in” to provide contact information Only name and affiliation may be posted publicly, as per IEEE rules No other personal information will not be publicly available Second, log attendance Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

TGy – March 2008 March 2008 Call Meeting to Order doc.: IEEE 802.11-08/0318r2 March 2008 TGy – March 2008 Call Meeting to Order Policies and Procedures, Attendance reminder: http://newton/ **IEEE Patent Policy http://standards.ieee.org/board/pat/pat-slideset.ppt Are there any patent claim(s)/patent application claim(s) and/or the holder of patent claim(s)/patent application claim(s) that the participant believes may be essential for the use of that standard? Minute any responses that were given, specifically the patent claim(s)/patent application claim(s) and/or the holder of the patent claim(s)/patent application claim(s) that were identified (if any) and by whom. ***Affiliation FAQ - http://standards.ieee.org/faqs/affiliationFAQ.html Anti-Trust FAQ - http://standards.ieee.org/resources/antitrust-guidelines.pdf Ethics - http://www.ieee.org/portal/cms_docs/about/CoE_poster.pdf IEEE 802.11 Policies and Procedures - http://www.ieee802.org/11/DocFiles/07/11-07-0360-04-0000-802-11-policies-and-proceedures.htm IEEE 802 Policies and Procedures - http://www.ieee802.org/policies-and-procedures.pdf ** Read slide deck *** Note especially items #7 & #11 Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Copyright Under the current US copyright law — the author of information is deemed to own the copyright from the moment of creation The IEEE Bylaws require copyright of all material to be held by the IEEE Must consult with IEEE for re-use of copyright material The IEEE Standards accomplishes transfer of copyright ownership through the Project Authorization Request (PAR) process The Copyright Act of 1976 made a dramatic change to U.S. copyright law. Copyright was now deemed to exist from the moment of creation. Thus anything that is created is deemed to be owned by its creator. Additionally, a work no longer needs to be published in order to be protected. Therefore, even your scribbles on a piece of note paper constitute copyrighted material that you own and control. The NII (National Information Infrastructure) and the GII (Global Information Infrastructure) are causing lawmakers and copyright owners to assess the ability of current copyright law to protect owners rights in a digital environment. While at this point the changes being talked about are not significant, they will make it clear that copyright protection is afforded to owners in the digital environment making it a requirement to honor the rights accorded to owners. It is a requirement under the IEEE Bylaws that copyright ownership of all material published by the IEEE resides with the IEEE. The Standards Department accomplishes the transfer of copyright ownership from the volunteer authors to the Institute via the Project Authorization Request (PAR) form. Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Equipment Well-dressed criminals often enter meetings and steal laptops, PDAs, and similar devices Do not leave your devices unattended!! Make sure you log your attendance http://newton.events.ieee.org Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

TGy Goals for Atlanta Planning through May 2008 March 2008 March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 TGy Goals for Atlanta Planning through May 2008 Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

TGy Agenda Tuesday 08:00 March 2008 March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 TGy Agenda Tuesday 08:00 * CBP TG Meeting Call To Order - Chair 1 08:00   Review IEEE/802 & 802.11 Policies and Rules Chair/All 8 08:01 Approve or Modify Agenda 5 08:09 II Review and Approve All Minutes 10 08:14 DT Set, Review Objectives All 08:24 Review of situation 08:29 Overview presentation, PHY, MAC topics 30 08:39 SB recirc-1 comment review 51 09:09 Adjourn  0 10:00 Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Motions (1) Motion: Move to approve TGy agenda in 11-08-0318r0 as the agenda for the Orlando meeting. Moved by: Seconded by: Vote: Motion: Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

Minutes review Any Modifications of the Minutes from CBP-TG March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Minutes review Any Modifications of the Minutes from CBP-TG Atlanta 07/2827r0; Taipei 08/0099r0 Any Modifications of the Minutes from teleconferences Dec 11th, Feb 5th, Feb 12th, Feb 19th, Feb 26th, Mar 11th 07/2956r0, 08/0232r0, 08/0237r0, 08/0245r0, 08/0254r0, 08/0283r0 Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Motions (2) Motion: Move to approve TGy minutes of meetings and teleconferences from Atlanta plenary to today: Atlanta 07/2827r0; Taipei 08/0099r0 teleconferences Dec 11th, Feb 5th, Feb 12th, Feb 19th, Feb 26th, Mar 11th 07/2956r0, 08/0232r0, 08/0237r0, 08/0245r0, 08/0254r0, 08/0283r0 Moved: Jim P Second: Dan L Vote: 5-0-0 Motion: Passes Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

PAR Scope, Purpose Scope of Proposed Project: March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 PAR Scope, Purpose Scope of Proposed Project: The scope of the proposed project is the application of 802.11 based systems to the 3650-3700 MHz band in the USA. Purpose of Proposed Project: The purpose of this project is to standardize the mechanisms required to allow shared 802.11 operation with other users in the 3650-3700 MHz band in the USA. Likely required mechanisms include: Specification of new regulatory classes (extending 802.11j) Sensing of other transmitters (extending 802.11a) Transmit Power Control (extending 802.11h) Dynamic Frequency Selection (extending 802.11h) Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

TGy Purpose, Principles March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 TGy Purpose, Principles Purpose : the Task Group should create an amendment whose implementation in solutions is likely to receive FCC approval for operation in 3650-3700 MHz under the 47 CFR 90 subpart z rules. Principles : If the FCC changes the rules, the Task Group should change the amendment accordingly. The amendment should not duplicate functionality that is being standardized in other Task Groups that are likely to complete before 802.11y. (Examples include parts of 802.11k and 802.11w) There is no need for backwards compatibility with 2.45 GHz ISM operation. The amendment should exclude some optional MAC and PHY behaviour, e.g. Point Coordination Function, FH, DSSS, and ERP. Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Vision/Outcome Use the OFDM PHY with 5-, 10- and 20-MHz channel widths, and extend DFS to operate with other primary band users, to specify the basis for a system that the FCC can approve for operation in the US 3650-3700 MHz band. Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

Proposal of 06/1023r0 The way forward for TGy March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Proposal of 06/1023r0 The way forward for TGy Clause 17 OFDM PHY, TPC and DFS procedures, use a non-overlapping channel plan, improve CCA for coexistence, use 5-, 10-, 20-MHz channel widths, and Regulatory Class/Coverage Class for outdoor operation Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

Four Themes of TGy Interference Identification and Resolution, March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Four Themes of TGy    Interference Identification and Resolution,    Enablement,    Energy Detect operation with the clause 17 PHY, and    Mechanisms for use by licensees to control dependent stations. Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

TGy Work completed to 16 Mar, 2008 March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 TGy Work completed to 16 Mar, 2008 Sponsor Recirculation Letter Ballot was conducted on P802.11y D8.0, 22 comments are recorded in 08/0277r2 SB recirc-1 results (not announced) Voter pool 128, 104 ballots received Approved 93, Do not approve 5, Abstain 6 (approval rate 94%, passes) 11 Mar Teleconference discussed all recirc-1 comments, approved resolutions and started recirculation-2. The current versions were posted on the server and announced on the TGy list last Wednesday. Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

Recirculation ballot Negative vote comments March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Recirculation ballot Negative vote comments IEEE-SA Standards Board Operations Manual  http://standards.ieee.org/guides/opman/sect5.html#5.3 Do Not Approve (Negative with comment). This vote must be accompanied by one or more specific objections with proposed resolution in sufficient detail in a legible form so that the specific wording of the changes that will cause the negative voter to change his or her vote to "approve" can readily be determined. The Sponsor shall encourage the submission of comments with all negative ballots. If a negative vote unaccompanied by comments, or a negative vote accompanied by comments not related to the proposal under consideration, is received despite these instructions, the vote shall be counted in the total tally of votes as a "negative without comment." Any comments that are explicitly identified not to be part of the negative vote shall be treated as Approve (Affirmative) comments, and action on such comments is left to the discretion of the Sponsor. Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

Recirculation Comment classifications March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Recirculation Comment classifications Accept Accept in Principle (Accepted but revised) Reject Out of Scope “[Negative comments] shall be based only on the changed portions of the balloted document, clauses affected by the changes, or portions of the balloted document that are the subject of the unresolved negative votes.” Reporting categories – Technical, Editorial, General Changes in the document “Changes may be made in the document to resolve negative votes that are accompanied by comments or for other reasons.” Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

Review SB recirc-1 comments March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Review SB recirc-1 comments 11-08/0277r2 has all 22 SB recirc-1 comments 11-08/0319r2 Conditional Sponsor Ballot Report Also see 11-08/0359r0 Orlando minutes Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Motions (3) Motion: To approve document 08/0319r2 as the report to the 802 Executive Committee (EC) on the requirements for conditional approval to forward 802.11y to RevCom. Moved: Rich K Second: Jim R Vote: 13-0-0 Motion: Passes Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Motions (4) Move to request conditional approval to send the draft of 802.11y to RevCom upon the conclusion of a Sponsor Recirculation Ballot that meets all requirements for recirculation ballots. Moved: Jim R Second: Rich K Vote: 12-0-0 Motion: Passes P802.11y Draft 8.0 had a 94.9% approval on the last Sponsor Recirculation Ballot. There were 5 voters that had voted Disapprove. 1 of the 5 NO voters changed to an Approve vote. Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

Process of Getting to Sponsor Ballot and Beyond March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Process of Getting to Sponsor Ballot and Beyond Completed Steps | Future Steps Adoption of PAR and 5 Criteria Letter Ballot – November 2006 Recirculation – March 2007, May 2007, July 2007, Sept 2007, Nov 2007 Sponsor Ballot – January 2008 Recirculation-1 – February 2008 Recirculation-2 – March 2008 29.53 man-weeks, 1633 comments, 72 body pages Conditional WG/EC Approval IEEE SB REVCOM Approval Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

3 Cycles of Comments and Resolution March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 3 Cycles of Comments and Resolution Call for Informal Comments Comment Resolution WG Letter Ballot Comment Resolution, Recirculation Sponsor Ballot Comment Resolution, Recirculation Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

Schedule Projected at Orlando (Mar) March 2008 doc.: IEEE 802.11-08/0318r2 March 2008 Schedule Projected at Orlando (Mar) March 2008 (Orlando) Sponsor Ballot Comment Resolution, 2nd SB Re-circ in progress WG, ExCom conditional approval May 2008 (Jacksonville) Sponsor Ballot conditions met, on RevCom agenda June 2008 RevCom Approval Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

Attendance March 2008 Tuesday AM1: Peter Ecclesine, Cisco Systems doc.: IEEE 802.11-08/0318r2 March 2008 Attendance Tuesday AM1: Peter Ecclesine, Cisco Systems Rich Kennedy, ETS-Lindgren Eldad Perahia, Intel Corp Jim Petranovich, Viasat Douglas Chan, Cisco Systems Dan Lubar, Relay Services Dick Roy, Connexis Jim Raab, Dell Computer Jeremy Landt, Transcore Alaistair Malarky, Mark IV Industries Wayne Fisher, ARINC Brian Hart, Cisco Systems Tushar Moorti, Broadcom Randy Roebuck, SIRIT/OmniAir Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems