Upload
katherine-morgan-harper
View
217
Download
0
Embed Size (px)
DESCRIPTION
doc.: IEEE /0147r0 Submission 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 January 2011 Rolf de Vegt (Qualcomm) Slide 3
Citation preview
doc.: IEEE 802.11-12/0147r0
Submission
January 2012
Rolf de Vegt (Qualcomm))Slide 1
802.11ai Spec Development Process Update Proposal
Date: 2012-01-18
Name Affiliations Phone email Rolf de Vegt Qualcomm, Inc +1 408 533 9545 [email protected]
Authors:
doc.: IEEE 802.11-12/0147r0
Submission
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
January 2011
Rolf de Vegt (Qualcomm)Slide 2
doc.: IEEE 802.11-12/0147r0
Submission
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
January 2011
Rolf de Vegt (Qualcomm)Slide 3
doc.: IEEE 802.11-12/0147r0
Submission
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
January 2011
Rolf de Vegt (Qualcomm)Slide 4
doc.: IEEE 802.11-12/0147r0
Submission Rolf de Vegt, Qualcomm, Inc.
May, 2008
Slide 5
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
doc.: IEEE 802.11-12/0147r0
Submission Rolf de Vegt, Qualcomm, Inc.
May, 2008
Slide 6
High Level Overview of Spec Framework based Process
1. 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
2. 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
3. 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
doc.: IEEE 802.11-12/0147r0
Submission Rolf de Vegt, Qualcomm, Inc.
May, 2008
Slide 7
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
doc.: IEEE 802.11-12/0147r0
Submission
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
January 2011
Rolf de Vegt (Qualcomm)Slide 8
doc.: IEEE 802.11-12/0147r0
Submission
Process FlowMay 2011
Tom Siep, CSRSlide 9Source: 11/0748r3
doc.: IEEE 802.11-12/0147r0
Submission Tom Siep, CSR
Description of steps1. Define process and requirements2. Call for Proposals (CFP)3. Evaluation Methodology4. Review submissions for adherence to CFP5. Conforms to CFP?6. Submitter(s) revision7. Solution overlap?8. Merge solutions9. 75% Approval? (Submissions)10. Prepare Draft11. 75% Approval? (Drafts)12. Comment Resolution13. Technically Complete?14. Ready for WG Ballot
May 2011
Slide 10Source: 11/0748r3
doc.: IEEE 802.11-12/0147r0
Submission
View of ‘De Facto’ Tgai Spec Development Process
January 2011
Rolf de Vegt (Qualcomm)Slide 11
Security Framework Spec Text
IP Address Assignment
Spec Text
Fast Network Discovery Spec Text
75%?
Y
75%?
Y
75%?
Y
.11ai Draft
75%?
Y
Go out to Letter Ballot
Security Framework
IP Address Assignment
Fast Network Discovery
Source: 12/0025r1
doc.: IEEE 802.11-12/0147r0
Submission
Alternative View of Existing process for Draft Creation
August 2011
Slide 12
Source: 11/1109r0 slide 4Rolf de Vegt (Qualcomm)
doc.: IEEE 802.11-12/0147r0
Submission
Potential Issues with Current Process1. 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
2. Significant risk of ‘Feature bloat’ due to emphasis of merging of overlapping contributions
3. Risk of inconsistencies and lack of attention to critical dependencies between the text proposals for the separate .11ai functional areas
4. Insufficient conflict resolution mechanism in case of overlapping solutions that have achieved 75% approval
5. Process is relatively complicated and appears to be not very well understood across Taskgroup membership
6. Vests relatively significant powers in Taskgroup leadership in determining whether a proposal is in scope and/or needs to be modified
January 2011
Rolf de Vegt (Qualcomm)Slide 13
doc.: IEEE 802.11-12/0147r0
Submission
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
January 2011
Rolf de Vegt (Qualcomm)Slide 14
doc.: IEEE 802.11-12/0147r0
Submission
Proposal for Updated Tgai Process
January 2011
Rolf de Vegt (Qualcomm)Slide 15
Functional Requirements(Doc 11/745)
TechnicalContributionTechnical
ContributionTechnicalContribution
75%
Y
Add to Spec
Framework? Spec FrameworkDocument
Detailed Spec Text
TechnicalContributionTechnical
ContributionSpec
FrameworkText
75%
Spec AddressesSpec Frameworkand ready for LB?
TG or WG Letter Ballot
Spec Text
Contributions
doc.: IEEE 802.11-12/0147r0
Submission
Overview of Proposed New Steps (part 1)
• 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
January 2011
Rolf de Vegt (Qualcomm)Slide 16
doc.: IEEE 802.11-12/0147r0
Submission
Overview of Proposed New Steps (Part 2)• Detailed Spec Text
– The Taskgroup Spec Editor is responsible for maintaining the .11ai Draft Spec Text
• 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 with 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
January 2011
Rolf de Vegt (Qualcomm)Slide 17
doc.: IEEE 802.11-12/0147r0
Submission
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
January 2011
Rolf de Vegt (Qualcomm)Slide 18
doc.: IEEE 802.11-12/0147r0
Submission
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
January 2011
Rolf de Vegt (Qualcomm)Slide 19
doc.: IEEE 802.11-12/0147r0
Submission
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– Do Not Agree– Abstain
January 2011
Rolf de Vegt (Qualcomm)Slide 20
doc.: IEEE 802.11-12/0147r0
Submission
Back Up
January 2011
Rolf de Vegt (Qualcomm)Slide 21
doc.: IEEE 802.11-12/0147r0
Submission
Proposal for Updated Process Flow*May 2011
Tom Siep, CSRSlide 22
TechnicalContributionTechnical
ContributionTechnicalContribution
75%
Y
Add to Spec
Framework? Spec FrameworkDocument
Detailed Spec Text
TechnicalContributionTechnical
ContributionSpec
FrameworkText
75%
Spec AddressesSpec Framework
and ready for LB?
TG or WG Letter Ballot
Spec Text
Contributions
* Depicting Linkage with existing process
doc.: IEEE 802.11-12/0147r0
Submission
Contingency: What to do with Detailed Spec text that has already been adoption by TG Motion?
January 2011
Rolf de Vegt (Qualcomm)Slide 23
Functional Requirements(Doc 11/745)
TechnicalContributionTechnical
ContributionTechnicalContribution
75%
Y
Add to Spec
Framework? Spec FrameworkDocument
Detailed Spec Text
TechnicalContributionTechnical
ContributionSpec
FrameworkText
75%
Spec AddressesSpec Frameworkand ready for LB?
TG or WG Letter Ballot
Spec Text
Contributions
1. Distill essence of Adopted Text and Insert statements into Spec Framework Document2. Use the detailed Spec Text Contribution when creating Detailed Spec Document