1. 802.11 Policies and Procedures Status and Plans
March 2009
doc.: IEEE /0363r0
March 2009
Policies and Procedures Status and Plans
Date:
Authors:
Jon Rosdahl, CSR
Jon Rosdahl, CSR

2. March 2009
doc.: IEEE /0363r0
March 2009
Abstract
This Presentation explains why and how the P&P are being updated.
Jon Rosdahl, CSR
Jon Rosdahl, CSR

3. What is the Status of our Sponsor’s P&P?
March 2009
What is the Status of our Sponsor’s P&P?
IEEE 802 is our Sponsor
Currently they have submitted the LMSC P&P to AudCom for approval.
The Requirements:
In accordance with Section the IEEE-SA Standards Board Operations Manual, a sponsor’s P&P shall be subject to review every 5 years. Since the baseline P&Ps are subject to frequent review, it is inevitable that significant changes in the baseline P&P will be made in the 5 year period following approval of a Sponsor’s P&P. Therefore, AudCom will initiate the 5-year review process by requiring the sponsor to submit a revised P&P reflecting the latest baseline P&P to AudCom for review. AudCom will review the revised P&P against the current baseline P&P.
Jon Rosdahl, CSR

4. What may we expect for the WG P&P?
March 2009
What may we expect for the WG P&P?
WG P&P are going to be required
My expectation is that next week AudCom and the Standards Board will mandate that by 1 Jan 2010 we will need to have a compliant P&P.
Baseline P&P
Jon Rosdahl, CSR

5. Policies and Procedures vs. Operation Manual
March 2009
Policies and Procedures vs. Operation Manual
The current P&P will be broken into two components
1. Policies and Procedures
Fundamental Principles
Working Group Responsibilities
2. Operations Manual
Voting privileges
Meeting operation
Task Group, Standing Committee, and AdHoc operation
Jon Rosdahl, CSR

6. New Philosophy Fewer “Rules More individual responsibility Principles
March 2009
New Philosophy
Fewer “Rules
More individual responsibility
Principles
Jon Rosdahl, CSR

7. Why We Need Operating Procedures
March 2009
doc.: IEEE /0363r0
March 2009
Why We Need Operating Procedures
Gives an orderly process for running meetings
Creates a public record of group policies
Contributes towards two imperative principles of standards development process
Due Process
Openness
So why do you need procedures? Procedures help to achieve several goals. First of all, they give you a method for setting up an orderly meeting process. They let everyone involved or anyone interested in becoming involved in your working group know exactly what the rules are that they will have to follow to be a member of your standards activity. This also helps to create a visible record of your policies for the general public to access and consult.
Because you’ll be doing these things, you’ll also be fulfilling two of the imperative principles that support the idea of consensus standards development–due process and openness. Due process is achieved in standards development by having procedures and making them available. One part of achieving openness is allowing everyone access to your methods of participation through publicly available procedures. (However, this is only one part of the principle of openness.) Contributing towards both of these goals is crucial to having well-supported standards development.
Jon Rosdahl, CSR
Jon Rosdahl, CSR

8. Key Points to Cover Membership/voting rights Fees Officers
March 2009
doc.: IEEE /0363r0
March 2009
Key Points to Cover
Membership/voting rights
Fees
Officers
Officer succession
Interpretations
Revising procedures
Notice
There are seven key issues that should be covered in your procedures: voting rights in your working group, fees, officers, officer succession, interpretations, revising procedures, and notice. If your sponsor procedures don’t outline rules and policies in these areas, you should. Let’s look at each issue in particular.
Jon Rosdahl, CSR
Jon Rosdahl, CSR

9. View of New P&P 1. Preface 2. Modifications to these procedures
March 2009
View of New P&P
1. Preface
2. Modifications to these procedures
3. Hierarchy
4. Fundamental Principles of Operation
5. Working Group Responsibilities
6. Working Group Officers
7. Working Group
8. Working Group Member Roster
9. Voting
10. Meetings
11. Conduct
12. Appeals
13. Communications
Jon Rosdahl, CSR

10. 6. Working Group Officers
March 2009
6. Working Group Officers
6.1 Working Group Officer Overview
6.2 Election of WG Officers
6.3 Temporary Appointments to Vacancies
6.4 Removal of officers
6.5 Responsibilities of Working Group Officers
6.5.1 WG Chair
6.5.2 WG Vice-Chair(s
6.5.3 WG Secretary
6.5.4 WG Treasurer
6.5.5 WG Technical Editor
Jon Rosdahl, CSR

11. 7. Working Group 7.1 Overview 7.2 Working group membership status
March 2009
7. Working Group
7.1 Overview
7.2 Working group membership status
7.3 Subgroups of the Working Group
Jon Rosdahl, CSR

12. 8. Working Group Member Roster
March 2009
8. Working Group Member Roster
8.1 Working Group Member list
Jon Rosdahl, CSR

13. 9. Voting 9.1 Approval of an action
March 2009
9. Voting
9.1 Approval of an action
9.2 Actions Requiring Approval by a Majority
9.3 Actions Requiring Approval by three-quarters Vote
9.4 Voting between meetings
9.5 Quorum
Jon Rosdahl, CSR

14. Plan going forward Receive comment Fix-up links and references
March 2009
Plan going forward
Receive comment
Fix-up links and references
Discuss new documents on reflector.
Discuss any major edits during May Meeting
Approval of new Documents in July Plenary Session
This is due to the existing P&P change policy.
Jon Rosdahl, CSR