March, 2004

Matthew Sherman, BAE SystemsSlide 1

doc.: IEEE 802.0-04/XXXr0

Submission

Keep 802 Together Proposal

Date: March 15, 2003

Point of Contact:Matthew Sherman

2nd Vice Chair, IEEE 802BAE Systems - CINR

Matthew.Sherman@BAESystems.com

Contributors:Bob Grow,

Matthew Sherman, Bill Quakenbush,

Roger Marks

March, 2004

Matthew Sherman, BAE SystemsSlide 2

doc.: IEEE 802.0-04/XXXr0

Submission

Goals

• Define reorganization within existing 802• Address concerns expressed at Nov. ’03 meeting

March, 2004

Matthew Sherman, BAE SystemsSlide 3

doc.: IEEE 802.0-04/XXXr0

Submission

Approach

• Develop resolutions to major concerns raised• Evolve strawman reorg proposal based on

resolutions• Present strawman to EC in March ‘04• Address additional concerns expressed• Refine proposal• Solicit inputs from CS and SA• Bring to vote in July ‘04

March, 2004

Matthew Sherman, BAE SystemsSlide 4

doc.: IEEE 802.0-04/XXXr0

Submission

New Organization Highlights

• Preserves 802 as market facing and oversight entity– 802 Architecture preserved

• Greater independence to WG• Changes purely through P&P

– Limit content to key topics• Center on Pars req, Sponsor ballot req, EC ballots, tutorials

• Rely on Higher P&P and WG P&P for all else

– May need / want to move to SCC

March, 2004

Matthew Sherman, BAE SystemsSlide 5

doc.: IEEE 802.0-04/XXXr0

Submission

Concerns and Suggested Resolutions

March, 2004

Matthew Sherman, BAE SystemsSlide 6

doc.: IEEE 802.0-04/XXXr0

Submission

Concern: Logistics problems associated with size

Resolution: Allow separate WG Plenary

802 hosted plenary 3 times per year if desiredFor WG who don’t want treasury

One full Plenary per yearEncourage cross-polinization between groupsHave every 2 years if every year too much

Short electronic EC after each plenaryAllows quick action by EC on issuesTelecom augmented with web conferencing

March, 2004

Matthew Sherman, BAE SystemsSlide 7

doc.: IEEE 802.0-04/XXXr0

Submission

Concern: Current P&P are broken

Resolution:Rework around Model P&P

Minimize content with ref to other docsIncorporate mods based on this docMove to SCC format if needed

March, 2004

Matthew Sherman, BAE SystemsSlide 8

doc.: IEEE 802.0-04/XXXr0

Submission

Concern: Maintaining architectural consistency across MACs wrt future organization

Resolution:802 still approves all PARs and Sponsor BallotsAll other issues determined by WG

March, 2004

Matthew Sherman, BAE SystemsSlide 9

doc.: IEEE 802.0-04/XXXr0

Submission

Concern: Increased friction between WGs

Resolution:Reduce interactions to

PARs Sponsor BallotsNew activity tutorial

If conflict with 802 tutorialsWG allocates WG time

Electronic pres in non-802 Plenary12 votes so limited impact of any one group

Hard to block unless serious problemAll other issues left to WG

March, 2004

Matthew Sherman, BAE SystemsSlide 10

doc.: IEEE 802.0-04/XXXr0

Submission

Concern: Continually at odds over operational style and procedures

Resolution:See section on “increased friction”

March, 2004

Matthew Sherman, BAE SystemsSlide 11

doc.: IEEE 802.0-04/XXXr0

Submission

Concern: Difficulty of coordinating technical work across a group of this size

Resolution: Don’t know how to do better than curret org

March, 2004

Matthew Sherman, BAE SystemsSlide 12

doc.: IEEE 802.0-04/XXXr0

Submission

Concern: Need to devolve power from EC to WGs

Resolution:See slide on “increased friction”

March, 2004

Matthew Sherman, BAE SystemsSlide 13

doc.: IEEE 802.0-04/XXXr0

Submission

Concern: Operational efficiency of WGs

Resolution:Up to WG to set their own paceMust comply with SA requirements, etc.

March, 2004

Matthew Sherman, BAE SystemsSlide 14

doc.: IEEE 802.0-04/XXXr0

Submission

Concern: Large groups need faster response time, more dynamic environment, without losing quality

Resolution:See slide on “increased friction”

March, 2004

Matthew Sherman, BAE SystemsSlide 15

doc.: IEEE 802.0-04/XXXr0

Submission

Detailed Reorganization Proposal

• To be added if fundamental approach approved by 2/3’s of EC

• Fully handled via P&P Changes

• Move to SCC format if needed