802.11ai Spec Development Process Update Proposal Month Year doc.: IEEE 802.11-10/0xxxr0 January 2012 802.11ai Spec Development Process Update Proposal Date: 2012-01-18 Authors: Rolf de Vegt (Qualcomm)) David Halasz, OakTree Wireless

Contents Context and Introduction Month Year doc.: IEEE 802.11-10/0xxxr0 January 2011 Contents Context and Introduction Rationale for introducing a Spec Framework Document step in previous projects Current TGai selection process and potential issues Proposed update to the TGai spec development process Next Steps Rolf de Vegt (Qualcomm) David Halasz, OakTree Wireless

Context and Introduction Month Year doc.: IEEE 802.11-10/0xxxr0 January 2011 Context and Introduction In document 12/0025r1 the concept of adding a Spec Framework step to the .11ai Selection Procedure was introduced Strawpolls showed significant support to further explore this approach This document contains further background on the intended benefits of a Spec Framework document and outlines proposed changes to the current TGai Selection Procedure as described in document 11/0748r2 Rolf de Vegt (Qualcomm) David Halasz, OakTree Wireless

Contents Context and Introduction Month Year doc.: IEEE 802.11-10/0xxxr0 January 2011 Contents Context and Introduction Rationale for introducing a Spec Framework Document step in previous projects Current TGai selection process and potential issues Proposed update to the TGai spec development process Next Steps Rolf de Vegt (Qualcomm) David Halasz, OakTree Wireless

Month Year doc.: IEEE 802.11-yy/xxxxr0 May, 2008 Historic Context The Selection Procedure used for 802.11n and other 802.11 was based on a process of continuous down selects of competing proposals The use of this down-select procedure has contributed to considerable delays in the standardization process ‘Battles’ between competing proposal camps Scope / feature / option creep In the case of .11ac and later in .11ah an alternative procedure was adopted Rolf de Vegt, Qualcomm, Inc. John Doe, Some Company

High Level Overview of Spec Framework based Process Month Year doc.: IEEE 802.11-yy/xxxxr0 May, 2008 High Level Overview of Spec Framework based Process Taskgroup develops consensus around a framework for spec elements Aim is to achieve consensus Spec Framework text is added with 75% Taskgroup approval Taskgroup votes to approve a document that describes all spec elements, with the intent that this solidifies the scope and contents of the new specification Participants create detailed text proposals for one or more spec elements Could in theory cover all Spec Elements (i.e. ‘Complete Proposal’) but not necessarily Once the Taskgroup has a coherent enough solution for all spec elements, a vote takes place to send the draft spec out for Taksgroup Review or Working Group Letterballot Rolf de Vegt, Qualcomm, Inc. John Doe, Some Company

Key Benefits of Spec Framework Approach* Month Year doc.: IEEE 802.11-yy/xxxxr0 May, 2008 Key Benefits of Spec Framework Approach* Emphasis on consensus building Technology selection based on technical merits Fair and balanced consideration of which elements to include in the spec Equal access for all participants to contribute technically sound elements to the specification Decision process favors a single solution for a problem over multiple alternative solutions Source: Doc 11-08-0579r0 slide 8 Rolf de Vegt, Qualcomm, Inc. John Doe, Some Company

Contents Context and Introduction Month Year doc.: IEEE 802.11-10/0xxxr0 January 2011 Contents Context and Introduction Rationale for introducing a Spec Framework Document step in previous projects Current TGai selection process and potential issues Proposed update to the TGai spec development process Next Steps Rolf de Vegt (Qualcomm) David Halasz, OakTree Wireless

Process Flow May 2011 Month Year doc.: IEEE 802.11-yy/xxxxr0 Source: 11/0748r3 Tom Siep, CSR John Doe, Some Company

Description of steps Define process and requirements Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2011 Description of steps Define process and requirements Call for Proposals (CFP) Evaluation Methodology Review submissions for adherence to CFP Conforms to CFP? Submitter(s) revision Solution overlap? Merge solutions 75% Approval? (Submissions) Prepare Draft 75% Approval? (Drafts) Comment Resolution Technically Complete? Ready for WG Ballot Source: 11/0748r3 Tom Siep, CSR John Doe, Some Company

View of ‘De Facto’ Tgai Spec Development Process Month Year doc.: IEEE 802.11-10/0xxxr0 January 2011 View of ‘De Facto’ Tgai Spec Development Process Security Framework Spec Text 75% ? Y .11ai Draft Security Framework Go out to Letter Ballot IP Address Assignment Spec Text 75% ? Y 75% ? Y IP Address Assignment Fast Network Discovery Fast Network Discovery Spec Text 75% ? Y Source: 12/0025r1 Rolf de Vegt (Qualcomm) David Halasz, OakTree Wireless

Alternative View of Existing process for Draft Creation Month Year doc.: IEEE 802.11-yy/xxxxr0 August 2011 Alternative View of Existing process for Draft Creation Source: 11/1109r0 slide 4 Rolf de Vegt (Qualcomm) Tom Siep, CSR

Potential Issues with Current Process Month Year doc.: IEEE 802.11-10/0xxxr0 Potential Issues with Current Process January 2011 Emphasizes creation of detailed Spec text, before taskgroup consensus / majority is established of the Spec Framework level contents of the specification Focuses taskgroup discussions on issues related to detailed text, before a common understanding of higher level concepts and rationale is established Risk of embarking on a process of continuous rewrites of detailed text which may be hard to follow for the broader audience Less efficient Significant risk of ‘Feature bloat’ due to emphasis of merging of overlapping contributions Risk of inconsistencies and lack of attention to critical dependencies between the text proposals for the separate .11ai functional areas Insufficient conflict resolution mechanism in case of overlapping solutions that have achieved 75% approval Process is relatively complicated and appears to be not very well understood across Taskgroup membership Vests relatively significant powers in Taskgroup leadership in determining whether a proposal is in scope and/or needs to be modified Rolf de Vegt (Qualcomm) David Halasz, OakTree Wireless

Contents Context and Introduction Month Year doc.: IEEE 802.11-10/0xxxr0 January 2011 Contents Context and Introduction Rationale for introducing a Spec Framework Document step in previous projects Current TGai selection process and potential issues Proposed update to the TGai spec development process Next Steps Rolf de Vegt (Qualcomm) David Halasz, OakTree Wireless

Proposal for Updated Tgai Process Month Year doc.: IEEE 802.11-10/0xxxr0 January 2011 Proposal for Updated Tgai Process Functional Requirements (Doc 11/745) Technical Contribution 75% Y Add to Spec Framework? Spec Framework Document Detailed Spec Text (Draft) Spec Framework Text Spec Addresses Spec Framework and ready for LB? TG or WG Letter Ballot Spec Text Contributions Rolf de Vegt (Qualcomm) David Halasz, OakTree Wireless

Overview of Proposed New Steps (part 1) Month Year doc.: IEEE 802.11-10/0xxxr0 Overview of Proposed New Steps (part 1) January 2011 Technical Contribution Based on the Functional Requirements and Criteria outlined in the Call for Proposals, submitters create a technical presentation that proposes to add certain feature/ set of features / spec element / technology to the spec Submitters will need to provide sufficient technical justification in order to convince at least 75% of the taskgroup Use of straw-polling to determine taskgroup support Spec Framework Text Technical contribution, or subsequent submission includes proposed text + Motion for addition to the spec framework document Taskgroup passes Motion (75%) to add statement / text to Spec Framework document Spec Framework Document Taskgroup appoints a Spec Framework Editor Taskgroup reviews and approves all additions and updates to the Spec Framework by Motion (75%) at the end of each face to face session during which Motions to add / change Spec Framework elements have passed Rolf de Vegt (Qualcomm) David Halasz, OakTree Wireless

Overview of Proposed New Steps (Part 2) Month Year doc.: IEEE 802.11-10/0xxxr0 Overview of Proposed New Steps (Part 2) January 2011 Detailed Spec Text The Taskgroup Spec Editor is responsible for maintaining the .11ai Draft Spec Text (This the text of the Draft Amendment) Spec Text Contribution The Taskgroup Editor solicits Spec Text contributions that implement the Full Spec Framework or Subsections of the Spec Framework Collaboration on a single contribution for a given subset of the Spec Framework or for the entire scope of the spec framework are encouraged In case of multiple contributions addressing the same spec framework elements, taskgroup straw-polling and Motions will guide the editor regarding which Spec Text Contribution to use TG or WG Letter Ballot By taskgroup Motion (75%), the group decides to conduct either a taskgroup comment resolution process on the completed Draft Spec, or go to Working Group Letter Ballot Rolf de Vegt (Qualcomm) David Halasz, OakTree Wireless

Contents Context and Introduction Month Year doc.: IEEE 802.11-10/0xxxr0 January 2011 Contents Context and Introduction Rationale for introducing a Spec Framework Document step in previous projects Current TGai selection process and potential issues Proposed update to the TGai spec development process Next Steps Rolf de Vegt (Qualcomm) David Halasz, OakTree Wireless

Month Year doc.: IEEE 802.11-10/0xxxr0 January 2011 Proposed Next Steps Solicit Taskgroup feedback on Proposed Update to the Process Conduct Strawpoll regarding the Updated Process If sufficient support for Updated Process exists, generate a detailed description of the Updated Process (word doc) and present to TG for review Iterate on detailed write up based on feedback Taskgroup Motion regarding adopting updated process Rolf de Vegt (Qualcomm) David Halasz, OakTree Wireless

Month Year doc.: IEEE 802.11-10/0xxxr0 January 2011 Strawpoll Agree with the Updated process described in this document in concept and approve proceeding with the generation of a detailed write up of the Updated Process for Taskgroup review Agree 38 Do Not Agree 2 Abstain 10 Rolf de Vegt (Qualcomm) David Halasz, OakTree Wireless

Month Year doc.: IEEE 802.11-10/0xxxr0 January 2011 Motion The group agrees to adopt the process as outlined on slide 15 of 11-12/0147r0 The agenda is modified so that work can begin on the spec framework immediately following this motion Moved: Robert Second: Lei Yes 28- No 5 – Abstain 3 Rolf de Vegt (Qualcomm) David Halasz, OakTree Wireless

Back Up January 2011 Month Year doc.: IEEE 802.11-10/0xxxr0 Rolf de Vegt (Qualcomm) David Halasz, OakTree Wireless

Proposal for Updated Process Flow* Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2011 Proposal for Updated Process Flow* * Depicting Linkage with existing process Tom Siep, CSR John Doe, Some Company

Month Year doc.: IEEE 802.11-10/0xxxr0 January 2011 Contingency: What to do with Detailed Spec text that has already been adoption by TG Motion? Functional Requirements (Doc 11/745) Technical Contribution 75% Y Add to Spec Framework? Spec Framework Document Detailed Spec Text Spec Framework Text Spec Addresses Spec Framework and ready for LB? TG or WG Letter Ballot Spec Text Contributions Distill essence of Adopted Text and Insert statements into Spec Framework Document Use the detailed Spec Text Contribution when creating Detailed Spec Document Rolf de Vegt (Qualcomm) David Halasz, OakTree Wireless