Re-charter Proposal

1
Re-charter Proposal

• Dorothy Gellert

2
Re-charter Proposal for WG Consensus

• Scope
• Build upon the original charter to develop a
  CAPWAP protocol to provide interoperability among
  WLAN controller backend architectures
• Comment to limit scope to specific cases of
  Centralized Architectures
• Goals
• Define a set of Objectives based on the
  architecture taxonomy work that list the
  requirements for an interoperable CAPWAP
  protocol.
• Evaluate a set of candidate protocols as a basis
  for the CAPWAP protocol.
• Develop a CAPWAP protocol standard.
• Create MIBs to support the CAPWAP protocol.

3
Objectives Draft

• Provides a Vendor and Customer perspective
• Based on the Architecture Taxonomy draft
• Includes Operational requirements
• Lists IEEE AP functional features to be
  distributed
• IEEE liaison help as needed
• Reviewed by IEEE and IETF Expert review
• Why Objectives?
• More than a requirement.
• Includes motivation for requirement
• Applicability to problem statement
• Description
• Classification and Prioritization into categories
• Mandatory and Accepted
• Desirable
• Rejected
• Designed to avoid requirement bloat

4
Evaluate proposals

• Evaluate set of candidate protocols
• Based on the Objectives draft
• New protocols
• Existing IETF protocols
• Prioritize if all considered protocols meet the
  stated Objectives.
• Selection will be the base protocol for CAPWAP
  Protocol

5
CAPWAP Protocol MIB

• Based on Selected Protocol from Evaluation
  Document
• Meets Mandatory and Accepted Objectives
• Desirable objectives may be considered in
  extensions
• Minimal Set of Features needed
• Performance considerations
• RFC 2418 format
• Architecture, Operations, Security, Network
  Management, Scalability
• MIB support for the CAPWAP Protocol

6
Goals Milestones

• Oct 04 Issue first Internet-Draft of CAPWAP
  Objectives document
• Jan 05 Call for candidate protocol proposals
• Feb 05 Submit CAPWAP Objectives to IEEE/IETF
  experts review
• Apr 05 Issue first Internet-Draft of CAPWAP
  Evaluation draft
• May 05 WGLC for CAPWAP Objectives Draft
• Jun 05 Submit CAPWAP Objectives draft to IESG as
  Informational RFC
• Jun 05 WGLC for CAPWAP Evaluation draft
• Jul 05 Submit CAPWAP Evaluation draft to IESG as
  Information RFC
• Aug 05 Issue first Internet Draft of CAPWAP
  protocol
• Sep 05 Issue first Internet-Draft of CAPWAP MIB.
• Oct 05 WGLC for CAPWAP protocol
• Nov 05 Submit CAPWAP protocol to IESG as
  Proposed Standard RFC
• Nov 05 WGLC for CAPWAP MIB
• Jan 06 Submit CAPWAP MIB to IESG as Proposed
  Standard RFC

7
Discussion

• WG Consensus
• On the approach
• Deliverables
• Timelines
• Issues to consider
• Requirement drafts tend to take years in IETF
• Protocol proposals may be so similar that
  consensus is not clear stalemate occurs
• AAA, Midcom
• Dependence on IEEE
• Preventative measures
• 6-9 month limit for requirements stage
• Objective approach
• Limited scope and minimal requirement set
• IEEE Liaisons in Place
• IEEE Agreement and AP Functions Study Group
  established