doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 1 TGy September Chair’s Report 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, 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. Date: Authors:

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 2 Abstract This submission summarizes the TGy agenda for IEEE Dallas (November 2006) meeting

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 3 Opening Report

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 4 Attendance Recording Sign-in at –“newton” is a local server, not reachable via a VPN –“newton” is active only during sessions – 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

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 5 Membership & Anti-Trust Individual membership –In all IEEE standards meetings, membership is by individual, hence you do not represent a company or organization. Anti-Trust laws –The Anti-Trust laws forbid the discussion of prices within our meetings.

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 6 6. Patents IEEE standards may include the known use of essential patents and patent applications provided the IEEE receives assurance from the patent holder or applicant with respect to patents whose infringement is, or in the case of patent applications, potential future infringement the applicant asserts will be, unavoidable in a compliant implementation of either mandatory or optional portions of the standard [essential patents]. This assurance shall be provided without coercion. The patent holder or applicant should provide this assurance as soon as reasonably feasible in the standards development process. This assurance shall be provided no later than the approval of the standard (or reaffirmation when a patent or patent application becomes known after initial approval of the standard). This assurance shall be either: a) A general disclaimer to the effect that the patentee will not enforce any of its present or future patent(s) whose use would be required to implement either mandatory or optional portions of the proposed IEEE standard against any person or entity complying with the standard; or b) A statement that a license for such implementation will be made available without compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair discrimination. This assurance shall apply, at a minimum, from the date of the standard's approval to the date of the standard's withdrawal and is irrevocable during that period. IEEE-SA Standards Board Bylaws on Patents in Standards Approved by IEEE-SA Standards Board – March 2003 (Revised January 2006)

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 7 Inappropriate Topics for IEEE WG Meetings Don’t discuss the validity/essentiality of patents/patent claims Don’t discuss the cost of specific patent use Don’t discuss licensing terms or conditions Don’t discuss product pricing, territorial restrictions, or market share Don’t discuss ongoing litigation or threatened litigation Don’t be silent if inappropriate topics are discussed… do formally object. If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at or visit This slide set is available at Approved by IEEE-SA Standards Board – March 2003 (Revised January 2006)

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 8 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

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 9 Equipment Well-dressed criminals often enter meetings and steal laptops, PDAs, and similar devices Do not leave your devices unattended!!

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 10 TGy Goals for Dallas Hear proposals addressing PHY, MAC and system operation in US 3650 MHz band Create a D0.02 text for WG consideration Planning through March 2007

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 11 Minutes (Re-) review Any Modifications of the Minutes from CBP-TG Melbourne Meeting 06/1537r0 Any Modifications of the Minutes from teleconferences –Sept 26 th 06/1561r0 –Oct 24 th 06/1608r0 –Nov 7 th 06/1674r0

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 12 Motions (1) Motion: Move to accept the minutes of the TGy Melbourne meeting 06/1537r0 and subsequent teleconferences 06/1561r0, 06/1608r0, 06/1674r0 Moved: Second: Yes: No: Abstain: Motion Passes/Fails:

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 13 TGy Agenda Tuesday 08:00 *CBP TG Meeting Call To Order - Chair108:00 *Review IEEE/802 & Policies and Rules - Chair/All808:01 *Approve or Modify Agenda - Chair508:09 IIReview and Approve All Minutes - Chair/All1008:14 DTSet, Review Objectives - All508:24 DTReview of situation - All1008:29 DTOverview presentation, PHY, MAC topics - All3008:39 DTPHY text - All5109:09 *Recess until 08:00 Thursday - Chair 010:00

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 14 TGy Agenda Thursday 11y/.16h Joint Meeting *CBP TG/.16h Joint Meeting Call To Order - Chair18:00 *Joint meeting with h, situation, draft topics, only straw polls - Chair/All1198:01 * - 0 * - 8:30 * - 9:31 *Recess until 13:30 Thursday - Chair010:00

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 15 TGy Agenda Thursday 13:30 *CBP TG Meeting Call To Order - Chair113:30 *Draft D0.02y topics - All9013:31 *Planning through Mar 07 and Motions for WG - All2915:01 *Adjourn - Chair015:30

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 16 PAR Scope, Purpose Scope of Proposed Project: The scope of the proposed project is the application of based systems to the MHz band in the USA. Purpose of Proposed Project: The purpose of this project is to standardize the mechanisms required to allow shared operation with other users in the MHz band in the USA. Likely required mechanisms include: –Specification of new regulatory classes (extending j) –Sensing of other transmitters (extending a) –Transmit Power Control (extending h) –Dynamic Frequency Selection (extending h)

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 17 TGy Purpose, Principles Purpose : the Task Group should create an amendment whose implementation in solutions is likely to receive FCC approval for operation in 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 y. (Examples include parts of k and w) –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.

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 18 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 MHz band.

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 19 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

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 20 Work completed to 14 Nov, 2006 WG internal technical review was conducted on P802.11y D0.01, 163 comments and resolutions are recorded in 06/1609 The following normative text has been accepted and will be integrated into the next TGy draft – y-ofdm-phy-3650-mhz-band.doc – y-3650-mhz-mobile-service-enablement.doc – y-extended-csa.doc

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 21 Next step is to merge 7 Nov comment resolution text 06/1xxx has changes from documents accepted 7 Nov

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 22 Joint.11y and.16h meeting agenda

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 23 Straw Poll template ?? –.11 Yes:.11 No:.11 Abstain: –.16 Yes:.16 No:.16 Abstain: –Others Yes:Others No:Others Abstain:

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 24 Work completed (Thursday afternoon) The following normative text has been accepted and was integrated into the next TGy draft – y-ofdm-phy-3650-mhz-band.doc – y-3650-mhz-mobile-service-enablement.doc – y-extended-csa.doc The group voted to approve the editor’s draft as TGy D0.02, and call for a WG x x x

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 25 Motion Moved: Instruct the technical editor to rename y draft 0.02 as y draft 1.0. Having addressed all comments arising from the WG internal technical review, Task Group y resolves to forward y draft 1.0 to the working group for the purpose of conducting a 40-day working group letter ballot. The purpose of the working group letter ballot is to forward the draft to sponsor ballot. –The text of the motion to be presented to the working group will be “Move to authorize a 40-day Working Group Letter Ballot of y draft 1.0, asking the question “Should the y draft 1.0 be forwarded to sponsor ballot?”” Task Group Vote: Moved Second Result x-x-x

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 26 3 Cycles of Comments and Resolution Call for Informal Comments Comment Resolution WG Letter Ballot Sponsor Ballot Comment Resolution, Recirculation

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 27 Schedule Projected at Dallas (Nov) November 2006 (Dallas, Texas) –Letter Ballot Authorization by WG January 2007 (London, England) –Comment Resolution, First Letter Ballot Re-circulation authorized March 2007 (Orlando, Florida) –Second Letter Ballot Re-circulation May 2007 (Montreal, Quebec) –Sponsor Ballot Authorization by WG July 2007 (San Francisco, California) –Comment Resolution, First Sponsor Ballot Re-circulation authorized September 2007 (Waikoloa, Hawaii) –Comment Resolution, 2 nd SB Re-circ November 2007 (Atlanta, Georgia) –Sponsor Ballot Comment Resolution, done

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 28 Attendance Tuesday AM1: Thursday AM1: Other Thursday PM1:

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 29 Output documents November chairs report – this document D0.02 TGy Draft Specification 11-06/xxxxr0 – TGy Dallas Minutes November

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 30 Goals for March Respond to WG LB comments TGy normative text submissions to create D2.0 for WG letter ballot recirc

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 31 Adjourn Meeting adjourned at 15:30 on Nov 16, 2006

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 32 Move to authorize a 15-day Recirculation Letter Ballot of TGy, draft x.x to conclude no later than 00/00/0000. Moved by XXX on behalf of the Task Group. Task Group Vote: Moved XXX Second XXX Result: Motion

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 33 Move to approve the comment response in document xx/xxxrx, believing that comment responses in the document mentioned above and the draft x draft 0.0 demonstrate that the WG LB rules have reached an orderly endpoint. Moved by XXX on behalf of the Task Group. Task Group Vote: Moved XXX Second XXX Result: Motion

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 34 Move to authorize TGx to hold an Ad-Hoc meeting the ( Month Day Year ) to ( Month Day Year ) for the purpose of (description). Moved by XXX on behalf of the Task Group. Task Group Vote: Moved XXX Second XXX Result: Motion

doc.: IEEE /1675r0 Submission November 2006 Peter Ecclesine, Cisco SystemsSlide 35 Move to authorize x Draft x.x to be forwarded to ExCom for Sponsor Ballot using LMSC Procedure 10, assuming that the conditions required for Procedure 10 are met. Moved by XXX on behalf of the Task Group. Task Group Vote: Moved XXX Second XXX Result: Motion