CAPWAP%20Working%20Group%20IETF%2059

1
CAPWAP Working GroupIETF 59

• Chairs
• Mahalingam Mani
• Dorothy Gellert

2
Agenda

• 1530 Agenda Chairs
• 1535 Status of Work Chairs
• 1550 Architecture Design Team Dorothy Gellert
• 1605 Architecture Draft Lily Yang
• 1620 IEEE Liaison Status Dorothy Stanley
• 1640 Current Issues List Mahalingam Mani
• 1700 Functionality Classification for CAPWAP
  draft Cheng Hong
• 1715 Open Discussion.

3
Changes since IETF 58

• New Charter
• http//www.ietf.org/html.charters/capwap-charter.h
  tml
• Phase 1, 6 months
• Problem Statement regarding deployment,
  management and usability of 802.11 networks
• No Architecture or Protocol Development at this
  time
• Analysis of currently Implemented 802.11 Network
  Architectures instead
• Includes threat analysis
• Expert reviews from IEEE and IETF
• IEEE cooperation for further work
• New Area Directors
• Bert Wijnen
• David Kessens

4
WG Last Call

• draft-ietf-capwap-problem-statement-00.txt
• Informational
• Last called ended March 2nd.
• 5 explicit responses, all I like it,
• Issues
• The Problem Statement section (2) does not seem
  to recognize the incompatibilities arising due to
  different types of functionality splits.
• Reference 1 is not found.
• Update draft and send to IESG for review.

5
Milestones

• Feb 04 Last call for problem statement
  draft. -DONE
• Mar 04 Discuss last call comments for problem
  statement at IETF 59.
• Mar 04 Last Call for architecture description
  document.
• Apr 04 Submit problem statement to IESG for
  publication approval.
• May 04 Architecture document to expert review.
• Jun 04 Stable Architecture document for
  review/sync-up with IEEE 802
• Jul 04 Discuss results of IEEE 802 review/sync-up
• Aug 04 Conclude WG OR Re-charter

6
Architecture Design Team

• Motivated by a need for focused, committed effort
  within a short timeframe.
• Poll for Volunteers
• Goal of 10, we have 12
• Selection based on industry representation
• Chair is a co-author of the current architecture
  draft.

7
DT Members

• Chair Lilly Yang, lily.l.yang_at_intel.com
• Partha Narasimhan, partha_at_arubanetworks.com
• Petros Zerfos, pzerfos_at_cs.ucla.edu
• Sadot, Emek, esadot_at_avaya.com
• Inderpreet Singh, isingh_at_chantrynetworks.com
• Matt Holdrege, matt.holdrege_at_verizon.net
• Jim Murphy, jmurphy_at_trapezenetworks.com
• Victor Lin, VLin_at_extremenetworks.com
• Bob O'Hara, bob_at_airespace.com
• Peyush AGARWAL, peyush.agarwal_at_st.com
• Parviz Yegani, pyegani_at_cisco.com
• Dave Hetherington, dhetheri_at_rovingplanet.com

8
DT Guidelines

• Mission Deliver an architecture taxonomy draft
  describing current market architectures to
  control and manage 802.11 networks. Each approach
  will provide
• a functional description of the interface between
  network elements
• the advantages/disadvantages of the approach.
• threat analysis
• Regular reports will be posted to the capwap
  mailing list after each meeting of the design
  team
• Major issues will brought to the list and decided
  based on WG consensus
• The DT will take input and comments from the list
• The output of the design team is subject to the
  approval and modification of the WG.

9
IEEE IETF Cooperation

• IEEE Interim meeting in January 2004
• CAPWAP represented by Bert Wijnen
• Architecture taxonomy draft will be input
  document from IETF to IEEE
• Validate and synchronize protocol development
  with IEEE 802.
• Merge work with IEEE
• Do the work in IETF
• Split the work between IETF/IEEE

10
Expert Review

• Experts in IETF chosen by ADs chairs
• Experts in IEEE chosen by Liaison
• Milestone is May, 2004
• Volunteers who believe they can provide and
  commit to an expert review should contact the
  chairs.