draft-ietf-capwap-protocol-specification-11.txt   draft-ietf-capwap-protocol-specification-12.txt 
Network Working Group P. Calhoun, Editor Network Working Group P. Calhoun, Editor
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track M. Montemurro, Editor Intended status: Standards Track M. Montemurro, Editor
Expires: January 11, 2009 Research In Motion Expires: March 13, 2009 Research In Motion
D. Stanley, Editor D. Stanley, Editor
Aruba Networks Aruba Networks
July 10, 2008 September 9, 2008
CAPWAP Protocol Specification CAPWAP Protocol Specification
draft-ietf-capwap-protocol-specification-11 draft-ietf-capwap-protocol-specification-12
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 37 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 11, 2009. This Internet-Draft will expire on March 13, 2009.
Abstract Abstract
This specification defines the Control And Provisioning of Wireless This specification defines the Control And Provisioning of Wireless
Access Points (CAPWAP) Protocol. The CAPWAP protocol meets the Access Points (CAPWAP) Protocol. The CAPWAP protocol meets the
Objectives for Control and Provisioning of Wireless Access Points Objectives for Control and Provisioning of Wireless Access Points
(CAPWAP). The CAPWAP protocol is designed to be flexible, allowing (CAPWAP). The CAPWAP protocol is designed to be flexible, allowing
it to be used for a variety of wireless technologies. This document it to be used for a variety of wireless technologies. This document
describes the base CAPWAP protocol, while separate binding extensions describes the base CAPWAP protocol, while separate binding extensions
will enable its use with additional wireless technologies. will enable its use with additional wireless technologies.
skipping to change at page 2, line 27 skipping to change at page 2, line 27
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 7 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2. Conventions used in this document . . . . . . . . . . . 9 1.2. Conventions used in this document . . . . . . . . . . . 9
1.3. Contributing Authors . . . . . . . . . . . . . . . . . . 9 1.3. Contributing Authors . . . . . . . . . . . . . . . . . . 9
1.4. Terminology . . . . . . . . . . . . . . . . . . . . . . 10 1.4. Terminology . . . . . . . . . . . . . . . . . . . . . . 10
2. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 12 2. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 12
2.1. Wireless Binding Definition . . . . . . . . . . . . . . 13 2.1. Wireless Binding Definition . . . . . . . . . . . . . . 13
2.2. CAPWAP Session Establishment Overview . . . . . . . . . 14 2.2. CAPWAP Session Establishment Overview . . . . . . . . . 14
2.3. CAPWAP State Machine Definition . . . . . . . . . . . . 16 2.3. CAPWAP State Machine Definition . . . . . . . . . . . . 16
2.3.1. CAPWAP Protocol State Transitions . . . . . . . . . . 18 2.3.1. CAPWAP Protocol State Transitions . . . . . . . . . . 18
2.3.2. CAPWAP/DTLS Interface . . . . . . . . . . . . . . . . 31 2.3.2. CAPWAP/DTLS Interface . . . . . . . . . . . . . . . . 32
2.4. Use of DTLS in the CAPWAP Protocol . . . . . . . . . . . 33 2.4. Use of DTLS in the CAPWAP Protocol . . . . . . . . . . . 34
2.4.1. DTLS Handshake Processing . . . . . . . . . . . . . . 34 2.4.1. DTLS Handshake Processing . . . . . . . . . . . . . . 34
2.4.2. DTLS Session Establishment . . . . . . . . . . . . . 35 2.4.2. DTLS Session Establishment . . . . . . . . . . . . . 36
2.4.3. DTLS Error Handling . . . . . . . . . . . . . . . . . 35 2.4.3. DTLS Error Handling . . . . . . . . . . . . . . . . . 36
2.4.4. DTLS EndPoint Authentication and Authorization . . . 37 2.4.4. DTLS EndPoint Authentication and Authorization . . . 37
3. CAPWAP Transport . . . . . . . . . . . . . . . . . . . . . . 41 3. CAPWAP Transport . . . . . . . . . . . . . . . . . . . . . . 41
3.1. UDP Transport . . . . . . . . . . . . . . . . . . . . . 41 3.1. UDP Transport . . . . . . . . . . . . . . . . . . . . . 41
3.2. UDP-Lite Transport . . . . . . . . . . . . . . . . . . . 41 3.2. UDP-Lite Transport . . . . . . . . . . . . . . . . . . . 41
3.3. AC Discovery . . . . . . . . . . . . . . . . . . . . . . 42 3.3. AC Discovery . . . . . . . . . . . . . . . . . . . . . . 42
3.4. Fragmentation/Reassembly . . . . . . . . . . . . . . . . 43 3.4. Fragmentation/Reassembly . . . . . . . . . . . . . . . . 43
3.5. MTU Discovery . . . . . . . . . . . . . . . . . . . . . 43 3.5. MTU Discovery . . . . . . . . . . . . . . . . . . . . . 43
4. CAPWAP Packet Formats . . . . . . . . . . . . . . . . . . . . 44 4. CAPWAP Packet Formats . . . . . . . . . . . . . . . . . . . . 45
4.1. CAPWAP Preamble . . . . . . . . . . . . . . . . . . . . 46 4.1. CAPWAP Preamble . . . . . . . . . . . . . . . . . . . . 47
4.2. CAPWAP DTLS Header . . . . . . . . . . . . . . . . . . . 46 4.2. CAPWAP DTLS Header . . . . . . . . . . . . . . . . . . . 47
4.3. CAPWAP Header . . . . . . . . . . . . . . . . . . . . . 47 4.3. CAPWAP Header . . . . . . . . . . . . . . . . . . . . . 48
4.4. CAPWAP Data Messages . . . . . . . . . . . . . . . . . . 50 4.4. CAPWAP Data Messages . . . . . . . . . . . . . . . . . . 51
4.4.1. CAPWAP Data Channel Keepalive . . . . . . . . . . . . 50 4.4.1. CAPWAP Data Channel Keepalive . . . . . . . . . . . . 51
4.4.2. Data Payload . . . . . . . . . . . . . . . . . . . . 51 4.4.2. Data Payload . . . . . . . . . . . . . . . . . . . . 52
4.4.3. Establishment of a DTLS Data Channel . . . . . . . . 52 4.4.3. Establishment of a DTLS Data Channel . . . . . . . . 53
4.5. CAPWAP Control Messages . . . . . . . . . . . . . . . . 52 4.5. CAPWAP Control Messages . . . . . . . . . . . . . . . . 53
4.5.1. Control Message Format . . . . . . . . . . . . . . . 53 4.5.1. Control Message Format . . . . . . . . . . . . . . . 54
4.5.2. Control Message Quality of Service . . . . . . . . . 56 4.5.2. Control Message Quality of Service . . . . . . . . . 57
4.5.3. Retransmissions . . . . . . . . . . . . . . . . . . . 56 4.5.3. Retransmissions . . . . . . . . . . . . . . . . . . . 57
4.6. CAPWAP Protocol Message Elements . . . . . . . . . . . . 57 4.6. CAPWAP Protocol Message Elements . . . . . . . . . . . . 59
4.6.1. AC Descriptor . . . . . . . . . . . . . . . . . . . . 59 4.6.1. AC Descriptor . . . . . . . . . . . . . . . . . . . . 61
4.6.2. AC IPv4 List . . . . . . . . . . . . . . . . . . . . 61 4.6.2. AC IPv4 List . . . . . . . . . . . . . . . . . . . . 64
4.6.3. AC IPv6 List . . . . . . . . . . . . . . . . . . . . 62 4.6.3. AC IPv6 List . . . . . . . . . . . . . . . . . . . . 64
4.6.4. AC Name . . . . . . . . . . . . . . . . . . . . . . . 62 4.6.4. AC Name . . . . . . . . . . . . . . . . . . . . . . . 65
4.6.5. AC Name with Index . . . . . . . . . . . . . . . . . 63 4.6.5. AC Name with Index . . . . . . . . . . . . . . . . . 65
4.6.6. AC Timestamp . . . . . . . . . . . . . . . . . . . . 63 4.6.6. AC Timestamp . . . . . . . . . . . . . . . . . . . . 66
4.6.7. Add MAC ACL Entry . . . . . . . . . . . . . . . . . . 64 4.6.7. Add MAC ACL Entry . . . . . . . . . . . . . . . . . . 66
4.6.8. Add Station . . . . . . . . . . . . . . . . . . . . . 64 4.6.8. Add Station . . . . . . . . . . . . . . . . . . . . . 67
4.6.9. Add Static MAC ACL Entry . . . . . . . . . . . . . . 65 4.6.9. CAPWAP Control IPv4 Address . . . . . . . . . . . . . 68
4.6.10. CAPWAP Control IPv4 Address . . . . . . . . . . . . . 65 4.6.10. CAPWAP Control IPv6 Address . . . . . . . . . . . . . 68
4.6.11. CAPWAP Control IPv6 Address . . . . . . . . . . . . . 66 4.6.11. CAPWAP Local IPv4 Address . . . . . . . . . . . . . . 69
4.6.12. CAPWAP Local IPv4 Address . . . . . . . . . . . . . . 67 4.6.12. CAPWAP Local IPv6 Address . . . . . . . . . . . . . . 69
4.6.13. CAPWAP Local IPv6 Address . . . . . . . . . . . . . . 67 4.6.13. CAPWAP Timers . . . . . . . . . . . . . . . . . . . . 70
4.6.14. CAPWAP Timers . . . . . . . . . . . . . . . . . . . . 68 4.6.14. CAPWAP Transport Protocol . . . . . . . . . . . . . . 70
4.6.15. CAPWAP Transport Protocol . . . . . . . . . . . . . . 68 4.6.15. Data Transfer Data . . . . . . . . . . . . . . . . . 71
4.6.16. Data Transfer Data . . . . . . . . . . . . . . . . . 69 4.6.16. Data Transfer Mode . . . . . . . . . . . . . . . . . 72
4.6.17. Data Transfer Mode . . . . . . . . . . . . . . . . . 70 4.6.17. Decryption Error Report . . . . . . . . . . . . . . . 73
4.6.18. Decryption Error Report . . . . . . . . . . . . . . . 71 4.6.18. Decryption Error Report Period . . . . . . . . . . . 73
4.6.19. Decryption Error Report Period . . . . . . . . . . . 71 4.6.19. Delete MAC ACL Entry . . . . . . . . . . . . . . . . 74
4.6.20. Delete MAC ACL Entry . . . . . . . . . . . . . . . . 72 4.6.20. Delete Station . . . . . . . . . . . . . . . . . . . 74
4.6.21. Delete Station . . . . . . . . . . . . . . . . . . . 72 4.6.21. Discovery Type . . . . . . . . . . . . . . . . . . . 75
4.6.22. Delete Static MAC ACL Entry . . . . . . . . . . . . . 73 4.6.22. Duplicate IPv4 Address . . . . . . . . . . . . . . . 76
4.6.23. Discovery Type . . . . . . . . . . . . . . . . . . . 74 4.6.23. Duplicate IPv6 Address . . . . . . . . . . . . . . . 77
4.6.24. Duplicate IPv4 Address . . . . . . . . . . . . . . . 74 4.6.24. Idle Timeout . . . . . . . . . . . . . . . . . . . . 77
4.6.25. Duplicate IPv6 Address . . . . . . . . . . . . . . . 75 4.6.25. Image Data . . . . . . . . . . . . . . . . . . . . . 78
4.6.26. Idle Timeout . . . . . . . . . . . . . . . . . . . . 76 4.6.26. Image Identifier . . . . . . . . . . . . . . . . . . 79
4.6.27. Image Data . . . . . . . . . . . . . . . . . . . . . 76 4.6.27. Image Information . . . . . . . . . . . . . . . . . . 79
4.6.28. Image Identifier . . . . . . . . . . . . . . . . . . 77 4.6.28. Initiate Download . . . . . . . . . . . . . . . . . . 80
4.6.29. Image Information . . . . . . . . . . . . . . . . . . 77 4.6.29. Location Data . . . . . . . . . . . . . . . . . . . . 80
4.6.30. Initiate Download . . . . . . . . . . . . . . . . . . 78 4.6.30. Maximum Message Length . . . . . . . . . . . . . . . 81
4.6.31. Location Data . . . . . . . . . . . . . . . . . . . . 79 4.6.31. MTU Discovery Padding . . . . . . . . . . . . . . . . 81
4.6.32. Maximum Message Length . . . . . . . . . . . . . . . 79 4.6.32. Radio Administrative State . . . . . . . . . . . . . 81
4.6.33. Radio Administrative State . . . . . . . . . . . . . 80 4.6.33. Radio Operational State . . . . . . . . . . . . . . . 82
4.6.34. Radio Operational State . . . . . . . . . . . . . . . 80 4.6.34. Result Code . . . . . . . . . . . . . . . . . . . . . 83
4.6.35. Result Code . . . . . . . . . . . . . . . . . . . . . 81 4.6.35. Returned Message Element . . . . . . . . . . . . . . 85
4.6.36. Returned Message Element . . . . . . . . . . . . . . 83 4.6.36. Session ID . . . . . . . . . . . . . . . . . . . . . 86
4.6.37. Session ID . . . . . . . . . . . . . . . . . . . . . 84 4.6.37. Statistics Timer . . . . . . . . . . . . . . . . . . 86
4.6.38. Statistics Timer . . . . . . . . . . . . . . . . . . 84 4.6.38. Vendor Specific Payload . . . . . . . . . . . . . . . 87
4.6.39. Vendor Specific Payload . . . . . . . . . . . . . . . 84 4.6.39. WTP Board Data . . . . . . . . . . . . . . . . . . . 87
4.6.40. WTP Board Data . . . . . . . . . . . . . . . . . . . 85 4.6.40. WTP Descriptor . . . . . . . . . . . . . . . . . . . 89
4.6.41. WTP Descriptor . . . . . . . . . . . . . . . . . . . 86 4.6.41. WTP Fallback . . . . . . . . . . . . . . . . . . . . 91
4.6.42. WTP Fallback . . . . . . . . . . . . . . . . . . . . 88 4.6.42. WTP Frame Tunnel Mode . . . . . . . . . . . . . . . . 91
4.6.43. WTP Frame Tunnel Mode . . . . . . . . . . . . . . . . 89 4.6.43. WTP MAC Type . . . . . . . . . . . . . . . . . . . . 92
4.6.44. WTP IPv4 IP Address . . . . . . . . . . . . . . . . . 89 4.6.44. WTP Name . . . . . . . . . . . . . . . . . . . . . . 93
4.6.45. WTP IPv6 IP Address . . . . . . . . . . . . . . . . . 90 4.6.45. WTP Radio Statistics . . . . . . . . . . . . . . . . 93
4.6.46. WTP MAC Type . . . . . . . . . . . . . . . . . . . . 90 4.6.46. WTP Reboot Statistics . . . . . . . . . . . . . . . . 95
4.6.47. WTP Name . . . . . . . . . . . . . . . . . . . . . . 91 4.6.47. WTP Static IP Address Information . . . . . . . . . . 96
4.6.48. WTP Radio Statistics . . . . . . . . . . . . . . . . 91 4.7. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . 97
4.6.49. WTP Reboot Statistics . . . . . . . . . . . . . . . . 93 4.7.1. ChangeStatePendingTimer . . . . . . . . . . . . . . . 97
4.6.50. WTP Static IP Address Information . . . . . . . . . . 94 4.7.2. DataChannelKeepAlive . . . . . . . . . . . . . . . . 97
4.7. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . 95 4.7.3. DataChannelDeadInterval . . . . . . . . . . . . . . . 98
4.7.1. ChangeStatePendingTimer . . . . . . . . . . . . . . . 95 4.7.4. DataCheckTimer . . . . . . . . . . . . . . . . . . . 98
4.7.2. DataChannelKeepAlive . . . . . . . . . . . . . . . . 95 4.7.5. DiscoveryInterval . . . . . . . . . . . . . . . . . . 98
4.7.3. DataChannelDeadInterval . . . . . . . . . . . . . . . 96 4.7.6. DTLSSessionDelete . . . . . . . . . . . . . . . . . . 98
4.7.4. DataCheckTimer . . . . . . . . . . . . . . . . . . . 96 4.7.7. EchoInterval . . . . . . . . . . . . . . . . . . . . 98
4.7.5. DiscoveryInterval . . . . . . . . . . . . . . . . . . 96 4.7.8. IdleTimeout . . . . . . . . . . . . . . . . . . . . . 98
4.7.6. DTLSSessionDelete . . . . . . . . . . . . . . . . . . 96 4.7.9. ImageDataStartTimer . . . . . . . . . . . . . . . . . 98
4.7.7. EchoInterval . . . . . . . . . . . . . . . . . . . . 96 4.7.10. MaxDiscoveryInterval . . . . . . . . . . . . . . . . 99
4.7.8. IdleTimeout . . . . . . . . . . . . . . . . . . . . . 96 4.7.11. ReportInterval . . . . . . . . . . . . . . . . . . . 99
4.7.9. ImageDataStartTimer . . . . . . . . . . . . . . . . . 97 4.7.12. RetransmitInterval . . . . . . . . . . . . . . . . . 99
4.7.10. MaxDiscoveryInterval . . . . . . . . . . . . . . . . 97 4.7.13. SilentInterval . . . . . . . . . . . . . . . . . . . 99
4.7.11. ReportInterval . . . . . . . . . . . . . . . . . . . 97 4.7.14. StatisticsTimer . . . . . . . . . . . . . . . . . . . 99
4.7.12. RetransmitInterval . . . . . . . . . . . . . . . . . 97 4.7.15. WaitDTLS . . . . . . . . . . . . . . . . . . . . . . 99
4.7.13. SilentInterval . . . . . . . . . . . . . . . . . . . 97 4.7.16. WaitJoin . . . . . . . . . . . . . . . . . . . . . . 100
4.7.14. StatisticsTimer . . . . . . . . . . . . . . . . . . . 97 4.8. CAPWAP Protocol Variables . . . . . . . . . . . . . . . 100
4.7.15. WaitDTLS . . . . . . . . . . . . . . . . . . . . . . 98 4.8.1. AdminState . . . . . . . . . . . . . . . . . . . . . 100
4.8. CAPWAP Protocol Variables . . . . . . . . . . . . . . . 98 4.8.2. DiscoveryCount . . . . . . . . . . . . . . . . . . . 100
4.8.1. AdminState . . . . . . . . . . . . . . . . . . . . . 98 4.8.3. FailedDTLSAuthFailCount . . . . . . . . . . . . . . . 100
4.8.2. DiscoveryCount . . . . . . . . . . . . . . . . . . . 98 4.8.4. FailedDTLSSessionCount . . . . . . . . . . . . . . . 100
4.8.3. FailedDTLSAuthFailCount . . . . . . . . . . . . . . . 98 4.8.5. MaxDiscoveries . . . . . . . . . . . . . . . . . . . 100
4.8.4. FailedDTLSSessionCount . . . . . . . . . . . . . . . 98 4.8.6. MaxFailedDTLSSessionRetry . . . . . . . . . . . . . . 100
4.8.5. MaxDiscoveries . . . . . . . . . . . . . . . . . . . 98 4.8.7. MaxRetransmit . . . . . . . . . . . . . . . . . . . . 101
4.8.6. MaxFailedDTLSSessionRetry . . . . . . . . . . . . . . 98 4.8.8. RetransmitCount . . . . . . . . . . . . . . . . . . . 101
4.8.7. MaxRetransmit . . . . . . . . . . . . . . . . . . . . 99 4.8.9. WTPFallBack . . . . . . . . . . . . . . . . . . . . . 101
4.8.8. RetransmitCount . . . . . . . . . . . . . . . . . . . 99 4.9. WTP Saved Variables . . . . . . . . . . . . . . . . . . 101
4.8.9. WTPFallBack . . . . . . . . . . . . . . . . . . . . . 99 4.9.1. AdminRebootCount . . . . . . . . . . . . . . . . . . 101
4.9. WTP Saved Variables . . . . . . . . . . . . . . . . . . 99 4.9.2. FrameEncapType . . . . . . . . . . . . . . . . . . . 101
4.9.1. AdminRebootCount . . . . . . . . . . . . . . . . . . 99 4.9.3. LastRebootReason . . . . . . . . . . . . . . . . . . 101
4.9.2. FrameEncapType . . . . . . . . . . . . . . . . . . . 99 4.9.4. MacType . . . . . . . . . . . . . . . . . . . . . . . 101
4.9.3. LastRebootReason . . . . . . . . . . . . . . . . . . 99 4.9.5. PreferredACs . . . . . . . . . . . . . . . . . . . . 102
4.9.4. MacType . . . . . . . . . . . . . . . . . . . . . . . 99 4.9.6. RebootCount . . . . . . . . . . . . . . . . . . . . . 102
4.9.5. PreferredACs . . . . . . . . . . . . . . . . . . . . 99 4.9.7. Static IP Address . . . . . . . . . . . . . . . . . . 102
4.9.6. RebootCount . . . . . . . . . . . . . . . . . . . . . 100 4.9.8. WTPLinkFailureCount . . . . . . . . . . . . . . . . . 102
4.9.7. Static ACL Table . . . . . . . . . . . . . . . . . . 100 4.9.9. WTPLocation . . . . . . . . . . . . . . . . . . . . . 102
4.9.8. Static IP Address . . . . . . . . . . . . . . . . . . 100 4.9.10. WTPName . . . . . . . . . . . . . . . . . . . . . . . 102
4.9.9. WTPLinkFailureCount . . . . . . . . . . . . . . . . . 100 5. CAPWAP Discovery Operations . . . . . . . . . . . . . . . . . 103
4.9.10. WTPLocation . . . . . . . . . . . . . . . . . . . . . 100 5.1. Discovery Request Message . . . . . . . . . . . . . . . 103
4.9.11. WTPName . . . . . . . . . . . . . . . . . . . . . . . 100 5.2. Discovery Response Message . . . . . . . . . . . . . . . 104
5. CAPWAP Discovery Operations . . . . . . . . . . . . . . . . . 101 5.3. Primary Discovery Request Message . . . . . . . . . . . 105
5.1. Discovery Request Message . . . . . . . . . . . . . . . 101 5.4. Primary Discovery Response . . . . . . . . . . . . . . . 106
5.2. Discovery Response Message . . . . . . . . . . . . . . . 102 6. CAPWAP Join Operations . . . . . . . . . . . . . . . . . . . 108
5.3. Primary Discovery Request Message . . . . . . . . . . . 103 6.1. Join Request . . . . . . . . . . . . . . . . . . . . . . 108
5.4. Primary Discovery Response . . . . . . . . . . . . . . . 104 6.2. Join Response . . . . . . . . . . . . . . . . . . . . . 109
6. CAPWAP Join Operations . . . . . . . . . . . . . . . . . . . 106 7. Control Channel Management . . . . . . . . . . . . . . . . . 112
6.1. Join Request . . . . . . . . . . . . . . . . . . . . . . 106 7.1. Echo Request . . . . . . . . . . . . . . . . . . . . . . 112
6.2. Join Response . . . . . . . . . . . . . . . . . . . . . 107 7.2. Echo Response . . . . . . . . . . . . . . . . . . . . . 112
7. Control Channel Management . . . . . . . . . . . . . . . . . 110 8. WTP Configuration Management . . . . . . . . . . . . . . . . 114
7.1. Echo Request . . . . . . . . . . . . . . . . . . . . . . 110 8.1. Configuration Consistency . . . . . . . . . . . . . . . 114
7.2. Echo Response . . . . . . . . . . . . . . . . . . . . . 110 8.1.1. Configuration Flexibility . . . . . . . . . . . . . . 115
8. WTP Configuration Management . . . . . . . . . . . . . . . . 112 8.2. Configuration Status Request . . . . . . . . . . . . . . 115
8.1. Configuration Consistency . . . . . . . . . . . . . . . 112 8.3. Configuration Status Response . . . . . . . . . . . . . 116
8.1.1. Configuration Flexibility . . . . . . . . . . . . . . 113 8.4. Configuration Update Request . . . . . . . . . . . . . . 117
8.2. Configuration Status . . . . . . . . . . . . . . . . . . 113 8.5. Configuration Update Response . . . . . . . . . . . . . 118
8.3. Configuration Status Response . . . . . . . . . . . . . 114 8.6. Change State Event Request . . . . . . . . . . . . . . . 118
8.4. Configuration Update Request . . . . . . . . . . . . . . 115 8.7. Change State Event Response . . . . . . . . . . . . . . 120
8.5. Configuration Update Response . . . . . . . . . . . . . 116 8.8. Clear Configuration Request . . . . . . . . . . . . . . 120
8.6. Change State Event Request . . . . . . . . . . . . . . . 116 8.9. Clear Configuration Response . . . . . . . . . . . . . . 120
8.7. Change State Event Response . . . . . . . . . . . . . . 118 9. Device Management Operations . . . . . . . . . . . . . . . . 122
8.8. Clear Configuration Request . . . . . . . . . . . . . . 118 9.1. Firmware Management . . . . . . . . . . . . . . . . . . 122
8.9. Clear Configuration Response . . . . . . . . . . . . . . 118 9.1.1. Image Data Request . . . . . . . . . . . . . . . . . 126
9. Device Management Operations . . . . . . . . . . . . . . . . 120 9.1.2. Image Data Response . . . . . . . . . . . . . . . . . 127
9.1. Firmware Management . . . . . . . . . . . . . . . . . . 120 9.2. Reset Request . . . . . . . . . . . . . . . . . . . . . 128
9.1.1. Image Data Request . . . . . . . . . . . . . . . . . 124 9.3. Reset Response . . . . . . . . . . . . . . . . . . . . . 129
9.1.2. Image Data Response . . . . . . . . . . . . . . . . . 125 9.4. WTP Event Request . . . . . . . . . . . . . . . . . . . 129
9.2. Reset Request . . . . . . . . . . . . . . . . . . . . . 126 9.5. WTP Event Response . . . . . . . . . . . . . . . . . . . 130
9.3. Reset Response . . . . . . . . . . . . . . . . . . . . . 127 9.6. Data Transfer . . . . . . . . . . . . . . . . . . . . . 130
9.4. WTP Event Request . . . . . . . . . . . . . . . . . . . 127 9.6.1. Data Transfer Request . . . . . . . . . . . . . . . . 131
9.5. WTP Event Response . . . . . . . . . . . . . . . . . . . 128 9.6.2. Data Transfer Response . . . . . . . . . . . . . . . 132
9.6. Data Transfer . . . . . . . . . . . . . . . . . . . . . 128 10. Station Session Management . . . . . . . . . . . . . . . . . 134
9.6.1. Data Transfer Request . . . . . . . . . . . . . . . . 129 10.1. Station Configuration Request . . . . . . . . . . . . . 134
9.6.2. Data Transfer Response . . . . . . . . . . . . . . . 130 10.2. Station Configuration Response . . . . . . . . . . . . . 134
10. Station Session Management . . . . . . . . . . . . . . . . . 132 11. NAT Considerations . . . . . . . . . . . . . . . . . . . . . 136
10.1. Station Configuration Request . . . . . . . . . . . . . 132 12. Security Considerations . . . . . . . . . . . . . . . . . . . 138
10.2. Station Configuration Response . . . . . . . . . . . . . 132 12.1. CAPWAP Security . . . . . . . . . . . . . . . . . . . . 138
11. NAT Considerations . . . . . . . . . . . . . . . . . . . . . 134 12.1.1. Converting Protected Data into Unprotected Data . . . 139
12. Security Considerations . . . . . . . . . . . . . . . . . . . 136
12.1. CAPWAP Security . . . . . . . . . . . . . . . . . . . . 136
12.1.1. Converting Protected Data into Unprotected Data . . . 137
12.1.2. Converting Unprotected Data into Protected Data 12.1.2. Converting Unprotected Data into Protected Data
(Insertion) . . . . . . . . . . . . . . . . . . . . . 137 (Insertion) . . . . . . . . . . . . . . . . . . . . . 139
12.1.3. Deletion of Protected Records . . . . . . . . . . . . 137 12.1.3. Deletion of Protected Records . . . . . . . . . . . . 139
12.1.4. Insertion of Unprotected Records . . . . . . . . . . 137 12.1.4. Insertion of Unprotected Records . . . . . . . . . . 139
12.2. Session ID Security . . . . . . . . . . . . . . . . . . 137 12.1.5. Use of MD5 . . . . . . . . . . . . . . . . . . . . . 139
12.3. Discovery or DTLS Setup Attacks . . . . . . . . . . . . 138 12.2. Session ID Security . . . . . . . . . . . . . . . . . . 139
12.4. Interference with a DTLS Session . . . . . . . . . . . . 139 12.3. Discovery or DTLS Setup Attacks . . . . . . . . . . . . 140
12.5. CAPWAP Pre-Provisioning . . . . . . . . . . . . . . . . 139 12.4. Interference with a DTLS Session . . . . . . . . . . . . 141
12.6. Use of Preshared Keys in CAPWAP . . . . . . . . . . . . 140 12.5. CAPWAP Pre-Provisioning . . . . . . . . . . . . . . . . 141
12.7. Use of Certificates in CAPWAP . . . . . . . . . . . . . 141 12.6. Use of Preshared Keys in CAPWAP . . . . . . . . . . . . 142
12.8. AAA Security . . . . . . . . . . . . . . . . . . . . . . 142 12.7. Use of Certificates in CAPWAP . . . . . . . . . . . . . 143
13. Operational Considerations . . . . . . . . . . . . . . . . . 143 12.8. AAA Security . . . . . . . . . . . . . . . . . . . . . . 144
14. Transport Considerations . . . . . . . . . . . . . . . . . . 144 13. Operational Considerations . . . . . . . . . . . . . . . . . 145
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 145 14. Transport Considerations . . . . . . . . . . . . . . . . . . 146
15.1. CAPWAP Message Types . . . . . . . . . . . . . . . . . . 145 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 147
15.2. CAPWAP Header Flags . . . . . . . . . . . . . . . . . . 145 15.1. Multicast Address . . . . . . . . . . . . . . . . . . . 147
15.3. CAPWAP Control Message Flags . . . . . . . . . . . . . . 145 15.2. UDP Port . . . . . . . . . . . . . . . . . . . . . . . . 147
15.4. CAPWAP Control Message Type . . . . . . . . . . . . . . 145 15.3. CAPWAP Message Types . . . . . . . . . . . . . . . . . . 148
15.5. Wireless Binding Identifiers . . . . . . . . . . . . . . 145 15.4. CAPWAP Header Flags . . . . . . . . . . . . . . . . . . 148
15.6. AC Security Types . . . . . . . . . . . . . . . . . . . 146 15.5. CAPWAP Control Message Flags . . . . . . . . . . . . . . 148
15.7. AC DTLS Policy . . . . . . . . . . . . . . . . . . . . . 146 15.6. CAPWAP Message Element Type . . . . . . . . . . . . . . 148
15.8. AC Information Type . . . . . . . . . . . . . . . . . . 146 15.7. Wireless Binding Identifiers . . . . . . . . . . . . . . 149
15.9. CAPWAP Transport Protocol Types . . . . . . . . . . . . 146 15.8. AC Security Types . . . . . . . . . . . . . . . . . . . 149
15.10. Data Transfer Type . . . . . . . . . . . . . . . . . . . 146 15.9. AC DTLS Policy . . . . . . . . . . . . . . . . . . . . . 149
15.11. Data Transfer Mode . . . . . . . . . . . . . . . . . . . 146 15.10. AC Information Type . . . . . . . . . . . . . . . . . . 149
15.12. Discovery Types . . . . . . . . . . . . . . . . . . . . 147 15.11. CAPWAP Transport Protocol Types . . . . . . . . . . . . 150
15.13. Radio Admin State . . . . . . . . . . . . . . . . . . . 147 15.12. Data Transfer Type . . . . . . . . . . . . . . . . . . . 150
15.14. Radio Operational State . . . . . . . . . . . . . . . . 147 15.13. Data Transfer Mode . . . . . . . . . . . . . . . . . . . 150
15.15. Radio Failure Causes . . . . . . . . . . . . . . . . . . 147 15.14. Discovery Types . . . . . . . . . . . . . . . . . . . . 151
15.16. Result Code . . . . . . . . . . . . . . . . . . . . . . 147 15.15. Radio Admin State . . . . . . . . . . . . . . . . . . . 151
15.17. Returned Message Element Reason . . . . . . . . . . . . 147 15.16. Radio Operational State . . . . . . . . . . . . . . . . 151
15.18. WTP Board Data Type . . . . . . . . . . . . . . . . . . 148 15.17. Radio Failure Causes . . . . . . . . . . . . . . . . . . 151
15.19. WTP Descriptor Type . . . . . . . . . . . . . . . . . . 148 15.18. Result Code . . . . . . . . . . . . . . . . . . . . . . 152
15.20. WTP Fallback Mode . . . . . . . . . . . . . . . . . . . 148 15.19. Returned Message Element Reason . . . . . . . . . . . . 152
15.21. WTP Frame Tunnel Mode . . . . . . . . . . . . . . . . . 148 15.20. WTP Board Data Type . . . . . . . . . . . . . . . . . . 152
15.22. WTP MAC Type . . . . . . . . . . . . . . . . . . . . . . 148 15.21. WTP Descriptor Type . . . . . . . . . . . . . . . . . . 152
15.23. WTP Radio Stats Failure Type . . . . . . . . . . . . . . 148 15.22. WTP Fallback Mode . . . . . . . . . . . . . . . . . . . 153
15.24. WTP Reboot Stats Failure Type . . . . . . . . . . . . . 149 15.23. WTP Frame Tunnel Mode . . . . . . . . . . . . . . . . . 153
16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 150 15.24. WTP MAC Type . . . . . . . . . . . . . . . . . . . . . . 153
17. References . . . . . . . . . . . . . . . . . . . . . . . . . 151 15.25. WTP Radio Stats Failure Type . . . . . . . . . . . . . . 154
17.1. Normative References . . . . . . . . . . . . . . . . . . 151 15.26. WTP Reboot Stats Failure Type . . . . . . . . . . . . . 154
17.2. Informational References . . . . . . . . . . . . . . . . 152 16. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 155
Editors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 154 17. References . . . . . . . . . . . . . . . . . . . . . . . . . 156
Intellectual Property and Copyright Statements . . . . . . . . . 155 17.1. Normative References . . . . . . . . . . . . . . . . . . 156
17.2. Informational References . . . . . . . . . . . . . . . . 157
Editors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 159
Intellectual Property and Copyright Statements . . . . . . . . . 160
1. Introduction 1. Introduction
This document describes the CAPWAP Protocol, a standard, This document describes the CAPWAP Protocol, a standard,
interoperable protocol which enables an Access Controller (AC) to interoperable protocol which enables an Access Controller (AC) to
manage a collection of Wireless Termination Points (WTPs). The manage a collection of Wireless Termination Points (WTPs). The
CAPWAP protocol is defined to be independent of layer 2 technology, CAPWAP protocol is defined to be independent of layer 2 technology,
and meets the Objectives for Control and Provisioning of Wireless and meets the Objectives for Control and Provisioning of Wireless
Access Points (CAPWAP) [RFC4564]. Access Points (CAPWAP) [RFC4564].
skipping to change at page 9, line 48 skipping to change at page 9, line 48
Phone: +1 408-754-8408, Email: skelly@arubanetworks.com Phone: +1 408-754-8408, Email: skelly@arubanetworks.com
Michael Glenn Williams, Nokia, Inc. Michael Glenn Williams, Nokia, Inc.
313 Fairchild Drive, Mountain View, CA 94043 313 Fairchild Drive, Mountain View, CA 94043
Phone: +1 650-714-7758, Email: Michael.G.Williams@Nokia.com Phone: +1 650-714-7758, Email: Michael.G.Williams@Nokia.com
Sue Hares, Green Hills Software Sue Hares, Green Hills Software
825 Victors Way, Suite 100, Ann Arbor, MI 48108 825 Victors Way, Suite 100, Ann Arbor, MI 48108
Phone: +1 734 222 1610, Email: shares@ndzh.com Phone: +1 734 222 1610, Email: shares@ndzh.com
Datagram Transport Layer Security (DTLS) [RFC4346] is used as the Datagram Transport Layer Security (DTLS) [RFC4347] is used as the
security solution for the CAPWAP protocol. The following people are security solution for the CAPWAP protocol. The following people are
authors of significant DTLS-related text included in this document: authors of significant DTLS-related text included in this document:
Scott Kelly, Aruba Networks Scott Kelly, Aruba Networks
1322 Crossman Ave, Sunnyvale, CA 94089 1322 Crossman Ave, Sunnyvale, CA 94089
Phone: +1 408-754-8408, Email: skelly@arubanetworks.com Phone: +1 408-754-8408, Email: skelly@arubanetworks.com
Eric Rescorla, Network Resonance Eric Rescorla, Network Resonance
2483 El Camino Real, #212,Palo Alto CA, 94303 2483 El Camino Real, #212,Palo Alto CA, 94303
Email: ekr@networkresonance.com Email: ekr@networkresonance.com
skipping to change at page 18, line 43 skipping to change at page 18, line 43
attacks that exist with non-authenticated frames. See Section 12 attacks that exist with non-authenticated frames. See Section 12
for more information. for more information.
Service Thread: The AC's Service thread handles the per-WTP states, Service Thread: The AC's Service thread handles the per-WTP states,
and one such thread exists per-WTP connection. This thread is and one such thread exists per-WTP connection. This thread is
created by the listener thread when the Authorize state is created by the listener thread when the Authorize state is
reached. When created, the Service thread inherits a copy of the reached. When created, the Service thread inherits a copy of the
state machine context from the Listener thread. When state machine context from the Listener thread. When
communication with the WTP is complete, the Service thread is communication with the WTP is complete, the Service thread is
terminated and all associated resources are released. The state terminated and all associated resources are released. The state
machine transitions in Figure 4 are represented by alphabetic machine transitions in Figure 4 are represented by alphabetic and
characters. punctuation characters.
2.3.1. CAPWAP Protocol State Transitions 2.3.1. CAPWAP Protocol State Transitions
This section describes the various state transitions, and the events This section describes the various state transitions, and the events
that cause them. This section does not discuss interactions between that cause them. This section does not discuss interactions between
DTLS- and CAPWAP-specific states. Those interactions, and DTLS- DTLS- and CAPWAP-specific states. Those interactions, and DTLS-
specific states and transitions, are discussed in Section 2.3.2. specific states and transitions, are discussed in Section 2.3.2.
Start to Idle (0): This transition occurs once device initialization Start to Idle (0): This transition occurs once device initialization
is complete. is complete.
skipping to change at page 24, line 10 skipping to change at page 24, line 10
DTLSEstablished notification (see Section 2.3.2.2), indicating DTLSEstablished notification (see Section 2.3.2.2), indicating
that the DTLS session was successfully established. When this that the DTLS session was successfully established. When this
notification is received, the FailedDTLSSessionCount counter is notification is received, the FailedDTLSSessionCount counter is
set to zero. The WTP enters the Join state by transmiting the set to zero. The WTP enters the Join state by transmiting the
Join Request to the AC. The WTP stops the WaitDTLS timer. Join Request to the AC. The WTP stops the WaitDTLS timer.
AC: This state transition occurs when the AC receives the AC: This state transition occurs when the AC receives the
DTLSEstablished notification (see Section 2.3.2.2), indicating DTLSEstablished notification (see Section 2.3.2.2), indicating
that the DTLS session was successfully established. When this that the DTLS session was successfully established. When this
notification is received, the FailedDTLSSessionCount counter is notification is received, the FailedDTLSSessionCount counter is
set to zero. The AC stops the WaitDTLS timer. set to zero. The AC stops the WaitDTLS timer, and starts the
WaitJoin timer.
Join to DTLS Teardown (e): This transition occurs when the join Join to DTLS Teardown (e): This transition occurs when the join
process failed. process failed.
WTP: This state transition occurs when the WTP receives a Join WTP: This state transition occurs when the WTP receives a Join
Response message with a Result Code message element containing Response message with a Result Code message element containing
an error, if the Image Identifier provided by the AC in the an error, or if the Image Identifier provided by the AC in the
Join Response message differs from the WTP's currently running Join Response message differs from the WTP's currently running
firmware version and the WTP has the requested image in its firmware version and the WTP has the requested image in its
non-volatile memory, or if the WaitDTLS timer expires. This non-volatile memory. This causes the WTP to initiate the
causes the WTP to initiate the DTLSShutdown command (see DTLSShutdown command (see Section 2.3.2.1). This transition
Section 2.3.2.1). This transition also occurs if the WTP also occurs if the WTP receives one of the following DTLS
receives one of the following DTLS notifications: DTLSAborted, notifications: DTLSAborted, DTLSReassemblyFailure or
DTLSReassemblyFailure or DTLSPeerDisconnect. The WTP starts DTLSPeerDisconnect. The WTP starts the DTLSSessionDelete timer
the DTLSSessionDelete timer (see Section 4.7.6). (see Section 4.7.6).
AC: This state transition occurs either if the WaitDTLS timer AC: This state transition occurs either if the WaitJoin timer
expires or if the AC transmits a Join Response message with a expires or if the AC transmits a Join Response message with a
Result Code message element containing an error. This causes Result Code message element containing an error. This causes
the AC to initiate the DTLSShutdown command (see the AC to initiate the DTLSShutdown command (see
Section 2.3.2.1). This transition also occurs if the AC Section 2.3.2.1). This transition also occurs if the AC
receives one of the following DTLS notifications: DTLSAborted, receives one of the following DTLS notifications: DTLSAborted,
DTLSReassemblyFailure or DTLSPeerDisconnect. The AC starts the DTLSReassemblyFailure or DTLSPeerDisconnect. The AC starts the
DTLSSessionDelete timer (see Section 4.7.6). DTLSSessionDelete timer (see Section 4.7.6).
Join to Image Data (f): This state transition is used by the WTP and Join to Image Data (f): This state transition is used by the WTP and
the AC to download executable firmware. the AC to download executable firmware.
skipping to change at page 25, line 7 skipping to change at page 25, line 7
the same as its currently running image. The WTP also detects the same as its currently running image. The WTP also detects
that the requested image version is not currently available in that the requested image version is not currently available in
the WTP's non-volatile storage (see Section 9.1 for a full the WTP's non-volatile storage (see Section 9.1 for a full
description of the firmware download process). The WTP description of the firmware download process). The WTP
initializes the EchoInterval timer (see Section 4.7), and initializes the EchoInterval timer (see Section 4.7), and
transmits the Image Data Request message (see Section 9.1.1) transmits the Image Data Request message (see Section 9.1.1)
requesting the start of the firmware download. requesting the start of the firmware download.
AC: This state transition occurs when the AC receives the Image AC: This state transition occurs when the AC receives the Image
Data Request message from the WTP, after having sent its Join Data Request message from the WTP, after having sent its Join
Response to the WTP. The AC MUST transmit an Image Data Response to the WTP. The AC stops the WaitJoin timer. The AC
Response message (see Section 9.1.2) to the WTP, which includes MUST transmit an Image Data Response message (see
a portion of the firmware. The AC MUST start the Section 9.1.2) to the WTP, which includes a portion of the
ImageDataStartTimer timer (see Section 4.7). firmware. The AC MUST start the ImageDataStartTimer timer (see
Section 4.7).
Join to Configure (g): This state transition is used by the WTP and Join to Configure (g): This state transition is used by the WTP and
the AC to exchange configuration information. the AC to exchange configuration information.
WTP: The WTP enters the Configure state when it receives a WTP: The WTP enters the Configure state when it receives a
successful Join Response message, and determines that the successful Join Response message, and determines that the
included Image Identifier message element is the same as its included Image Identifier message element is the same as its
currently running image. The WTP transmits the Configuration currently running image. The WTP transmits the Configuration
Status message (see Section 8.2) to the AC with message Status Request message (see Section 8.2) to the AC with message
elements describing its current configuration. elements describing its current configuration.
AC: This state transition occurs when it receives the AC: This state transition occurs when it receives the
Configuration Status message from the WTP (see Section 8.2), Configuration Status Request message from the WTP (see
which MAY include specific message elements to override the Section 8.2), which MAY include specific message elements to
WTP's configuration. The AC transmits the Configuration Status override the WTP's configuration. The AC stops the WaitJoin
Response message (see Section 8.3) and starts the timer. The AC transmits the Configuration Status Response
message (see Section 8.3) and starts the
ChangeStatePendingTimer timer (see Section 4.7). ChangeStatePendingTimer timer (see Section 4.7).
Configure to Reset (h): This state transition is used to reset the Configure to Reset (h): This state transition is used to reset the
connection either due to an error during the configuration phase, connection either due to an error during the configuration phase,
or when the WTP determines it needs to reset in order for the new or when the WTP determines it needs to reset in order for the new
configuration to take effect. The CAPWAP Reset command is used to configuration to take effect. The CAPWAP Reset command is used to
indicate to the peer that it will initiate a DTLS teardown. indicate to the peer that it will initiate a DTLS teardown.
WTP: The WTP enters the Reset state when it receives a WTP: The WTP enters the Reset state when it receives a
Configuration Status Response message indicating an error or Configuration Status Response message indicating an error or
skipping to change at page 34, line 51 skipping to change at page 35, line 36
(AC callout for WTP authorization (AC callout for WTP authorization
occurs in CAPWAP Auth state) occurs in CAPWAP Auth state)
ChangeCipherSpec ChangeCipherSpec
<------ Finished <------ Finished
Figure 5: DTLS Handshake Figure 5: DTLS Handshake
DTLS, as specified, provides its own retransmit timers with an DTLS, as specified, provides its own retransmit timers with an
exponential back-off. However, DTLS will never terminate the exponential back-off. [RFC4347] does not specify how long
handshake due to non-responsiveness; instead, DTLS will continue to retransmissions should continue. Consequently, timing out incomplete
increase its back-off timer period. Hence, timing out incomplete
DTLS handshakes is entirely the responsibility of the CAPWAP module. DTLS handshakes is entirely the responsibility of the CAPWAP module.
The DTLS implementation used by CAPWAP MUST support TLS Session The DTLS implementation used by CAPWAP MUST support TLS Session
Resumption. Session resumption is used to establish the DTLS session Resumption. Session resumption is used to establish the DTLS session
used for the data channel. The DTLS implementation on the WTP MUST used for the data channel. The DTLS implementation on the WTP MUST
return some unique identifier to the CAPWAP module to enable return some unique identifier to the CAPWAP module to enable
subsequent establishment of a DTLS-encrypted data channel, if subsequent establishment of a DTLS-encrypted data channel, if
necessary. necessary.
The DTLS implementation used by CAPWAP MUST use replay detection, per
Section 3.3 of [RFC4347]. Since the CAPWAP protocol handles
retransmissions by re-encrypting lost frames, any duplicate DTLS
frames are either unintentional or malicious, and should be silently
discarded.
2.4.2. DTLS Session Establishment 2.4.2. DTLS Session Establishment
The WTP, either through the Discovery process, or through pre- The WTP, either through the Discovery process, or through pre-
configuration, determines the AC to connect to. The WTP uses the configuration, determines the AC to connect to. The WTP uses the
DTLSStart command to request that a secure connection be established DTLSStart command to request that a secure connection be established
to the selected AC. Prior to initiation of the DTLS handshake, the to the selected AC. Prior to initiation of the DTLS handshake, the
WTP sets the WaitDTLS timer. Upon receiving the DTLSPeerAuthorize WTP sets the WaitDTLS timer. Upon invoking the DTLSStart or
DTLS notification, the AC sets the WaitDTLS timer. If the DTLSListen commands, the WTP and AC, respectively, set the WaitDTLS
DTLSEstablished notification is not received prior to timer timer. If the DTLSEstablished notification is not received prior to
expiration, the DTLS session is aborted by issuing the timer expiration, the DTLS session is aborted by issuing the
DTLSAbortSession DTLS command. This notification causes the CAPWAP DTLSAbortSession DTLS command. This notification causes the CAPWAP
module to transition to the Idle state. Upon receiving a module to transition to the Idle state. Upon receiving a
DTLSEstablished notification, the WaitDTLS timer is deactivated. DTLSEstablished notification, the WaitDTLS timer is deactivated.
2.4.3. DTLS Error Handling 2.4.3. DTLS Error Handling
If the AC does not respond to any DTLS messages sent by the WTP, the If the AC or WTP does not respond to any DTLS handshake messages sent
DTLS specification calls for the WTP to retransmit these messages. by its peer, the DTLS specification calls for the message to be
If the WaitDTLS timer expires, CAPWAP will issue the DTLSAbortSession retransmited. Note that during the handshake, when both the AC and
command, causing DTLS to terminate the handshake and remove any the WTP are expecting additional handshake messages, they both
allocated session context. Note that DTLS MAY send a single TLS retransmit if an expected message has not been received (note that
Alert message to the AC to indicate session termination. retransmissions for CAPWAP Control messages work differently: all
CAPWAP Control messages are either requests or responses, and the
If the WTP does not respond to any DTLS messages sent by the AC, the peer who sent the request is responsible for retransmissions).
CAPWAP protocol allows for three possibilities, listed below. Note
that DTLS MAY send a single TLS Alert message to the AC to indicate
session termination.
o The message was lost in transit; in this case, the WTP will re-
transmit its last outstanding message, since it did not receive a
reply.
o The WTP sent a DTLS Alert, which was lost in transit; in this
case, the AC's WaitDTLS timer will expire, and the session will be
terminated.
o Communication with the WTP has completely failed; in this case,
the AC's WaitDTLS timer will expire, and the session will be
terminated.
The DTLS specification provides for retransmission of unacknowledged If the WTP or the AC does not receive an expected DTLS handshake
requests. If retransmissions remain unacknowledged, the WaitDTLS message despite of retransmissions, the WaitDTLS timer will
timer will eventually expire, at which time the CAPWAP component will eventually expire, and the session will be terminated. This can
terminate the session. happen if communication between the peers has completely failed, or
if one of the peers sent a DTLS Alert message which was lost in
transit (DTLS does not retransmit Alert messages).
If a cookie fails to validate, this could represent a WTP error, or If a cookie fails to validate, this could represent a WTP error, or
it could represent a DoS attack. Hence, AC resource utilization it could represent a DoS attack. Hence, AC resource utilization
SHOULD be minimized. The AC MAY log a message indicating the SHOULD be minimized. The AC MAY log a message indicating the
failure, but SHOULD NOT attempt to reply to the WTP. failure, and SHOULD treat the message as though no cookie were
present.
Since DTLS handshake messages are potentially larger than the maximum Since DTLS handshake messages are potentially larger than the maximum
record size, DTLS supports fragmenting of handshake messages across record size, DTLS supports fragmenting of handshake messages across
multiple records. There are several potential causes of re-assembly multiple records. There are several potential causes of re-assembly
errors, including overlapping and/or lost fragments. The DTLS errors, including overlapping and/or lost fragments. The DTLS
component MUST send a DTLSReassemblyFailure notification to the component MUST send a DTLSReassemblyFailure notification to the
CAPWAP component. Whether precise information is given along with CAPWAP component. Whether precise information is given along with
notification is an implementation issue, and hence is beyond the notification is an implementation issue, and hence is beyond the
scope of this document. Upon receipt of such an error, the CAPWAP scope of this document. Upon receipt of such an error, the CAPWAP
component SHOULD log an appropriate error message. Whether component SHOULD log an appropriate error message. Whether
skipping to change at page 37, line 19 skipping to change at page 37, line 43
keys. The TLS algorithm suites for each endpoint authentication keys. The TLS algorithm suites for each endpoint authentication
method are described below. method are described below.
2.4.4.1. Authenticating with Certificates 2.4.4.1. Authenticating with Certificates
CAPWAP implementations only use cipher suites that are recommended CAPWAP implementations only use cipher suites that are recommended
for use with DTLS, see [DTLS-DESIGN]. At present, the following for use with DTLS, see [DTLS-DESIGN]. At present, the following
algorithms MUST be supported when using certificates for CAPWAP algorithms MUST be supported when using certificates for CAPWAP
authentication: authentication:
o TLS_RSA_WITH_AES_128_CBC_SHA [RFC4279] o TLS_RSA_WITH_AES_128_CBC_SHA [RFC4346]
The following algorithms SHOULD be supported when using certificates: The following algorithms SHOULD be supported when using certificates:
o TLS_DHE_RSA_WITH_AES_128_CBC_SHA [RFC4279] o TLS_DHE_RSA_WITH_AES_128_CBC_SHA [RFC4346]
The following algorithms MAY be supported when using certificates: The following algorithms MAY be supported when using certificates:
o TLS_RSA_WITH_AES_256_CBC_SHA [RFC4279] o TLS_RSA_WITH_AES_256_CBC_SHA [RFC4346]
o TLS_DHE_RSA_WITH_AES_256_CBC_SHA [RFC4279] o TLS_DHE_RSA_WITH_AES_256_CBC_SHA [RFC4346]
Additional ciphers MAY be defined in follow on CAPWAP specifications. Additional ciphers MAY be defined in follow on CAPWAP specifications.
2.4.4.2. Authenticating with Preshared Keys 2.4.4.2. Authenticating with Preshared Keys
Pre-shared keys present significant challenges from a security Pre-shared keys present significant challenges from a security
perspective, and for that reason, their use is strongly discouraged. perspective, and for that reason, their use is strongly discouraged.
Several methods for authenticating with preshared keys are defined Several methods for authenticating with preshared keys are defined
[RFC4279], and we focus on the following two: [RFC4279], and we focus on the following two:
skipping to change at page 38, line 9 skipping to change at page 38, line 35
The first approach (plain PSK) is susceptible to passive dictionary The first approach (plain PSK) is susceptible to passive dictionary
attacks; hence, while this algorithm MUST be supported, special care attacks; hence, while this algorithm MUST be supported, special care
should be taken when choosing that method. In particular, user- should be taken when choosing that method. In particular, user-
readable passphrases SHOULD NOT be used, and use of short PSKs SHOULD readable passphrases SHOULD NOT be used, and use of short PSKs SHOULD
be strongly discouraged. be strongly discouraged.
The following cryptographic algorithms MUST be supported when using The following cryptographic algorithms MUST be supported when using
preshared keys: preshared keys:
o TLS_PSK_WITH_AES_128_CBC_SHA [RFC4279] o TLS_PSK_WITH_AES_128_CBC_SHA [RFC4346]
o TLS_DHE_PSK_WITH_AES_128_CBC_SHA [RFC4279] o TLS_DHE_PSK_WITH_AES_128_CBC_SHA [RFC4346]
The following algorithms MAY be supported when using preshared keys: The following algorithms MAY be supported when using preshared keys:
o TLS_PSK_WITH_AES_256_CBC_SHA [RFC4279] o TLS_PSK_WITH_AES_256_CBC_SHA [RFC4346]
o TLS_DHE_PSK_WITH_AES_256_CBC_SHA [RFC4279]
o TLS_DHE_PSK_WITH_AES_256_CBC_SHA [RFC4279] o TLS_DHE_PSK_WITH_AES_256_CBC_SHA [RFC4346]
Additional ciphers MAY be defined in follow on CAPWAP specifications. Additional ciphers MAY be defined in follow on CAPWAP specifications.
2.4.4.3. Certificate Usage 2.4.4.3. Certificate Usage
Certificate authorization by the AC and WTP is required so that only Certificate authorization by the AC and WTP is required so that only
an AC may perform the functions of an AC and that only a WTP may an AC may perform the functions of an AC and that only a WTP may
perform the functions of a WTP. This restriction of functions to the perform the functions of a WTP. This restriction of functions to the
AC or WTP requires that the certificates used by the AC MUST be AC or WTP requires that the certificates used by the AC MUST be
distinguishable from the certificate used by the WTP. To accomplish distinguishable from the certificate used by the WTP. To accomplish
skipping to change at page 41, line 20 skipping to change at page 41, line 20
UDP is used for the CAPWAP control and data channels. UDP is used for the CAPWAP control and data channels.
When run over IPv6, the CAPWAP control channel always uses UDP, while When run over IPv6, the CAPWAP control channel always uses UDP, while
the CAPWAP data channel may use either UDP or UDP-Lite. UDP-Lite is the CAPWAP data channel may use either UDP or UDP-Lite. UDP-Lite is
the default transport protocol for the CAPWAP data channel. However, the default transport protocol for the CAPWAP data channel. However,
if a middlebox or IPv4 to IPv6 gateway has been discovered, UDP is if a middlebox or IPv4 to IPv6 gateway has been discovered, UDP is
used for the CAPWAP data channel. used for the CAPWAP data channel.
This section describes how the CAPWAP protocol is carried over IP and This section describes how the CAPWAP protocol is carried over IP and
UDP/UDP-Lite transport protocols. The CAPWAP Transport Protocol UDP/UDP-Lite transport protocols. The CAPWAP Transport Protocol
message element Section 4.6.15 describes the rules to use in message element Section 4.6.14 describes the rules to use in
determining which transport protocol is to be used. determining which transport protocol is to be used.
3.1. UDP Transport 3.1. UDP Transport
One of the CAPWAP protocol requirements is to allow a WTP to reside One of the CAPWAP protocol requirements is to allow a WTP to reside
behind a middlebox, firewall and/or Network Address Translation (NAT) behind a middlebox, firewall and/or Network Address Translation (NAT)
device. Since a CAPWAP session is initiated by the WTP (client) to device. Since a CAPWAP session is initiated by the WTP (client) to
the well-known UDP port of the AC (server), the use of UDP is a the well-known UDP port of the AC (server), the use of UDP is a
logical choice. The UDP checksum field in CAPWAP packets MUST be set logical choice. The UDP checksum field in CAPWAP packets MUST be set
to zero. to zero.
CAPWAP protocol control packets sent from the WTP to the AC use the CAPWAP protocol control packets sent from the WTP to the AC use the
CAPWAP control channel, as defined in Section 1.4. The CAPWAP CAPWAP control channel, as defined in Section 1.4. The CAPWAP
control port at the AC is the well known UDP port 5246. The CAPWAP control port at the AC is the well known UDP port 5246. The CAPWAP
control port at the WTP can be any port selected by the WTP. control port at the WTP can be any port selected by the WTP.
CAPWAP protocol data packets sent from the WTP to the AC use the CAPWAP protocol data packets sent from the WTP to the AC use the
CAPWAP data channel, as defined in Section 1.4. The CAPWAP data port CAPWAP data channel, as defined in Section 1.4. The CAPWAP data port
at the AC is the well known UDP port 5247. The CAPWAP data port at at the AC is the well known UDP port 5247. If an AC permits the
administrator to change the CAPWAP control port, the CAPWAP data port
MUST be the next consecutive port number. The CAPWAP data port at
the WTP can be any port selected by the WTP. the WTP can be any port selected by the WTP.
3.2. UDP-Lite Transport 3.2. UDP-Lite Transport
When CAPWAP is run over IPv6, UDP-Lite is the default transport When CAPWAP is run over IPv6, UDP-Lite is the default transport
protocol, which reduces the checksum processing required for each protocol, which reduces the checksum processing required for each
packet (compared to the use of UDP over IPv6 [RFC2460]). When UDP- packet (compared to the use of UDP over IPv6 [RFC2460]). When UDP-
Lite is used, the checksum field MUST have a coverage of 8 [RFC3828]. Lite is used, the checksum field MUST have a coverage of 8 [RFC3828].
UDP-Lite uses the same port assignments as UDP. UDP-Lite uses the same port assignments as UDP.
skipping to change at page 42, line 43 skipping to change at page 42, line 43
When a WTP transmits a Discovery Request message to a unicast When a WTP transmits a Discovery Request message to a unicast
address, the WTP must first obtain the IP address of the AC. Any address, the WTP must first obtain the IP address of the AC. Any
static configuration of an AC's IP address on the WTP non-volatile static configuration of an AC's IP address on the WTP non-volatile
storage is implementation dependent. However, additional dynamic storage is implementation dependent. However, additional dynamic
schemes are possible, for example: schemes are possible, for example:
DHCP: See [I-D.ietf-capwap-dhc-ac-option] for more information on DHCP: See [I-D.ietf-capwap-dhc-ac-option] for more information on
the use of DHCP to discover AC IP addresses. the use of DHCP to discover AC IP addresses.
DNS: The DNS name "CAPWAP-AC-Address" MAY be resolvable to one or DNS: The WTP MAY support use of DNS SRV records [RFC2782] to
more AC addresses. discover the AC address(es). In this case, the WTP first obtains
(e.g., from local configuration) the correct domain name suffix
(e.g., "example.com") and performs a SRV lookup with Service name
"capwap-control" and Proto "udp". Thus, the name resolved in DNS
would be, e.g., "_capwap-control._udp.example.com". Note that the
SRV record MAY specify a non-default port number for the control
channel; the port number for the data channel is the next port
number (control channel port + 1).
An AC MAY also communicate alternative ACs to the WTP within the An AC MAY also communicate alternative ACs to the WTP within the
Discovery Response message through the AC IPv4 List (see Discovery Response message through the AC IPv4 List (see
Section 4.6.2) and AC IPv6 List (see Section 4.6.2). The addresses Section 4.6.2) and AC IPv6 List (see Section 4.6.2). The addresses
provided in these two message elements are intended to help the WTP provided in these two message elements are intended to help the WTP
discover additional ACs through means other than those listed above. discover additional ACs through means other than those listed above.
The AC Name with Index message element (see Section 4.6.5), is used The AC Name with Index message element (see Section 4.6.5), is used
to communicate a list of preferred ACs to the WTP. The WTP SHOULD to communicate a list of preferred ACs to the WTP. The WTP SHOULD
attempt to utilize the ACs listed in the order provided by the AC. attempt to utilize the ACs listed in the order provided by the AC.
skipping to change at page 43, line 35 skipping to change at page 43, line 43
attacks. By providing fragmentation and reassembly at the attacks. By providing fragmentation and reassembly at the
application layer, any fragmentation required due to the tunneling application layer, any fragmentation required due to the tunneling
component of the CAPWAP protocol becomes transparent to these component of the CAPWAP protocol becomes transparent to these
intermediate devices. Consequently, the CAPWAP protocol can be used intermediate devices. Consequently, the CAPWAP protocol can be used
in any network topology including firewall, NAT and middlebox in any network topology including firewall, NAT and middlebox
devices. devices.
3.5. MTU Discovery 3.5. MTU Discovery
Once a WTP has discovered the AC it wishes to establish a CAPWAP Once a WTP has discovered the AC it wishes to establish a CAPWAP
session with, it SHOULD perform a Path MTU (PMTU) discovery. The MTU session with, it SHOULD perform a Path MTU (PMTU) discovery. One
discovered is used to configure the DTLS component (see recommendation for performing PMTU discovery is to have the WTP
Section 2.3.2.1), while non-DTLS frames need to be fragmented to fit transmit Discovery Request (see Section 5.1) messages, and include
the MTU, defined in Section 3.4. The procedures described in the MTU Discovery Padding message element (see Section 4.6.31). The
[RFC1191], for IPv4, or [RFC1981], for IPv6 SHOULD be used. actual procedures used for PMTU discovery are described in [RFC1191],
Alternatively, implementers MAY use the procedures defined in for IPv4, or for IPv6 [RFC1981] SHOULD be used. Alternatively,
[RFC4821]. The WTP SHOULD also periodically re-evaluate the MTU implementers MAY use the procedures defined in [RFC4821]. The WTP
using the guidelines provided in these two RFCs. SHOULD also periodically re-evaluate the PMTU using the guidelines
provided in these two RFCs, using the Primary Discovery Request (see
Section 5.3) along with the MTU Discovery Padding message element
(see Section 4.6.31). When the MTU is initially known, or updated in
the case where an existing session already exists, the discovered
PMTU is used to configure the DTLS component (see Section 2.3.2.1),
while non-DTLS frames need to be fragmented to fit the MTU, defined
in Section 3.4.
4. CAPWAP Packet Formats 4. CAPWAP Packet Formats
This section contains the CAPWAP protocol packet formats. A CAPWAP This section contains the CAPWAP protocol packet formats. A CAPWAP
protocol packet consists of one or more CAPWAP Transport Layer packet protocol packet consists of one or more CAPWAP Transport Layer packet
headers followed by a CAPWAP message. The CAPWAP message can be headers followed by a CAPWAP message. The CAPWAP message can be
either of type Control or Data, where Control packets carry either of type Control or Data, where Control packets carry
signaling, and Data packets carry user payloads. The CAPWAP frame signaling, and Data packets carry user payloads. The CAPWAP frame
formats for CAPWAP Data packets, and for DTLS encapsulated CAPWAP formats for CAPWAP Data packets, and for DTLS encapsulated CAPWAP
Data and Control packets are defined below. Data and Control packets are defined below.
skipping to change at page 46, line 5 skipping to change at page 47, line 5
Message Elements: A CAPWAP Control packet includes one or more Message Elements: A CAPWAP Control packet includes one or more
message elements, which are found immediately following the message elements, which are found immediately following the
Control Header. These message elements are in a Type/Length/value Control Header. These message elements are in a Type/Length/value
style header, defined in Section 4.6. style header, defined in Section 4.6.
A CAPWAP implementation MUST be capable of receiving a reassembled A CAPWAP implementation MUST be capable of receiving a reassembled
CAPWAP message of length 4096 bytes. A CAPWAP implementation MAY CAPWAP message of length 4096 bytes. A CAPWAP implementation MAY
indicate that it supports a higher maximum message length, by indicate that it supports a higher maximum message length, by
including the Maximum Message Length message element, see including the Maximum Message Length message element, see
Section 4.6.32 in the Join Request message or the Join Response Section 4.6.30 in the Join Request message or the Join Response
message. message.
4.1. CAPWAP Preamble 4.1. CAPWAP Preamble
The CAPWAP preamble is common to all CAPWAP transport headers and is The CAPWAP preamble is common to all CAPWAP transport headers and is
used to identify the header type that immediately follows. The used to identify the header type that immediately follows. The
reason for this preamble is to avoid needing to perform byte reason for this preamble is to avoid needing to perform byte
comparisons in order to guess whether the frame is DTLS encrypted or comparisons in order to guess whether the frame is DTLS encrypted or
not. It also provides an extensibility framework that can be used to not. It also provides an extensibility framework that can be used to
support additional transport types. The format of the preamble is as support additional transport types. The format of the preamble is as
skipping to change at page 48, line 23 skipping to change at page 49, line 23
with. with.
WBID: A 5 bit field which is the wireless binding identifier. The WBID: A 5 bit field which is the wireless binding identifier. The
identifier will indicate the type of wireless packet associated identifier will indicate the type of wireless packet associated
with the radio. The following values are defined: with the radio. The following values are defined:
0 - Reserved 0 - Reserved
1 - IEEE 802.11 1 - IEEE 802.11
2 - IEEE 802.16 2 - Reserved
3 - EPCGlobal [EPCGlobal] 3 - EPCGlobal [EPCGlobal]
T: The Type 'T' bit indicates the format of the frame being T: The Type 'T' bit indicates the format of the frame being
transported in the payload. When this bit is set to one (1), the transported in the payload. When this bit is set to one (1), the
payload has the native frame format indicated by the WBID field. payload has the native frame format indicated by the WBID field.
When this bit is zero (0) the payload is an IEEE 802.3 frame. When this bit is zero (0) the payload is an IEEE 802.3 frame.
F: The Fragment 'F' bit indicates whether this packet is a fragment. F: The Fragment 'F' bit indicates whether this packet is a fragment.
When this bit is one (1), the packet is a fragment and MUST be When this bit is one (1), the packet is a fragment and MUST be
skipping to change at page 51, line 32 skipping to change at page 52, line 32
The CAPWAP Data Channel Keep Alive packet contains the following The CAPWAP Data Channel Keep Alive packet contains the following
payload immediately following the CAPWAP Header (see Section 4.3) payload immediately following the CAPWAP Header (see Section 4.3)
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Element Length | Message Element [0..N] ... | Message Element Length | Message Element [0..N] ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message Element Length: The 8 bit Length field indicates the number Message Element Length: The 16 bit Length field indicates the
of bytes following the CAPWAP Header, with a maximum size of number of bytes following the CAPWAP Header, with a maximum size
65535. of 65535.
Message Element[0..N]: The message element(s) carry the information Message Element[0..N]: The message element(s) carry the information
pertinent to each of the CAPWAP Data Channel Keepalive message. pertinent to each of the CAPWAP Data Channel Keepalive message.
The following message elements MUST be present in this CAPWAP The following message elements MUST be present in this CAPWAP
message: message:
Session ID, see Section 4.6.37 Session ID, see Section 4.6.36
4.4.2. Data Payload 4.4.2. Data Payload
A CAPWAP protocol Data Payload packet encapsulates a forwarded A CAPWAP protocol Data Payload packet encapsulates a forwarded
wireless frame. The CAPWAP protocol defines two different modes of wireless frame. The CAPWAP protocol defines two different modes of
encapsulation; IEEE 802.3 and native wireless. IEEE 802.3 encapsulation; IEEE 802.3 and native wireless. IEEE 802.3
encapsulation requires that for 802.11 frames, the 802.11 encapsulation requires that for 802.11 frames, the 802.11
*Integration* function be performed in the WTP. An IEEE 802.3 *Integration* function be performed in the WTP. An IEEE 802.3
encapsulated user payload frame has the following format: encapsulated user payload frame has the following format:
skipping to change at page 52, line 17 skipping to change at page 53, line 17
+------------------------------------------------------+ +------------------------------------------------------+
The CAPWAP protocol also defines the native wireless encapsulation The CAPWAP protocol also defines the native wireless encapsulation
mode. The format of the encapsulated CAPWAP data frame is subject to mode. The format of the encapsulated CAPWAP data frame is subject to
the rules defined by the specific wireless technology binding. Each the rules defined by the specific wireless technology binding. Each
wireless technology binding MUST contain a section entitled "Payload wireless technology binding MUST contain a section entitled "Payload
Encapsulation", which defines the format of the wireless payload that Encapsulation", which defines the format of the wireless payload that
is encapsulated within CAPWAP Data packets. is encapsulated within CAPWAP Data packets.
For 802.3 payload frames, the 802.3 frame is encapsulated (excluding For 802.3 payload frames, the 802.3 frame is encapsulated (excluding
the IEEE 802.3 FCS checksum). If the encapsulated frame would exceed the IEEE 802.3 Preamble, Start Frame Delimiter (SFD) and Frame Check
the transport layer's MTU, the sender is responsible for Sequence (FCS) Fields). If the encapsulated frame would exceed the
fragmentation of the frame, as specified in Section 3.4. The CAPWAP transport layer's MTU, the sender is responsible for fragmentation of
protocol can support IEEE 802.3 frames whose length is defined in the the frame, as specified in Section 3.4. The CAPWAP protocol can
IEEE 802.3as specification [FRAME-EXT]. support IEEE 802.3 frames whose length is defined in the IEEE 802.3as
specification [FRAME-EXT].
4.4.3. Establishment of a DTLS Data Channel 4.4.3. Establishment of a DTLS Data Channel
If the AC and WTP are configured to tunnel the data channel over If the AC and WTP are configured to tunnel the data channel over
DTLS, the proper DTLS session must be initiated. To avoid having to DTLS, the proper DTLS session must be initiated. To avoid having to
reauthenticate and reauthorize an AC and WTP, the DTLS data channel reauthenticate and reauthorize an AC and WTP, the DTLS data channel
MUST be initiated using the TLS session resumption feature [RFC4346]. SHOULD be initiated using the TLS session resumption feature
[RFC4346].
When establishing the DTLS-encrypted data channel, the WTP MUST
provide the identifier returned during the initialization of the
control channel to the DTLS component so it can perform the
resumption using the proper session information.
The AC DTLS implementation MUST NOT accept a session resumption The AC DTLS implementation MUST NOT initiate a data channel session
request for a DTLS session in which the control channel for the for a DTLS session for which there is no active control channel
session has been torn down. session.
4.5. CAPWAP Control Messages 4.5. CAPWAP Control Messages
The CAPWAP Control protocol provides a control channel between the The CAPWAP Control protocol provides a control channel between the
WTP and the AC. Control messages are divided into the following WTP and the AC. Control messages are divided into the following
message types: message types:
Discovery: CAPWAP Discovery messages are used to identify potential Discovery: CAPWAP Discovery messages are used to identify potential
ACs, their load and capabilities. ACs, their load and capabilities.
skipping to change at page 55, line 11 skipping to change at page 56, line 11
The valid values for CAPWAP Control Message Types are specified in The valid values for CAPWAP Control Message Types are specified in
the table below: the table below:
CAPWAP Control Message Message Type CAPWAP Control Message Message Type
Value Value
Discovery Request 1 Discovery Request 1
Discovery Response 2 Discovery Response 2
Join Request 3 Join Request 3
Join Response 4 Join Response 4
Configuration Status 5 Configuration Status Request 5
Configuration Status Response 6 Configuration Status Response 6
Configuration Update Request 7 Configuration Update Request 7
Configuration Update Response 8 Configuration Update Response 8
WTP Event Request 9 WTP Event Request 9
WTP Event Response 10 WTP Event Response 10
Change State Event Request 11 Change State Event Request 11
Change State Event Response 12 Change State Event Response 12
Echo Request 13 Echo Request 13
Echo Response 14 Echo Response 14
Image Data Request 15 Image Data Request 15
skipping to change at page 57, line 5 skipping to change at page 58, line 5
4.5.3. Retransmissions 4.5.3. Retransmissions
The CAPWAP control protocol operates as a reliable transport. For The CAPWAP control protocol operates as a reliable transport. For
each Request message, a Response message is defined, which is used to each Request message, a Response message is defined, which is used to
acknowledge receipt of the Request message. In addition, the control acknowledge receipt of the Request message. In addition, the control
header Sequence Number field is used to pair the Request and Response header Sequence Number field is used to pair the Request and Response
messages (see Section 4.5.1). messages (see Section 4.5.1).
Response messages are not explicitly acknowledged, therefore if a Response messages are not explicitly acknowledged, therefore if a
Response message is not received, the original Request message is Response message is not received, the original Request message is
retransmitted. Implementations MAY cache Response messages to retransmitted.
respond to a retransmitted Request messages with minimal local
processing. Retransmitted Request messages MUST NOT be altered by Implementations MUST keep track of the Sequence Number of the last
the sender. The sender MUST assume that the original Request message received Request message, and MUST cache the corresponding Response
was processed, but that the Response message was lost. Any message. If a retransmission with the same Sequence Number is
alterations to the original Request message MUST have a new Sequence received, the cached Response message MUST be retransmitted without
Number, and be treated as a new Request message by the receiver. re-processing the Request. If an older Request message (with smaller
Sequence Number modulo 32) is received, it MUST be ignored. A newer
Request message (with larger Sequence Number modulo 32) is processed
as usual.
Both the WTP and the AC can only have a single request outstanding at
any given time. Retransmitted Request messages MUST NOT be altered
by the sender.
After transmitting a Request message, the RetransmitInterval (see After transmitting a Request message, the RetransmitInterval (see
Section 4.7) timer and MaxRetransmit (see Section 4.8) variable are Section 4.7) timer and MaxRetransmit (see Section 4.8) variable are
used to determine if the original Request message needs to be used to determine if the original Request message needs to be
retransmitted. The RetransmitInterval timer is used the first time retransmitted. The RetransmitInterval timer is used the first time
the Request is retransmitted. The timer is then doubled every the Request is retransmitted. The timer is then doubled every
subsequent time the same Request message is retransmitted, up to subsequent time the same Request message is retransmitted, up to
MaxRetransmit but no more than half the EchoInterval timer (see MaxRetransmit but no more than half the EchoInterval timer (see
Section 4.7.7). Response messages are not subject to these timers. Section 4.7.7). Response messages are not subject to these timers.
If the sender stops retransmitting a Request message before reaching
MaxRetransmit retransmissions (which leads to transition to DTLS
Teardown, as described in Section 2.3.1), it cannot know whether the
recipient received and processed the Request or not. In most
situations, the sender SHOULD NOT do this, and instead continue
retransmitting until a Response message is received, or transition to
DTLS Teardown occurs. However, if the sender does decide to continue
the connection with a new or modified Request message, the new
message MUST have a new Sequence Number, and be treated as a new
Request message by the receiver.
When a Request message is retransmitted, it MUST be re-encrypted via When a Request message is retransmitted, it MUST be re-encrypted via
the DTLS stack. If the peer had received the Request message, and the DTLS stack. If the peer had received the Request message, and
the corresponding Response message was lost, it is necessary to the corresponding Response message was lost, it is necessary to
ensure that retransmitted Request messages are not identified as ensure that retransmitted Request messages are not identified as
replays by the DTLS stack. Similarly, any cached Response messages replays by the DTLS stack. Similarly, any cached Response messages
that are retransmitted as a result of receiving a retransmitted that are retransmitted as a result of receiving a retransmitted
Request message MUST be re-encrypted via DTLS. Request message MUST be re-encrypted via DTLS.
Duplicate Response messages, identified by the Sequence Number field Duplicate Response messages, identified by the Sequence Number field
in the CAPWAP control message header, SHOULD be discarded upon in the CAPWAP control message header, SHOULD be discarded upon
skipping to change at page 58, line 33 skipping to change at page 60, line 9
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
The 16 bit Type field identifies the information carried in the Value The 16 bit Type field identifies the information carried in the Value
field and Length (16 bits) indicates the number of bytes in the Value field and Length (16 bits) indicates the number of bytes in the Value
field. Type field values are allocated as follows: field. Type field values are allocated as follows:
Usage Type Values Usage Type Values
CAPWAP Protocol Message Elements 1-1023 CAPWAP Protocol Message Elements 1-1023
IEEE 802.11 Message Elements 1024-2047 IEEE 802.11 Message Elements 1024-2047
IEEE 802.16 Message Elements 2048 - 3071 Reserved for Future Use 2048 - 3071
EPCGlobal Message Elements 3072 - 4095 EPCGlobal Message Elements 3072 - 4095
Reserved for Future Use 4096 - 65024 Reserved for Future Use 4096 - 65024
The table below lists the CAPWAP protocol Message Elements and their The table below lists the CAPWAP protocol Message Elements and their
Type values. Type values.
CAPWAP Message Element Type Value CAPWAP Message Element Type Value
AC Descriptor 1 AC Descriptor 1
AC IPv4 List 2 AC IPv4 List 2
AC IPv6 List 3 AC IPv6 List 3
AC Name 4 AC Name 4
AC Name with Index 5 AC Name with Index 5
AC Timestamp 6 AC Timestamp 6
Add MAC ACL Entry 7 Add MAC ACL Entry 7
Add Station 8 Add Station 8
Add Static MAC ACL Entry 9 Reserved 9
CAPWAP Control IPV4 Address 10 CAPWAP Control IPV4 Address 10
CAPWAP Control IPV6 Address 11 CAPWAP Control IPV6 Address 11
CAPWAP Local IPV4 Address 12 CAPWAP Local IPV4 Address 30
CAPWAP Local IPV6 Address 13 CAPWAP Local IPV6 Address 50
CAPWAP Timers 14 CAPWAP Timers 12
CAPWAP Transport Protocol 15 CAPWAP Transport Protocol 51
Data Transfer Data 16 Data Transfer Data 13
Data Transfer Mode 17 Data Transfer Mode 14
Decryption Error Report 18 Decryption Error Report 15
Decryption Error Report Period 19 Decryption Error Report Period 16
Delete MAC ACL Entry 20 Delete MAC ACL Entry 17
Delete Station 21 Delete Station 18
Delete Static MAC ACL Entry 22 Reserved 19
Discovery Type 23 Discovery Type 20
Duplicate IPv4 Address 24 Duplicate IPv4 Address 21
Duplicate IPv6 Address 25 Duplicate IPv6 Address 22
Idle Timeout 26 Idle Timeout 23
Image Data 27 Image Data 24
Image Identifier 28 Image Identifier 25
Image Info 29 Image Information 26
Initiate Download 30 Initiate Download 27
Location Data 31 Location Data 28
Maximum Message Length 32 Maximum Message Length 29
Radio Administrative State 33 MTU Discovery Padding 52
Radio Operational State 34 Radio Administrative State 31
Result Code 35 Radio Operational State 32
Returned Message Element 36 Result Code 33
Session ID 37 Returned Message Element 34
Statistics Timer 38 Session ID 35
Vendor Specific Payload 39 Statistics Timer 36
WTP Board Data 40 Vendor Specific Payload 37
WTP Descriptor 41 WTP Board Data 38
WTP Fallback 42 WTP Descriptor 39
WTP Frame Tunnel Mode 43 WTP Fallback 40
WTP IPv4 IP Address 44 WTP Frame Tunnel Mode 41
WTP IPv6 IP Address 45 Reserved 42
WTP MAC Type 46 Reserved 43
WTP Name 47 WTP MAC Type 44
Unused/Reserved 48 WTP Name 45
WTP Radio Statistics 49 Unused/Reserved 46
WTP Reboot Statistics 50 WTP Radio Statistics 47
WTP Static IP Address Information 51 WTP Reboot Statistics 48
WTP Static IP Address Information 49
4.6.1. AC Descriptor 4.6.1. AC Descriptor
The AC Descriptor message element is used by the AC to communicate The AC Descriptor message element is used by the AC to communicate
its current state. The value contains the following fields. its current state. The value contains the following fields.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stations | Limit | | Stations | Limit |
skipping to change at page 60, line 26 skipping to change at page 62, line 4
Type: 1 for AC Descriptor Type: 1 for AC Descriptor
Length: >= 12 Length: >= 12
Stations: The number of stations currently served by the AC Stations: The number of stations currently served by the AC
Limit: The maximum number of stations supported by the AC Limit: The maximum number of stations supported by the AC
Active WTPs: The number of WTPs currently attached to the AC Active WTPs: The number of WTPs currently attached to the AC
Max WTPs: The maximum number of WTPs supported by the AC Max WTPs: The maximum number of WTPs supported by the AC
Security: A 8 bit mask specifying the authentication credential Security: A 8 bit mask specifying the authentication credential
type supported by the AC. The following values are supported (see type supported by the AC (See Section 2.4.4). The field has the
Section 2.4.4): following format:
1 - X.509 Certificate Based 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|Reserved |S|X|U|
+-+-+-+-+-+-+-+-+
2 - Pre-Shared Secret Reserved: A set of reserved bits for future use. All
implementations complying with this protocol MUST set to zero
any bits that are reserved in the version of the protocol
supported by that implementation. Receivers MUST ignore all
bits not defined for the version of the protocol they support.
S: The AC supports the pre-shared secret authentication, as
described in Section 12.6.
X: The AC supports X.509 Certificate authentication, as
described in Section 12.7.
U: This bit is set to zero and is unused.
R-MAC Field: The AC supports the optional Radio MAC Address field R-MAC Field: The AC supports the optional Radio MAC Address field
in the CAPWAP transport Header (see Section 4.3). in the CAPWAP transport Header (see Section 4.3). The following
enumerated values are supported:
0 - Reserved
1 - Supported
2 - Not Supported
Reserved: A set of reserved bits for future use. All Reserved: A set of reserved bits for future use. All
implementations complying with this protocol MUST set to zero any implementations complying with this protocol MUST set to zero any
bits that are reserved in the version of the protocol supported by bits that are reserved in the version of the protocol supported by
that implementation. Receivers MUST ignore all bits not defined that implementation. Receivers MUST ignore all bits not defined
for the version of the protocol they support. for the version of the protocol they support.
DTLS Policy: The AC communicates its policy on the use of DTLS for DTLS Policy: The AC communicates its policy on the use of DTLS for
the CAPWAP data channel. The AC MAY communicate more than one the CAPWAP data channel. The AC MAY communicate more than one
supported option, represented by the bit field below. The WTP supported option, represented by the bit field below. The WTP
MUST abide by one of the options communicated by AC. The MUST abide by one of the options communicated by AC. The field
following bit field values are supported: has the following format:
1 - Clear Text Data Channel Supported 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|Reserved |D|C|U|
+-+-+-+-+-+-+-+-+
2 - DTLS Enabled Data Channel Supported Reserved: A set of reserved bits for future use. All
implementations complying with this protocol MUST set to zero
any bits that are reserved in the version of the protocol
supported by that implementation. Receivers MUST ignore all
bits not defined for the version of the protocol they support.
D: DTLS Enabled Data Channel Supported
C: Clear Text Data Channel Supported
U: This bit is set to zero and is unused.
AC Information Sub-Element: The AC Descriptor message element AC Information Sub-Element: The AC Descriptor message element
contains multiple AC Information sub-elements, and defines two contains multiple AC Information sub-elements, and defines two
sub-types, each of which MUST be present. The AC Information sub- sub-types, each of which MUST be present. The AC Information sub-
element has the following format: element has the following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AC Information Vendor Identifier | | AC Information Vendor Identifier |
skipping to change at page 61, line 30 skipping to change at page 63, line 43
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AC Information Data... | AC Information Data...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AC Information Vendor Identifier: A 32-bit value containing the AC Information Vendor Identifier: A 32-bit value containing the
IANA assigned "SMI Network Management Private Enterprise Codes" IANA assigned "SMI Network Management Private Enterprise Codes"
AC Information Type: Vendor specific encoding of AC information. AC Information Type: Vendor specific encoding of AC information.
The following enumerated values are supported. Both the The following enumerated values are supported. Both the
Hardware and Software Version sub-elements MUST be included in Hardware and Software Version sub-elements MUST be included in
the AC Descriptor message element. the AC Descriptor message element. The values listed below are
used in conjunction with the AC Information Vendor Identifier
field, whose value MUST be set to zero (0).
4 - Hardware Version: The AC's hardware version number. 4 - Hardware Version: The AC's hardware version number.
5 - Software Version: The AC's Software (firmware) version 5 - Software Version: The AC's Software (firmware) version
number. number.
AC Information Length: Length of vendor specific encoding of AC AC Information Length: Length of vendor specific encoding of AC
information, with a maximum size of 1024. information, with a maximum size of 1024.
AC Information Data: Vendor specific encoding of AC information. AC Information Data: Vendor specific encoding of AC information.
skipping to change at page 62, line 29 skipping to change at page 65, line 4
| AC IP Address[] | | AC IP Address[] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AC IP Address[] | | AC IP Address[] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AC IP Address[] | | AC IP Address[] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AC IP Address[] | | AC IP Address[] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 3 for AC IPV6 List Type: 3 for AC IPV6 List
Length: >= 16 Length: >= 16
AC IP Address: An array of 128-bit integers containing AC IPv6 AC IP Address: An array of 128-bit integers containing AC IPv6
Addresses, containing no more than 1024 addresses. Addresses, containing no more than 1024 addresses.
4.6.4. AC Name 4.6.4. AC Name
The AC Name message element contains an UTF-8 representation of the The AC Name message element contains an UTF-8 [RFC3629]
AC identity. The value is a variable length byte string. The string representation of the AC identity. The value is a variable length
is NOT zero terminated. byte string. The string is NOT zero terminated.
0 0
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Name ... | Name ...
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Type: 4 for AC Name Type: 4 for AC Name
Length: >= 1 Length: >= 1
Name: A variable length UTF-8 encoded string containing the AC's Name: A variable length UTF-8 encoded string [RFC3629] containing
name, whose maximum size MUST NOT exceed 512 bytes. the AC's name, whose maximum size MUST NOT exceed 512 bytes.
4.6.5. AC Name with Index 4.6.5. AC Name with Index
The AC Name with Index message element is sent by the AC to the WTP The AC Name with Index message element is sent by the AC to the WTP
to configure preferred ACs. The number of instances of this message to configure preferred ACs. The number of instances of this message
element is equal to the number of ACs configured on the WTP. element is equal to the number of ACs configured on the WTP. The WTP
also uses this message element to send its configuration to the AC.
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Index | AC Name... | Priority | AC Name...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 5 for AC Name with Index Type: 5 for AC Name with Index
Length: >= 2 Length: >= 2
Index: The index of the preferred server (1=primary, 2=secondary). Priority: A value between 1 and 255 specifying the priority order
of the preferred AC. For instance, the value of one (1) is used
to set the primary AC, the value of two (2) is used to set the
secondary, etc.
AC Name: A variable length UTF-8 encoded string containing the AC AC Name: A variable length UTF-8 encoded string [RFC3629]
name, whose maximum size MUST NOT exceed 512 bytes. containing the AC name, whose maximum size MUST NOT exceed 512
bytes.
4.6.6. AC Timestamp 4.6.6. AC Timestamp
The AC Timestamp message element is sent by the AC to synchronize the The AC Timestamp message element is sent by the AC to synchronize the
WTP clock. WTP clock.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp | | Timestamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 6 for AC Timestamp Type: 6 for AC Timestamp
Length: 4 Length: 4
Timestamp: The AC's current time, allowing all of the WTPs to be Timestamp: The AC's current time, allowing all of the WTPs to be
time synchronized in the format defined by Network Time Protocol time synchronized in the format defined by Network Time Protocol
(NTP) in RFC 1305 [RFC1305]. (NTP) in RFC 1305 [RFC1305]. Only the most significant 32 bits of
the NTP time is included in this field.
4.6.7. Add MAC ACL Entry 4.6.7. Add MAC ACL Entry
The Add MAC Access Control List (ACL) Entry message element is used The Add MAC Access Control List (ACL) Entry message element is used
by an AC to add a MAC ACL list entry on a WTP, ensuring that the WTP by an AC to add a MAC ACL list entry on a WTP, ensuring that the WTP
no longer provides service to the MAC addresses provided in the no longer provides service to the MAC addresses provided in the
message. The MAC Addresses provided in this message element are not message. The MAC Addresses provided in this message element are not
expected to be saved in non-volatile memory on the WTP. expected to be saved in non-volatile memory on the WTP. The MAC ACL
table on the WTP is cleared everytime the WTP establishes a new
session with an AC.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Num of Entries| Length | MAC Address ... | Num of Entries| Length | MAC Address ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 7 for Add MAC ACL Entry Type: 7 for Add MAC ACL Entry
Length: >= 8 Length: >= 8
Num of Entries: The number of instances of the Type/MAC Addresses Num of Entries: The number of instances of the Length/MAC Addresses
fields in the array. This value MUST NOT exceed 255. fields in the array. This value MUST NOT exceed 255.
Length: The length of the MAC Address field. The following formats, Length: The length of the MAC Address field. The following formats,
and lengths, are supported [EUI-48] and [EUI-64]. and lengths, are supported [EUI-48] and [EUI-64].
MAC Address: MAC Addresses to add to the ACL. MAC Address: MAC Addresses to add to the ACL.
4.6.8. Add Station 4.6.8. Add Station
The Add Station message element is used by the AC to inform a WTP The Add Station message element is used by the AC to inform a WTP
skipping to change at page 65, line 15 skipping to change at page 67, line 44
Length: >= 8 Length: >= 8
Radio ID: An 8-bit value representing the radio Radio ID: An 8-bit value representing the radio
Length: The length of the MAC Address field. The following formats, Length: The length of the MAC Address field. The following formats,
and lengths, are supported [EUI-48] and [EUI-64]. and lengths, are supported [EUI-48] and [EUI-64].
MAC Address: The station's MAC Address MAC Address: The station's MAC Address
VLAN Name: An optional variable length UTF-8 encoded string, with a VLAN Name: An optional variable length UTF-8 encoded
maximum length of 512 octets, containing the VLAN Name on which string[RFC3629], with a maximum length of 512 octets, containing
the WTP is to locally bridge user data. Note this field is only the VLAN Name on which the WTP is to locally bridge user data.
valid with WTPs configured in Local MAC mode. Note this field is only valid with WTPs configured in Local MAC
mode.
4.6.9. Add Static MAC ACL Entry
The Add Static MAC ACL Entry message element is used by an AC to add
a permanent ACL entry on a WTP, ensuring that the WTP no longer
provides any service to the MAC addresses provided in the message.
The MAC Addresses provided in this message element are expected to be
saved in non-volatile memory on the WTP.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Num of Entries| Length | MAC Address ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 9 for Add Static MAC ACL Entry
Length: >= 8
Num of Entries: The number of instances of the Type/MAC Addresses
fields in the array. This value MUST NOT exceed 255.
Length: The length of the MAC Address field. The following formats,
and lengths, are supported [EUI-48] and [EUI-64].
MAC Address: MAC Addresses to add to the permanent ACL.
4.6.10. CAPWAP Control IPv4 Address 4.6.9. CAPWAP Control IPv4 Address
The CAPWAP Control IPv4 Address message element is sent by the AC to The CAPWAP Control IPv4 Address message element is sent by the AC to
the WTP during the discovery process and is used by the AC to provide the WTP during the discovery process and is used by the AC to provide
the interfaces available on the AC, and the current number of WTPs the interfaces available on the AC, and the current number of WTPs
connected. When multiple CAPWAP Control IPV4 Address message connected. When multiple CAPWAP Control IPV4 Address message
elements are returned, the WTP SHOULD perform load balancing across elements are returned, the WTP SHOULD perform load balancing across
the multiple interfaces. the multiple interfaces.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
skipping to change at page 66, line 24 skipping to change at page 68, line 31
Type: 10 for CAPWAP Control IPv4 Address Type: 10 for CAPWAP Control IPv4 Address
Length: 6 Length: 6
IP Address: The IP Address of an interface. IP Address: The IP Address of an interface.
WTP Count: The number of WTPs currently connected to the interface, WTP Count: The number of WTPs currently connected to the interface,
with a maximum value of 65535. with a maximum value of 65535.
4.6.11. CAPWAP Control IPv6 Address 4.6.10. CAPWAP Control IPv6 Address
The CAPWAP Control IPv6 Address message element is sent by the AC to The CAPWAP Control IPv6 Address message element is sent by the AC to
the WTP during the discovery process and is used by the AC to provide the WTP during the discovery process and is used by the AC to provide
the interfaces available on the AC, and the current number of WTPs the interfaces available on the AC, and the current number of WTPs
connected. This message element is useful for the WTP to perform connected. This message element is useful for the WTP to perform
load balancing across multiple interfaces. load balancing across multiple interfaces.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 66, line 45 skipping to change at page 69, line 4
| IP Address | | IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP Address | | IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP Address | | IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP Address | | IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| WTP Count | | WTP Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 11 for CAPWAP Control IPv6 Address Type: 11 for CAPWAP Control IPv6 Address
Length: 18 Length: 18
IP Address: The IP Address of an interface. IP Address: The IP Address of an interface.
WTP Count: The number of WTPs currently connected to the interface, WTP Count: The number of WTPs currently connected to the interface,
with a maximum value of 65535. with a maximum value of 65535.
4.6.12. CAPWAP Local IPv4 Address 4.6.11. CAPWAP Local IPv4 Address
The CAPWAP Local IPv4 Address message element is sent by either the The CAPWAP Local IPv4 Address message element is sent by either the
WTP or the AC in the Join Request, Configuration Status Request or WTP, in the Join Request, or by the AC, in the Join Response. The
Image Data Request message in order to communicate the IP Address of CAPWAP Local IPv4 Address message element is used to communicate the
the transmitter. The receiver uses this to determine whether a IP Address of the transmitter. The receiver uses this to determine
middlebox exists between the two peers, by comparing the source IP whether a middlebox exists between the two peers, by comparing the
address of the packet against the value of the message element. source IP address of the packet against the value of the message
element.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP Address | | IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 12 for CAPWAP Local IPv4 Address Type: 30 for CAPWAP Local IPv4 Address
Length: 4 Length: 4
IP Address: The IP Address of the sender. IP Address: The IP Address of the sender.
4.6.13. CAPWAP Local IPv6 Address 4.6.12. CAPWAP Local IPv6 Address
The CAPWAP Local IPv6 Address message element is sent by either the The CAPWAP Local IPv6 Address message element is sent by either the
WTP or the AC in the Discovery Response or Join Request in order to WTP, in the Join Request, or by the AC, in the Join Response. The
communicate the IP Address of the transmitter. The receiver uses CAPWAP Local IPv6 Address message element is used to communicate the
this to determine whether a middlebox exists between the two peers, IP Address of the transmitter. The receiver uses this to determine
by comparing the source IP address of the packet against the value of whether a middlebox exists between the two peers, by comparing the
the message element. source IP address of the packet against the value of the message
element.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP Address | | IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP Address | | IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP Address | | IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP Address | | IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 13 for CAPWAP Local IPv6 Address
Type: 50 for CAPWAP Local IPv6 Address
Length: 16 Length: 16
IP Address: The IP Address of the sender. IP Address: The IP Address of the sender.
4.6.14. CAPWAP Timers 4.6.13. CAPWAP Timers
The CAPWAP Timers message element is used by an AC to configure The CAPWAP Timers message element is used by an AC to configure
CAPWAP timers on a WTP. CAPWAP timers on a WTP.
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Discovery | Echo Request | | Discovery | Echo Request |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 14 for CAPWAP Timers Type: 12 for CAPWAP Timers
Length: 2 Length: 2
Discovery: The number of seconds between CAPWAP Discovery messages, Discovery: The number of seconds between CAPWAP Discovery messages,
when the WTP is in the discovery phase. This value is used to when the WTP is in the discovery phase. This value is used to
configure the MaxDiscoveryInterval timer (see Section 4.7.10). configure the MaxDiscoveryInterval timer (see Section 4.7.10).
Echo Request: The number of seconds between WTP Echo Request CAPWAP Echo Request: The number of seconds between WTP Echo Request CAPWAP
messages. This value is used to configure the EchoInterval timer messages. This value is used to configure the EchoInterval timer
(see Section 4.7.7). The AC sets its EchoInterval timer to this (see Section 4.7.7). The AC sets its EchoInterval timer to this
value, plus the maximum retransmission time as described in value, plus the maximum retransmission time as described in
Section 4.5.3. Section 4.5.3.
4.6.15. CAPWAP Transport Protocol 4.6.14. CAPWAP Transport Protocol
When CAPWAP is run over IPv6, the UDP-Lite or UDP transports MAY be When CAPWAP is run over IPv6, the UDP-Lite or UDP transports MAY be
used (see Section 3). The CAPWAP IPv6 Transport Protocol message used (see Section 3). The CAPWAP IPv6 Transport Protocol message
element is used by either the WTP or the AC to signal which transport element is used by either the WTP or the AC to signal which transport
protocol is to be used for the CAPWAP data channel. protocol is to be used for the CAPWAP data channel.
Upon receiving the Join Request, the AC MAY set the CAPWAP Transport Upon receiving the Join Request, the AC MAY set the CAPWAP Transport
Protocol to UDP-Lite in the Configuration Status Request or Image Protocol to UDP-Lite in the Join Response message if the CAPWAP
Data Request message if the CAPWAP message was received over IPv6, message was received over IPv6, and the CAPWAP Local IPv6 Address
and the CAPWAP Local IPv6 Address message element (see message element (see Section 4.6.12) is present and no middlebox was
Section 4.6.13) is present and the address matches the packet's detected (see Section 11).
source IP address.
Upon receiving the Configuration Status Request or Image Data Request Upon receiving the Join Response, the WTP MAY set the CAPWAP
message, the WTP MAY set the CAPWAP Transport Protocol to UDP-Lite in Transport Protocol to UDP-Lite in the Configuration Status Request or
the Configuration Status Response or Image Data Response message if Image Data Request message if the AC advertised support for UDP-Lite,
the message was received over IPv6, and the CAPWAP Local IPv6 Address the message was received over IPv6, the CAPWAP Local IPv6 Address
message element (see Section 4.6.13) is present and the address message element (see Section 4.6.12) and no middlebox was detected
matches the packet's source IP address. (see Section 11). Upon receiving either the Configuration Status
Request or the Image Data Request, the AC MUST observe the preference
indicated by the WTP in the CAPWAP Transport Protocol, as long as it
is consistent with what the AC advertised in the Join Response.
For any other condition, the CAPWAP Transport Protocol MUST be set to For any other condition, the CAPWAP Transport Protocol MUST be set to
UDP. UDP.
0 0
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Transport | | Transport |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Type: 15 for CAPWAP Transport Protocol Type: 51 for CAPWAP Transport Protocol
Length: 1 Length: 1
Transport: The transport to use for the CAPWAP data channel. The Transport: The transport to use for the CAPWAP data channel. The
following enumerated values are supported: following enumerated values are supported:
1 - UDP-Lite: The UDP-Lite transport protocol is to be used for 1 - UDP-Lite: The UDP-Lite transport protocol is to be used for
the CAPWAP data channel. Note that this option is illegal is the CAPWAP data channel. Note that this option is illegal is
either the WTP or the AC uses IPv4. either the WTP or the AC uses IPv4.
2 - UDP: The UDP transport protocol is to be used for the CAPWAP 2 - UDP: The UDP transport protocol is to be used for the CAPWAP
data channel. data channel.
4.6.16. Data Transfer Data 4.6.15. Data Transfer Data
The Data Transfer Data message element is used by the WTP to provide The Data Transfer Data message element is used by the WTP to provide
information to the AC for debugging purposes. information to the AC for debugging purposes.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Type | Data Mode | Data Length | | Data Type | Data Mode | Data Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data .... | Data ....
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Type: 16 for Data Transfer Data Type: 13 for Data Transfer Data
Length: >= 5 Length: >= 5
Data Type: An 8-bit value representing the transfer Data Type. The Data Type: An 8-bit value representing the transfer Data Type. The
following enumerated values are supported: following enumerated values are supported:
1 - Transfer data is included 1 - Transfer data is included
2 - Last Transfer Data Block is included (EOF) 2 - Last Transfer Data Block is included (EOF)
skipping to change at page 70, line 25 skipping to change at page 72, line 40
1 - WTP Crash Data 1 - WTP Crash Data
2 - WTP Memory Dump 2 - WTP Memory Dump
Data Length: Length of data field, with a maximum size of 65535. Data Length: Length of data field, with a maximum size of 65535.
Data: Data being transferred from the WTP to the AC, whose type is Data: Data being transferred from the WTP to the AC, whose type is
identified via the Data Mode field. identified via the Data Mode field.
4.6.17. Data Transfer Mode 4.6.16. Data Transfer Mode
The Data Transfer Mode message element is used by the WTP to indicate The Data Transfer Mode message element is used by the WTP to indicate
the type of data transfer information it is sending to the AC for the type of data transfer information it is sending to the AC for
debugging purposes. debugging purposes.
0 0
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Data Mode | | Data Mode |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Type: 14 for Data Transfer Mode
Type: 17 for Data Transfer Mode
Length: 1 Length: 1
Data Mode: An 8-bit value the type of information being requested. Data Mode: An 8-bit value the type of information being requested.
The following enumerated values are supported: The following enumerated values are supported:
0 - Reserved 0 - Reserved
1 - WTP Crash Data 1 - WTP Crash Data
2 - WTP Memory Dump 2 - WTP Memory Dump
4.6.18. Decryption Error Report 4.6.17. Decryption Error Report
The Decryption Error Report message element value is used by the WTP The Decryption Error Report message element value is used by the WTP
to inform the AC of decryption errors that have occurred since the to inform the AC of decryption errors that have occurred since the
last report. Note that this error reporting mechanism is not used if last report. Note that this error reporting mechanism is not used if
encryption and decryption services are provided in the AC. encryption and decryption services are provided in the AC.
0 1 2 0 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Radio ID |Num Of Entries | Length | MAC Address... | Radio ID |Num Of Entries | Length | MAC Address...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 18 for Decryption Error Report Type: 15 for Decryption Error Report
Length: >= 9 Length: >= 9
Radio ID: The Radio Identifier refers to an interface index on the Radio ID: The Radio Identifier refers to an interface index on the
WTP. WTP.
Num of Entries: The number of instances of the Type/MAC Addresses Num of Entries: The number of instances of the Length/MAC Addresses
fields in the array. This field MUST NOT exceed the value of 255. fields in the array. This field MUST NOT exceed the value of 255.
Length: The length of the MAC Address field. The following formats, Length: The length of the MAC Address field. The following formats,
and lengths, are supported [EUI-48] and [EUI-64]. and lengths, are supported [EUI-48] and [EUI-64].
MAC Address: MAC addresses of the station that has caused MAC Address: MAC addresses of the station that has caused
decryption errors. decryption errors.
4.6.19. Decryption Error Report Period 4.6.18. Decryption Error Report Period
The Decryption Error Report Period message element value is used by The Decryption Error Report Period message element value is used by
the AC to inform the WTP how frequently it should send decryption the AC to inform the WTP how frequently it should send decryption
error report messages. Note that this error reporting mechanism is error report messages. Note that this error reporting mechanism is
not used if encryption and decryption services are provided in the not used if encryption and decryption services are provided in the
AC. AC.
0 1 2 0 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Radio ID | Report Interval | | Radio ID | Report Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 19 for Decryption Error Report Period Type: 16 for Decryption Error Report Period
Length: 3 Length: 3
Radio ID: The Radio Identifier refers to an interface index on the Radio ID: The Radio Identifier refers to an interface index on the
WTP. WTP.
Report Interval: A 16-bit unsigned integer indicating the time, in Report Interval: A 16-bit unsigned integer indicating the time, in
seconds. The default value for this message element can be found seconds. The default value for this message element can be found
in Section 4.7.11. in Section 4.7.11.
4.6.20. Delete MAC ACL Entry 4.6.19. Delete MAC ACL Entry
The Delete MAC ACL Entry message element is used by an AC to delete a The Delete MAC ACL Entry message element is used by an AC to delete a
MAC ACL entry on a WTP, ensuring that the WTP provides service to the MAC ACL entry on a WTP, ensuring that the WTP provides service to the
MAC addresses provided in the message. MAC addresses provided in the message.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Num of Entries| Length | MAC Address ... | Num of Entries| Length | MAC Address ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 20 for Delete MAC ACL Entry Type: 17 for Delete MAC ACL Entry
Length: >= 8 Length: >= 8
Num of Entries: The number of instances of the Type/MAC Addresses Num of Entries: The number of instances of the Length/MAC Addresses
fields in the array. This field MUST NOT exceed the value of 255. fields in the array. This field MUST NOT exceed the value of 255.
Length: The length of the MAC Address field. The following formats, Length: The length of the MAC Address field. The following formats,
and lengths, are supported [EUI-48] and [EUI-64]. and lengths, are supported [EUI-48] and [EUI-64].
MAC Address: An array of MAC Addresses to delete from the ACL. MAC Address: An array of MAC Addresses to delete from the ACL.
4.6.21. Delete Station 4.6.20. Delete Station
The Delete Station message element is used by the AC to inform a WTP The Delete Station message element is used by the AC to inform a WTP
that it should no longer provide service to a particular station. that it should no longer provide service to a particular station.
The WTP MUST terminate service to the station immediately upon The WTP MUST terminate service to the station immediately upon
receiving this message element. receiving this message element.
The transmission of a Delete Station message element could occur for The transmission of a Delete Station message element could occur for
various reasons, including for administrative reasons, or if the various reasons, including for administrative reasons, or if the
station has roamed to another WTP. station has roamed to another WTP.
skipping to change at page 73, line 12 skipping to change at page 75, line 22
no longer being provided service. This could occur as a result of an no longer being provided service. This could occur as a result of an
Idle Timeout (see section 4.4.43), due to internal resource shortages Idle Timeout (see section 4.4.43), due to internal resource shortages
or for some other reason. or for some other reason.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Radio ID | Length | MAC Address... | Radio ID | Length | MAC Address...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 21 for Delete Station Type: 18 for Delete Station
Length: >= 8 Length: >= 8
Radio ID: An 8-bit value representing the radio Radio ID: An 8-bit value representing the radio
Length: The length of the MAC Address field. The following formats, Length: The length of the MAC Address field. The following formats,
and lengths, are supported [EUI-48] and [EUI-64]. and lengths, are supported [EUI-48] and [EUI-64].
MAC Address: The station's MAC Address MAC Address: The station's MAC Address
4.6.22. Delete Static MAC ACL Entry 4.6.21. Discovery Type
The Delete Static MAC ACL Entry message element is used by an AC to
delete a previously added static MAC ACL entry on a WTP, ensuring
that the WTP provides service to the MAC addresses provided in the
message.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Num of Entries| Length | MAC Address ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 22 for Delete Static MAC ACL Entry
Length: >= 8
Num of Entries: The number of instances of the Type/MAC Addresses
fields in the array. This field MUST NOT exceed the value of
1024.
Length: The length of the MAC Address field. The following formats,
and lengths, are supported [EUI-48] and [EUI-64].
MAC Address: An array of MAC Addresses to delete from the static
MAC ACL entry.
4.6.23. Discovery Type
The Discovery Type message element is used by the WTP to indicate how The Discovery Type message element is used by the WTP to indicate how
it has come to know about the existence of the AC to which it is it has come to know about the existence of the AC to which it is
sending the Discovery Request message. sending the Discovery Request message.
0 0
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Discovery Type| | Discovery Type|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Type: 23 for Discovery Type Type: 20 for Discovery Type
Length: 1 Length: 1
Discovery Type: An 8-bit value indicating how the WTP discovered Discovery Type: An 8-bit value indicating how the WTP discovered
the AC. The following enumerated values are supported: the AC. The following enumerated values are supported:
0 - Unknown 0 - Unknown
1 - Static Configuration 1 - Static Configuration
2 - DHCP 2 - DHCP
3 - DNS 3 - DNS
skipping to change at page 74, line 35 skipping to change at page 76, line 18
1 - Static Configuration 1 - Static Configuration
2 - DHCP 2 - DHCP
3 - DNS 3 - DNS
4 - AC Referral (used when the AC was configured either through 4 - AC Referral (used when the AC was configured either through
the AC IPv4 List or AC IPv6 List message element) the AC IPv4 List or AC IPv6 List message element)
4.6.24. Duplicate IPv4 Address 4.6.22. Duplicate IPv4 Address
The Duplicate IPv4 Address message element is used by a WTP to inform The Duplicate IPv4 Address message element is used by a WTP to inform
an AC that it has detected another IP device using the same IP an AC that it has detected another IP device using the same IP
address that the WTP is currently using. address that the WTP is currently using.
The WTP MUST transmit this message element with the status set to 1 The WTP MUST transmit this message element with the status set to 1
after it has detected a duplicate IP address. When the WTP detects after it has detected a duplicate IP address. When the WTP detects
that the duplicate IP address has been cleared, it MUSY send this that the duplicate IP address has been cleared, it MUSY send this
message element with the status set to 0. message element with the status set to 0.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP Address | | IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status | Length | MAC Address ... | Status | Length | MAC Address ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 24 for Duplicate IPv4 Address
Type: 21 for Duplicate IPv4 Address
Length: >= 12 Length: >= 12
IP Address: The IP Address currently used by the WTP. IP Address: The IP Address currently used by the WTP.
Status: The status of the duplicate IP address. The value MUST be Status: The status of the duplicate IP address. The value MUST be
set to 1 when a duplicate address is detected, and 0 when the set to 1 when a duplicate address is detected, and 0 when the
duplicate address has been cleared. duplicate address has been cleared.
Length: The length of the MAC Address field. The following formats, Length: The length of the MAC Address field. The following formats,
and lengths, are supported [EUI-48] and [EUI-64]. and lengths, are supported [EUI-48] and [EUI-64].
MAC Address: The MAC Address of the offending device. MAC Address: The MAC Address of the offending device.
4.6.25. Duplicate IPv6 Address 4.6.23. Duplicate IPv6 Address
The Duplicate IPv6 Address message element is used by a WTP to inform The Duplicate IPv6 Address message element is used by a WTP to inform
an AC that it has detected another host using the same IP address an AC that it has detected another host using the same IP address
that the WTP is currently using. that the WTP is currently using.
The WTP MUST transmit this message element with the status set to 1 The WTP MUST transmit this message element with the status set to 1
after it has detected a duplicate IP address. When the WTP detects after it has detected a duplicate IP address. When the WTP detects
that the duplicate IP address has been cleared, it MUST send this that the duplicate IP address has been cleared, it MUST send this
message element with the status set to 0. message element with the status set to 0.
skipping to change at page 75, line 44 skipping to change at page 77, line 32
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP Address | | IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP Address | | IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP Address | | IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status | Length | MAC Address ... | Status | Length | MAC Address ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 25 for Duplicate IPv6 Address Type: 22 for Duplicate IPv6 Address
Length: >= 24 Length: >= 24
IP Address: The IP Address currently used by the WTP. IP Address: The IP Address currently used by the WTP.
Status: The status of the duplicate IP address. The value MUST be Status: The status of the duplicate IP address. The value MUST be
set to 1 when a duplicate address is detected, and 0 when the set to 1 when a duplicate address is detected, and 0 when the
duplicate address has been cleared. duplicate address has been cleared.
Length: The length of the MAC Address field. The following formats, Length: The length of the MAC Address field. The following formats,
and lengths, are supported [EUI-48] and [EUI-64]. and lengths, are supported [EUI-48] and [EUI-64].
MAC Address: The MAC Address of the offending device. MAC Address: The MAC Address of the offending device.
4.6.26. Idle Timeout 4.6.24. Idle Timeout
The Idle Timeout message element is sent by the AC to the WTP to The Idle Timeout message element is sent by the AC to the WTP to
provide the idle timeout value that the WTP SHOULD enforce for its provide the idle timeout value that the WTP SHOULD enforce for its
active stations. The value applies to all radios on the WTP. active stations. The value applies to all radios on the WTP.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timeout | | Timeout |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 26 for Idle Timeout Type: 23 for Idle Timeout
Length: 4 Length: 4
Timeout: The current idle timeout, in seconds, to be enforced by Timeout: The current idle timeout, in seconds, to be enforced by
the WTP. The default value for this message element is specified the WTP. The default value for this message element is specified
in Section 4.7.8. in Section 4.7.8.
4.6.27. Image Data 4.6.25. Image Data
The Image Data message element is present in the Image Data Request The Image Data message element is present in the Image Data Request
message sent by the AC and contains the following fields. message sent by the AC and contains the following fields.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Type | Data .... | Data Type | Data ....
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 27 for Image Data Type: 24 for Image Data
Length: >= 1 Length: >= 1
Data Type: An 8-bit value representing the image Data Type. The Data Type: An 8-bit value representing the image Data Type. The
following enumerated values are supported: following enumerated values are supported:
1 - Image data is included 1 - Image data is included
2 - Last Image Data Block is included (EOF) 2 - Last Image Data Block is included (EOF)
5 - An error occurred. Transfer is aborted 5 - An error occurred. Transfer is aborted
Data: The Image Data field contains up to 1024 characters, and its Data: The Image Data field contains up to 1024 characters, and its
length is inferred from this message element's length field. If length is inferred from this message element's length field. If
the block being sent is the last one, the Opcode is set to 2. The the block being sent is the last one, the Opcode is set to 2. The
AC MAY opt to abort the data transfer by setting the Opcode to 5. AC MAY opt to abort the data transfer by setting the Opcode to 5.
When the Opcode is 5, the Value field has a zero length. When the Opcode is 5, the Value field has a zero length.
4.6.28. Image Identifier 4.6.26. Image Identifier
The Image Identifier message element is sent by the AC to the WTP and The Image Identifier message element is sent by the AC to the WTP to
is used to indicate the expected active software version that is to indicate the expected active software version that is to be run on
be run on the WTP. The value is a variable length UTF-8 encoded the WTP. The WTP sends the Image Identifier message element in order
string, which is NOT zero terminated. to request a specific software version from the AC. The actual
download process is defined in Section 9.1. The value is a variable
length UTF-8 encoded string [RFC3629], which is NOT zero terminated.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor Identifier | | Vendor Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data... | Data...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 28 for Image Identifier Type: 25 for Image Identifier
Length: >= 1 Length: >= 5
Data Length: Length of data field, with a maximum size of 65535. Vendor Identifier: A 32-bit value containing the IANA assigned "SMI
Network Management Private Enterprise Codes"
Data: A variable length UTF-8 encoded string containing the Data: A variable length UTF-8 encoded string [RFC3629] containing
firmware identifier to be run on the WTP, whose length MUST NOT the firmware identifier to be run on the WTP, whose length MUST
exceed 1024 octets. The length of this field is inferred from NOT exceed 1024 octets. The length of this field is inferred from
this message element's length field. this message element's length field.
4.6.29. Image Information 4.6.27. Image Information
The Image Information message element is present in the Image Data The Image Information message element is present in the Image Data
Response message sent by the AC to the WTP and contains the following Response message sent by the AC to the WTP and contains the following
fields. fields.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| File Size | | File Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hash | | Hash |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hash | | Hash |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hash | | Hash |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hash | | Hash |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 26 for Image Information
Type: 29 for Image Information
Length: 20 Length: 20
File Size: A 32-bit value containing the size of the file, in File Size: A 32-bit value containing the size of the file, in
bytes, that will be transferred by the AC to the WTP. bytes, that will be transferred by the AC to the WTP.
Hash: A 16 octet hash of the image. The hash is computed using Hash: A 16 octet MD5 hash of the image using the procedures defined
MD5, using the following pseudo-code: in [RFC1321].
#include <md5.h>
CapwapCreateHash(char *hash, char *image, int image_len)
{
MD_CTX context;
MDInit (&context);
MDUpdate (&context, buffer, len);
MDFinal (hash, &context);
}
4.6.30. Initiate Download 4.6.28. Initiate Download
The Initiate Download message element is used by the AC to inform the The Initiate Download message element is used by the WTP to inform
WTP that the WTP SHOULD initiate a firmware upgrade. The WTP the AC that the AC SHOULD initiate a firmware upgrade. The AC
subsequently transmits an Image Data Request message which includes subsequently transmits an Image Data Request message which includes
the Image Download message element. This message element does not the Image Data message element. This message element does not
contain any data. contain any data.
Type: 30 for Initiate Download Type: 27 for Initiate Download
Length: 0 Length: 0
4.6.31. Location Data 4.6.29. Location Data
The Location Data message element is a variable length byte UTF-8 The Location Data message element is a variable length byte UTF-8
encoded string containing user defined location information (e.g. encoded string [RFC3629] containing user defined location information
"Next to Fridge"). This information is configurable by the network (e.g. "Next to Fridge"). This information is configurable by the
administrator, and allows the WTP location to be determined. The network administrator, and allows the WTP location to be determined.
string is not zero terminated. The string is not zero terminated.
0 0
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-
| Location ... | Location ...
+-+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-
Type: 31 for Location Data Type: 28 for Location Data
Length: >= 1 Length: >= 1
Location: A non-zero terminated UTF-8 encoded string containing the Location: A non-zero terminated UTF-8 encoded string [RFC3629]
WTP location, whose maximum size MUST NOT exceed 1024. containing the WTP location, whose maximum size MUST NOT exceed
1024.
4.6.32. Maximum Message Length 4.6.30. Maximum Message Length
The Maximum Message Length message element is included in the Join The Maximum Message Length message element is included in the Join
Request message by the WTP to indicate the maximum CAPWAP message Request message by the WTP to indicate the maximum CAPWAP message
length that it supports to the AC. The Maximum Message Length length that it supports to the AC. The Maximum Message Length
message element is optionally included in Join Response message by message element is optionally included in Join Response message by
the AC to indicate the maximum CAPWAP message length that it supports the AC to indicate the maximum CAPWAP message length that it supports
to the WTP. to the WTP.
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Maximum Message Length | | Maximum Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 32 for Maximum Message Length Type: 29 for Maximum Message Length
Length: 2 Length: 2
Maximum Message Length An 16-bit unsigned integer indicating the Maximum Message Length An 16-bit unsigned integer indicating the
maximum message length. maximum message length.
4.6.33. Radio Administrative State 4.6.31. MTU Discovery Padding
The MTU Discovery Padding message element is used as padding to
perform MTU discovery, and MUST contain octets of value 0xFF, of any
length.
0
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
| Padding...
+-+-+-+-+-+-+-+-
Type: 52 for MTU Discovery Padding
Length: variable
Pad: A variable length pad, filled with the value 0xFF.
4.6.32. Radio Administrative State
The Radio Administrative State message element is used to communicate The Radio Administrative State message element is used to communicate
the state of a particular radio. The Radio Administrative State the state of a particular radio. The Radio Administrative State
message element is sent by the AC to change the state of the WTP. message element is sent by the AC to change the state of the WTP.
The WTP saves the value, to ensure that it remains across WTP resets. The WTP saves the value, to ensure that it remains across WTP resets.
The WTP communicates this message element during the configuration The WTP communicates this message element during the configuration
phase, in the Configuration Status Request message, to ensure that AC phase, in the Configuration Status Request message, to ensure that AC
has the WTP radio current administrative state settings. The message has the WTP radio current administrative state settings. The message
element contains the following fields. element contains the following fields.
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Radio ID | Admin State | | Radio ID | Admin State |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 80, line 22 skipping to change at page 82, line 16
phase, in the Configuration Status Request message, to ensure that AC phase, in the Configuration Status Request message, to ensure that AC
has the WTP radio current administrative state settings. The message has the WTP radio current administrative state settings. The message
element contains the following fields. element contains the following fields.
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Radio ID | Admin State | | Radio ID | Admin State |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 33 for Radio Administrative State Type: 31 for Radio Administrative State
Length: 2 Length: 2
Radio ID: An 8-bit value representing the radio to configure. The Radio ID: An 8-bit value representing the radio to configure. The
Radio ID field MAY also include the value of 0xff, which is used Radio ID field MAY also include the value of 0xff, which is used
to identify the WTP. If an AC wishes to change the administrative to identify the WTP. If an AC wishes to change the administrative
state of a WTP, it includes 0xff in the Radio ID field. state of a WTP, it includes 0xff in the Radio ID field.
Admin State: An 8-bit value representing the administrative state Admin State: An 8-bit value representing the administrative state
of the radio. The default value for the Admin State field is of the radio. The default value for the Admin State field is
listed in Section 4.8.1. The following enumerated values are listed in Section 4.8.1. The following enumerated values are
supported: supported:
0 - Reserved 0 - Reserved
1 - Enabled 1 - Enabled
2 - Disabled 2 - Disabled
4.6.34. Radio Operational State 4.6.33. Radio Operational State
The Radio Operational State message element is sent by the WTP to the The Radio Operational State message element is sent by the WTP to the
AC to communicate a radio's operational state. This message element AC to communicate a radio's operational state. This message element
is included in the Configuration Update Response message by the WTP is included in the Configuration Update Response message by the WTP
if it was requested to change the state of its radio, via the Radio if it was requested to change the state of its radio, via the Radio
Administrative State message element, but was unable to comply to the Administrative State message element, but was unable to comply to the
request. This message element is included in the Change State Event request. This message element is included in the Change State Event
message when a WTP radio state was changed unexpectedly. This could message when a WTP radio state was changed unexpectedly. This could
occur due to a hardware failure. Note that the operational state occur due to a hardware failure. Note that the operational state
setting is not saved on the WTP, and therefore does not remain across setting is not saved on the WTP, and therefore does not remain across
WTP resets. The value contains three fields, as shown below. WTP resets. The value contains three fields, as shown below.
0 1 2 0 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Radio ID | State | Cause | | Radio ID | State | Cause |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 34 for Radio Operational State Type: 32 for Radio Operational State
Length: 3 Length: 3
Radio ID: The Radio Identifier refers to an interface index on the Radio ID: The Radio Identifier refers to an interface index on the
WTP. A value of 0xFF is invalid, as it is not possible to change WTP. A value of 0xFF is invalid, as it is not possible to change
the WTP's operational state. the WTP's operational state.
State: An 8-bit boolean value representing the state of the radio. State: An 8-bit boolean value representing the state of the radio.
The following enumerated values are supported: The following enumerated values are supported:
skipping to change at page 81, line 41 skipping to change at page 83, line 35
values are supported: values are supported:
0 - Normal 0 - Normal
1 - Radio Failure 1 - Radio Failure
2 - Software Failure 2 - Software Failure
3 - Administratively Set 3 - Administratively Set
4.6.35. Result Code 4.6.34. Result Code
The Result Code message element value is a 32-bit integer value, The Result Code message element value is a 32-bit integer value,
indicating the result of the Request message corresponding to the indicating the result of the Request message corresponding to the
Sequence Number included in the Response message. Sequence Number included in the Response message.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Result Code | | Result Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 35 for Result Code
Type: 33 for Result Code
Length: 4 Length: 4
Result Code: The following enumerated values are defined: Result Code: The following enumerated values are defined:
0 Success 0 Success
1 Failure (AC List message element MUST be present) 1 Failure (AC List message element MUST be present)
2 Success (NAT detected) 2 Success (NAT detected)
skipping to change at page 83, line 4 skipping to change at page 84, line 47
14 Image Data Error (Invalid Checksum) 14 Image Data Error (Invalid Checksum)
15 Image Data Error (Invalid Data Length) 15 Image Data Error (Invalid Data Length)
16 Image Data Error (Other Error) 16 Image Data Error (Other Error)
17 Image Data Error (Image Already Present) 17 Image Data Error (Image Already Present)
18 Message Unexpected (Invalid in current state) 18 Message Unexpected (Invalid in current state)
19 Message Unexpected (Unrecognized Request)
19 Message Unexpected (Unrecognized Request)
20 Failure - Missing Mandatory Message Element 20 Failure - Missing Mandatory Message Element
21 Failure - Unrecognized Message Element 21 Failure - Unrecognized Message Element
22 Data Transfer Error (No Information to Transfer) 22 Data Transfer Error (No Information to Transfer)
4.6.36. Returned Message Element 4.6.35. Returned Message Element
The Returned Message Element is sent by the WTP in the Change State The Returned Message Element is sent by the WTP in the Change State
Event Request message to communicate to the AC which message elements Event Request message to communicate to the AC which message elements
in the Configuration Status Response it was unable to apply locally. in the Configuration Status Response it was unable to apply locally.
The Returned Message Element message element contains a result code The Returned Message Element message element contains a result code
indicating the reason that the configuration could not be applied, indicating the reason that the configuration could not be applied,
and encapsulates the failed message element. and encapsulates the failed message element.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reason | Length | Message Element... | Reason | Length | Message Element...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 36 for Returned Message Element Type: 34 for Returned Message Element
Length: >= 6 Length: >= 6
Reason: The reason why the configuration in the offending message Reason: The reason why the configuration in the offending message
element could not be applied by the WTP. The following enumerated element could not be applied by the WTP. The following enumerated
values are supported: values are supported:
0 - Reserved 0 - Reserved
1 - Unknown Message Element 1 - Unknown Message Element
skipping to change at page 84, line 5 skipping to change at page 86, line 5
4 - Unsupported Message Element Value 4 - Unsupported Message Element Value
Length: The length of the Message Element field, which MUST NOT Length: The length of the Message Element field, which MUST NOT
exceed 65535 octets. exceed 65535 octets.
Message Element: The Message Element field encapsulates the message Message Element: The Message Element field encapsulates the message
element sent by the AC in the Configuration Status Response element sent by the AC in the Configuration Status Response
message that caused the error. message that caused the error.
4.6.37. Session ID 4.6.36. Session ID
The Session ID message element value contains a randomly generated The Session ID message element value contains a randomly generated
unsigned 32-bit integer. unsigned 32-bit integer.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session ID | | Session ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 37 for Session ID Type: 35 for Session ID
Length: 4 Length: 32
Session ID: A 32-bit unsigned integer used as a random session Session ID: A 32-bit unsigned integer used as a random session
identifier identifier
4.6.38. Statistics Timer 4.6.37. Statistics Timer
The Statistics Timer message element value is used by the AC to The Statistics Timer message element value is used by the AC to
inform the WTP of the frequency with which it expects to receive inform the WTP of the frequency with which it expects to receive
updated statistics. updated statistics.
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Statistics Timer | | Statistics Timer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 38 for Statistics Timer Type: 36 for Statistics Timer
Length: 2 Length: 2
Statistics Timer: A 16-bit unsigned integer indicating the time, in Statistics Timer: A 16-bit unsigned integer indicating the time, in
seconds. The default value for this timer is specified in seconds. The default value for this timer is specified in
Section 4.7.14. Section 4.7.14.
4.6.39. Vendor Specific Payload 4.6.38. Vendor Specific Payload
The Vendor Specific Payload message element is used to communicate The Vendor Specific Payload message element is used to communicate
vendor specific information between the WTP and the AC. The Vendor vendor specific information between the WTP and the AC. The Vendor
Specific Payload message element MAY be present in any CAPWAP Specific Payload message element MAY be present in any CAPWAP
message. The message element uses the following format: message. The message element uses the following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor Identifier | | Vendor Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Element ID | Data... | Element ID | Data...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 39 for Vendor Specific Type: 37 for Vendor Specific Payload
Length: >= 7 Length: >= 7
Vendor Identifier: A 32-bit value containing the IANA assigned "SMI Vendor Identifier: A 32-bit value containing the IANA assigned "SMI
Network Management Private Enterprise Codes" [RFC3232] Network Management Private Enterprise Codes" [RFC3232]
Element ID: A 16-bit Element Identifier which is managed by the Element ID: A 16-bit Element Identifier which is managed by the
vendor. vendor.
Data: Variable length vendor specific information, whose contents Data: Variable length vendor specific information, whose contents
and format are proprietary and understood based on the Element ID and format are proprietary and understood based on the Element ID
field. This field MUST NOT exceed 2048 octets. field. This field MUST NOT exceed 2048 octets.
4.6.40. WTP Board Data 4.6.39. WTP Board Data
The WTP Board Data message element is sent by the WTP to the AC and The WTP Board Data message element is sent by the WTP to the AC and
contains information about the hardware present. contains information about the hardware present.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor Identifier | | Vendor Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Board Data Sub-Element... | Board Data Sub-Element...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 40 for WTP Board Data Type: 38 for WTP Board Data
Length: >=14 Length: >=14
Vendor Identifier: A 32-bit value containing the IANA assigned "SMI Vendor Identifier: A 32-bit value containing the IANA assigned "SMI
Network Management Private Enterprise Codes" Network Management Private Enterprise Codes", identifying the WTP
hardware manufacturer.
Board Data Sub-Element: The WTP Board Data message element contains Board Data Sub-Element: The WTP Board Data message element contains
multiple Board Data sub-elements, some of which are mandatory and multiple Board Data sub-elements, some of which are mandatory and
some are optional, as described below. The Board Data sub-element some are optional, as described below. The Board Data sub-element
has the following format: has the following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Board Data Type | Board Data Length | | Board Data Type | Board Data Length |
skipping to change at page 86, line 39 skipping to change at page 89, line 5
4 - Base MAC Address The WTP's Base MAC Address, which MAY be 4 - Base MAC Address The WTP's Base MAC Address, which MAY be
assigned to the primary Ethernet interface. assigned to the primary Ethernet interface.
Board Data Length: The length of the data in the Board Data Board Data Length: The length of the data in the Board Data
Value field, whose length MUST NOT exceed 1024 octets. Value field, whose length MUST NOT exceed 1024 octets.
Board Data Value: The data associated with the Board Data Type Board Data Value: The data associated with the Board Data Type
field for this Board Data sub-element. field for this Board Data sub-element.
4.6.41. WTP Descriptor 4.6.40. WTP Descriptor
The WTP Descriptor message element is used by a WTP to communicate The WTP Descriptor message element is used by a WTP to communicate
its current hardware and software (firmware) configuration. The its current hardware and software (firmware) configuration. The
value contains the following fields. value contains the following fields.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max Radios | Radios in use | Encryption Capabilities | | Max Radios | Radios in use | Encryption Sub-Element |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Descriptor Sub-Element... | Descriptor Sub-Element...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 41 for WTP Descriptor
Type: 39 for WTP Descriptor
Length: >= 31 Length: >= 31
Max Radios: An 8-bit value representing the number of radios (where Max Radios: An 8-bit value representing the number of radios (where
each radio is identified via the Radio ID field) supported by the each radio is identified via the Radio ID field) supported by the
WTP. WTP.
Radios in use: An 8-bit value representing the number of radios in Radios in use: An 8-bit value representing the number of radios in
use in the WTP. use in the WTP.
Encryption Sub-Element: The WTP Descriptor message element MUST
contain at least one Encryption sub-element. One sub-element is
present for each binding supported by the WTP. The Encryption
sub-element has the following format:
0 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Resvd| WBID | Encryption Capabilities |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Resvd: The 3-bit field is reserved for future use. All
implementations complying with this protocol MUST set to zero
any bits that are reserved in the version of the protocol
supported by that implementation. Receivers MUST ignore all
bits not defined for the version of the protocol they support.
WBID: A 5 bit field which is the wireless binding identifier.
The identifier will indicate the type of wireless packet
associated with the radio. The WBIDs defined in this
specification can be found in Section 4.3
Encryption Capabilities: This 16-bit field is used by the WTP to Encryption Capabilities: This 16-bit field is used by the WTP to
communicate its capabilities to the AC. A WTP that does not have communicate its capabilities to the AC. A WTP that does not
any encryption capabilities sets this field to zero (0). Refer to have any encryption capabilities sets this field to zero (0).
the specific wireless binding for further specification of the Refer to the specific wireless binding for further
Encryption Capabilities field. specification of the Encryption Capabilities field.
Descriptor Sub-Element: The WTP Descriptor message element contains Descriptor Sub-Element: The WTP Descriptor message element contains
multiple Descriptor sub-elements, some of which are mandatory and multiple Descriptor sub-elements, some of which are mandatory and
some are optional, as described below. The Descriptor sub-element some are optional, as described below. The Descriptor sub-element
has the following format: has the following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Descriptor Vendor Identifier | | Descriptor Vendor Identifier |
skipping to change at page 87, line 42 skipping to change at page 90, line 31
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Descriptor Data... | Descriptor Data...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Descriptor Vendor Identifier: A 32-bit value containing the IANA Descriptor Vendor Identifier: A 32-bit value containing the IANA
assigned "SMI Network Management Private Enterprise Codes". assigned "SMI Network Management Private Enterprise Codes".
Descriptor Type: The Descriptor Type field identifies the data Descriptor Type: The Descriptor Type field identifies the data
being encoded. The CAPWAP protocol defines the following being encoded. The CAPWAP protocol defines the following
values, and each of these types identify whether their presence values, and each of these types identify whether their presence
is mandatory or optional: is mandatory or optional. The values listed below are used in
conjunction with the Descriptor Vendor Identifier field, whose
value MUST be set to zero (0).
0 - Hardware Version: The WTP hardware version number MUST be 0 - Hardware Version: The WTP hardware version number MUST be
present. present.
1 - Active Software Version: The WTP running software version 1 - Active Software Version: The WTP running software version
number MUST be present. number MUST be present.
2 - Boot Version: The WTP boot loader version number MUST be 2 - Boot Version: The WTP boot loader version number MUST be
present. present.
3 - Other Software Version: The WTP non-running software 3 - Other Software Version: The WTP non-running software
(firmware) version number MAY be present. This type is used (firmware) version number MAY be present. This type is used
to communicate alternate software versions that are to communicate alternate software versions that are
available on the WTP's non-volatile storage. available on the WTP's non-volatile storage.
Descriptor Length: Length of vendor specific encoding of Descriptor Length: Length of vendor specific encoding of
Descriptor Data field, whose length MUST NOT exceed 1024 Descriptor Data field, whose length MUST NOT exceed 1024
octets. octets.
Descriptor Data: Vendor specific data of WTP information encoded Descriptor Data: Vendor specific data of WTP information encoded
in the UTF-8 format. in the UTF-8 format [RFC3629].
4.6.42. WTP Fallback 4.6.41. WTP Fallback
The WTP Fallback message element is sent by the AC to the WTP to The WTP Fallback message element is sent by the AC to the WTP to
enable or disable automatic CAPWAP fallback in the event that a WTP enable or disable automatic CAPWAP fallback in the event that a WTP
detects its preferred AC, and is not currently connected to it. detects its preferred AC, and is not currently connected to it.
0 0
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Mode | | Mode |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Type: 42 for WTP Fallback Type: 40 for WTP Fallback
Length: 1 Length: 1
Mode: The 8-bit value indicates the status of automatic CAPWAP Mode: The 8-bit value indicates the status of automatic CAPWAP
fallback on the WTP. When enabled, if the WTP detects that its fallback on the WTP. When enabled, if the WTP detects that its
primary AC is available, and that the WTP is not connected to the primary AC is available, and that the WTP is not connected to the
primary AC, the WTP SHOULD automatically disconnect from its primary AC, the WTP SHOULD automatically disconnect from its
current AC and reconnect to its primary AC. If disabled, the WTP current AC and reconnect to its primary AC. If disabled, the WTP
will only reconnect to its primary AC through manual intervention will only reconnect to its primary AC through manual intervention
(e.g., through the Reset Request message). The default value for (e.g., through the Reset Request message). The default value for
skipping to change at page 89, line 4 skipping to change at page 91, line 41
primary AC, the WTP SHOULD automatically disconnect from its primary AC, the WTP SHOULD automatically disconnect from its
current AC and reconnect to its primary AC. If disabled, the WTP current AC and reconnect to its primary AC. If disabled, the WTP
will only reconnect to its primary AC through manual intervention will only reconnect to its primary AC through manual intervention
(e.g., through the Reset Request message). The default value for (e.g., through the Reset Request message). The default value for
this field is specified in Section 4.8.9. The following this field is specified in Section 4.8.9. The following
enumerated values are supported: enumerated values are supported:
0 - Reserved 0 - Reserved
1 - Enabled 1 - Enabled
2 - Disabled 2 - Disabled
4.6.43. WTP Frame Tunnel Mode 4.6.42. WTP Frame Tunnel Mode
The WTP Frame Tunnel Mode message element allows the WTP to The WTP Frame Tunnel Mode message element allows the WTP to
communicate the tunneling modes of operation which it supports to the communicate the tunneling modes of operation which it supports to the
AC. A WTP that advertises support for all types allows the AC to AC. A WTP that advertises support for all types allows the AC to
select which type will be used, based on its local policy. select which type will be used, based on its local policy.
0 0
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Tunnel Mode | |Reservd|N|E|L|U|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Type: 43 for WTP Frame Tunnel Mode Type: 41 for WTP Frame Tunnel Mode
Length: 1 Length: 1
Frame Tunnel Mode: The Frame Tunnel mode specifies the tunneling Reservd: A set of reserved bits for future use. All
modes for station data that are supported by the WTP. The implementations complying with this protocol MUST set to zero any
following values are supported for this bit field: bits that are reserved in the version of the protocol supported by
that implementation. Receivers MUST ignore all bits not defined
1 - Local Bridging: When Local Bridging is used, the WTP does for the version of the protocol they support.
not tunnel user traffic to the AC; all user traffic is locally
bridged. This value MUST NOT be used when the WTP MAC Type is
set to Split-MAC.
2 - 802.3 Frame Tunnel Mode: The 802.3 Frame Tunnel Mode
requires the WTP and AC to encapsulate all user payload as
native IEEE 802.3 frames (see Section 4.4). All user traffic
is tunneled to the AC. This value MUST NOT be used when the
WTP MAC Type is set to Split-MAC.
4 - Native Frame Tunnel Mode: Native Frame Tunnel mode requires
the WTP and AC to encapsulate all user payloads as native
wireless frames, as defined by the wireless binding (see for
example Section 4.4).
7 - All: The WTP is capable of supporting all frame tunnel
modes.
4.6.44. WTP IPv4 IP Address
The WTP IPv4 address is used to perform NAT detection.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| WTP IPv4 IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 44 for WTP IPv4 IP Address
Length: 4
WTP IPv4 IP Address: The IPv4 address from which the WTP is sending
packets. This field is used for NAT detection.
4.6.45. WTP IPv6 IP Address
The WTP IPv6 address is used to perform NAT detection (e.g., IPv4 to
IPv6 NAT to help with technology transition).
0 1 2 3 N: Native Frame Tunnel mode requires the WTP and AC to encapsulate
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 all user payloads as native wireless frames, as defined by the
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ wireless binding (see for example Section 4.4)
| WTP IPv6 IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| WTP IPv6 IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| WTP IPv6 IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| WTP IPv6 IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 45 for WTP IPv6 IP Address E: The 802.3 Frame Tunnel Mode requires the WTP and AC to
encapsulate all user payload as native IEEE 802.3 frames (see
Section 4.4). All user traffic is tunneled to the AC. This value
MUST NOT be used when the WTP MAC Type is set to Split-MAC.
Length: 32 L: When Local Bridging is used, the WTP does not tunnel user
traffic to the AC; all user traffic is locally bridged. This
value MUST NOT be used when the WTP MAC Type is set to Split-MAC.
WTP IPv6 IP Address: The IPv6 address from which the WTP is sending U: This bit is set to zero and is unused.
packets. This field is used for NAT detection.
4.6.46. WTP MAC Type 4.6.43. WTP MAC Type
The WTP MAC-Type message element allows the WTP to communicate its The WTP MAC-Type message element allows the WTP to communicate its
mode of operation to the AC. A WTP that advertises support for both mode of operation to the AC. A WTP that advertises support for both
modes allows the AC to select the mode to use, based on local policy. modes allows the AC to select the mode to use, based on local policy.
0 0
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| MAC Type | | MAC Type |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Type: 46 for WTP MAC Type Type: 44 for WTP MAC Type
Length: 1 Length: 1
MAC Type: The MAC mode of operation supported by the WTP. The MAC Type: The MAC mode of operation supported by the WTP. The
following enumerated values are supported: following enumerated values are supported:
0 - Local-MAC: Local-MAC is the default mode that MUST be 0 - Local-MAC: Local-MAC is the default mode that MUST be
supported by all WTPs. supported by all WTPs. When tunneling is enabled (see
Section 4.6.42), the encapsulated frames MUST be in the 802.3
format (see Section 4.4.2), unless a wireless management or
control frame which MAY be in its native format. Any CAPWAP
binding needs to specify the format of management and control
wireless frames.
1 - Split-MAC: Split-MAC support is optional, and allows the AC 1 - Split-MAC: Split-MAC support is optional, and allows the AC
to receive and process native wireless frames. to receive and process native wireless frames.
2 - Both: WTP is capable of supporting both Local-MAC and Split- 2 - Both: WTP is capable of supporting both Local-MAC and Split-
MAC. MAC.
4.6.47. WTP Name 4.6.44. WTP Name
The WTP Name message element is a variable length byte UTF-8 encoded The WTP Name message element is a variable length byte UTF-8 encoded
string. The string is not zero terminated. string [RFC3629]. The string is not zero terminated.
0 0
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-
| WTP Name ... | WTP Name ...
+-+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-
Type: 47 for WTP Name Type: 45 for WTP Name
Length: >= 1 Length: >= 1
WTP Name: A non-zero terminated UTF-8 encoded string containing the WTP Name: A non-zero terminated UTF-8 encoded string [RFC3629]
WTP name, whose maximum size MUST NOT exceed 512 bytes. containing the WTP name, whose maximum size MUST NOT exceed 512
bytes.
4.6.48. WTP Radio Statistics 4.6.45. WTP Radio Statistics
The WTP Radio Statistics message element is sent by the WTP to the AC The WTP Radio Statistics message element is sent by the WTP to the AC
to communicate statistics on radio behavior and reasons why the WTP to communicate statistics on radio behavior and reasons why the WTP
radio has been reset. These counters are never reset on the WTP, and radio has been reset. These counters are never reset on the WTP, and
will therefore roll over to zero when the maximum size has been will therefore roll over to zero when the maximum size has been
reached. reached.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 92, line 19 skipping to change at page 94, line 19
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SW Failure Count | HW Failure Count | | SW Failure Count | HW Failure Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Other Failure Count | Unknown Failure Count | | Other Failure Count | Unknown Failure Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Config Update Count | Channel Change Count | | Config Update Count | Channel Change Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Band Change Count | Current Noise Floor | | Band Change Count | Current Noise Floor |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 49 for WTP Radio Statistics Type: 47 for WTP Radio Statistics
Length: 20 Length: 20
Radio ID: The radio ID of the radio to which the statistics apply. Radio ID: The radio ID of the radio to which the statistics apply.
Last Failure Type: The last WTP failure. The following enumerated Last Failure Type: The last WTP failure. The following enumerated
values are supported: values are supported:
0 - Statistic Not Supported 0 - Statistic Not Supported
skipping to change at page 93, line 20 skipping to change at page 95, line 20
Channel Change Count: The number of times that the radio channel Channel Change Count: The number of times that the radio channel
has been changed. has been changed.
Band Change Count: The number of times that the radio has changed Band Change Count: The number of times that the radio has changed
frequency bands. frequency bands.
Current Noise Floor: A signed integer which indicates the noise Current Noise Floor: A signed integer which indicates the noise
floor of the radio receiver in units of dBm. floor of the radio receiver in units of dBm.
4.6.49. WTP Reboot Statistics 4.6.46. WTP Reboot Statistics
The WTP Reboot Statistics message element is sent by the WTP to the The WTP Reboot Statistics message element is sent by the WTP to the
AC to communicate reasons why WTP reboots have occurred. These AC to communicate reasons why WTP reboots have occurred. These
counters are never reset on the WTP, and will therefore roll over to counters are never reset on the WTP, and will therefore roll over to
zero when the maximum size has been reached. zero when the maximum size has been reached.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reboot Count | AC Initiated Count | | Reboot Count | AC Initiated Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Failure Count | SW Failure Count | | Link Failure Count | SW Failure Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| HW Failure Count | Other Failure Count | | HW Failure Count | Other Failure Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unknown Failure Count |Last Failure Type| | Unknown Failure Count |Last Failure Type|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 50 for WTP Reboot Statistics Type: 48 for WTP Reboot Statistics
Length: 15 Length: 15
Reboot Count: The number of reboots that have occurred due to a WTP Reboot Count: The number of reboots that have occurred due to a WTP
crash. A value of 65535 implies that this information is not crash. A value of 65535 implies that this information is not
available on the WTP. available on the WTP.
AC Initiated Count: The number of reboots that have occurred at the AC Initiated Count: The number of reboots that have occurred at the
request of a CAPWAP protocol message, such as a change in request of a CAPWAP protocol message, such as a change in
configuration that required a reboot or an explicit CAPWAP configuration that required a reboot or an explicit CAPWAP
skipping to change at page 94, line 38 skipping to change at page 96, line 38
2 - Link Failure 2 - Link Failure
3 - Software Failure 3 - Software Failure
4 - Hardware Failure 4 - Hardware Failure
5 - Other Failure 5 - Other Failure
255 - Unknown (e.g., WTP doesn't keep track of info) 255 - Unknown (e.g., WTP doesn't keep track of info)
4.6.50. WTP Static IP Address Information 4.6.47. WTP Static IP Address Information
The WTP Static IP Address Information message element is used by an The WTP Static IP Address Information message element is used by an
AC to configure or clear a previously configured static IP address on AC to configure or clear a previously configured static IP address on
a WTP. a WTP. IPv6 WTPs are expected to use dynamic addresses.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP Address | | IP Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Netmask | | Netmask |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Gateway | | Gateway |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Static | | Static |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Type: 51 for WTP Static IP Address Information Type: 49 for WTP Static IP Address Information
Length: 13 Length: 13
IP Address: The IP Address to assign to the WTP. This field is IP Address: The IP Address to assign to the WTP. This field is
only valid if the static field is set to one. only valid if the static field is set to one.
Netmask: The IP Netmask. This field is only valid if the static Netmask: The IP Netmask. This field is only valid if the static
field is set to one. field is set to one.
Gateway: The IP address of the gateway. This field is only valid Gateway: The IP address of the gateway. This field is only valid
if the static field is set to one. if the static field is set to one.
Netmask: The IP Netmask. This field is only valid if the static
field is set to one.
Static: An 8-bit boolean stating whether the WTP should use a Static: An 8-bit boolean stating whether the WTP should use a
static IP address or not. A value of zero disables the static IP static IP address or not. A value of zero disables the static IP
address, while a value of one enables it. address, while a value of one enables it.
4.7. CAPWAP Protocol Timers 4.7. CAPWAP Protocol Timers
This section contains the definition of the CAPWAP timers. This section contains the definition of the CAPWAP timers.
4.7.1. ChangeStatePendingTimer 4.7.1. ChangeStatePendingTimer
skipping to change at page 98, line 13 skipping to change at page 100, line 7
Default: 120 seconds Default: 120 seconds
4.7.15. WaitDTLS 4.7.15. WaitDTLS
The maximum time, in seconds, a WTP MUST wait without having received The maximum time, in seconds, a WTP MUST wait without having received
a DTLS Handshake message from an AC. This timer MUST be greater than a DTLS Handshake message from an AC. This timer MUST be greater than
30 seconds. 30 seconds.
Default: 60 Default: 60
4.7.16. WaitJoin
The maximum time, in seconds, an AC will wait after the DTLS session
has been established until it receives the Join Request from the WTP.
This timer MUST be greater than 20 seconds.
Default: 60
4.8. CAPWAP Protocol Variables 4.8. CAPWAP Protocol Variables
This section defines the CAPWAP protocol variables, which are used This section defines the CAPWAP protocol variables, which are used
for various protocol functions. Some of these variables are for various protocol functions. Some of these variables are
configurable, while others are counters or have a fixed value. For configurable, while others are counters or have a fixed value. For
non counter related variables, default values are specified. non counter related variables, default values are specified.
However, when a WTP's variable configuration is explicitly overridden However, when a WTP's variable configuration is explicitly overridden
by an AC, the WTP MUST save the new value. by an AC, the WTP MUST save the new value.
4.8.1. AdminState 4.8.1. AdminState
skipping to change at page 99, line 31 skipping to change at page 101, line 33
4.9. WTP Saved Variables 4.9. WTP Saved Variables
In addition to the values defined in Section 4.8, the following In addition to the values defined in Section 4.8, the following
values SHOULD be saved on the WTP in non-volatile memory. CAPWAP values SHOULD be saved on the WTP in non-volatile memory. CAPWAP
wireless bindings MAY define additional values that SHOULD be stored wireless bindings MAY define additional values that SHOULD be stored
on the WTP. on the WTP.
4.9.1. AdminRebootCount 4.9.1. AdminRebootCount
The number of times the WTP has rebooted administratively, defined in The number of times the WTP has rebooted administratively, defined in
Section 4.6.49. Section 4.6.46.
4.9.2. FrameEncapType 4.9.2. FrameEncapType
For WTPs that support multiple Frame Encapsulation Types, it is For WTPs that support multiple Frame Encapsulation Types, it is
useful to save the value configured by the AC. The Frame useful to save the value configured by the AC. The Frame
Encapsulation Type is defined in Section 4.6.43. Encapsulation Type is defined in Section 4.6.42.
4.9.3. LastRebootReason 4.9.3. LastRebootReason
The reason why the WTP last rebooted, defined in Section 4.6.49. The reason why the WTP last rebooted, defined in Section 4.6.46.
4.9.4. MacType 4.9.4. MacType
For WTPs that support multiple MAC Types, it is useful to save the For WTPs that support multiple MAC Types, it is useful to save the
value configured by the AC. The MACType is defined in value configured by the AC. The MACType is defined in
Section 4.6.46. Section 4.6.43.
4.9.5. PreferredACs 4.9.5. PreferredACs
The preferred ACs, with the index, defined in Section 4.6.5. The preferred ACs, with the index, defined in Section 4.6.5.
4.9.6. RebootCount 4.9.6. RebootCount
The number of times the WTP has rebooted, defined in Section 4.6.49. The number of times the WTP has rebooted, defined in Section 4.6.46.
4.9.7. Static ACL Table
The static ACL table saved on the WTP, as configured by the Add
Static MAC ACL Entry message element, see Section 4.6.9.
4.9.8. Static IP Address 4.9.7. Static IP Address
The static IP Address assigned to the WTP, as configured by the WTP The static IP Address assigned to the WTP, as configured by the WTP
Static IP Address Information message element (see Section 4.6.50). Static IP Address Information message element (see Section 4.6.47).
4.9.9. WTPLinkFailureCount 4.9.8. WTPLinkFailureCount
The number of times the link to the AC has failed, see The number of times the link to the AC has failed, see
Section 4.6.49. Section 4.6.46.
4.9.10. WTPLocation 4.9.9. WTPLocation
The WTP Location, defined in Section 4.6.31. The WTP Location, defined in Section 4.6.29.
4.9.11. WTPName 4.9.10. WTPName
The WTP Name, defined in Section 4.6.47. The WTP Name, defined in Section 4.6.44.
5. CAPWAP Discovery Operations 5. CAPWAP Discovery Operations
The Discovery messages are used by a WTP to determine which ACs are The Discovery messages are used by a WTP to determine which ACs are
available to provide service, and the capabilities and load of the available to provide service, and the capabilities and load of the
ACs. ACs.
5.1. Discovery Request Message 5.1. Discovery Request Message
The Discovery Request message is used by the WTP to automatically The Discovery Request message is used by the WTP to automatically
skipping to change at page 102, line 13 skipping to change at page 104, line 13
The binding specific WTP Radio Information message element (see The binding specific WTP Radio Information message element (see
Section 2.1) is included in the Discovery Request message to Section 2.1) is included in the Discovery Request message to
advertise WTP support for one or more CAPWAP bindings. advertise WTP support for one or more CAPWAP bindings.
The Discovery Request message is sent by the WTP when in the The Discovery Request message is sent by the WTP when in the
Discovery State. The AC does not transmit this message. Discovery State. The AC does not transmit this message.
The following message elements MUST be included in the Discovery The following message elements MUST be included in the Discovery
Request message: Request message:
o Discovery Type, see Section 4.6.23 o Discovery Type, see Section 4.6.21
o WTP Board Data, see Section 4.6.40 o WTP Board Data, see Section 4.6.39
o WTP Descriptor, see Section 4.6.41 o WTP Descriptor, see Section 4.6.40
o WTP Frame Tunnel Mode, see Section 4.6.43 o WTP Frame Tunnel Mode, see Section 4.6.42
o WTP MAC Type, see Section 4.6.46 o WTP MAC Type, see Section 4.6.43
o WTP Radio Information message element(s)that the WTP supports; o WTP Radio Information message element(s)that the WTP supports;
These are defined by the individual link layer CAPWAP Binding These are defined by the individual link layer CAPWAP Binding
Protocols (see Section 2.1). Protocols (see Section 2.1).
The following message elements MAY be included in the Discovery The following message elements MAY be included in the Discovery
Request message: Request message:
o Vendor Specific Payload, see Section 4.6.39 o MTU Discovery Padding, see Section 4.6.31
o Vendor Specific Payload, see Section 4.6.38
5.2. Discovery Response Message 5.2. Discovery Response Message
The Discovery Response message provides a mechanism for an AC to The Discovery Response message provides a mechanism for an AC to
advertise its services to requesting WTPs. advertise its services to requesting WTPs.
When a WTP receives a Discovery Response message, it MUST wait for an When a WTP receives a Discovery Response message, it MUST wait for an
interval not less than DiscoveryInterval for receipt of additional interval not less than DiscoveryInterval for receipt of additional
Discovery Response messages. After the DiscoveryInterval elapses, Discovery Response messages. After the DiscoveryInterval elapses,
the WTP enters the DTLS-Init state and selects one of the ACs that the WTP enters the DTLS-Init state and selects one of the ACs that
skipping to change at page 103, line 24 skipping to change at page 105, line 27
o AC Name, see Section 4.6.4 o AC Name, see Section 4.6.4
o WTP Radio Information message element(s)that the AC supports; o WTP Radio Information message element(s)that the AC supports;
These are defined by the individual link layer CAPWAP Binding These are defined by the individual link layer CAPWAP Binding
Protocols (see Section 2.1 for more information). Protocols (see Section 2.1 for more information).
o One of the following message elements MUST be included in the o One of the following message elements MUST be included in the
Discovery Response Message: Discovery Response Message:
* CAPWAP Control IPv4 Address, see Section 4.6.10 * CAPWAP Control IPv4 Address, see Section 4.6.9
* CAPWAP Control IPv6 Address, see Section 4.6.11 * CAPWAP Control IPv6 Address, see Section 4.6.10
The following message elements MAY be included in the Discovery The following message elements MAY be included in the Discovery
Response message: Response message:
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
5.3. Primary Discovery Request Message 5.3. Primary Discovery Request Message
The Primary Discovery Request message is sent by the WTP to determine The Primary Discovery Request message is sent by the WTP to determine
whether its preferred (or primary) AC is available. whether its preferred (or primary) AC is available or to perform a
Path MTU Discovery (see section Section 3.5.
A Primary Discovery Request message is sent by a WTP when it has a A Primary Discovery Request message is sent by a WTP when it has a
primary AC configured, and is connected to another AC. This primary AC configured, and is connected to another AC. This
generally occurs as a result of a failover, and is used by the WTP as generally occurs as a result of a failover, and is used by the WTP as
a means to discover when its primary AC becomes available. Since the a means to discover when its primary AC becomes available. Since the
WTP only has a single instance of the CAPWAP state machine, the WTP only has a single instance of the CAPWAP state machine, the
Primary Discovery Request is sent by the WTP when in the Run State. Primary Discovery Request is sent by the WTP when in the Run State.
The AC does not transmit this message. The AC does not transmit this message.
The frequency of the Primary Discovery Request messages should be no The frequency of the Primary Discovery Request messages should be no
more often than the sending of the Echo Request message. more often than the sending of the Echo Request message.
Upon receipt of a Primary Discovery Request message, the AC responds Upon receipt of a Primary Discovery Request message, the AC responds
with a Primary Discovery Response message sent to the address in the with a Primary Discovery Response message sent to the address in the
source address of the received Primary Discovery Request message. source address of the received Primary Discovery Request message.
The following message elements MUST be included in the Primary The following message elements MUST be included in the Primary
Discovery Request message. Discovery Request message.
o Discovery Type, see Section 4.6.23 o Discovery Type, see Section 4.6.21
o WTP Board Data, see Section 4.6.40 o WTP Board Data, see Section 4.6.39
o WTP Descriptor, see Section 4.6.41 o WTP Descriptor, see Section 4.6.40
o WTP Frame Tunnel Mode, see Section 4.6.43 o WTP Frame Tunnel Mode, see Section 4.6.42
o WTP MAC Type, see Section 4.6.46 o WTP MAC Type, see Section 4.6.43
o WTP Radio Information message element(s)that the WTP supports; o WTP Radio Information message element(s)that the WTP supports;
These are defined by the individual link layer CAPWAP Binding These are defined by the individual link layer CAPWAP Binding
Protocols (see Section 2.1 for more information). Protocols (see Section 2.1 for more information).
The following message elements MAY be included in the Primary The following message elements MAY be included in the Primary
Discovery Request message: Discovery Request message:
o Vendor Specific Payload, see Section 4.6.39 o MTU Discovery Padding, see Section 4.6.31
o Vendor Specific Payload, see Section 4.6.38
5.4. Primary Discovery Response 5.4. Primary Discovery Response
The Primary Discovery Response message enables an AC to advertise its The Primary Discovery Response message enables an AC to advertise its
availability and services to requesting WTPs that are configured to availability and services to requesting WTPs that are configured to
have the AC as its primary AC. have the AC as its primary AC.
The Primary Discovery Response message is sent by an AC after The Primary Discovery Response message is sent by an AC after
receiving a Primary Discovery Request message. receiving a Primary Discovery Request message.
skipping to change at page 105, line 9 skipping to change at page 107, line 16
o AC Name, see Section 4.6.4 o AC Name, see Section 4.6.4
o WTP Radio Information message element(s)that the AC supports; o WTP Radio Information message element(s)that the AC supports;
These are defined by the individual link layer CAPWAP Binding These are defined by the individual link layer CAPWAP Binding
Protocols (see Section 2.1 for more information). Protocols (see Section 2.1 for more information).
One of the following message elements MUST be included in the One of the following message elements MUST be included in the
Discovery Response Message: Discovery Response Message:
o CAPWAP Control IPv4 Address, see Section 4.6.10 o CAPWAP Control IPv4 Address, see Section 4.6.9
o CAPWAP Control IPv6 Address, see Section 4.6.11 o CAPWAP Control IPv6 Address, see Section 4.6.10
The following message elements MAY be included in the Primary The following message elements MAY be included in the Primary
Discovery Response message: Discovery Response message:
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
6. CAPWAP Join Operations 6. CAPWAP Join Operations
The Join Request message is used by a WTP to request service from an The Join Request message is used by a WTP to request service from an
AC after a DTLS connection is established to that AC. The Join AC after a DTLS connection is established to that AC. The Join
Response message is used by the AC to indicate that it will or will Response message is used by the AC to indicate that it will or will
not provide service. not provide service.
6.1. Join Request 6.1. Join Request
skipping to change at page 106, line 46 skipping to change at page 108, line 46
If an invalid (i.e. malformed) Join Request message is received, the If an invalid (i.e. malformed) Join Request message is received, the
message MUST be silently discarded by the AC. No response is sent to message MUST be silently discarded by the AC. No response is sent to
the WTP. The AC SHOULD log this event. the WTP. The AC SHOULD log this event.
The Join Request is sent by the WTP when in the Join State. The AC The Join Request is sent by the WTP when in the Join State. The AC
does not transmit this message. does not transmit this message.
The following message elements MUST be included in the Join Request The following message elements MUST be included in the Join Request
message. message.
o Location Data, see Section 4.6.31 o Location Data, see Section 4.6.29
o WTP Board Data, see Section 4.6.40 o WTP Board Data, see Section 4.6.39
o WTP Descriptor, see Section 4.6.41 o WTP Descriptor, see Section 4.6.40
o WTP Name, see Section 4.6.47 o WTP Name, see Section 4.6.44
o Session ID, see Section 4.6.37 o Session ID, see Section 4.6.36
o WTP Frame Tunnel Mode, see Section 4.6.43 o WTP Frame Tunnel Mode, see Section 4.6.42
o WTP MAC Type, see Section 4.6.46 o WTP MAC Type, see Section 4.6.43
o WTP Radio Information message element(s)that the WTP supports; o WTP Radio Information message element(s)that the WTP supports;
These are defined by the individual link layer CAPWAP Binding These are defined by the individual link layer CAPWAP Binding
Protocols (see Section 2.1 for more information). Protocols (see Section 2.1 for more information).
At least one of the following message element MUST be included in the At least one of the following message element MUST be included in the
Join Request message. Join Request message.
o WTP IPv4 IP Address, see Section 4.6.44 o CAPWAP Local IPv4 Address, see Section 4.6.11
o WTP IPv6 IP Address, see Section 4.6.45 o CAPWAP Local IPv6 Address, see Section 4.6.12
The following message element MAY be included in the Join Request The following message element MAY be included in the Join Request
message. message.
o Maximum Message Length, see Section 4.6.32 o CAPWAP Transport Protocol, see Section 4.6.14
o WTP Reboot Statistics, see Section 4.6.49
o WTP IPv4 IP Address, see Section 4.6.44 o Maximum Message Length, see Section 4.6.30
o WTP IPv6 IP Address, see Section 4.6.45 o WTP Reboot Statistics, see Section 4.6.46
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
6.2. Join Response 6.2. Join Response
The Join Response message is sent by the AC to indicate to a WTP that The Join Response message is sent by the AC to indicate to a WTP that
it is capable and willing to provide service to the WTP. it is capable and willing to provide service to the WTP.
The WTP, receiving a Join Response message, checks for success or The WTP, receiving a Join Response message, checks for success or
failure. If the message indicates success, the WTP clears the failure. If the message indicates success, the WTP clears the
WaitDTLS timer for the session and proceeds to the Configure state. WaitDTLS timer for the session and proceeds to the Configure state.
skipping to change at page 108, line 23 skipping to change at page 110, line 21
software version it expects the WTP to run. This information is used software version it expects the WTP to run. This information is used
to determine whether the WTP MUST either change its currently running to determine whether the WTP MUST either change its currently running
firmware image, or download a new version (see Section 9.1.1). firmware image, or download a new version (see Section 9.1.1).
The Join Response message is sent by the AC when in the Join State. The Join Response message is sent by the AC when in the Join State.
The WTP does not transmit this message. The WTP does not transmit this message.
The following message elements MUST be included in the Join Response The following message elements MUST be included in the Join Response
message. message.
o Result Code, see Section 4.6.35 o Result Code, see Section 4.6.34
o AC Descriptor, see Section 4.6.1 o AC Descriptor, see Section 4.6.1
o AC Name, see Section 4.6.4 o AC Name, see Section 4.6.4
o WTP Radio Information message element(s)that the AC supports; o WTP Radio Information message element(s)that the AC supports;
These are defined by the individual link layer CAPWAP Binding These are defined by the individual link layer CAPWAP Binding
Protocols (see Section 2.1). Protocols (see Section 2.1).
One of the following message elements MUST be included in the Join One of the following message elements MUST be included in the Join
Response Message: Response Message:
o CAPWAP Control IPv4 Address, see Section 4.6.10 o CAPWAP Control IPv4 Address, see Section 4.6.9
o CAPWAP Control IPv6 Address, see Section 4.6.11 o CAPWAP Control IPv6 Address, see Section 4.6.10
One of the following message elements MUST be included in the Join
Response Message:
o CAPWAP Local IPv4 Address, see Section 4.6.11
o CAPWAP Local IPv6 Address, see Section 4.6.12
The following message elements MAY be included in the Join Response The following message elements MAY be included in the Join Response
message. message.
o AC IPv4 List, see Section 4.6.2 o AC IPv4 List, see Section 4.6.2
o AC IPv6 List, see Section 4.6.3 o AC IPv6 List, see Section 4.6.3
o CAPWAP Transport Protocol, see Section 4.6.14
o Image Identifier, see Section 4.6.28 o Image Identifier, see Section 4.6.26
o Maximum Message Length, see Section 4.6.32 o Maximum Message Length, see Section 4.6.30
o Vendor Specific Payload, see Section 4.6.39
o Vendor Specific Payload, see Section 4.6.38
7. Control Channel Management 7. Control Channel Management
The Control Channel Management messages are used by the WTP and AC to The Control Channel Management messages are used by the WTP and AC to
maintain a control communication channel. CAPWAP control messages, maintain a control communication channel. CAPWAP control messages,
such as the WTP Event Request message sent from the WTP to the AC such as the WTP Event Request message sent from the WTP to the AC
indicate to the AC that the WTP is operational. When such control indicate to the AC that the WTP is operational. When such control
messages are not being sent, the Echo Request and Echo Response messages are not being sent, the Echo Request and Echo Response
messages are used to maintain the control communication channel. messages are used to maintain the control communication channel.
skipping to change at page 110, line 30 skipping to change at page 112, line 30
(see Section 2.3) to determine the state of the control connection (see Section 2.3) to determine the state of the control connection
between the WTP and the AC. The Echo Request message is sent by the between the WTP and the AC. The Echo Request message is sent by the
WTP when the EchoInterval timer expires. WTP when the EchoInterval timer expires.
The Echo Request message is sent by the WTP when in the Run State. The Echo Request message is sent by the WTP when in the Run State.
The AC does not transmit this message. The AC does not transmit this message.
The following message elements MAY be included in the Echo Request The following message elements MAY be included in the Echo Request
message: message:
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
When an AC receives an Echo Request message it responds with an Echo When an AC receives an Echo Request message it responds with an Echo
Response message. Response message.
7.2. Echo Response 7.2. Echo Response
The Echo Response message acknowledges the Echo Request message. The Echo Response message acknowledges the Echo Request message.
An Echo Response message is sent by an AC after receiving an Echo An Echo Response message is sent by an AC after receiving an Echo
Request message. After transmitting the Echo Response message, the Request message. After transmitting the Echo Response message, the
skipping to change at page 111, line 5 skipping to change at page 113, line 5
another Echo Request message or other control message is not received another Echo Request message or other control message is not received
by the AC when the timer expires, the AC SHOULD consider the WTP to by the AC when the timer expires, the AC SHOULD consider the WTP to
be no longer reachable. be no longer reachable.
The Echo Response message is sent by the AC when in the Run State. The Echo Response message is sent by the AC when in the Run State.
The WTP does not transmit this message. The WTP does not transmit this message.
The following message elements MAY be included in the Echo Response The following message elements MAY be included in the Echo Response
message: message:
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
When a WTP receives an Echo Response message it initializes the When a WTP receives an Echo Response message it initializes the
EchoInterval to the configured value. EchoInterval to the configured value.
8. WTP Configuration Management 8. WTP Configuration Management
WTP Configuration messages are used to exchange configuration WTP Configuration messages are used to exchange configuration
information between the AC and the WTP. information between the AC and the WTP.
8.1. Configuration Consistency 8.1. Configuration Consistency
skipping to change at page 112, line 27 skipping to change at page 114, line 27
provided by the AC. provided by the AC.
2. The WTP saves the configuration of parameters provided by the AC 2. The WTP saves the configuration of parameters provided by the AC
that are non-default values into local non-volatile memory, and that are non-default values into local non-volatile memory, and
are enforced during the WTP's power up initialization phase. are enforced during the WTP's power up initialization phase.
If the WTP opts to save configuration locally, the CAPWAP protocol If the WTP opts to save configuration locally, the CAPWAP protocol
state machine defines the Configure state, which allows for state machine defines the Configure state, which allows for
configuration exchange. In the Configure state, the WTP sends its configuration exchange. In the Configure state, the WTP sends its
current configuration overrides to the AC via the Configuration current configuration overrides to the AC via the Configuration
Status message. A configuration override is a non-default parameter. Status Request message. A configuration override is a non-default
As an example, in the CAPWAP protocol, the default antenna parameter. As an example, in the CAPWAP protocol, the default
configuration is internal omni antenna. A WTP that either has no antenna configuration is internal omni antenna. A WTP that either
internal antennas, or has been explicitly configured by the AC to use has no internal antennas, or has been explicitly configured by the AC
external antennas, sends its antenna configuration during the to use external antennas, sends its antenna configuration during the
configure phase, allowing the AC to become aware of the WTP's current configure phase, allowing the AC to become aware of the WTP's current
configuration. configuration.
Once the WTP has provided its configuration to the AC, the AC sends Once the WTP has provided its configuration to the AC, the AC sends
its configuration to the WTP. This allows the WTP to receive its configuration to the WTP. This allows the WTP to receive
configuration and policies from the AC. configuration and policies from the AC.
The AC maintains a copy of each active WTP configuration. There is The AC maintains a copy of each active WTP configuration. There is
no need for versioning or other means to identify configuration no need for versioning or other means to identify configuration
changes. If a WTP becomes inactive, the AC MAY delete the inactive changes. If a WTP becomes inactive, the AC MAY delete the inactive
skipping to change at page 113, line 18 skipping to change at page 115, line 18
8.1.1. Configuration Flexibility 8.1.1. Configuration Flexibility
The CAPWAP protocol provides the flexibility to configure and manage The CAPWAP protocol provides the flexibility to configure and manage
WTPs of varying design and functional characteristics. When a WTP WTPs of varying design and functional characteristics. When a WTP
first discovers an AC, it provides primary functional information first discovers an AC, it provides primary functional information
relating to its type of MAC and to the nature of frames to be relating to its type of MAC and to the nature of frames to be
exchanged. The AC configures the WTP appropriately. The AC also exchanged. The AC configures the WTP appropriately. The AC also
establishes corresponding internal state for the WTP. establishes corresponding internal state for the WTP.
8.2. Configuration Status 8.2. Configuration Status Request
The Configuration Status message is sent by a WTP to deliver its The Configuration Status Request message is sent by a WTP to deliver
current configuration to the AC. its current configuration to the AC.
The Configuration Status message carries binding specific message The Configuration Status Request message carries binding specific
elements. Refer to the appropriate binding for the definition of message elements. Refer to the appropriate binding for the
this structure. definition of this structure.
When an AC receives a Configuration Status message it acts upon the When an AC receives a Configuration Status Request message it acts
content of the message and responds to the WTP with a Configuration upon the content of the message and responds to the WTP with a
Status Response message. Configuration Status Response message.
The Configuration Status message includes multiple Radio The Configuration Status Request message includes multiple Radio
Administrative State message elements, one for the WTP, and one for Administrative State message elements, one for the WTP, and one for
each radio in the WTP. each radio in the WTP.
The Configuration Status message is sent by the WTP when in the The Configuration Status Request message is sent by the WTP when in
Configure State. The AC does not transmit this message. the Configure State. The AC does not transmit this message.
The following message elements MUST be included in the Configuration The following message elements MUST be included in the Configuration
Status message. Status Request message.
o AC Name, see Section 4.6.4 o AC Name, see Section 4.6.4
o AC Name with Index, see Section 4.6.5 o Radio Administrative State, see Section 4.6.32
o Radio Administrative State, see Section 4.6.33
o Statistics Timer, see Section 4.6.38 o Statistics Timer, see Section 4.6.37
o WTP Reboot Statistics, see Section 4.6.49 o WTP Reboot Statistics, see Section 4.6.46
The following message elements MAY be included in the Configuration The following message elements MAY be included in the Configuration
Status message. Status Request message.
o WTP Static IP Address Information, see Section 4.6.50 o AC Name with Index, see Section 4.6.5
o Vendor Specific Payload, see Section 4.6.39 o CAPWAP Transport Protocol, see Section 4.6.14
o WTP Static IP Address Information, see Section 4.6.47
o Vendor Specific Payload, see Section 4.6.38
8.3. Configuration Status Response 8.3. Configuration Status Response
The Configuration Status Response message is sent by an AC and The Configuration Status Response message is sent by an AC and
provides a mechanism for the AC to override a WTP's requested provides a mechanism for the AC to override a WTP's requested
configuration. configuration.
A Configuration Status Response message is sent by an AC after A Configuration Status Response message is sent by an AC after
receiving a Configuration Request message. receiving a Configuration Status Request message.
The Configuration Status Response message carries binding specific The Configuration Status Response message carries binding specific
message elements. Refer to the appropriate binding for the message elements. Refer to the appropriate binding for the
definition of this structure. definition of this structure.
When a WTP receives a Configuration Status Response message it acts When a WTP receives a Configuration Status Response message it acts
upon the content of the message, as appropriate. If the upon the content of the message, as appropriate. If the
Configuration Status Response message includes a Radio Operational Configuration Status Response message includes a Radio Operational
State message element that causes a change in the operational state State message element that causes a change in the operational state
of one of the radios, the WTP transmits a Change State Event to the of one of the radios, the WTP transmits a Change State Event to the
AC, as an acknowledgement of the change in state. AC, as an acknowledgement of the change in state.
The Configuration Status Response message is sent by the AC when in The Configuration Status Response message is sent by the AC when in
the Configure State. The WTP does not transmit this message. the Configure State. The WTP does not transmit this message.
The following message elements MUST be included in the Configuration The following message elements MUST be included in the Configuration
Status Response message. Status Response message.
o AC IPv4 List, see Section 4.6.2 o CAPWAP Timers, see Section 4.6.13
o AC IPv6 List, see Section 4.6.3 o Decryption Error Report Period, see Section 4.6.18
o CAPWAP Timers, see Section 4.6.14 o Idle Timeout, see Section 4.6.24
o Decryption Error Report Period, see Section 4.6.19 o WTP Fallback, see Section 4.6.41
o Idle Timeout, see Section 4.6.26 One or both of the following message elements MUST be included in the
Configuration Status Response Message:
o WTP Fallback, see Section 4.6.42 o AC IPv4 List, see Section 4.6.2
o AC IPv6 List, see Section 4.6.3
The following message element MAY be included in the Configuration The following message element MAY be included in the Configuration
Status Response message. Status Response message.
o WTP Static IP Address Information, see Section 4.6.50 o WTP Static IP Address Information, see Section 4.6.47
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
8.4. Configuration Update Request 8.4. Configuration Update Request
Configuration Update Request messages are sent by the AC to provision Configuration Update Request messages are sent by the AC to provision
the WTP while in the Run state. This is used to modify the the WTP while in the Run state. This is used to modify the
configuration of the WTP while it is operational. configuration of the WTP while it is operational.
When a WTP receives a Configuration Update Request message, it When a WTP receives a Configuration Update Request message, it
responds with a Configuration Update Response message, with a Result responds with a Configuration Update Response message, with a Result
Code message element indicating the result of the configuration Code message element indicating the result of the configuration
request. request.
The AC includes the Image Identifier and Initiate Download message The AC includes the Image Identifier message element (see
elements to force the WTP to update its firmware while in the Run Section 4.6.26) to force the WTP to update its firmware while in the
state. The WTP MAY proceed to download the requested firmware if it Run state. The WTP MAY proceed to download the requested firmware if
determines the version specified in the Image Identifier message it determines the version specified in the Image Identifier message
element is not in its non-volatile storage (see Section 9.1.1). element is not in its non-volatile storage by transmitting an Image
Data Request (see Section 9.1.1) that includes the Initiate Download
message element (see Section 4.6.28).
The Configuration Update Request is sent by the AC when in the Run The Configuration Update Request is sent by the AC when in the Run
State. The WTP does not transmit this message. State. The WTP does not transmit this message.
One or more of the following message elements MAY be included in the One or more of the following message elements MAY be included in the
Configuration Update message. Configuration Update message.
o AC Name with Index, see Section 4.6.5 o AC Name with Index, see Section 4.6.5
o AC Timestamp, see Section 4.6.6 o AC Timestamp, see Section 4.6.6
o Add MAC ACL Entry, see Section 4.6.7 o Add MAC ACL Entry, see Section 4.6.7
o Add Static MAC ACL Entry, see Section 4.6.9 o CAPWAP Timers, see Section 4.6.13
o CAPWAP Timers, see Section 4.6.14
o Decryption Error Report Period, see Section 4.6.19
o Delete MAC ACL Entry, see Section 4.6.20
o Delete Static MAC ACL Entry, see Section 4.6.22 o Decryption Error Report Period, see Section 4.6.18
o Idle Timeout, see Section 4.6.26 o Delete MAC ACL Entry, see Section 4.6.19
o Location Data, see Section 4.6.31 o Idle Timeout, see Section 4.6.24
o Radio Administrative State, see Section 4.6.33 o Location Data, see Section 4.6.29
o Statistics Timer, see Section 4.6.38 o Radio Administrative State, see Section 4.6.32
o WTP Fallback, see Section 4.6.42 o Statistics Timer, see Section 4.6.37
o WTP Name, see Section 4.6.47 o WTP Fallback, see Section 4.6.41
o WTP Static IP Address Information, see Section 4.6.50 o WTP Name, see Section 4.6.44
o Image Identifier, see Section 4.6.28 o WTP Static IP Address Information, see Section 4.6.47
o Initiate Download, see Section 4.6.30 o Image Identifier, see Section 4.6.26
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
8.5. Configuration Update Response 8.5. Configuration Update Response
The Configuration Update Response message is the acknowledgement The Configuration Update Response message is the acknowledgement
message for the Configuration Update Request message. message for the Configuration Update Request message.
The Configuration Update Response message is sent by a WTP after The Configuration Update Response message is sent by a WTP after
receiving a Configuration Update Request message. receiving a Configuration Update Request message.
When an AC receives a Configuration Update Response message the When an AC receives a Configuration Update Response message the
result code indicates if the WTP successfully accepted the result code indicates if the WTP successfully accepted the
configuration. configuration.
The Configuration Update Response message is sent by the WTP when in The Configuration Update Response message is sent by the WTP when in
the Run State. The AC does not transmit this message. the Run State. The AC does not transmit this message.
The following message element MUST be present in the Configuration The following message element MUST be present in the Configuration
Update message. Update message.
Result Code, see Section 4.6.35 Result Code, see Section 4.6.34
The following message elements MAY be present in the Configuration The following message elements MAY be present in the Configuration
Update Response message. Update Response message.
o Radio Operational State, see Section 4.6.34 o Radio Operational State, see Section 4.6.33
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
8.6. Change State Event Request 8.6. Change State Event Request
The Change State Event Request message is used by the WTP for two The Change State Event Request message is used by the WTP for two
main purposes: main purposes:
o When sent by the WTP following the reception of a Configuration o When sent by the WTP following the reception of a Configuration
Status Response message from the AC, the WTP uses the Change State Status Response message from the AC, the WTP uses the Change State
Event Request message to provide an update on the WTP radio's Event Request message to provide an update on the WTP radio's
operational state and to confirm that the configuration provided operational state and to confirm that the configuration provided
skipping to change at page 117, line 28 skipping to change at page 119, line 28
service to the WTP if it receives an error, based on local policy, service to the WTP if it receives an error, based on local policy,
and to transition to the Reset state. and to transition to the Reset state.
The Change State Event Request message is sent by a WTP to The Change State Event Request message is sent by a WTP to
acknowledge or report an error condition to the AC for a requested acknowledge or report an error condition to the AC for a requested
configuration in the Configuration Status Response message. The configuration in the Configuration Status Response message. The
Change State Event Request message includes the Result Code message Change State Event Request message includes the Result Code message
element, which indicates whether the configuration was successfully element, which indicates whether the configuration was successfully
applied. If the WTP is unable to apply a specific configuration applied. If the WTP is unable to apply a specific configuration
request, it indicates the failure by including one or more Returned request, it indicates the failure by including one or more Returned
Message Element message elements (see Section 4.6.36). Message Element message elements (see Section 4.6.35).
The Change State Event Request message is sent by the WTP in the The Change State Event Request message is sent by the WTP in the
Configure or Run State. The AC does not transmit this message. Configure or Run State. The AC does not transmit this message.
The WTP MAY save its configuration to persistent storage prior to The WTP MAY save its configuration to persistent storage prior to
transmitting the response. However, this is implementation specific transmitting the response. However, this is implementation specific
and is not required. and is not required.
The following message elements MUST be present in the Change State The following message elements MUST be present in the Change State
Event Request message. Event Request message.
o Radio Operational State, see Section 4.6.34 o Radio Operational State, see Section 4.6.33
o Result Code, see Section 4.6.35 o Result Code, see Section 4.6.34
One or more of the following message elements MAY be present in the One or more of the following message elements MAY be present in the
Change State Event Request message. Change State Event Request message.
o Returned Message Element(s), see Section 4.6.36 o Returned Message Element(s), see Section 4.6.35
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
8.7. Change State Event Response 8.7. Change State Event Response
The Change State Event Response message acknowledges the Change State The Change State Event Response message acknowledges the Change State
Event Request message. Event Request message.
A Change State Event Response message is sent by an AC in response to A Change State Event Response message is sent by an AC in response to
a Change State Event Request message. a Change State Event Request message.
The Change State Event Response message is sent by the AC when in the The Change State Event Response message is sent by the AC when in the
Configure or Run state. The WTP does not transmit this message. Configure or Run state. The WTP does not transmit this message.
The following message elements MAY be included in the Change State The following message elements MAY be included in the Change State
Event Response message: Event Response message:
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
The WTP does not take any action upon receipt of the Change State The WTP does not take any action upon receipt of the Change State
Event Response message. Event Response message.
8.8. Clear Configuration Request 8.8. Clear Configuration Request
The Clear Configuration Request message is used to reset the WTP The Clear Configuration Request message is used to reset the WTP
configuration. configuration.
The Clear Configuration Request message is sent by an AC to request The Clear Configuration Request message is sent by an AC to request
that a WTP reset its configuration to the manufacturing default that a WTP reset its configuration to the manufacturing default
configuration. The Clear Config Request message is sent while in the configuration. The Clear Config Request message is sent while in the
Run state. Run state.
The Clear Configuration Request is sent by the AC when in the Run The Clear Configuration Request is sent by the AC when in the Run
State. The WTP does not transmit this message. State. The WTP does not transmit this message.
The following message elements MAY be included in the Clear The following message elements MAY be included in the Clear
Configuration Request message: Configuration Request message:
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
When a WTP receives a Clear Configuration Request message it resets When a WTP receives a Clear Configuration Request message it resets
its configuration to the manufacturing default configuration. its configuration to the manufacturing default configuration.
8.9. Clear Configuration Response 8.9. Clear Configuration Response
The Clear Configuration Response message is sent by the WTP after The Clear Configuration Response message is sent by the WTP after
receiving a Clear Configuration Request message and resetting its receiving a Clear Configuration Request message and resetting its
configuration parameters to the manufacturing default values. configuration parameters to the manufacturing default values.
The Clear Configuration Response is sent by the WTP when in the Run The Clear Configuration Response is sent by the WTP when in the Run
State. The AC does not transmit this message. State. The AC does not transmit this message.
The Clear Configuration Response message MUST include the following The Clear Configuration Response message MUST include the following
message element. message element.
o Result Code, see Section 4.6.35 o Result Code, see Section 4.6.34
The following message elements MAY be included in the Clear The following message elements MAY be included in the Clear
Configuration Request message: Configuration Request message:
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
9. Device Management Operations 9. Device Management Operations
This section defines CAPWAP operations responsible for debugging, This section defines CAPWAP operations responsible for debugging,
gathering statistics, logging, and firmware management. The gathering statistics, logging, and firmware management. The
management operations defined in this section are used by the AC to management operations defined in this section are used by the AC to
either push/pull information to/from the WTP, or request that the WTP either push/pull information to/from the WTP, or request that the WTP
reboot. This section does not deal with the management of the AC per reboot. This section does not deal with the management of the AC per
se, and assumes that the AC is operational and configured. se, and assumes that the AC is operational and configured.
skipping to change at page 121, line 13 skipping to change at page 123, line 13
downloads the image from the AC. downloads the image from the AC.
WTP AC WTP AC
Join Request Join Request
--------------------------------------------------------> -------------------------------------------------------->
Join Response (Image Identifier = x) Join Response (Image Identifier = x)
<------------------------------------------------------ <------------------------------------------------------
Image Data Request (Image Identifier = x) Image Data Request (Image Identifier = x,
Initiate Download)
--------------------------------------------------------> -------------------------------------------------------->
Image Data Response (Result Code = Success, Image Data Response (Result Code = Success,
Image Information = {size,hash}, Image Information = {size,hash})
Initiate Download)
<------------------------------------------------------ <------------------------------------------------------
Image Data Request (Image Data = Data) Image Data Request (Image Data = Data)
<------------------------------------------------------ <------------------------------------------------------
Image Data Response (Result Code = Success) Image Data Response (Result Code = Success)
--------------------------------------------------------> -------------------------------------------------------->
..... .....
skipping to change at page 123, line 13 skipping to change at page 125, line 13
with a Reset Request message. with a Reset Request message.
WTP AC WTP AC
Configuration Update Request (Image Identifier = x) Configuration Update Request (Image Identifier = x)
<------------------------------------------------------ <------------------------------------------------------
Configuration Update Response (Result Code = Success) Configuration Update Response (Result Code = Success)
--------------------------------------------------------> -------------------------------------------------------->
Image Data Request (Image Identifier = x) Image Data Request (Image Identifier = x,
Initiate Download)
--------------------------------------------------------> -------------------------------------------------------->
Image Data Response (Result Code = Success, Image Data Response (Result Code = Success,
Image Information = {size,hash}, Image Information = {size,hash})
Initiate Download)
<------------------------------------------------------ <------------------------------------------------------
Image Data Request (Image Data = Data) Image Data Request (Image Data = Data)
<------------------------------------------------------ <------------------------------------------------------
Image Data Response (Result Code = Success) Image Data Response (Result Code = Success)
--------------------------------------------------------> -------------------------------------------------------->
..... .....
skipping to change at page 124, line 7 skipping to change at page 126, line 7
Figure 8: WTP Firmware Download Case 3 Figure 8: WTP Firmware Download Case 3
Figure 9 provides another example of the firmware download while in Figure 9 provides another example of the firmware download while in
the Run state. In this example, the WTP already has the image the Run state. In this example, the WTP already has the image
specified by the AC in its non-volative storage. The WTP opts to NOT specified by the AC in its non-volative storage. The WTP opts to NOT
download the firmware. The WTP resets upon receipt of a Reset download the firmware. The WTP resets upon receipt of a Reset
Request message from the AC. Request message from the AC.
WTP AC WTP AC
Configuration Update Request (Image Identifier = x, Configuration Update Request (Image Identifier = x)
Image Information = {size,hash},
Initiate Download)
<------------------------------------------------------ <------------------------------------------------------
Configuration Update Response (Result Code = Already Have Image) Configuration Update Response (Result Code = Already Have Image)
--------------------------------------------------------> -------------------------------------------------------->
..... .....
(administratively requested reboot request) (administratively requested reboot request)
Reset Request (Image Identifier = x) Reset Request (Image Identifier = x)
<------------------------------------------------------ <------------------------------------------------------
skipping to change at page 125, line 6 skipping to change at page 126, line 50
When the WTP joins the AC, the Join Response message includes the When the WTP joins the AC, the Join Response message includes the
Image Identifier message element, which informs the WTP of the Image Identifier message element, which informs the WTP of the
firmware it is expected to run. if the WTP does not currently have firmware it is expected to run. if the WTP does not currently have
the requested firmware version, it transmits an Image Data Request the requested firmware version, it transmits an Image Data Request
message, with the appropriate Image Identifier message element. message, with the appropriate Image Identifier message element.
If the WTP already has the requested firmware in its non-volatile If the WTP already has the requested firmware in its non-volatile
flash, but is not its currently running image, it simply resets to flash, but is not its currently running image, it simply resets to
run the proper firmware. run the proper firmware.
Once the WTP is in the Run state, it is possible for the AC to Once the WTP is in the Run state, it is possible for the AC to
cause the WTP to initiate a firmware download by sending a cause the WTP to initiate a firmware download by sending an
Configuration Update Request message with the Initiate Download Configuration Update Request message with the Image Identifier
and Image Identifier message elements. The WTP then transmits the message elements. This will cause the WTP to transmit an Image
Image Data Request message, which includes the Image Identifier Data Request with the Image Identifier and the Initiate Download
message element to start the download process. Note that when the message elements. Note that when the firmware is downloaded in
firmware is downloaded in this way, the WTP does not automatically this way, the WTP does not automatically reset after the download
reset after the download is complete. The WTP will only reset is complete. The WTP will only reset when it receives a Reset
when it receives a Reset Request message from the AC. If the WTP Request message from the AC. If the WTP already had the requested
already had the requested firmware version in its non-volatile firmware version in its non-volatile storage, the WTP does not
storage, the WTP does not transmit the Image Data Request message transmit the Image Data Request message and responds with a
and responds with a Configuration Update Response message with the Configuration Update Response message with the Result Code set to
Result Code set to Image Already Present. Image Already Present.
Regardless of how the download was initiated, once the AC receives an Regardless of how the download was initiated, once the AC receives an
Image Data Request message with the Image Identifier message element, Image Data Request message with the Image Identifier message element,
it begins the transfer process by transmitting an Image Data Request it begins the transfer process by transmitting an Image Data Request
message that includes the Image Data message element. This continues message that includes the Image Data message element. This continues
until the firmware image has been transferred. until the firmware image has been transferred.
The Image Data Request message is sent by the WTP or the AC when in The Image Data Request message is sent by the WTP or the AC when in
the Image Data or Run State. the Image Data or Run State.
The following message elements MAY be included in the Image Data The following message elements MAY be included in the Image Data
Request message. Request message.
o Image Data, see Section 4.6.27 o CAPWAP Transport Protocol, see Section 4.6.14
o Image Identifier, see Section 4.6.28 o Image Data, see Section 4.6.25
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
The following message elements MAY be included in the Image Data
Request message when sent by the WTP.
o Image Identifier, see Section 4.6.26
o Initiate Download, see Section 4.6.28
9.1.2. Image Data Response 9.1.2. Image Data Response
The Image Data Response message acknowledges the Image Data Request The Image Data Response message acknowledges the Image Data Request
message. message.
An Image Data Response message is sent in response to a received An Image Data Response message is sent in response to a received
Image Data Request message. Its purpose is to acknowledge the Image Data Request message. Its purpose is to acknowledge the
receipt of the Image Data Request message. The Result Code is receipt of the Image Data Request message. The Result Code is
included to indicate whether a previously sent Image Data Request included to indicate whether a previously sent Image Data Request
message was invalid. message was invalid.
The Image Data Response message is sent by the WTP or the AC when in The Image Data Response message is sent by the WTP or the AC when in
the Image Data or Run State. the Image Data or Run State.
The following message element MUST be included in the Image Data The following message element MUST be included in the Image Data
Response message. Response message.
o Result Code, see Section 4.6.35 o Result Code, see Section 4.6.34
The following message elements MAY be included in the Image Data The following message elements MAY be included in the Image Data
Response message. Response message.
o Image Information, see Section 4.6.29 o Vendor Specific Payload, see Section 4.6.38
o Initiate Download, see Section 4.6.30 The following message elements MAY be included in the Image Data
Response message when sent by the AC.
o Vendor Specific Payload, see Section 4.6.39 o Image Information, see Section 4.6.27
Upon receiving an Image Data Response message indicating an error, Upon receiving an Image Data Response message indicating an error,
the WTP MAY retransmit a previous Image Data Request message, or the WTP MAY retransmit a previous Image Data Request message, or
abandon the firmware download to the WTP by transitioning to the abandon the firmware download to the WTP by transitioning to the
Reset state. Reset state.
9.2. Reset Request 9.2. Reset Request
The Reset Request message is used to cause a WTP to reboot. The Reset Request message is used to cause a WTP to reboot.
A Reset Request message is sent by an AC to cause a WTP to A Reset Request message is sent by an AC to cause a WTP to
reinitialize its operation. reinitialize its operation. If the AC includes the Image Identifier
message element (see Section 4.6.26), it indicates to the WTP that it
SHOULD use that version of software upon reboot.
The Reset Request is sent by the AC when in the Run State. The WTP The Reset Request is sent by the AC when in the Run State. The WTP
does not transmit this message. does not transmit this message.
The following message elements MUST be included in the Reset Request The following message elements MUST be included in the Reset Request
message. message.
o Image Identifier, see Section 4.6.28 o Image Identifier, see Section 4.6.26
The following message elements MAY be included in the Reset Request The following message elements MAY be included in the Reset Request
message: message:
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
When a WTP receives a Reset Request message, it responds with a Reset When a WTP receives a Reset Request message, it responds with a Reset
Response message indicating success and then reinitialize itself. If Response message indicating success and then reinitialize itself. If
the WTP is unable to write to its non-volatile storage, to ensure the WTP is unable to write to its non-volatile storage, to ensure
that it runs the requested software version indicated in the Image that it runs the requested software version indicated in the Image
Identifier message element, it MAY send the appropriate Result Code Identifier message element, it MAY send the appropriate Result Code
message element, but MUST reboot. If the WTP is unable to reset, message element, but MUST reboot. If the WTP is unable to reset,
including a hardware reset, it sends a Reset Response message to the including a hardware reset, it sends a Reset Response message to the
AC with a Result Code message element indicating failure. The AC no AC with a Result Code message element indicating failure. The AC no
longer provides service to the WTP. longer provides service to the WTP.
skipping to change at page 127, line 18 skipping to change at page 129, line 21
A Reset Response message is sent by the WTP after receiving a Reset A Reset Response message is sent by the WTP after receiving a Reset
Request message. Request message.
The Reset Response is sent by the WTP when in the Run State. The AC The Reset Response is sent by the WTP when in the Run State. The AC
does not transmit this message. does not transmit this message.
The following message element MAY be included in the Reset Response The following message element MAY be included in the Reset Response
message. message.
o Result Code, see Section 4.6.35 o Result Code, see Section 4.6.34
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
When an AC receives a successful Reset Response message, it is When an AC receives a successful Reset Response message, it is
notified that the WTP will reinitialize its operation. An AC that notified that the WTP will reinitialize its operation. An AC that
receives a Reset Response message indicating failure may opt to no receives a Reset Response message indicating failure may opt to no
longer provide service to the WTP. longer provide service to the WTP.
9.4. WTP Event Request 9.4. WTP Event Request
The WTP Event Request message is used by a WTP to send information to The WTP Event Request message is used by a WTP to send information to
its AC. The WTP Event Request message MAY be sent periodically, or its AC. The WTP Event Request message MAY be sent periodically, or
sent in response to an asynchronous event on the WTP. For example, a sent in response to an asynchronous event on the WTP. For example, a
WTP MAY collect statistics and use the WTP Event Request message to WTP MAY collect statistics and use the WTP Event Request message to
transmit the statistics to the AC. transmit the statistics to the AC.
When an AC receives a WTP Event Request message it will respond with When an AC receives a WTP Event Request message it will respond with
a WTP Event Response message. a WTP Event Response message.
The presence of the Delete Station message element is used by the WTP The presence of the Delete Station message element is used by the WTP
to inform the AC that it is no longer providing service to the to inform the AC that it is no longer providing service to the
station. This could be the result of an Idle Timeout (see station. This could be the result of an Idle Timeout (see
Section 4.6.26), due to resource shortages, or some other reason. Section 4.6.24), due to resource shortages, or some other reason.
The WTP Event Request message is sent by the WTP when in the Run The WTP Event Request message is sent by the WTP when in the Run
State. The AC does not transmit this message. State. The AC does not transmit this message.
The WTP Event Request message MUST contain one of the message The WTP Event Request message MUST contain one of the message
elements listed below, or a message element that is defined for a elements listed below, or a message element that is defined for a
specific wireless technology. More than one of each message element specific wireless technology. More than one of each message element
listed MAY be included in the WTP Event Request message. listed MAY be included in the WTP Event Request message.
o Decryption Error Report, see Section 4.6.18 o Decryption Error Report, see Section 4.6.17
o Duplicate IPv4 Address, see Section 4.6.24
o Duplicate IPv6 Address, see Section 4.6.25 o Duplicate IPv4 Address, see Section 4.6.22
o WTP Radio Statistics, see Section 4.6.48 o Duplicate IPv6 Address, see Section 4.6.23
o WTP Reboot Statistics, see Section 4.6.49 o WTP Radio Statistics, see Section 4.6.45
o Delete Station, see Section 4.6.21 o WTP Reboot Statistics, see Section 4.6.46
o Vendor Specific Payload, see Section 4.6.39 o Delete Station, see Section 4.6.20
o Vendor Specific Payload, see Section 4.6.38
9.5. WTP Event Response 9.5. WTP Event Response
The WTP Event Response message acknowledges receipt of the WTP Event The WTP Event Response message acknowledges receipt of the WTP Event
Request message. Request message.
A WTP Event Response message is sent by an AC after receiving a WTP A WTP Event Response message is sent by an AC after receiving a WTP
Event Request message. Event Request message.
The WTP Event Response message is sent by the AC when in the Run The WTP Event Response message is sent by the AC when in the Run
State. The WTP does not transmit this message. State. The WTP does not transmit this message.
The following message elements MAY be included in the WTP Event The following message elements MAY be included in the WTP Event
Response message: Response message:
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
9.6. Data Transfer 9.6. Data Transfer
This section describes the data transfer procedures used by the This section describes the data transfer procedures used by the
CAPWAP protocol. The data transfer mechanism is used to upload CAPWAP protocol. The data transfer mechanism is used to upload
information available at the WTP to the AC, such as crash or debug information available at the WTP to the AC, such as crash or debug
information. The data transfer messages can only be exchanged while information. The data transfer messages can only be exchanged while
in the Run state. in the Run state.
Figure 10 provides an example of an AC that requests that the WTP Figure 10 provides an example of an AC that requests that the WTP
skipping to change at page 130, line 33 skipping to change at page 132, line 33
responds to the WTP with a Data Transfer Response message. The AC responds to the WTP with a Data Transfer Response message. The AC
MAY log the information received through the Data Transfer Data MAY log the information received through the Data Transfer Data
message element. message element.
The Data Transfer Request message is sent by the WTP or AC when in The Data Transfer Request message is sent by the WTP or AC when in
the Run State. the Run State.
When sent by the AC, the Data Transfer Request message MUST contain When sent by the AC, the Data Transfer Request message MUST contain
the following message elements: the following message elements:
o Data Transfer Mode, see Section 4.6.17 o Data Transfer Mode, see Section 4.6.16
When sent by the WTP, the Data Transfer Request message MUST contain When sent by the WTP, the Data Transfer Request message MUST contain
the following message elements: the following message elements:
o Data Transfer Data, see Section 4.6.16 o Data Transfer Data, see Section 4.6.15
Regardless of whether the Data Transfer Request is sent by the AC or Regardless of whether the Data Transfer Request is sent by the AC or
WTP, the following message elements MAY be included in the Data WTP, the following message elements MAY be included in the Data
Transfer Request message: Transfer Request message:
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
9.6.2. Data Transfer Response 9.6.2. Data Transfer Response
The Data Transfer Response message acknowledges the Data Transfer The Data Transfer Response message acknowledges the Data Transfer
Request message. Request message.
A Data Transfer Response message is sent in response to a received A Data Transfer Response message is sent in response to a received
Data Transfer Request message. Its purpose is to acknowledge receipt Data Transfer Request message. Its purpose is to acknowledge receipt
of the Data Transfer Request message. When sent by the WTP, the of the Data Transfer Request message. When sent by the WTP, the
Result Code message element is used to indicate whether the data Result Code message element is used to indicate whether the data
transfer requested by the AC can be completed. When sent by the AC, transfer requested by the AC can be completed. When sent by the AC,
the Result Code message element is used to indicate receipt of the the Result Code message element is used to indicate receipt of the
data transfered in the Data Transfer Request message. data transfered in the Data Transfer Request message.
The Data Transfer Response message is sent by the WTP or AC when in The Data Transfer Response message is sent by the WTP or AC when in
the Run State. the Run State.
The following message element MUST be included in the Data Transfer The following message element MUST be included in the Data Transfer
Response message. Response message.
o Result Code, see Section 4.6.35 o Result Code, see Section 4.6.34
The following message elements MAY be included in the Data Transfer The following message elements MAY be included in the Data Transfer
Response message: Response message:
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
Upon receipt of a Data Transfer Response message, the WTP transmits Upon receipt of a Data Transfer Response message, the WTP transmits
more information, if more information is available. more information, if more information is available.
10. Station Session Management 10. Station Session Management
Messages in this section are used by the AC to create, modify or Messages in this section are used by the AC to create, modify or
delete station session state on the WTPs. delete station session state on the WTPs.
10.1. Station Configuration Request 10.1. Station Configuration Request
skipping to change at page 132, line 30 skipping to change at page 134, line 30
The Station Configuration Request message is sent by the AC when in The Station Configuration Request message is sent by the AC when in
the Run State. The WTP does not transmit this message. the Run State. The WTP does not transmit this message.
The following CAPWAP Control message elements MAY be included in the The following CAPWAP Control message elements MAY be included in the
Station Configuration Request message. More than one of each message Station Configuration Request message. More than one of each message
element listed MAY be included in the Station Configuration Request element listed MAY be included in the Station Configuration Request
message. message.
o Add Station, see Section 4.6.8 o Add Station, see Section 4.6.8
o Delete Station, see Section 4.6.21 o Delete Station, see Section 4.6.20
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
10.2. Station Configuration Response 10.2. Station Configuration Response
The Station Configuration Response message is used to acknowledge a The Station Configuration Response message is used to acknowledge a
previously received Station Configuration Request message. previously received Station Configuration Request message.
The Station Configuration Response message is sent by the WTP when in The Station Configuration Response message is sent by the WTP when in
the Run State. The AC does not transmit this message. the Run State. The AC does not transmit this message.
The following message element MUST be present in the Station The following message element MUST be present in the Station
Configuration Response message. Configuration Response message.
o Result Code, see Section 4.6.35 o Result Code, see Section 4.6.34
The following message elements MAY be included in the Station The following message elements MAY be included in the Station
Configuration Response message: Configuration Response message:
o Vendor Specific Payload, see Section 4.6.39 o Vendor Specific Payload, see Section 4.6.38
The Result Code message element indicates that the requested The Result Code message element indicates that the requested
configuration was successfully applied, or that an error related to configuration was successfully applied, or that an error related to
processing of the Station Configuration Request message occurred on processing of the Station Configuration Request message occurred on
the WTP. the WTP.
11. NAT Considerations 11. NAT Considerations
There are three specific situations in which a NAT deployment may be There are three specific situations in which a NAT deployment may be
used in conjunction with a CAPWAP-enabled deployment. The first used in conjunction with a CAPWAP-enabled deployment. The first
skipping to change at page 134, line 38 skipping to change at page 136, line 38
Address and CAPWAP Control IPv6 Address message elements. This Address and CAPWAP Control IPv6 Address message elements. This
message element is mandatory, but contains invalid information if a message element is mandatory, but contains invalid information if a
middlebox is present between the AC and WTP. The WTP MUST NOT middlebox is present between the AC and WTP. The WTP MUST NOT
utilize the information in these message elements if it detects a NAT utilize the information in these message elements if it detects a NAT
(as described in the CAPWAP Transport Protocol message element). (as described in the CAPWAP Transport Protocol message element).
Note this would disable the load balancing capabilities of the CAPWAP Note this would disable the load balancing capabilities of the CAPWAP
protocol. Alternatively, the AC could have a configured NAT'ed protocol. Alternatively, the AC could have a configured NAT'ed
address, which it would include in either of the two control address address, which it would include in either of the two control address
message elements. message elements.
In order for a CAPWAP WTP or AC to detect whether a middlebox is
present, both the Join Request (see Section 6.1) and the Join
Response (see Section 6.2) include either the CAPWAP Local IPv4
Address (see Section 4.6.11), or the CAPWAP Local IPv6 Address (see
Section 4.6.12) message element. Upon receiving one of these
messages, if the packet's source IP address differs from the address
found in either one of these message elements, it indicates that a
middlebox is present.
The CAPWAP protocol allows for all of the AC identities supporting a The CAPWAP protocol allows for all of the AC identities supporting a
group of WTPs to be communicated through the AC List message element. group of WTPs to be communicated through the AC List message element.
This feature MUST be ignored by the WTP when it detects the AC is This feature MUST be ignored by the WTP when it detects the AC is
behind a middlebox. behind a middlebox.
The CAPWAP protocol allows an AC to configure a static IP address on The CAPWAP protocol allows an AC to configure a static IP address on
a WTP using the WTP Static IP Address Information message element. a WTP using the WTP Static IP Address Information message element.
This message element SHOULD NOT be used in NAT'ed environments, This message element SHOULD NOT be used in NAT'ed environments,
unless the administrator is familiar with the internal IP addressing unless the administrator is familiar with the internal IP addressing
scheme within the WTP's private network, and does not rely on the scheme within the WTP's private network, and does not rely on the
skipping to change at page 137, line 39 skipping to change at page 139, line 39
12.1.4. Insertion of Unprotected Records 12.1.4. Insertion of Unprotected Records
An attacker could inject packets into the unprotected channel, but An attacker could inject packets into the unprotected channel, but
this may become evident if sequence number desynchronization occurs this may become evident if sequence number desynchronization occurs
as a result. Only if the attacker is a MiM can packets be inserted as a result. Only if the attacker is a MiM can packets be inserted
undetectably. This is a consequence of that channel's lack of undetectably. This is a consequence of that channel's lack of
protection, and not a new threat resulting from the CAPWAP security protection, and not a new threat resulting from the CAPWAP security
mechanism. mechanism.
12.1.5. Use of MD5
The Image Information Section 4.6.27) message element makes use of
MD5 to compute the hash field. The authenticity and integrity of the
image file is protected by DTLS, and in this context, MD5 is not used
as a cryptographically secure hash, but just as a basic checksum.
Therefore, the use of MD5 is not considered a security vulnerability,
and no mechanisms for algorithm agility are provided.
12.2. Session ID Security 12.2. Session ID Security
Since DTLS does not export a unique session identifier, there can be Since DTLS does not export a unique session identifier, there can be
no explicit protocol binding between the DTLS layer and CAPWAP layer. no explicit protocol binding between the DTLS layer and CAPWAP layer.
As a result, implementations MUST provide a mechanism for performing As a result, implementations MUST provide a mechanism for performing
this binding. For example, an AC MUST NOT associate decrypted DTLS this binding. For example, an AC MUST NOT associate decrypted DTLS
control packets with a particular WTP session based solely on the control packets with a particular WTP session based solely on the
Session ID in the packet header. Instead, identification should be Session ID in the packet header. Instead, identification should be
done based on which DTLS session decrypted the packet. Otherwise one done based on which DTLS session decrypted the packet. Otherwise one
authenticated WTP could spoof another authenticated WTP by altering authenticated WTP could spoof another authenticated WTP by altering
skipping to change at page 139, line 45 skipping to change at page 142, line 8
established. To support this mode of operation, one or more entries established. To support this mode of operation, one or more entries
of the following table may be configured on either the AC or WTP: of the following table may be configured on either the AC or WTP:
o Identity: The identity of the peering AC or WTP. This format MAY o Identity: The identity of the peering AC or WTP. This format MAY
be either in the form of an IP address or host name (the latter of be either in the form of an IP address or host name (the latter of
which needs to be resolved to an IP address using DNS). which needs to be resolved to an IP address using DNS).
o Key: The pre-shared key for use with the peer when establishing o Key: The pre-shared key for use with the peer when establishing
the DTLS session (see Section 12.6 for more information). the DTLS session (see Section 12.6 for more information).
o Key Identifier: The pre-shared key identifier, as described in RFC o PSK Identity: Identity hint associated with the provisioned key
4279 [RFC4279]. (see Section 2.4.4.4 for more information).
When using certificates, the following items need to be pre- When using certificates, the following items need to be pre-
provisioned: provisioned:
o Device Certificate: The local device's certificate (see o Device Certificate: The local device's certificate (see
Section 12.7 for more information) Section 12.7 for more information)
o Trust Anchor: Trusted root certificate chain used to validate any o Trust Anchor: Trusted root certificate chain used to validate any
certificate received from CAPWAP peers. Note that one or more certificate received from CAPWAP peers. Note that one or more
root certificate MAY be configured on a given device. root certificate MAY be configured on a given device.
skipping to change at page 145, line 7 skipping to change at page 147, line 7
cause the firmware download process to take some time, depending upon cause the firmware download process to take some time, depending upon
the RTT. This is not expected to be a problem since the CAPWAP the RTT. This is not expected to be a problem since the CAPWAP
protocol allows firmware to be downloaded while the WTP provides protocol allows firmware to be downloaded while the WTP provides
service to wireless clients/devices. service to wireless clients/devices.
It is necessary for the WTP and AC to configure their MTU based on It is necessary for the WTP and AC to configure their MTU based on
the capabilities of the path. See Section 3.5 for more information. the capabilities of the path. See Section 3.5 for more information.
15. IANA Considerations 15. IANA Considerations
IANA needs to assign an organization local multicast address called This section details the actions to be taken by IANA during the
the "All ACs multicast address" from the IPv6 multicast address publication of the specification. There are numerous registries that
registry in Section 3.3 need to be created, and the contents, document action (see [RFC5226],
and registry format are all included below. Note that in cases where
bit fields are referred to, the bit numbering is left to right, where
the leftmost bit is labelled as bit zero (0).
15.1. CAPWAP Message Types For registration requests where an Expert Review is required, a
Designated Expert should be consulted, which is appointed by the
responsible IESG area director. The intention is that any allocation
will be accompanied by a published RFC, but given that other SDOs may
want to create standards built on top of CAPWAP, a document the
Designated Expert can review is also acceptable. IANA should allow
for allocation of values prior to documents being approved for
publication, so the Designated Expert can approve allocations once it
seems clear that publication will occur. The Designated expert will
post a request to the CAPWAP WG mailing list (or a successor
designated by the Area Director) for comment and review. Before a
period of 30 days has passed, the Designated Expert will either
approve or deny the registration request and publish a notice of the
decision to the CAPWAP WG mailing list or its successor, as well as
informing IANA. A denial notice must be justified by an explanation,
and in the cases where it is possible, concrete suggestions on how
the request can be modified so as to become acceptable should be
provided.
15.1. Multicast Address
This document requires a new organization local multicast address
called the "All ACs multicast address" from the IPv6 multicast
address registry [to be removed upon publication
http://www.iana.org/assignments/ipv6-multicast-addresses]. The new
multicast address is to be inserted in Section 3.3.
15.2. UDP Port
This document requires a two UDP Ports organization local multicast
address from the registered port numbers registry [to be removed upon
publication http://www.iana.org/assignments/port-numbers]. The new
UDP Ports numbers have already been assigned and can be found in
Section 3.1. The following values are being registered:
Keyword Decimal Description References
------- ------- ----------- ----------
capwap-control 5246/udp CAPWAP Control Protocol This Document
capwap-data 5247/udp CAPWAP Data Protocol This Document
15.3. CAPWAP Message Types
The Message Type field in the CAPWAP header (see Section 4.5.1.1) is The Message Type field in the CAPWAP header (see Section 4.5.1.1) is
used to identify the operation performed by the message. There are used to identify the operation performed by the message. There are
multiple namespaces, which is identified via the first three octets multiple namespaces, which is identified via the first three octets
of the field containing the IANA Enterprise Number [RFC5226]. When of the field containing the IANA Enterprise Number [RFC5226].
the Enterprise Number is set to zero, the message types are reserved
for use by the base CAPWAP specification which are controlled and
maintained by IANA and requires a Standards Action.
15.2. CAPWAP Header Flags IANA will create and maintain the CAPWAP Message Types registry for
all message types whose Enterprise Number is set to zero (0). The
namespace is 32 bits (0-4294967295), where the value of zero (0) is
reserved and must not be assigned. The values one (1) through 26 are
allocated in this specification, and can be found in Section 4.5.1.1.
Any new assignments of a CAPWAP Message Type, whose Enterprise Number
is set to zero (0) requires a Expert Review. The format of the
registry to be maintained by IANA has the following format:
The Flags field in the CAPWAP header (see Section 4.3) is used to CAPWAP Control Message Message Type Reference
identify any special treatment related to the message. There are Value
currently three unused, reserved bits. These bits are controlled and
maintained by IANA and requires a Standards Action.
15.3. CAPWAP Control Message Flags 15.4. CAPWAP Header Flags
The Flags field in the CAPWAP header (see Section 4.3) is 9 bits in
length and is used to identify any special treatment related to the
message. This specification defines bits zero (0) through five (5),
while bits six (6) through eight (8) are reserved. There are
currently three unused, reserved bits which are managed by IANA and
whose assignment requires a Expert Review. IANA will create the
CAPWAP Header Flags registry, whose format is:
Flag Field Name Bit Position Reference
15.5. CAPWAP Control Message Flags
The Flags field in the CAPWAP Control Message header (see The Flags field in the CAPWAP Control Message header (see
Section 4.5.1.4) is used to identify any special treatment related to Section 4.5.1.4) is used to identify any special treatment related to
the control message. There are currently eight unused, reserved the control message. There are currently eight (8) unused, reserved
bits. These bits are controlled and maintained by IANA and requires bits. These bits whose assignment is managed by IANA and requires a
a Standards Action. Expert Review. IANA will create the CAPWAP Control Message Flags
registry, whose format is:
15.4. CAPWAP Control Message Type Flag Field Name Bit Position Reference
The Type field in the CAPWAP Control Message header (see Section 4.6) 15.6. CAPWAP Message Element Type
is used to identify the data being transported. The 32 bit
enumerated values are currently defined in Section 4.5.1.1. These
values are controlled and maintained by IANA and requires a Standards
Action.
15.5. Wireless Binding Identifiers The Type field in the CAPWAP Message Element header (see Section 4.6)
is used to identify the data being transported. The namespace is 16
bits (0-65535), where the value of zero (0) is reserved and must not
be assigned. The values one (1) through 52 are allocated in this
specification, and can be found in Section 4.5.1.1. This namespace
is managed by IANA and assignments require a Expert Review. IANA
will create the CAPWAP Message Element Type registry, whose format
is:
CAPWAP Message Element Type Value Reference
15.7. Wireless Binding Identifiers
The Wireless Binding Identifier (WBID) field in the CAPWAP header The Wireless Binding Identifier (WBID) field in the CAPWAP header
(see Section 4.3) is used to identify the wireless technology (see Section 4.3) is used to identify the wireless technology
associated with the packet. Due to the limited address space associated with the packet. This specification allocates the values
available, a new WBID request requires Standards Action. one (1) and three (3). Due to the limited address space available, a
new WBID request requires Expert Review. IANA will create the CAPWAP
Wireless Binding Identifier registry, whose format is:
15.6. AC Security Types CAPWAP Wireless Binding Identifier Type Value Reference
15.8. AC Security Types
The Security field in the AC Descriptor message element (see The Security field in the AC Descriptor message element (see
Section 4.6.1) is used to identify the authentication type available Section 4.6.1) is 8 bits in length and used to identify the
on the AC. This document defines two bits, and the remaining bits authentication methods available on the AC. This specification
are controlled and maintained by IANA and requires a Standards defines bits five (5) and six (6), while bits zero (0) through four
Action. (4) as well as bit seven (7) are reserved and unused. These reserved
bits are managed by IANA and assignment requires a Standards Action.
IANA will create the AC Security Types registry, whose format is:
15.7. AC DTLS Policy AC Security Type Bit Position Reference
15.9. AC DTLS Policy
The DTLS Policy field in the AC Descriptor message element (see The DTLS Policy field in the AC Descriptor message element (see
Section 4.6.1) is used to identify the how, and if, the CAPWAP Data Section 4.6.1) is 8 bits in length and used to identify whether the
Channel is to be secured. This document defines two bits, and the CAPWAP Data Channel is to be secured. This specification defines
remaining bits are controlled and maintained by IANA and requires a bits five (5) and six (6), while bits zero (0) through four (4) as
Standards Action. well as bit seven (7) are reserved and unused. These reserved bits
are managed by IANA and assignment requires a Standards Action. IANA
will create the AC DTLS Policy registry, whose format is:
15.8. AC Information Type AC DTLS Policy Bit Position Reference
15.10. AC Information Type
The Information Type field in the AC Descriptor message element (see The Information Type field in the AC Descriptor message element (see
Section 4.6.1) is used to represent information about the AC. This Section 4.6.1) is used to represent information about the AC. The
document defines two values, and the remaining values are controlled namespace is 16 bits (0-65535), where the value of zero (0) is
and maintained by IANA and requires a Standards Action. reserved and must not be assigned. This field, combined with the AC
Information Vendor ID, allows vendors to use a private namespace.
This specification defines the AC Information Type namespace when the
AC Information Vendor ID is set to zero (0), for which the values
four (4) and five (5) are allocated in this specification, and can be
found in Section 4.6.1. This namespace is managed by IANA and
assignments require a Expert Review. IANA will create the AC
Information Type registry, whose format is:
15.9. CAPWAP Transport Protocol Types AC Information Type Type Value Reference
15.11. CAPWAP Transport Protocol Types
The Transport field in the CAPWAP Transport Protocol message element The Transport field in the CAPWAP Transport Protocol message element
(see Section 4.6.15) is used to identify the transport to use for the (see Section 4.6.14) is used to identify the transport to use for the
CAPWAP Data Channel. This document defines two values, and the CAPWAP Data Channel. The namespace is 8 bits (0-255), where the
remaining values are controlled and maintained by IANA and requires a value of zero (0) is reserved and must not be assigned. The values
Standards Action. one (1) and two (2) are allocated in this specification, and can be
found in Section 4.6.14. This namespace is managed by IANA and
assignments require a Expert Review. IANA will create the CAPWAP
Transport Protocol Types registry, whose format is:
15.10. Data Transfer Type CAPWAP Transport Protocol Type Type Value Reference
15.12. Data Transfer Type
The Data Type field in the Data Transfer Data message element (see The Data Type field in the Data Transfer Data message element (see
Section 4.6.16) and Image Data message element (see Section 4.6.27) Section 4.6.15) and Image Data message element (see Section 4.6.25)
is used to provide information about the data being carried. This is used to provide information about the data being carried. The
document defines three values, and the remaining values are namespace is 8 bits (0-255), where the value of zero (0) is reserved
controlled and maintained by IANA and requires a Standards Action. and must not be assigned. The values one (1), two (2) and five (5)
are allocated in this specification, and can be found in
Section 4.6.15. This namespace is managed by IANA and assignments
require a Expert Review. IANA will create the Data Transfer Type
registry, whose format is:
15.11. Data Transfer Mode Data Transfer Type Type Value Reference
15.13. Data Transfer Mode
The Data Mode field in the Data Transfer Data message element (see The Data Mode field in the Data Transfer Data message element (see
Section 4.6.16) and Data Transfer Mode message element (see Section 4.6.15) and Data Transfer Mode message element (see
Section 15.11) is used to provide information about the data being Section 15.13) is used to provide information about the data being
carried. This document defines three values, and the remaining carried. The namespace is 8 bits (0-255), where the value of zero
values are controlled and maintained by IANA and requires a Standards (0) is reserved and must not be assigned. The values one (1) and two
Action. (2) are allocated in this specification, and can be found in
Section 15.13. This namespace is managed by IANA and assignments
require a Expert Review. IANA will create the Data Transfer Mode
registry, whose format is:
15.12. Discovery Types Data Transfer Mode Type Value Reference
15.14. Discovery Types
The Discovery Type field in the Discovery Type message element (see The Discovery Type field in the Discovery Type message element (see
Section 4.6.23) is used by the WTP to indicate to the AC how it was Section 4.6.21) is used by the WTP to indicate to the AC how it was
discovered. This document defines five values, and the remaining discovered. The namespace is 8 bits (0-255). The values zero (0)
values are controlled and maintained by IANA and requires a Standards through four (4) are allocated in this specification, and can be
Action. found in Section 4.6.21. This namespace is managed by IANA and
assignments require a Expert Review. IANA will create the Discovery
Types registry, whose format is:
15.13. Radio Admin State Discovery Types Type Value Reference
15.15. Radio Admin State
The Radio Admin field in the Radio Administrative State message The Radio Admin field in the Radio Administrative State message
element (see Section 4.6.33) is used by the WTP to represent the element (see Section 4.6.32) is used by the WTP to represent the
state of its radios. This document defines two bits, and the state of its radios. The namespace is 8 bits (0-255), where the
remaining bits are controlled and maintained by IANA and requires a value of zero (0) is reserved and must not be assigned. The values
Standards Action. one (1) and two (2) are allocated in this specification, and can be
found in Section 4.6.32. This namespace is managed by IANA and
assignments require a Expert Review. IANA will create the Radio
Admin State registry, whose format is:
15.14. Radio Operational State Radio Admin State Type Value Reference
15.16. Radio Operational State
The State field in the Radio Operational State message element (see The State field in the Radio Operational State message element (see
Section 4.6.34) is used by the WTP to represent the operational state Section 4.6.33) is used by the WTP to represent the operational state
of its radios. This document defines two bits, and the remaining of its radios. The namespace is 8 bits (0-255), where the value of
bits are controlled and maintained by IANA and requires a Standards zero (0) is reserved and must not be assigned. The values one (1)
Action. and two (2) are allocated in this specification, and can be found in
Section 4.6.33. This namespace is managed by IANA and assignments
require a Expert Review. IANA will create the Radio Operational
State registry, whose format is:
15.15. Radio Failure Causes Radio Operational State Type Value Reference
15.17. Radio Failure Causes
The Cause field in the Radio Operational State message element (see The Cause field in the Radio Operational State message element (see
Section 4.6.34) is used by the WTP to represent the reason why a Section 4.6.33) is used by the WTP to represent the reason why a
radio may have failed. This document defines four values, and the radio may have failed. The namespace is 8 bits (0-255), where the
remaining values are controlled and maintained by IANA and requires a value of zero (0) through three (3) are allocated in this
Standards Action. specification, and can be found in Section 4.6.33. This namespace is
managed by IANA and assignments require a Expert Review. IANA will
create the Radio Failure Causes registry, whose format is:
15.16. Result Code Radio Failure Causes Type Value Reference
15.18. Result Code
The Result Code field in the Result Code message element (see The Result Code field in the Result Code message element (see
Section 4.6.35) is used to indicate the success, or failure, of a Section 4.6.34) is used to indicate the success, or failure, of a
CAPWAP control message. This document defines 23 values, and the CAPWAP control message. The namespace is 32 bits (0-4294967295),
remaining values are controlled and maintained by IANA and requires a where the value of zero (0) through 22 are allocated in this
Standards Action. specification, and can be found in Section 4.6.34. This namespace is
managed by IANA and assignments require a Expert Review. IANA will
create the Result Code registry, whose format is:
15.17. Returned Message Element Reason Result Code Type Value Reference
15.19. Returned Message Element Reason
The Reason field in the Returned Message Element message element (see The Reason field in the Returned Message Element message element (see
Section 4.6.36) is used to indicate the reason why a message element Section 4.6.35) is used to indicate the reason why a message element
was not processed successfully. This document defines five values, was not processed successfully. The namespace is 8 bits (0-255),
and the remaining values are controlled and maintained by IANA and where the value of zero (0) is reserved and must not be assigned.
requires a Standards Action. The values one (1) through four (4) are allocated in this
specification, and can be found in Section 4.6.35. This namespace is
managed by IANA and assignments require a Expert Review. IANA will
create the Returned Message Element Reason registry, whose format is:
15.18. WTP Board Data Type Returned Message Element Reason Type Value Reference
15.20. WTP Board Data Type
The Board Data Type field in the WTP Board Data message element (see The Board Data Type field in the WTP Board Data message element (see
Section 4.6.40) is used to represent information about the WTP Section 4.6.39) is used to represent information about the WTP
hardware. This document defines five values, and the remaining hardware. The namespace is 16 bits (0-65535). The WTP Board Data
values are controlled and maintained by IANA and requires a Standards Type values zero (0) through four (4) are allocated in this
Action. specification, and can be found in Section 4.6.39. This namespace is
managed by IANA and assignments require a Expert Review. IANA will
create the WTP Board Data Type registry, whose format is:
15.19. WTP Descriptor Type WTP Board Data Type Type Value Reference
15.21. WTP Descriptor Type
The Descriptor Type field in the WTP Descriptor message element (see The Descriptor Type field in the WTP Descriptor message element (see
Section 4.6.41) is used to represent information about the WTP Section 4.6.40) is used to represent information about the WTP
software. This document defines four values, and the remaining software. The namespace is 16 bits (0-65535). This field, combined
values are controlled and maintained by IANA and requires a Standards with the Descriptor Vendor ID, allows vendors to use a private
Action. namespace. This specification defines the WTP Descriptor Type
namespace when the Descriptor Vendor ID is set to zero (0), for which
the values zero (0) through three (3) are allocated in this
specification, and can be found in Section 4.6.40. This namespace is
managed by IANA and assignments require a Expert Review. IANA will
create the WTP Board Data Type registry, whose format is:
15.20. WTP Fallback Mode WTP Descriptor Type Type Value Reference
15.22. WTP Fallback Mode
The Mode field in the WTP Fallback message element (see The Mode field in the WTP Fallback message element (see
Section 4.6.42) is used to indicate to the WTP the type of AC Section 4.6.41) is used to indicate to the WTP the type of AC
fallback mechanism it should employ. This document defines three fallback mechanism it should employ. The namespace is 8 bits
values, and the remaining values are controlled and maintained by (0-255), where the value of zero (0) is reserved and must not be
IANA and requires a Standards Action. assigned. The values one (1) and two (2) are allocated in this
specification, and can be found in Section 4.6.41. This namespace is
managed by IANA and assignments require a Expert Review. IANA will
create the WTP Fallback Mode registry, whose format is:
15.21. WTP Frame Tunnel Mode WTP Fallback Mode Type Value Reference
15.23. WTP Frame Tunnel Mode
The Tunnel Type field in the WTP Frame Tunnel Mode message element The Tunnel Type field in the WTP Frame Tunnel Mode message element
(see Section 4.6.43) is used to indicate the type of tunneling to use (see Section 4.6.42) is 8 bits and is used to indicate the type of
between the WTP and the AC. This document defines four values, and tunneling to use between the WTP and the AC. This specification
the remaining values are controlled and maintained by IANA and defines bits four (4) through six (6), while bits zero (0) through
requires a Standards Action. four (4) as well as bit seven (7) are reserved and unused. These
reserved bits are managed by IANA and assignment requires a Expert
Review. IANA will create the AC DTLS Policy registry, whose format
is:
15.22. WTP MAC Type WTP Frame Tunnel Mode Bit Position Reference
15.24. WTP MAC Type
The MAC Type field in the WTP MAC Type message element (see The MAC Type field in the WTP MAC Type message element (see
Section 4.6.46) is used to indicate the type of MAC to use in Section 4.6.43) is used to indicate the type of MAC to use in
tunneled frames between the WTP and the AC. This document defines tunneled frames between the WTP and the AC. The namespace is 8 bits
three values, and the remaining values are controlled and maintained (0-255), where the value of zero (0) through two (2) are allocated in
by IANA and requires a Standards Action. this specification, and can be found in Section 4.6.43. This
namespace is managed by IANA and assignments require a Expert Review.
IANA will create the WTP MAC Type registry, whose format is:
15.23. WTP Radio Stats Failure Type WTP MAC Type Type Value Reference
15.25. WTP Radio Stats Failure Type
The Last Failure Type field in the WTP Radio Statistics message The Last Failure Type field in the WTP Radio Statistics message
element (see Section 4.6.48) is used to indicate the last WTP element (see Section 4.6.45) is used to indicate the last WTP
failure. This document defines five values, and the remaining values failure. The namespace is 8 bits (0-255), where the value of zero
are controlled and maintained by IANA and requires a Standards (0) through three (3) as well as the value 255 are allocated in this
Action. specification, and can be found in Section 4.6.45. This namespace is
managed by IANA and assignments require a Expert Review. IANA will
create the WTP Radio Stats Failure Type registry, whose format is:
15.24. WTP Reboot Stats Failure Type WTP Radio Stats Failure Type Type Value Reference
15.26. WTP Reboot Stats Failure Type
The Last Failure Type field in the WTP Reboot Statistics message The Last Failure Type field in the WTP Reboot Statistics message
element (see Section 4.6.49) is used to indicate the last reboot element (see Section 4.6.46) is used to indicate the last reboot
reason. This document defines seven values, and the remaining values reason. The namespace is 8 bits (0-255), where the value of zero (0)
are controlled and maintained by IANA and requires a Standards through five (5) as well as the value 255 are allocated in this
Action. specification, and can be found in Section 4.6.46. This namespace is
managed by IANA and assignments require a Expert Review. IANA will
create the WTP Reboot Stats Failure Type registry, whose format is:
16. Acknowledgements WTP Reboot Stats Failure Type Type Value Reference
16. Acknowledgments
The following individuals are acknowledged for their contributions to The following individuals are acknowledged for their contributions to
this protocol specification: Puneet Agarwal, Abhijit Choudhury, this protocol specification: Puneet Agarwal, Abhijit Choudhury, Pasi
Saravanan Govindan, Peter Nilsson, David Perkins and Yong Zhang. Eronen, Saravanan Govindan, Peter Nilsson, David Perkins and Yong
Zhang.
Michael Vakulenko contributed text to describe how CAPWAP can be used Michael Vakulenko contributed text to describe how CAPWAP can be used
over layer 3 (IP/UDP) networks. over layer 3 (IP/UDP) networks.
17. References 17. References
17.1. Normative References 17.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321,
April 1992.
[RFC4086] Eastlake, D., Schiller, J., and S. Crocker, "Randomness [RFC4086] Eastlake, D., Schiller, J., and S. Crocker, "Randomness
Requirements for Security", BCP 106, RFC 4086, June 2005. Requirements for Security", BCP 106, RFC 4086, June 2005.
[RFC1305] Mills, D., "Network Time Protocol (Version 3) [RFC1305] Mills, D., "Network Time Protocol (Version 3)
Specification, Implementation", RFC 1305, March 1992. Specification, Implementation", RFC 1305, March 1992.
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,
Housley, R., and W. Polk, "Internet X.509 Public Key Housley, R., and W. Polk, "Internet X.509 Public Key
Infrastructure Certificate and Certificate Revocation List Infrastructure Certificate and Certificate Revocation List
(CRL) Profile", RFC 5280, May 2008. (CRL) Profile", RFC 5280, May 2008.
skipping to change at page 152, line 8 skipping to change at page 157, line 11
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998.
[RFC1191] Mogul, J. and S. Deering, "Path MTU discovery", RFC 1191, [RFC1191] Mogul, J. and S. Deering, "Path MTU discovery", RFC 1191,
November 1990. November 1990.
[RFC1981] McCann, J., Deering, S., and J. Mogul, "Path MTU Discovery [RFC1981] McCann, J., Deering, S., and J. Mogul, "Path MTU Discovery
for IP version 6", RFC 1981, August 1996. for IP version 6", RFC 1981, August 1996.
[RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for
specifying the location of services (DNS SRV)", RFC 2782,
February 2000.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003.
[I-D.ietf-capwap-protocol-binding-ieee80211] [I-D.ietf-capwap-protocol-binding-ieee80211]
Calhoun, P., "CAPWAP Protocol Binding for IEEE 802.11", Calhoun, P., "CAPWAP Protocol Binding for IEEE 802.11",
draft-ietf-capwap-protocol-binding-ieee80211-06 (work in draft-ietf-capwap-protocol-binding-ieee80211-07 (work in
progress), February 2008. progress), July 2008.
[I-D.ietf-capwap-dhc-ac-option] [I-D.ietf-capwap-dhc-ac-option]
Calhoun, P., "CAPWAP Access Controller DHCP Option", Calhoun, P., "CAPWAP Access Controller DHCP Option",
draft-ietf-capwap-dhc-ac-option-01 (work in progress), draft-ietf-capwap-dhc-ac-option-01 (work in progress),
March 2008. March 2008.
[FRAME-EXT] [FRAME-EXT]
IEEE, "IEEE Standard 802.3as-2006", 2005. IEEE, "IEEE Standard 802.3as-2006", 2005.
17.2. Informational References 17.2. Informational References
 End of changes. 377 change blocks. 
942 lines changed or deleted 1182 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/