TGu Process Date: 2005-01-18 Authors: January 2005 January 2005 doc.: IEEE 802.11-05/1584r1 January 2005 TGu Process Date: 2005-01-18 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>. Stephen McCann, Siemens Roke Manor Stephen McCann, Siemens Roke Manor

January 2005 doc.: IEEE 802.11-05/1584r1 January 2005 Abstract Presentation of a possible TGu process, indicating what the goals of the TG are and what work has to be done, by when. Stephen McCann, Siemens Roke Manor Stephen McCann, Siemens Roke Manor

Generic Process of Getting to Letter Ballot January 2005 doc.: IEEE 802.11-05/1584r1 January 2005 Generic Process of Getting to Letter Ballot Adoption of PAR and 5 Criteria Technical Presentations and Discussions Specify Any Additional Requirements, Comparison Criteria, or Other Documents Call For Proposals Select/Combine from Submitted Complete/Partial Proposals to Produce a Draft Refine Draft Letter Ballot Stephen McCann, Siemens Roke Manor Stephen McCann, Siemens Roke Manor

Historical 802.11 Project Timelines January 2005 Historical 802.11 Project Timelines Time from PAR approval to first Letter Ballot – average of 6.6 meetings / 13 months TGe-7, TGf-7, TGg-9, TGh-4, TGi-6 Time from first Letter Ballot to first Sponsor Ballot – average of 9 meetings / 18 months TGe-12, TGf-9, TGg-6, TGh-8, TGi-10 (above data compiled by Bruce Kraemer) Stephen McCann, Siemens Roke Manor

802.11u Project Timelines PAR approval was on 15 September 2004 January 2005 802.11u Project Timelines PAR approval was on 15 September 2004 At the normal pace for a Task Group, our first Letter Ballot would open in October 2005 and our first Sponsor Ballot in July 2006. Requirements and Selection Criteria Work on these procedural documents should be completed by May 2005, so that we can then have a call for proposals in July 2005. Things will generally happen slower than what we aim for. Stephen McCann, Siemens Roke Manor

January 2005 802.11u Project Timelines December 2004: call for input for January 2005: use cases requirements January 2005: Define selection criteria, formal scope and requirements January 2005: Define set of external entities to liaise with. Compile liaison letter requesting requirement input. January 2005: Call for informal preliminary presentations for March 2005 (on server by February 12th 2005) March 2005: Finish supporting documents March 14th 2005: Informal preliminary presentations March 2005: Call for formal proposals to be presented May 2005 (on server by April 15th 2005) May 16th, 2004: give preliminary one hour presentations; carry out first step of selection procedure Stephen McCann, Siemens Roke Manor

January 2005 802.11u Project Timelines June 15, 2005: Preliminary draft text and presentations available on server July 18, 2005: Extensive presentations (preliminary draft text), with feedback from group; carry out second step in selection procedure August 15, 2005: Extensive draft text and slides available on server. September 19, 2005: Give final proposals (final draft text and slides); carry out next step in selection procedure. September 2005: Start draft version 0 November 2005: Internal Task Group letter ballot on draft January 2006: Address comments from letter ballot Stephen McCann, Siemens Roke Manor

Ad Hoc Subgroups and TGs Working Documents January 2005 doc.: IEEE 802.11-05/1584r1 January 2005 Ad Hoc Subgroups and TGs Working Documents Ad Hoc Subgroups Have no special status unless TGs votes on them or their output. Any group of 802.11 members can get together and make submissions. Within the Policies and Procedures (11-04/510r0), we can do what we want internally: “Adopted” internal TGs motions/documents can be amended, replaced, or un-adopted. We can have a “Functional Requirements” document that is as general or specific as we like. Stephen McCann, Siemens Roke Manor Stephen McCann, Siemens Roke Manor

Documentation Procedure January 2005 Documentation Procedure Scenarios Requirements Selection Criteria Proposals Stephen McCann, Siemens Roke Manor

Example Problem Breakdown January 2005 Example Problem Breakdown Network Selection Problem Additional information is required for STAs regarding the characteristics of the network to support network selection decisions (e.g. roaming capabilities) Requirements To enable network selection decisions to be made prior to the commencement of the authentication procedure Selection Criteria Must not contain secure information Solutions ? Stephen McCann, Siemens Roke Manor

Possible Documents Functional Requirements and Scope – coordinator xxx January 2005 doc.: IEEE 802.11-05/1584r1 January 2005 Possible Documents Functional Requirements and Scope – coordinator xxx “Functional Requirements & Scope”, 11-05/1583r0 Selection Criteria – coordinator xxx “Selection Criteria”, 11-05/xxxxr0 Definitions – coordinator xxx “Terms and Definitions”, 11-05/1619r0 Usage Models – coordinator xxx “Usage Models”, 11-05/xxxxr0 Stephen McCann, Siemens Roke Manor Stephen McCann, Siemens Roke Manor

Informal Ad Hoc Subgroups January 2005 doc.: IEEE 802.11-05/1584r1 January 2005 Informal Ad Hoc Subgroups Form Ad Hoc subgroups for each document: Functional Requirements and Scope Comparison Criteria Definitions Usage Models Stephen McCann, Siemens Roke Manor Stephen McCann, Siemens Roke Manor

Internal Co-ordination January 2005 doc.: IEEE 802.11-05/1584r1 January 2005 Internal Co-ordination TGs Support for interfacing an ESS Mesh with other IEEE 802 LANs using 802.1D. E.g. something along the lines of 802.17 Annex F Advanced Security Group Portal Page requirement, MAC address anonymity TGr Network Detection and Selection requirement TGk ARID requirement TGe External QoS Mapping IEEE 802.21 Stephen McCann, Siemens Roke Manor Stephen McCann, Siemens Roke Manor

External Co-ordination January 2005 doc.: IEEE 802.11-05/1584r1 January 2005 External Co-ordination INTRWRK_SCP3Support for interfacing an ESS Mesh with other IEEE 802 LANs using 802.1DE.g. something along the lines of 802.17 Annex F Requirements capture from: 3GPP 3GPP2 WiFi Alliance GSMA TiSPAN Spacewire/IEEE 1394 UMA Etc Form External Entities Requirements Capture Ad Hoc subgroup Stephen McCann, Siemens Roke Manor Stephen McCann, Siemens Roke Manor

Schedule Projected at Monterey Meeting January 2005 doc.: IEEE 802.11-05/1584r1 January 2005 Schedule Projected at Monterey Meeting January 2005 (Monterey, California) Initial Work on procedural documentation: Functional Requirements and Scope Comparison Criteria Definitions Usage Models Call for preliminary presentations issued immediately after meeting with deadline for submission of two weeks before the March meeting. March 2005 (Atlanta, Georgia) Work on functional requirements and other documents that may be referenced in a future Call for Proposals Preliminary presentations, refinement of selection criteria Call for formal presentations issued immediately after meeting with deadline for submission of two weeks before the May meeting. May 2005 (Beijing, China) Presentation of proposals, refinement of selection criteria Stephen McCann, Siemens Roke Manor Stephen McCann, Siemens Roke Manor

Possibilities Between the January 2005 and March 2005 Meetings doc.: IEEE 802.11-05/1584r1 January 2005 Possibilities Between the January 2005 and March 2005 Meetings Possibilities for TGs Activity Between January 2005 and March 2005 Meetings to accelerate action : Multiple Teleconferences (require 10 days notice, cannot be held more often than weekly (P&P clause 3.6.3)) One Teleconference Additional official face to face meeting is probably not practical due to holidays and requirement for 30 days notice (P&P clause 3.6.2) Stephen McCann, Siemens Roke Manor Stephen McCann, Siemens Roke Manor

Teleconferences Motion January 2005 Teleconferences Motion Teleconferences Motion: Moved, that TGs have teleconferences at 11:00 Eastern Standard Time on 4 January, 5 January and 6 January 2005 . Notice will be given, including UTC time, at least 10 days in advance. Stephen McCann, Siemens Roke Manor