CAPWAP Protocol Specification Editors' Report

1
CAPWAP Protocol Specification Editors' Report

• November 2006
• pcalhoun_at_cisco.com
• mmontemurro_at_rim.com
• dstanley_at_arubanetworks.com

2
Editors Report Agenda

1. Issue Resolution Summary
2. Schedule

3
Issue Resolution Highlights

• Issue 201 - Clean Separation Between Base and
  Binding Resulted in split of -02 into two
  documents,
• draft-ietf-capwap-protocol-specification-03, and
• draft-ietf-capwap-protocol-binding-ieee802.11-00
  Includes updated binding (previous section 11),
  802.11 security, terminology, references,
  abstract, intro and goals sections.
  Author/acknowledgement sections left as TBD for
  the subsequent versions.
• Issue 158 Added new Protocol Variables section
  to base
• Issue 161 Use of station to refer to the end
  user equipment
• Issues 160, 162, 166 Change ASCII to UTF-8
  encoding
• Issue 210, 213 Text changes to clarify that
  802.11 MAC management frames are CAPWAP data
  frames
• Issue 204 More General Wireless Support
• WTP Radio Information Message Element moved to
  IEEE 802.11 binding document
• Added 802.16 and EPCglobal to control message
  sections where previously only 802.11 was present
• Issue 143 Corrections to CAPWAP Certificate use
  descriptions

4
Issue Resolution Highlights

• Issue 85 Add AC Descriptor to Join Response,
  Changes version number of AC and WTPs to require
  compatible rather than the same, add ability
  of AC to initiate firmware download
• Issue 150 Message elements can be in any order
• Issue 170 Added new failure result code for
  Join failure
• Issue 182 New text for Radio Administrative
  State Message Element usage
• Issue 184 Added text to clarify that the Idle
  timeout value is per WTP
• Issue 193 Reset and Reset Response Code changes
  to allow WTP to indicate that reboot request
  could not be carried out
• Issue 202 Added MAC address to IEEE 802.11
  Mobile Message element, enabling Mobile Config
  Request to provide updates for more than one
  station.
• Issue 208 Message length value corrections
• Issue 209 Clarified reserved values
• Issue 215 Made CAPWAP Header section titles
  uniform
• Issue 220 Join Request, Response text
  corrections re setting of the Waitjoin timer,
  state machine correction
• Issue 225 WTP Event Request text (editorial) to
  clarify messages that provide keep-alive function

5
Issues closed, no change

• Issues 82, 145, 147, 151, 154, 155, 156, 157,163,
  164, 165, 167, 169, 172, 173, 174,
  176,178,179,180,185,186,188,189,192,195,197,198
• Please see descriptions at www.capwap.org for
  details

6
Goals for CAPWAP-04, binding-01

• Incorporate additional text changes, including
  mailing list, editorial resolutions and
  resolutions for
•   1 How to differentiate between
  encrypted and unencrypted packets?    2 What
  RSC value should AC use when the WTP does
  encryption?    3 How does DTLS establishment
  interact with CAPWAP start-up?    4 How/if to
  handle QoS across DTLS-encrypted CAPWAP
  connections?    5 Proposed CAPWAP header
  changes    (and, if time allows...)    6
  Firmware upgrade/image data issues    7
  Configuration error handling
• Please see descriptions at www.capwap.org for
  details

7
Schedule

• Completed schedule dates
• Feb 25, 2006 revision 00 published
• March 20, 2006 IETF meeting review plans for
  revision-01, based on list discussion
• May 5th publish revision 01
• June 24th publish revision 02
• July 10th IETF meeting review plans for
  revision-03
• July Sept resolve issues, consensus for 2
  documents
• October 13th publish revision-03, 01 (binding)
• November 6th, 2006 IETF Meeting review plans
  for next revision
• Tentative editors plan publish next versions
  late Feb, 2007 in advance of March 18-23, 2007
  IETF)