1. TGy Sept Opening Report
September 2007
doc.: IEEE /2464r1
September 2007
TGy Sept Opening Report
Date:
Authors:
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

2. September 2007
doc.: IEEE /2464r1
September 2007
Abstract
This submission summarizes the TGy agenda for IEEE Waikoloa (September 2007) meeting
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

3. Opening Report September 2007 September 2007
doc.: IEEE /2464r1
September 2007
Opening Report
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

4. Attendance Recording -802.11
September 2007
doc.: IEEE /2464r1
September 2007
Attendance Recording
Sign-in at
“newton” is a local server, not reachable via a VPN
“newton” is active only during sessions
is not to be used unless the new attendance recorder fails
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

5. TGy – Sept 2007 September 2007 Call Meeting to Order
doc.: IEEE /2464r1
September 2007
TGy – Sept 2007
Call Meeting to Order
Policies and Procedures, Attendance reminder:
**IEEE Patent Policy
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 -
Anti-Trust FAQ -
Ethics -
IEEE Policies and Procedures -
IEEE 802 Policies and Procedures -
** Read slide deck
*** Note especially items #7 & #11
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

6. September 2007
doc.: IEEE /2464r1
September 2007
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

7. September 2007
doc.: IEEE /2464r1
September 2007
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
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

8. TGy Goals for Waikoloa Resolve LB109 Ballot comments
September 2007
doc.: IEEE /2464r1
September 2007
TGy Goals for Waikoloa
Resolve LB109 Ballot comments
Planning through November 2007
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

9. TGy Agenda Tuesday 08:00 September 2007 September 2007
doc.: IEEE /2464r1
September 2007
TGy Agenda Tuesday 08:00 *
CBP TG Meeting Call To Order -
Chair 1
08:00
Review IEEE/802 & 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
LB109 comment review 51
09:09
Recess until 16:00 Thursday  0
10:00
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

10. TGy Agenda Thursday 16:00 September 2007 September 2007
doc.: IEEE /2464r1
September 2007
TGy Agenda Thursday 16:00 *
CBP TG Meeting Call To Order -
Chair 1
16:00
Draft D4.1 and 5.0y topics
All 90
16:01
Planning through Nov 07 and Motions for WG 29
17:31
Adjourn
18:00
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

11. Minutes review Any Modifications of the Minutes from CBP-TG
September 2007
doc.: IEEE /2464r1
September 2007
Minutes review
Any Modifications of the Minutes from CBP-TG
San Francisco 07/2269r1
Any Modifications of the Minutes from teleconferences
August 28th, September 4th and September 11th
07/2353r1, 07/2366r0, 07/2395r0
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

12. September 2007
doc.: IEEE /2464r1
September 2007
Motions (1)
Motion: Move to approve TGy agenda in r0 as the agenda for the Waikoloa meeting.
Moved by:
Seconded by:
Vote:
Motion:
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

13. September 2007
doc.: IEEE /2464r1
September 2007
Motions (2)
Motion: Move to approve TGy minutes of meetings and teleconferences from San Francisco plenary to today:
San Francisco 07/2269r1
teleconferences
August 28th, September 4th and September 11th
07/2353r1, 07/2366r0, 07/2395r0
Moved:
Second:
Vote:
Motion:
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

14. PAR Scope, Purpose Scope of Proposed Project:
September 2007
doc.: IEEE /2464r1
September 2007
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)
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

15. TGy Purpose, Principles
September 2007
doc.: IEEE /2464r1
September 2007
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.
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

16. September 2007
doc.: IEEE /2464r1
September 2007
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.
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

17. Proposal of 06/1023r0 The way forward for TGy
September 2007
doc.: IEEE /2464r1
September 2007
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

18. Four Themes of TGy Interference Identification and Resolution,
September 2007
doc.: IEEE /2464r1
September 2007
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

19. TGy Work completed to 15 Sept, 2007
September 2007
doc.: IEEE /2464r1
September 2007
TGy Work completed to 15 Sept, 2007
WG Letter Ballot was conducted on P802.11y D4.0, 189 comments are recorded in 07/2333r4
LB109 results (as announced 29 August by WG vice-chair)
Voter pool 347, 327 ballots received
Approved 250, Do not approve 17, Abstain 60
(approval rate 93.63%, passes)
11 Sept Teleconference discussed all technical comments, and five submissions (07/2364, 07/2365, 07/2382, 07/2383 and 07/2384). The current versions were posted on the server and announced on the TGy list Monday morning.
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

20. Recirculation ballot Negative vote comments
September 2007
doc.: IEEE /2464r1
September 2007
Recirculation ballot Negative vote comments
IEEE-SA Standards Board Operations Manual  
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

21. Recirculation Comment classifications
September 2007
doc.: IEEE /2464r1
September 2007
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

22. Review LB109 comments and Submissions
September 2007
doc.: IEEE /2464r1
September 2007
Review LB109 comments and Submissions
11-07/2333r4 has all comments
Review ‘Master LB109 Original Comments’ and ‘Master LB ’ sheets
y-phy misc comments resolution.doc
y-LB109-ECSA-comments
y-LB109-Submission-for-DSE-comments.doc
y-LB109-Non-Editorial-comments-submission.doc
y-LB109-Editorial-comments-submission.doc
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

23. September 2007
doc.: IEEE /2464r1
September 2007
Motions (3)
Motion: Move to accept draft normative text changes in submissions 07/2364r0, 07/2365r2, 07/2382r2, 07/2383r1, 07/2384r1, and merge their comment resolutions into r4, and instruct the technical editor to prepare P802.11y draft 4.1.
Moved:
Second:
Vote:
Motion:
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

24. September 2007
doc.: IEEE /2464r1
September 2007
Motions (4)
Motion: Instruct the technical editor to rename y draft 4.1 as P802.11y draft 5.0. Having addressed all comments arising from the WG Letter Ballot 109, Task Group y resolves to forward P802.11y draft 5.0 to the working group for the purpose of conducting a 15-day recirculation 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 15-day Working Group Recirculation Letter Ballot of P802.11y draft 5.0, asking the question “Should the P802.11y draft 5.0 be forwarded to sponsor ballot?””
Moved:
Second:
Vote:
Motion:
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

25. Process of Getting to Letter Ballot and Beyond
September 2007
doc.: IEEE /2464r1
September 2007
Process of Getting to Letter Ballot and Beyond
Completed Steps | Future Steps
Adoption of PAR and 5 Criteria
Technical Presentations and Discussions
Specify Any Additional Requirements, Comparison Criteria, or Other Documents
Call For Proposals
Presentation of Proposals
Select from Submitted Complete Proposals to Produce a Draft
Refine Draft
Letter Ballot – November 2006
Recirculation – March, May 2007, July 2007, Sept 2007
Sponsor Ballot – November 2007(?)
Recirculation
Final WG/EC Approval
IEEE SB REVCOM Approval
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

26. 3 Cycles of Comments and Resolution
September 2007
doc.: IEEE /2464r1
September 2007
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

27. Schedule Projected at Waikoloa (Sept)
September 2007
doc.: IEEE /2464r1
September 2007
Schedule Projected at Waikoloa (Sept)
September 2007 (Waikoloa, Hawaii)
Comment Resolution, recirculation
October 23 ad hoc comment resolution meeting
November 2007 (Atlanta, Georgia)
In Sponsor Ballot
January 2008
Sponsor Ballot Comment Resolution
March 2008
WG, ExCom Approval, RevCom Approval
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems

28. Attendance Tuesday AM1: Thursday PM2: September 2007 September 2007
doc.: IEEE /2464r1
September 2007
Attendance
Tuesday AM1:
Thursday PM2:
Peter Ecclesine, Cisco Systems
Peter Ecclesine, Cisco Systems