130 likes | 140 Views
This report summarizes the TGy activity at the IEEE 802.11 San Francisco meeting in July 2007, including motions, comment resolutions, and the schedule for future steps.
E N D
TGy July Closing Report Authors: Date: 2007-07-18 Peter Ecclesine, Cisco Systems
Abstract This submission summarizes the TGy activity for IEEE 802.11 San Francisco (July 2007) meeting Peter Ecclesine, Cisco Systems
Review LB106 comments and Submissions • 11-07/2019r5 has all comments • Review ‘Master LB106 Original Comments’ and ‘Master LB94-104-106’ sheets • 11-07-2058-02-000y-phy misc comments resolution.doc • 11-07-2066-01-000y-coexistence-assurance.doc • 11-07-2080-02-000y-LB106-Submission-for-DSE-comments.doc • 11-07-2073-02-000y-LB106-Non-Editorial-comments-submission.doc • 11-07-2072-02-000y-LB106-Editorial-comments-submission.doc • 11-07-2197-00-000y-discussion-on-cca-ed.doc • 11-07-2208-01-000y-tgy-conditional-sponsor-ballot-report.pdf Peter Ecclesine, Cisco Systems
Motions (4) Motion: Move to accept draft normative text changes in submissions 07/2058r2, 07/2072r2, 07/2073r2, 07/2080r2, and merge their comment resolutions into 07-2019r4, and instruct the technical editor to prepare P802.11y draft 3.1. Moved:Victoria Poncini Second:Jim Raab Vote: 6-0-0 Motion: Passes Peter Ecclesine, Cisco Systems
Motions (5) Motion: Move to change the resolutions of comments #288, #289, #436 from Declined to Counter, and #1034, #1101 to Accept in Principle Moved: Second: Vote: Motion: Peter Ecclesine, Cisco Systems
Motions (6) Motion: Move to accept draft normative text changes in submission 07/2197r0, and merge the comment resolutions into 07-2019r5, and instruct the technical editor to prepare P802.11y draft 3.2. Moved: Second: Vote: Motion: Peter Ecclesine, Cisco Systems
Motions (7) Motion: Instruct the technical editor to rename 802.11y draft 3.2 as P802.11y draft 4.0.Having addressed all comments arising from the WG Letter Ballot 106, Task Group y resolves to forward P802.11y draft 4.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 4.0, asking the question “Should the P802.11y draft 4.0 be forwarded to sponsor ballot?”” Moved: Second: Vote: Motion: Peter Ecclesine, Cisco Systems
Motions (8) Motion: Move to accept 07/2066r1 as the Coexistence Assurance letter from 802.11y to satisfy the requirements of the TGy 5 Criteria Moved: Second: Vote: Motion: Peter Ecclesine, Cisco Systems
Motions (9) Motion: To approve document 07/2208r1 as the report to the 802 Executive Committee (EC) on the requirements for conditional approval to forward 802.11y to sponsor ballot, requesting the chair of 802.11 to forward this report to the EC on behalf of the working group. Moved: Second: Vote: Motion: Peter Ecclesine, Cisco Systems
Motions (10) • To request conditional approval to send 802.11y to sponsor ballot upon conclusion of a working group recirculation ballot that meets all requirements in the LMSC Policies and Procedures. Moved: Second: Vote: Motion: Peter Ecclesine, Cisco Systems
Motion (11) • To authorize the 802.11 working group chair to send 802.11y to sponsor ballot, upon successful completion of a working group recirculation ballot that meets all requirements for conditional approval as set forth in the LMSC Policies and Procedures. Moved: Second: Vote: Motion: Peter Ecclesine, Cisco Systems
Schedule Projected at San Francisco (July) • May 2007 (Montreal, Quebec) • Second Letter Ballot Re-circulation, Sponsor Ballot pool formed • July 2007 (San Francisco, California) • Comment Resolution, Sponsor Ballot conditionally authorized • September 2007 (Waikoloa, Hawaii) • Comment Resolution, 1st SB Issued • November 2007 (Atlanta, Georgia) • Sponsor Ballot Comment Resolution, 1st SB Re-circ • January 2008 • Sponsor Ballot Comment Resolution • March 2008 • WG, ExCom Approval, RevCom Approval Peter Ecclesine, Cisco Systems
Attendance Tuesday AM1: 12 Thursday PM2: Peter Ecclesine, Cisco Systems