CAPWAP%20Protocol%20Specification%20Update

1
CAPWAP Protocol Specification Update

• March 2006
• pcalhoun_at_cisco.com
• Michael.Montemurro_at_siemens.com
• dstanley_at_arubanetworks.com

2
Update on Tracker

• Number of issues submitted 85
• Number of issues closed (in -00) 41
• Number of issues targeted for -01 19
• Number of remaining issues (for -02) 25
• http//www.capwap.org/cgi-bin/roundup/CAPWAP/index

3
CAPWAP Protocol Specification-00

• Protocol name change to "CAPWAP", per list
  discussion
• Addition of the three editors, per AD, Chair
  decisions
• Addition of a "Contributing Author section, with
  the known contributing authors to date.
• IETF guidelines allow additional info to be
  provided
• Inclusion of DTLS as the CAPWAP protocol security
  mechanism, replacing the proprietary LWAPP
  mechanism.
• Inserted and modified text reflects Eric and
  Scott's latest dtls spec, and the list comment
  discussion to address Sue and Nancy's questions to
  date.
• Note that the DTLS entry in the issues tracker
  remains open. Inclusion of the text at this point
  is intended to facilitate resolution of any
  remaining issues. Major changes to sections
  2,6,10,15, and smaller changes throughout.
• Work underway to identify changes needed to
  complete the DTLS specification
• Wording changes to clarify that the message types
  are messages--changessections 5,6,7,8. Also
  re-numbered the message type values to remove
  gaps.

4
CAPWAP Protocol Specification-00

• Addition of a section for WaitJoin Timer, which
  was not defined.
• Need to determine a default value.
• Wording changes in the intro and abstract partly
  due to DTLS changes, partly changing from passive
  to active voice, clarity.
• Removed "gold, platinum, bronze" and the like QOS
  descriptions, retaining the technical terms only
• The "metal" terms were used inconsistently in two
  places - one had uranium but the other didn't,
  and one included the technical terms and the
  other didn't.
• Inserted "IEEE" prior to "802.11" in reference -
  various sections

5
CAPWAP Protocol Specification-00Other major
changes

• Expand Information Element type field to 16 bits
  Issue 1
• Allow for 802.3 tunneling in Local MAC mode
  Issue 3
• Define a mandatory mode and tunnel type - Issue
  4
• Remove layer 2 mode Issue 6
• Specify CAPWAP Fragmentation Issue 36
• Define optional tunneling in Local MAC section -
  Issue 52
• An additional 35 issues also resolved see
  Tracker

6
CAPWAP Protocol Specification-01

• DTLS related edits Issue 2
• AC Address (39), PMK Sharing (42), Combining
  Messages (45), Model Serial number (46,71), Max
  BSSs (50), Config names (58)
• Replace CKIP with a generic vendor proprietary
  extension
• Add Waitjoin Timer Default Value
• Author, Acknowledgement section updates
• Possibly re-structure message element definition
  organization simplify cross references.
  Opinions?
• Create a separate section for all of the message
  elements, e.g. new 4.3.3, rather than having each
  element defined in the first place it appears,
  with subsequent cross references, e.g. 5.3.1
  5.3.5
• Create a table in each of the message definition
  sections which lists the message elements and if
  they are optional or mandatory

7
CAPWAP Protocol Specification-01

1. IEEE 802.11i/RADIUS considerations Issues 83,
   68, and 43
2. IEEE 802.11 configuration and statistics Issue
   62, 84
3. Mechanism for adding other non-802.11 bindings to
   CAPWAP Issue 66
4. Minor edits to CAPWAP-00 Issue 81

8
CAPWAP Protocol Specification-01

1. Vendor specific message types - Issue 37
2. Add Data Rate to LWAPP Header Issue 53
3. Add Tunnel Indication to Add WLAN - issue 59
4. Are all fields in IEEE 802.11 Add Mobile required
   for Local MAC? - Issue 63
5. Clarify the contents of the key field in
   add/update WLAN - Issue 69

9
Major Open Issues

1. Issue 43 - IEEE 802.11i Considerations
2. Issue 66 - Unclear how Clear Config Indication
   is acknowledged
3. Issue 75 - recommend LWAPP add a new
   notification message "Gratuitous disconnect
   notification"
4. Issue 40 - Adapt firmware trigger state machine
   to allow transition from Run state
5. Issue 72 - get WLAN Config message
6. Issue 74 - About "IEEE 802.11 Binding"

10
Schedule

• Current target is July 06 for WGLC- (seems
  aggressive, need active support of WG)
• Proposed schedule
• Feb 25 revision 00
• March 20 IETF meeting review plans for
  revision-01, based on list discussion
• May 5th publish revision 01
• July ID Deadline publish revision 02
• July  10th IETF meeting review plans for
  revision-03
• July WGLC on 03? 

11
CAPWAP State Machine