draft-ietf-capwap-protocol-specification-14.txt   draft-ietf-capwap-protocol-specification-15.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: April 17, 2009 Research In Motion Expires: May 4, 2009 Research In Motion
D. Stanley, Editor D. Stanley, Editor
Aruba Networks Aruba Networks
October 14, 2008 October 31, 2008
CAPWAP Protocol Specification CAPWAP Protocol Specification
draft-ietf-capwap-protocol-specification-14 draft-ietf-capwap-protocol-specification-15
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 April 17, 2009. This Internet-Draft will expire on May 4, 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, meeting the objectives defined by Access Points (CAPWAP) Protocol, meeting the objectives defined by
the CAPWAP working group in RFC 4564. The CAPWAP protocol is the CAPWAP working group in RFC 4564. The CAPWAP protocol is
designed to be flexible, allowing it to be used for a variety of designed to be flexible, allowing it to be used for a variety of
wireless technologies. This document describes the base CAPWAP wireless technologies. This document describes the base CAPWAP
protocol, while separate binding extensions will enable its use with protocol, while separate binding extensions will enable its use with
additional wireless technologies. additional wireless technologies.
skipping to change at page 3, line 28 skipping to change at page 3, line 28
4.6.15. Data Transfer Data . . . . . . . . . . . . . . . . . 72 4.6.15. Data Transfer Data . . . . . . . . . . . . . . . . . 72
4.6.16. Data Transfer Mode . . . . . . . . . . . . . . . . . 73 4.6.16. Data Transfer Mode . . . . . . . . . . . . . . . . . 73
4.6.17. Decryption Error Report . . . . . . . . . . . . . . . 73 4.6.17. Decryption Error Report . . . . . . . . . . . . . . . 73
4.6.18. Decryption Error Report Period . . . . . . . . . . . 74 4.6.18. Decryption Error Report Period . . . . . . . . . . . 74
4.6.19. Delete MAC ACL Entry . . . . . . . . . . . . . . . . 75 4.6.19. Delete MAC ACL Entry . . . . . . . . . . . . . . . . 75
4.6.20. Delete Station . . . . . . . . . . . . . . . . . . . 75 4.6.20. Delete Station . . . . . . . . . . . . . . . . . . . 75
4.6.21. Discovery Type . . . . . . . . . . . . . . . . . . . 76 4.6.21. Discovery Type . . . . . . . . . . . . . . . . . . . 76
4.6.22. Duplicate IPv4 Address . . . . . . . . . . . . . . . 76 4.6.22. Duplicate IPv4 Address . . . . . . . . . . . . . . . 76
4.6.23. Duplicate IPv6 Address . . . . . . . . . . . . . . . 77 4.6.23. Duplicate IPv6 Address . . . . . . . . . . . . . . . 77
4.6.24. Idle Timeout . . . . . . . . . . . . . . . . . . . . 78 4.6.24. Idle Timeout . . . . . . . . . . . . . . . . . . . . 78
4.6.25. Image Data . . . . . . . . . . . . . . . . . . . . . 79 4.6.25. ECN Support . . . . . . . . . . . . . . . . . . . . . 79
4.6.26. Image Identifier . . . . . . . . . . . . . . . . . . 79 4.6.26. Image Data . . . . . . . . . . . . . . . . . . . . . 79
4.6.27. Image Information . . . . . . . . . . . . . . . . . . 80 4.6.27. Image Identifier . . . . . . . . . . . . . . . . . . 80
4.6.28. Initiate Download . . . . . . . . . . . . . . . . . . 81 4.6.28. Image Information . . . . . . . . . . . . . . . . . . 80
4.6.29. Location Data . . . . . . . . . . . . . . . . . . . . 81 4.6.29. Initiate Download . . . . . . . . . . . . . . . . . . 81
4.6.30. Maximum Message Length . . . . . . . . . . . . . . . 81 4.6.30. Location Data . . . . . . . . . . . . . . . . . . . . 81
4.6.31. MTU Discovery Padding . . . . . . . . . . . . . . . . 82 4.6.31. Maximum Message Length . . . . . . . . . . . . . . . 82
4.6.32. Radio Administrative State . . . . . . . . . . . . . 82 4.6.32. MTU Discovery Padding . . . . . . . . . . . . . . . . 82
4.6.33. Radio Operational State . . . . . . . . . . . . . . . 83 4.6.33. Radio Administrative State . . . . . . . . . . . . . 83
4.6.34. Result Code . . . . . . . . . . . . . . . . . . . . . 84 4.6.34. Radio Operational State . . . . . . . . . . . . . . . 84
4.6.35. Returned Message Element . . . . . . . . . . . . . . 86 4.6.35. Result Code . . . . . . . . . . . . . . . . . . . . . 85
4.6.36. Session ID . . . . . . . . . . . . . . . . . . . . . 86 4.6.36. Returned Message Element . . . . . . . . . . . . . . 86
4.6.37. Statistics Timer . . . . . . . . . . . . . . . . . . 87 4.6.37. Session ID . . . . . . . . . . . . . . . . . . . . . 87
4.6.38. Vendor Specific Payload . . . . . . . . . . . . . . . 87 4.6.38. Statistics Timer . . . . . . . . . . . . . . . . . . 87
4.6.39. WTP Board Data . . . . . . . . . . . . . . . . . . . 88 4.6.39. Vendor Specific Payload . . . . . . . . . . . . . . . 88
4.6.40. WTP Descriptor . . . . . . . . . . . . . . . . . . . 89 4.6.40. WTP Board Data . . . . . . . . . . . . . . . . . . . 89
4.6.41. WTP Fallback . . . . . . . . . . . . . . . . . . . . 92 4.6.41. WTP Descriptor . . . . . . . . . . . . . . . . . . . 90
4.6.42. WTP Frame Tunnel Mode . . . . . . . . . . . . . . . . 92 4.6.42. WTP Fallback . . . . . . . . . . . . . . . . . . . . 92
4.6.43. WTP MAC Type . . . . . . . . . . . . . . . . . . . . 93 4.6.43. WTP Frame Tunnel Mode . . . . . . . . . . . . . . . . 93
4.6.44. WTP Name . . . . . . . . . . . . . . . . . . . . . . 94 4.6.44. WTP MAC Type . . . . . . . . . . . . . . . . . . . . 94
4.6.45. WTP Radio Statistics . . . . . . . . . . . . . . . . 94 4.6.45. WTP Name . . . . . . . . . . . . . . . . . . . . . . 95
4.6.46. WTP Reboot Statistics . . . . . . . . . . . . . . . . 96 4.6.46. WTP Radio Statistics . . . . . . . . . . . . . . . . 95
4.6.47. WTP Static IP Address Information . . . . . . . . . . 97 4.6.47. WTP Reboot Statistics . . . . . . . . . . . . . . . . 97
4.7. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . 98 4.6.48. WTP Static IP Address Information . . . . . . . . . . 98
4.7.1. ChangeStatePendingTimer . . . . . . . . . . . . . . . 98 4.7. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . 99
4.7.2. DataChannelKeepAlive . . . . . . . . . . . . . . . . 98 4.7.1. ChangeStatePendingTimer . . . . . . . . . . . . . . . 99
4.7.2. DataChannelKeepAlive . . . . . . . . . . . . . . . . 99
4.7.3. DataChannelDeadInterval . . . . . . . . . . . . . . . 99 4.7.3. DataChannelDeadInterval . . . . . . . . . . . . . . . 99
4.7.4. DataCheckTimer . . . . . . . . . . . . . . . . . . . 99 4.7.4. DataCheckTimer . . . . . . . . . . . . . . . . . . . 99
4.7.5. DiscoveryInterval . . . . . . . . . . . . . . . . . . 99 4.7.5. DiscoveryInterval . . . . . . . . . . . . . . . . . . 100
4.7.6. DTLSSessionDelete . . . . . . . . . . . . . . . . . . 99 4.7.6. DTLSSessionDelete . . . . . . . . . . . . . . . . . . 100
4.7.7. EchoInterval . . . . . . . . . . . . . . . . . . . . 99 4.7.7. EchoInterval . . . . . . . . . . . . . . . . . . . . 100
4.7.8. IdleTimeout . . . . . . . . . . . . . . . . . . . . . 99 4.7.8. IdleTimeout . . . . . . . . . . . . . . . . . . . . . 100
4.7.9. ImageDataStartTimer . . . . . . . . . . . . . . . . . 99 4.7.9. ImageDataStartTimer . . . . . . . . . . . . . . . . . 100
4.7.10. MaxDiscoveryInterval . . . . . . . . . . . . . . . . 100 4.7.10. MaxDiscoveryInterval . . . . . . . . . . . . . . . . 100
4.7.11. ReportInterval . . . . . . . . . . . . . . . . . . . 100 4.7.11. ReportInterval . . . . . . . . . . . . . . . . . . . 100
4.7.12. RetransmitInterval . . . . . . . . . . . . . . . . . 100 4.7.12. RetransmitInterval . . . . . . . . . . . . . . . . . 101
4.7.13. SilentInterval . . . . . . . . . . . . . . . . . . . 100 4.7.13. SilentInterval . . . . . . . . . . . . . . . . . . . 101
4.7.14. StatisticsTimer . . . . . . . . . . . . . . . . . . . 100 4.7.14. StatisticsTimer . . . . . . . . . . . . . . . . . . . 101
4.7.15. WaitDTLS . . . . . . . . . . . . . . . . . . . . . . 100 4.7.15. WaitDTLS . . . . . . . . . . . . . . . . . . . . . . 101
4.7.16. WaitJoin . . . . . . . . . . . . . . . . . . . . . . 101 4.7.16. WaitJoin . . . . . . . . . . . . . . . . . . . . . . 101
4.8. CAPWAP Protocol Variables . . . . . . . . . . . . . . . 101 4.8. CAPWAP Protocol Variables . . . . . . . . . . . . . . . 101
4.8.1. AdminState . . . . . . . . . . . . . . . . . . . . . 101 4.8.1. AdminState . . . . . . . . . . . . . . . . . . . . . 102
4.8.2. DiscoveryCount . . . . . . . . . . . . . . . . . . . 101 4.8.2. DiscoveryCount . . . . . . . . . . . . . . . . . . . 102
4.8.3. FailedDTLSAuthFailCount . . . . . . . . . . . . . . . 101 4.8.3. FailedDTLSAuthFailCount . . . . . . . . . . . . . . . 102
4.8.4. FailedDTLSSessionCount . . . . . . . . . . . . . . . 101 4.8.4. FailedDTLSSessionCount . . . . . . . . . . . . . . . 102
4.8.5. MaxDiscoveries . . . . . . . . . . . . . . . . . . . 101 4.8.5. MaxDiscoveries . . . . . . . . . . . . . . . . . . . 102
4.8.6. MaxFailedDTLSSessionRetry . . . . . . . . . . . . . . 101 4.8.6. MaxFailedDTLSSessionRetry . . . . . . . . . . . . . . 102
4.8.7. MaxRetransmit . . . . . . . . . . . . . . . . . . . . 102 4.8.7. MaxRetransmit . . . . . . . . . . . . . . . . . . . . 102
4.8.8. RetransmitCount . . . . . . . . . . . . . . . . . . . 102 4.8.8. RetransmitCount . . . . . . . . . . . . . . . . . . . 102
4.8.9. WTPFallBack . . . . . . . . . . . . . . . . . . . . . 102 4.8.9. WTPFallBack . . . . . . . . . . . . . . . . . . . . . 103
4.9. WTP Saved Variables . . . . . . . . . . . . . . . . . . 102 4.9. WTP Saved Variables . . . . . . . . . . . . . . . . . . 103
4.9.1. AdminRebootCount . . . . . . . . . . . . . . . . . . 102 4.9.1. AdminRebootCount . . . . . . . . . . . . . . . . . . 103
4.9.2. FrameEncapType . . . . . . . . . . . . . . . . . . . 102 4.9.2. FrameEncapType . . . . . . . . . . . . . . . . . . . 103
4.9.3. LastRebootReason . . . . . . . . . . . . . . . . . . 102 4.9.3. LastRebootReason . . . . . . . . . . . . . . . . . . 103
4.9.4. MacType . . . . . . . . . . . . . . . . . . . . . . . 102 4.9.4. MacType . . . . . . . . . . . . . . . . . . . . . . . 103
4.9.5. PreferredACs . . . . . . . . . . . . . . . . . . . . 103 4.9.5. PreferredACs . . . . . . . . . . . . . . . . . . . . 103
4.9.6. RebootCount . . . . . . . . . . . . . . . . . . . . . 103 4.9.6. RebootCount . . . . . . . . . . . . . . . . . . . . . 103
4.9.7. Static IP Address . . . . . . . . . . . . . . . . . . 103 4.9.7. Static IP Address . . . . . . . . . . . . . . . . . . 103
4.9.8. WTPLinkFailureCount . . . . . . . . . . . . . . . . . 103 4.9.8. WTPLinkFailureCount . . . . . . . . . . . . . . . . . 104
4.9.9. WTPLocation . . . . . . . . . . . . . . . . . . . . . 103 4.9.9. WTPLocation . . . . . . . . . . . . . . . . . . . . . 104
4.9.10. WTPName . . . . . . . . . . . . . . . . . . . . . . . 103 4.9.10. WTPName . . . . . . . . . . . . . . . . . . . . . . . 104
5. CAPWAP Discovery Operations . . . . . . . . . . . . . . . . . 104 5. CAPWAP Discovery Operations . . . . . . . . . . . . . . . . . 105
5.1. Discovery Request Message . . . . . . . . . . . . . . . 104 5.1. Discovery Request Message . . . . . . . . . . . . . . . 105
5.2. Discovery Response Message . . . . . . . . . . . . . . . 105 5.2. Discovery Response Message . . . . . . . . . . . . . . . 106
5.3. Primary Discovery Request Message . . . . . . . . . . . 106 5.3. Primary Discovery Request Message . . . . . . . . . . . 107
5.4. Primary Discovery Response . . . . . . . . . . . . . . . 107 5.4. Primary Discovery Response . . . . . . . . . . . . . . . 108
6. CAPWAP Join Operations . . . . . . . . . . . . . . . . . . . 109 6. CAPWAP Join Operations . . . . . . . . . . . . . . . . . . . 110
6.1. Join Request . . . . . . . . . . . . . . . . . . . . . . 109 6.1. Join Request . . . . . . . . . . . . . . . . . . . . . . 110
6.2. Join Response . . . . . . . . . . . . . . . . . . . . . 110 6.2. Join Response . . . . . . . . . . . . . . . . . . . . . 111
7. Control Channel Management . . . . . . . . . . . . . . . . . 113 7. Control Channel Management . . . . . . . . . . . . . . . . . 114
7.1. Echo Request . . . . . . . . . . . . . . . . . . . . . . 113 7.1. Echo Request . . . . . . . . . . . . . . . . . . . . . . 114
7.2. Echo Response . . . . . . . . . . . . . . . . . . . . . 113 7.2. Echo Response . . . . . . . . . . . . . . . . . . . . . 114
8. WTP Configuration Management . . . . . . . . . . . . . . . . 115 8. WTP Configuration Management . . . . . . . . . . . . . . . . 116
8.1. Configuration Consistency . . . . . . . . . . . . . . . 115 8.1. Configuration Consistency . . . . . . . . . . . . . . . 116
8.1.1. Configuration Flexibility . . . . . . . . . . . . . . 116 8.1.1. Configuration Flexibility . . . . . . . . . . . . . . 117
8.2. Configuration Status Request . . . . . . . . . . . . . . 116 8.2. Configuration Status Request . . . . . . . . . . . . . . 117
8.3. Configuration Status Response . . . . . . . . . . . . . 117 8.3. Configuration Status Response . . . . . . . . . . . . . 118
8.4. Configuration Update Request . . . . . . . . . . . . . . 118 8.4. Configuration Update Request . . . . . . . . . . . . . . 119
8.5. Configuration Update Response . . . . . . . . . . . . . 119 8.5. Configuration Update Response . . . . . . . . . . . . . 120
8.6. Change State Event Request . . . . . . . . . . . . . . . 119 8.6. Change State Event Request . . . . . . . . . . . . . . . 120
8.7. Change State Event Response . . . . . . . . . . . . . . 121 8.7. Change State Event Response . . . . . . . . . . . . . . 122
8.8. Clear Configuration Request . . . . . . . . . . . . . . 121 8.8. Clear Configuration Request . . . . . . . . . . . . . . 122
8.9. Clear Configuration Response . . . . . . . . . . . . . . 121 8.9. Clear Configuration Response . . . . . . . . . . . . . . 122
9. Device Management Operations . . . . . . . . . . . . . . . . 123 9. Device Management Operations . . . . . . . . . . . . . . . . 124
9.1. Firmware Management . . . . . . . . . . . . . . . . . . 123 9.1. Firmware Management . . . . . . . . . . . . . . . . . . 124
9.1.1. Image Data Request . . . . . . . . . . . . . . . . . 127 9.1.1. Image Data Request . . . . . . . . . . . . . . . . . 128
9.1.2. Image Data Response . . . . . . . . . . . . . . . . . 128 9.1.2. Image Data Response . . . . . . . . . . . . . . . . . 129
9.2. Reset Request . . . . . . . . . . . . . . . . . . . . . 129 9.2. Reset Request . . . . . . . . . . . . . . . . . . . . . 130
9.3. Reset Response . . . . . . . . . . . . . . . . . . . . . 130 9.3. Reset Response . . . . . . . . . . . . . . . . . . . . . 131
9.4. WTP Event Request . . . . . . . . . . . . . . . . . . . 130 9.4. WTP Event Request . . . . . . . . . . . . . . . . . . . 131
9.5. WTP Event Response . . . . . . . . . . . . . . . . . . . 131 9.5. WTP Event Response . . . . . . . . . . . . . . . . . . . 132
9.6. Data Transfer . . . . . . . . . . . . . . . . . . . . . 131 9.6. Data Transfer . . . . . . . . . . . . . . . . . . . . . 132
9.6.1. Data Transfer Request . . . . . . . . . . . . . . . . 132 9.6.1. Data Transfer Request . . . . . . . . . . . . . . . . 133
9.6.2. Data Transfer Response . . . . . . . . . . . . . . . 133 9.6.2. Data Transfer Response . . . . . . . . . . . . . . . 134
10. Station Session Management . . . . . . . . . . . . . . . . . 135 10. Station Session Management . . . . . . . . . . . . . . . . . 136
10.1. Station Configuration Request . . . . . . . . . . . . . 135 10.1. Station Configuration Request . . . . . . . . . . . . . 136
10.2. Station Configuration Response . . . . . . . . . . . . . 135 10.2. Station Configuration Response . . . . . . . . . . . . . 136
11. NAT Considerations . . . . . . . . . . . . . . . . . . . . . 137 11. NAT Considerations . . . . . . . . . . . . . . . . . . . . . 138
12. Security Considerations . . . . . . . . . . . . . . . . . . . 139 12. Security Considerations . . . . . . . . . . . . . . . . . . . 140
12.1. CAPWAP Security . . . . . . . . . . . . . . . . . . . . 139 12.1. CAPWAP Security . . . . . . . . . . . . . . . . . . . . 140
12.1.1. Converting Protected Data into Unprotected Data . . . 140 12.1.1. Converting Protected Data into Unprotected Data . . . 141
12.1.2. Converting Unprotected Data into Protected Data 12.1.2. Converting Unprotected Data into Protected Data
(Insertion) . . . . . . . . . . . . . . . . . . . . . 140 (Insertion) . . . . . . . . . . . . . . . . . . . . . 141
12.1.3. Deletion of Protected Records . . . . . . . . . . . . 140 12.1.3. Deletion of Protected Records . . . . . . . . . . . . 141
12.1.4. Insertion of Unprotected Records . . . . . . . . . . 140 12.1.4. Insertion of Unprotected Records . . . . . . . . . . 141
12.1.5. Use of MD5 . . . . . . . . . . . . . . . . . . . . . 140 12.1.5. Use of MD5 . . . . . . . . . . . . . . . . . . . . . 141
12.1.6. CAPWAP Fragmentation . . . . . . . . . . . . . . . . 140 12.1.6. CAPWAP Fragmentation . . . . . . . . . . . . . . . . 141
12.2. Session ID Security . . . . . . . . . . . . . . . . . . 141 12.2. Session ID Security . . . . . . . . . . . . . . . . . . 142
12.3. Discovery or DTLS Setup Attacks . . . . . . . . . . . . 141 12.3. Discovery or DTLS Setup Attacks . . . . . . . . . . . . 142
12.4. Interference with a DTLS Session . . . . . . . . . . . . 142 12.4. Interference with a DTLS Session . . . . . . . . . . . . 143
12.5. CAPWAP Pre-Provisioning . . . . . . . . . . . . . . . . 142 12.5. CAPWAP Pre-Provisioning . . . . . . . . . . . . . . . . 143
12.6. Use of Preshared Keys in CAPWAP . . . . . . . . . . . . 143 12.6. Use of Preshared Keys in CAPWAP . . . . . . . . . . . . 144
12.7. Use of Certificates in CAPWAP . . . . . . . . . . . . . 144 12.7. Use of Certificates in CAPWAP . . . . . . . . . . . . . 145
12.8. Use of MAC Address in CN Field . . . . . . . . . . . . . 145 12.8. Use of MAC Address in CN Field . . . . . . . . . . . . . 146
12.9. AAA Security . . . . . . . . . . . . . . . . . . . . . . 145 12.9. AAA Security . . . . . . . . . . . . . . . . . . . . . . 146
12.10. WTP Firmware . . . . . . . . . . . . . . . . . . . . . . 146 12.10. WTP Firmware . . . . . . . . . . . . . . . . . . . . . . 147
13. Operational Considerations . . . . . . . . . . . . . . . . . 147 13. Operational Considerations . . . . . . . . . . . . . . . . . 148
14. Transport Considerations . . . . . . . . . . . . . . . . . . 148 14. Transport Considerations . . . . . . . . . . . . . . . . . . 149
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 149 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 150
15.1. IPv4 Multicast Address . . . . . . . . . . . . . . . . . 149 15.1. IPv4 Multicast Address . . . . . . . . . . . . . . . . . 150
15.2. IPv6 Multicast Address . . . . . . . . . . . . . . . . . 149 15.2. IPv6 Multicast Address . . . . . . . . . . . . . . . . . 150
15.3. UDP Port . . . . . . . . . . . . . . . . . . . . . . . . 149 15.3. UDP Port . . . . . . . . . . . . . . . . . . . . . . . . 150
15.4. CAPWAP Message Types . . . . . . . . . . . . . . . . . . 150 15.4. CAPWAP Message Types . . . . . . . . . . . . . . . . . . 151
15.5. CAPWAP Header Flags . . . . . . . . . . . . . . . . . . 150 15.5. CAPWAP Header Flags . . . . . . . . . . . . . . . . . . 151
15.6. CAPWAP Control Message Flags . . . . . . . . . . . . . . 150 15.6. CAPWAP Control Message Flags . . . . . . . . . . . . . . 151
15.7. CAPWAP Message Element Type . . . . . . . . . . . . . . 151 15.7. CAPWAP Message Element Type . . . . . . . . . . . . . . 152
15.8. Wireless Binding Identifiers . . . . . . . . . . . . . . 151 15.8. Wireless Binding Identifiers . . . . . . . . . . . . . . 152
15.9. AC Security Types . . . . . . . . . . . . . . . . . . . 151 15.9. AC Security Types . . . . . . . . . . . . . . . . . . . 152
15.10. AC DTLS Policy . . . . . . . . . . . . . . . . . . . . . 152 15.10. AC DTLS Policy . . . . . . . . . . . . . . . . . . . . . 153
15.11. AC Information Type . . . . . . . . . . . . . . . . . . 152 15.11. AC Information Type . . . . . . . . . . . . . . . . . . 153
15.12. CAPWAP Transport Protocol Types . . . . . . . . . . . . 152 15.12. CAPWAP Transport Protocol Types . . . . . . . . . . . . 153
15.13. Data Transfer Type . . . . . . . . . . . . . . . . . . . 152 15.13. Data Transfer Type . . . . . . . . . . . . . . . . . . . 153
15.14. Data Transfer Mode . . . . . . . . . . . . . . . . . . . 153 15.14. Data Transfer Mode . . . . . . . . . . . . . . . . . . . 154
15.15. Discovery Types . . . . . . . . . . . . . . . . . . . . 153 15.15. Discovery Types . . . . . . . . . . . . . . . . . . . . 154
15.16. Radio Admin State . . . . . . . . . . . . . . . . . . . 153 15.16. ECN Support . . . . . . . . . . . . . . . . . . . . . . 154
15.17. Radio Operational State . . . . . . . . . . . . . . . . 154 15.17. Radio Admin State . . . . . . . . . . . . . . . . . . . 155
15.18. Radio Failure Causes . . . . . . . . . . . . . . . . . . 154 15.18. Radio Operational State . . . . . . . . . . . . . . . . 155
15.19. Result Code . . . . . . . . . . . . . . . . . . . . . . 154 15.19. Radio Failure Causes . . . . . . . . . . . . . . . . . . 155
15.20. Returned Message Element Reason . . . . . . . . . . . . 154 15.20. Result Code . . . . . . . . . . . . . . . . . . . . . . 155
15.21. WTP Board Data Type . . . . . . . . . . . . . . . . . . 155 15.21. Returned Message Element Reason . . . . . . . . . . . . 156
15.22. WTP Descriptor Type . . . . . . . . . . . . . . . . . . 155 15.22. WTP Board Data Type . . . . . . . . . . . . . . . . . . 156
15.23. WTP Fallback Mode . . . . . . . . . . . . . . . . . . . 155 15.23. WTP Descriptor Type . . . . . . . . . . . . . . . . . . 156
15.24. WTP Frame Tunnel Mode . . . . . . . . . . . . . . . . . 155 15.24. WTP Fallback Mode . . . . . . . . . . . . . . . . . . . 156
15.25. WTP MAC Type . . . . . . . . . . . . . . . . . . . . . . 156 15.25. WTP Frame Tunnel Mode . . . . . . . . . . . . . . . . . 157
15.26. WTP Radio Stats Failure Type . . . . . . . . . . . . . . 156 15.26. WTP MAC Type . . . . . . . . . . . . . . . . . . . . . . 157
15.27. WTP Reboot Stats Failure Type . . . . . . . . . . . . . 156 15.27. WTP Radio Stats Failure Type . . . . . . . . . . . . . . 157
16. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 157 15.28. WTP Reboot Stats Failure Type . . . . . . . . . . . . . 158
17. References . . . . . . . . . . . . . . . . . . . . . . . . . 158 16. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 159
17.1. Normative References . . . . . . . . . . . . . . . . . . 158 17. References . . . . . . . . . . . . . . . . . . . . . . . . . 160
17.2. Informational References . . . . . . . . . . . . . . . . 160 17.1. Normative References . . . . . . . . . . . . . . . . . . 160
Editors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 162 17.2. Informational References . . . . . . . . . . . . . . . . 162
Intellectual Property and Copyright Statements . . . . . . . . . 163 Editors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 164
Intellectual Property and Copyright Statements . . . . . . . . . 165
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 44, line 33 skipping to change at page 44, line 33
over a Wide Area Network (WAN). Therefore, future versions of the over a Wide Area Network (WAN). Therefore, future versions of the
CAPWAP protocol SHOULD either consider increasing the size of the CAPWAP protocol SHOULD either consider increasing the size of the
Fragment ID field, or provide alternatives extensions. Fragment ID field, or provide alternatives extensions.
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. One session with, it SHOULD perform a Path MTU (PMTU) discovery. One
recommendation for performing PMTU discovery is to have the WTP recommendation for performing PMTU discovery is to have the WTP
transmit Discovery Request (see Section 5.1) messages, and include transmit Discovery Request (see Section 5.1) messages, and include
the MTU Discovery Padding message element (see Section 4.6.31). The the MTU Discovery Padding message element (see Section 4.6.32). The
actual procedures used for PMTU discovery are described in [RFC1191], actual procedures used for PMTU discovery are described in [RFC1191],
for IPv4, or for IPv6 [RFC1981] SHOULD be used. Alternatively, for IPv4, or for IPv6 [RFC1981] SHOULD be used. Alternatively,
implementers MAY use the procedures defined in [RFC4821]. The WTP implementers MAY use the procedures defined in [RFC4821]. The WTP
SHOULD also periodically re-evaluate the PMTU using the guidelines SHOULD also periodically re-evaluate the PMTU using the guidelines
provided in these two RFCs, using the Primary Discovery Request (see provided in these two RFCs, using the Primary Discovery Request (see
Section 5.3) along with the MTU Discovery Padding message element 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 (see Section 4.6.32). When the MTU is initially known, or updated in
the case where an existing session already exists, the discovered the case where an existing session already exists, the discovered
PMTU is used to configure the DTLS component (see Section 2.3.2.1), 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 while non-DTLS frames need to be fragmented to fit the MTU, defined
in Section 3.4. 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
skipping to change at page 47, 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.30 in the Join Request message or the Join Response Section 4.6.31 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 52, line 41 skipping to change at page 52, line 41
Message Element Length: The 16 bit Length field indicates the Message Element Length: The 16 bit Length field indicates the
number of bytes following the CAPWAP Header, with a maximum size number of bytes following the CAPWAP Header, with a maximum size
of 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.36 Session ID, see Section 4.6.37
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 57, line 41 skipping to change at page 57, line 41
4.5.2. Quality of Service 4.5.2. Quality of Service
The CAPWAP base protocol does not provide any Quality of Service The CAPWAP base protocol does not provide any Quality of Service
(QoS) recommendations for use with the CAPWAP data messages. Any (QoS) recommendations for use with the CAPWAP data messages. Any
wireless specific CAPWAP binding specification that has QoS wireless specific CAPWAP binding specification that has QoS
requirements MUST define the application of QoS to the CAPWAP data requirements MUST define the application of QoS to the CAPWAP data
messages. messages.
The IP header also includes the Explicit Congestion Notification The IP header also includes the Explicit Congestion Notification
(ECN) bits [RFC3168]. When packets received from stations are (ECN) bits [RFC3168]. Section 9.1.1 of [RFC3168] describes two
encapsulated by the WTP, the ECN bits are set to zero (0) in the levels of ECN functionality, full functionality and limited
outer header. The WTP does not modify the ECN bits in the original functionality. CAPWAP ACs and WTPs SHALL implement the limited
station's packet header. This mode of operation is detailed as the functionality and are RECOMMENDED to implement the full functionality
"limited functionality option" in [RFC3168]. described in [RFC3168].
4.5.2.1. Applying QoS to CAPWAP Control Message 4.5.2.1. Applying QoS to CAPWAP Control Message
It is recommended that CAPWAP control messages be sent by both the AC It is recommended that CAPWAP control messages be sent by both the AC
and the WTP with an appropriate Quality of Service precedence value, and the WTP with an appropriate Quality of Service precedence value,
ensuring that congestion in the network minimizes occurrences of ensuring that congestion in the network minimizes occurrences of
CAPWAP control channel disconnects. Therefore, a Quality of Service CAPWAP control channel disconnects. Therefore, a Quality of Service
enabled CAPWAP device SHOULD use the following values: enabled CAPWAP device SHOULD use the following values:
802.1Q: The priority tag of 7 SHOULD be used. 802.1Q: The priority tag of 7 SHOULD be used.
skipping to change at page 61, line 12 skipping to change at page 61, line 12
Data Transfer Data 13 Data Transfer Data 13
Data Transfer Mode 14 Data Transfer Mode 14
Decryption Error Report 15 Decryption Error Report 15
Decryption Error Report Period 16 Decryption Error Report Period 16
Delete MAC ACL Entry 17 Delete MAC ACL Entry 17
Delete Station 18 Delete Station 18
Reserved 19 Reserved 19
Discovery Type 20 Discovery Type 20
Duplicate IPv4 Address 21 Duplicate IPv4 Address 21
Duplicate IPv6 Address 22 Duplicate IPv6 Address 22
ECN Support 53
Idle Timeout 23 Idle Timeout 23
Image Data 24 Image Data 24
Image Identifier 25 Image Identifier 25
Image Information 26 Image Information 26
Initiate Download 27 Initiate Download 27
Location Data 28 Location Data 28
Maximum Message Length 29 Maximum Message Length 29
MTU Discovery Padding 52 MTU Discovery Padding 52
Radio Administrative State 31 Radio Administrative State 31
Radio Operational State 32 Radio Operational State 32
skipping to change at page 79, line 8 skipping to change at page 79, line 8
| Timeout | | Timeout |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 23 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.25. Image Data 4.6.25. ECN Support
The ECN Support message element is sent by both the WTP and the AC to
indicate their support for the Explicit Congestion Notification (ECN)
bits, as defined in [RFC3168].
0
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
| ECN Support |
+-+-+-+-+-+-+-+-+
Type: 53 for ECN Support
Length: 1
ECN Support: An 8-bit value representing the sender's support for
ECN, as defined in [RFC3168].
0 - Limited ECN Support
1 - Full and Limited ECN Support
4.6.26. 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 ....
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 79, line 39 skipping to change at page 80, line 18
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 Data Type field is set the block being sent is the last one, the Data Type field is set
to 2. The AC MAY opt to abort the data transfer by setting the to 2. The AC MAY opt to abort the data transfer by setting the
Data Type field to 5. When the Data Type field is 5, the Value Data Type field to 5. When the Data Type field is 5, the Value
field has a zero length. field has a zero length.
4.6.26. Image Identifier 4.6.27. Image Identifier
The Image Identifier message element is sent by the AC to the WTP to The Image Identifier message element is sent by the AC to the WTP to
indicate the expected active software version that is to be run on indicate the expected active software version that is to be run on
the WTP. The WTP sends the Image Identifier message element in order the WTP. The WTP sends the Image Identifier message element in order
to request a specific software version from the AC. The actual to request a specific software version from the AC. The actual
download process is defined in Section 9.1. The value is a variable download process is defined in Section 9.1. The value is a variable
length UTF-8 encoded string [RFC3629], which is NOT zero terminated. 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
skipping to change at page 80, line 25 skipping to change at page 80, line 47
Length: >= 5 Length: >= 5
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"
Data: A variable length UTF-8 encoded string [RFC3629] containing Data: A variable length UTF-8 encoded string [RFC3629] containing
the firmware identifier to be run on the WTP, whose length MUST the firmware identifier to be run on the WTP, whose length MUST
NOT 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.27. Image Information 4.6.28. 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 81, line 8 skipping to change at page 81, line 29
Type: 26 for Image Information Type: 26 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 MD5 hash of the image using the procedures defined Hash: A 16 octet MD5 hash of the image using the procedures defined
in [RFC1321]. in [RFC1321].
4.6.28. Initiate Download 4.6.29. Initiate Download
The Initiate Download message element is used by the WTP to inform The Initiate Download message element is used by the WTP to inform
the AC that the AC SHOULD initiate a firmware upgrade. The AC 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 Data message element. This message element does not the Image Data message element. This message element does not
contain any data. contain any data.
Type: 27 for Initiate Download Type: 27 for Initiate Download
Length: 0 Length: 0
4.6.29. Location Data 4.6.30. 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 [RFC3629] containing user defined location information encoded string [RFC3629] containing user defined location information
(e.g. "Next to Fridge"). This information is configurable by the (e.g. "Next to Fridge"). This information is configurable by the
network administrator, and allows the WTP location to be determined. network administrator, and allows the WTP location to be determined.
The 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
+-+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-
skipping to change at page 81, line 42 skipping to change at page 82, line 15
+-+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-
Type: 28 for Location Data Type: 28 for Location Data
Length: >= 1 Length: >= 1
Location: A non-zero terminated UTF-8 encoded string [RFC3629] Location: A non-zero terminated UTF-8 encoded string [RFC3629]
containing the WTP location, whose maximum size MUST NOT exceed containing the WTP location, whose maximum size MUST NOT exceed
1024. 1024.
4.6.30. Maximum Message Length 4.6.31. 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
skipping to change at page 82, line 18 skipping to change at page 82, line 37
| Maximum Message Length | | Maximum Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 29 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.31. MTU Discovery Padding 4.6.32. MTU Discovery Padding
The MTU Discovery Padding message element is used as padding to The MTU Discovery Padding message element is used as padding to
perform MTU discovery, and MUST contain octets of value 0xFF, of any perform MTU discovery, and MUST contain octets of value 0xFF, of any
length. length.
0 0
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Padding... | Padding...
+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-
skipping to change at page 82, line 29 skipping to change at page 83, line 4
The MTU Discovery Padding message element is used as padding to The MTU Discovery Padding message element is used as padding to
perform MTU discovery, and MUST contain octets of value 0xFF, of any perform MTU discovery, and MUST contain octets of value 0xFF, of any
length. length.
0 0
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Padding... | Padding...
+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-
Type: 52 for MTU Discovery Padding Type: 52 for MTU Discovery Padding
Length: variable Length: variable
Pad: A variable length pad, filled with the value 0xFF. Pad: A variable length pad, filled with the value 0xFF.
4.6.32. Radio Administrative State 4.6.33. 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.
skipping to change at page 83, line 27 skipping to change at page 84, line 5
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.33. Radio Operational State 4.6.34. 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
skipping to change at page 84, line 25 skipping to change at page 85, line 4
2 - Disabled 2 - Disabled
Cause: When a radio is inoperable, the cause field contains the Cause: When a radio is inoperable, the cause field contains the
reason the radio is out of service. The following enumerated reason the radio is out of service. The following enumerated
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.34. Result Code 4.6.35. 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 86, line 5 skipping to change at page 86, line 28
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.35. Returned Message Element 4.6.36. 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
skipping to change at page 86, line 45 skipping to change at page 87, line 22
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 255 octets. exceed 255 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.36. Session ID 4.6.37. Session ID
The Session ID message element value contains a randomly generated The Session ID message element value contains a randomly generated
unsigned 128-bit integer. unsigned 128-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 |
skipping to change at page 87, line 24 skipping to change at page 87, line 46
| Session ID | | Session ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 35 for Session ID Type: 35 for Session ID
Length: 16 Length: 16
Session ID: A 128-bit unsigned integer used as a random session Session ID: A 128-bit unsigned integer used as a random session
identifier identifier
4.6.37. Statistics Timer 4.6.38. 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: 36 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.38. Vendor Specific Payload 4.6.39. 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 exchange of vendor specific data between the MUST NOT message. The exchange of vendor specific data between the MUST NOT
modify the behavior of the base CAPWAP protocol and state machine. modify the behavior of the base CAPWAP protocol and state machine.
The message element uses the following format: 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
skipping to change at page 88, line 27 skipping to change at page 89, line 5
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.39. WTP Board Data 4.6.40. 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...
skipping to change at page 89, line 46 skipping to change at page 90, line 23
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.40. WTP Descriptor 4.6.41. 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 | Num Encrypt |Encryp Sub-Elmt| | Max Radios | Radios in use | Num Encrypt |Encryp Sub-Elmt|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 92, line 12 skipping to change at page 92, line 36
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 [RFC3629]. in the UTF-8 format [RFC3629].
4.6.41. WTP Fallback 4.6.42. 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 |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
skipping to change at page 92, line 44 skipping to change at page 93, line 22
(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.42. WTP Frame Tunnel Mode 4.6.43. 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
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Reservd|N|E|L|U| |Reservd|N|E|L|U|
skipping to change at page 93, line 40 skipping to change at page 94, line 19
L: When Local Bridging is used, the WTP does not tunnel user L: When Local Bridging is used, the WTP does not tunnel user
traffic to the AC; all user traffic is locally bridged. This 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. value MUST NOT be used when the WTP MAC Type is set to Split-MAC.
R: A reserved bit for future use. All implementations complying R: A reserved bit for future use. All implementations complying
with this protocol MUST set to zero any bits that are reserved in with this protocol MUST set to zero any bits that are reserved in
the version of the protocol supported by that implementation. the version of the protocol supported by that implementation.
Receivers MUST ignore all bits not defined for the version of the Receivers MUST ignore all bits not defined for the version of the
protocol they support. protocol they support.
4.6.43. WTP MAC Type 4.6.44. 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 |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
skipping to change at page 94, line 4 skipping to change at page 94, line 30
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: 44 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. When tunneling is enabled (see supported by all WTPs. When tunneling is enabled (see
Section 4.6.42), the encapsulated frames MUST be in the 802.3 Section 4.6.43), the encapsulated frames MUST be in the 802.3
format (see Section 4.4.2), unless a wireless management or format (see Section 4.4.2), unless a wireless management or
control frame which MAY be in its native format. Any CAPWAP control frame which MAY be in its native format. Any CAPWAP
binding needs to specify the format of management and control binding needs to specify the format of management and control
wireless frames. 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.44. WTP Name 4.6.45. 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 [RFC3629]. 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: 45 for WTP Name Type: 45 for WTP Name
Length: >= 1 Length: >= 1
WTP Name: A non-zero terminated UTF-8 encoded string [RFC3629] WTP Name: A non-zero terminated UTF-8 encoded string [RFC3629]
containing the WTP name, whose maximum size MUST NOT exceed 512 containing the WTP name, whose maximum size MUST NOT exceed 512
bytes. bytes.
4.6.45. WTP Radio Statistics 4.6.46. 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 96, line 20 skipping to change at page 97, line 5
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.46. WTP Reboot Statistics 4.6.47. 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 |
skipping to change at page 97, line 38 skipping to change at page 98, line 25
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.47. WTP Static IP Address Information 4.6.48. 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. IPv6 WTPs are expected to use dynamic addresses. 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 102, line 33 skipping to change at page 103, line 19
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.46. Section 4.6.47.
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.42. Encapsulation Type is defined in Section 4.6.43.
4.9.3. LastRebootReason 4.9.3. LastRebootReason
The reason why the WTP last rebooted, defined in Section 4.6.46. The reason why the WTP last rebooted, defined in Section 4.6.47.
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.43. Section 4.6.44.
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.46. The number of times the WTP has rebooted, defined in Section 4.6.47.
4.9.7. 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.47). Static IP Address Information message element (see Section 4.6.48).
4.9.8. 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.46. Section 4.6.47.
4.9.9. WTPLocation 4.9.9. WTPLocation
The WTP Location, defined in Section 4.6.29. The WTP Location, defined in Section 4.6.30.
4.9.10. WTPName 4.9.10. WTPName
The WTP Name, defined in Section 4.6.44. The WTP Name, defined in Section 4.6.45.
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 105, line 15 skipping to change at page 106, line 15
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.21 o Discovery Type, see Section 4.6.21
o WTP Board Data, see Section 4.6.39 o WTP Board Data, see Section 4.6.40
o WTP Descriptor, see Section 4.6.40 o WTP Descriptor, see Section 4.6.41
o WTP Frame Tunnel Mode, see Section 4.6.42 o WTP Frame Tunnel Mode, see Section 4.6.43
o WTP MAC Type, see Section 4.6.43 o WTP MAC Type, see Section 4.6.44
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 MTU Discovery Padding, see Section 4.6.31 o MTU Discovery Padding, see Section 4.6.32
o Vendor Specific Payload, see Section 4.6.38 o Vendor Specific Payload, see Section 4.6.39
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 106, line 34 skipping to change at page 107, line 34
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.9 * CAPWAP Control IPv4 Address, see Section 4.6.9
* CAPWAP Control IPv6 Address, see Section 4.6.10 * 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.38 o Vendor Specific Payload, see Section 4.6.39
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 or to perform a whether its preferred (or primary) AC is available or to perform a
Path MTU Discovery (see section Section 3.5. 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
skipping to change at page 107, line 14 skipping to change at page 108, line 14
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.21 o Discovery Type, see Section 4.6.21
o WTP Board Data, see Section 4.6.39 o WTP Board Data, see Section 4.6.40
o WTP Descriptor, see Section 4.6.40 o WTP Descriptor, see Section 4.6.41
o WTP Frame Tunnel Mode, see Section 4.6.42 o WTP Frame Tunnel Mode, see Section 4.6.43
o WTP MAC Type, see Section 4.6.43 o WTP MAC Type, see Section 4.6.44
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 MTU Discovery Padding, see Section 4.6.31 o MTU Discovery Padding, see Section 4.6.32
o Vendor Specific Payload, see Section 4.6.38 o Vendor Specific Payload, see Section 4.6.39
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 108, line 23 skipping to change at page 109, line 23
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.9 o CAPWAP Control IPv4 Address, see Section 4.6.9
o CAPWAP Control IPv6 Address, see Section 4.6.10 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.38 o Vendor Specific Payload, see Section 4.6.39
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 110, line 8 skipping to change at page 111, line 8
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.29 o Location Data, see Section 4.6.30
o WTP Board Data, see Section 4.6.39 o WTP Board Data, see Section 4.6.40
o WTP Descriptor, see Section 4.6.40 o WTP Descriptor, see Section 4.6.41
o WTP Name, see Section 4.6.44 o WTP Name, see Section 4.6.45
o Session ID, see Section 4.6.36 o Session ID, see Section 4.6.37
o WTP Frame Tunnel Mode, see Section 4.6.42 o WTP Frame Tunnel Mode, see Section 4.6.43
o WTP MAC Type, see Section 4.6.43 o WTP MAC Type, see Section 4.6.44
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).
o ECN Support, see Section 4.6.25
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 CAPWAP Local IPv4 Address, see Section 4.6.11 o CAPWAP Local IPv4 Address, see Section 4.6.11
o CAPWAP Local IPv6 Address, see Section 4.6.12 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 CAPWAP Transport Protocol, see Section 4.6.14 o CAPWAP Transport Protocol, see Section 4.6.14
o Maximum Message Length, see Section 4.6.30 o Maximum Message Length, see Section 4.6.31
o WTP Reboot Statistics, see Section 4.6.46 o WTP Reboot Statistics, see Section 4.6.47
o Vendor Specific Payload, see Section 4.6.38 o Vendor Specific Payload, see Section 4.6.39
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 111, line 31 skipping to change at page 112, line 32
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.34 o Result Code, see Section 4.6.35
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).
o ECN Support, see Section 4.6.25
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.9 o CAPWAP Control IPv4 Address, see Section 4.6.9
o CAPWAP Control IPv6 Address, see Section 4.6.10 o CAPWAP Control IPv6 Address, see Section 4.6.10
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:
skipping to change at page 112, line 15 skipping to change at page 113, line 19
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 CAPWAP Transport Protocol, see Section 4.6.14
o Image Identifier, see Section 4.6.26 o Image Identifier, see Section 4.6.27
o Maximum Message Length, see Section 4.6.30 o Maximum Message Length, see Section 4.6.31
o Vendor Specific Payload, see Section 4.6.38 o Vendor Specific Payload, see Section 4.6.39
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 113, line 30 skipping to change at page 114, line 30
Data or Run state (see Section 2.3) to determine the state of the Data or Run state (see Section 2.3) to determine the state of the
control connection between the WTP and the AC. The Echo Request control connection between the WTP and the AC. The Echo Request
message is sent by the WTP when the EchoInterval timer expires. message is sent by the 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.38 o Vendor Specific Payload, see Section 4.6.39
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 114, line 5 skipping to change at page 115, 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.38 o Vendor Specific Payload, see Section 4.6.39
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 116, line 43 skipping to change at page 117, line 43
each radio in the WTP. each radio in the WTP.
The Configuration Status Request message is sent by the WTP when in The Configuration Status Request message is sent by the WTP when in
the 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 Request message. Status Request message.
o AC Name, see Section 4.6.4 o AC Name, see Section 4.6.4
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.37 o Statistics Timer, see Section 4.6.38
o WTP Reboot Statistics, see Section 4.6.46 o WTP Reboot Statistics, see Section 4.6.47
The following message elements MAY be included in the Configuration The following message elements MAY be included in the Configuration
Status Request message. Status Request message.
o AC Name with Priority, see Section 4.6.5 o AC Name with Priority, see Section 4.6.5
o CAPWAP Transport Protocol, see Section 4.6.14 o CAPWAP Transport Protocol, see Section 4.6.14
o WTP Static IP Address Information, see Section 4.6.47 o WTP Static IP Address Information, see Section 4.6.48
o Vendor Specific Payload, see Section 4.6.38 o Vendor Specific Payload, see Section 4.6.39
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 Status Request message. receiving a Configuration Status Request message.
skipping to change at page 117, line 45 skipping to change at page 118, line 45
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 CAPWAP Timers, see Section 4.6.13 o CAPWAP Timers, see Section 4.6.13
o Decryption Error Report Period, see Section 4.6.18 o Decryption Error Report Period, see Section 4.6.18
o Idle Timeout, see Section 4.6.24 o Idle Timeout, see Section 4.6.24
o WTP Fallback, see Section 4.6.41 o WTP Fallback, see Section 4.6.42
One or both of the following message elements MUST be included in the One or both of the following message elements MUST be included in the
Configuration Status Response Message: Configuration Status Response 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
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.47 o WTP Static IP Address Information, see Section 4.6.48
o Vendor Specific Payload, see Section 4.6.38 o Vendor Specific Payload, see Section 4.6.39
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 message element (see The AC includes the Image Identifier message element (see
Section 4.6.26) to force the WTP to update its firmware while in the Section 4.6.27) to force the WTP to update its firmware while in the
Run state. The WTP MAY proceed to download the requested firmware if Run state. The WTP MAY proceed to download the requested firmware if
it 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 by transmitting an Image element is not in its non-volatile storage by transmitting an Image
Data Request (see Section 9.1.1) that includes the Initiate Download Data Request (see Section 9.1.1) that includes the Initiate Download
message element (see Section 4.6.28). message element (see Section 4.6.29).
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 Priority, see Section 4.6.5 o AC Name with Priority, 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 CAPWAP Timers, see Section 4.6.13 o CAPWAP Timers, see Section 4.6.13
o Decryption Error Report Period, see Section 4.6.18 o Decryption Error Report Period, see Section 4.6.18
o Delete MAC ACL Entry, see Section 4.6.19 o Delete MAC ACL Entry, see Section 4.6.19
o Idle Timeout, see Section 4.6.24 o Idle Timeout, see Section 4.6.24
o Location Data, see Section 4.6.29 o Location Data, see Section 4.6.30
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.37 o Statistics Timer, see Section 4.6.38
o WTP Fallback, see Section 4.6.41 o WTP Fallback, see Section 4.6.42
o WTP Name, see Section 4.6.44 o WTP Name, see Section 4.6.45
o WTP Static IP Address Information, see Section 4.6.47 o WTP Static IP Address Information, see Section 4.6.48
o Image Identifier, see Section 4.6.26 o Image Identifier, see Section 4.6.27
o Vendor Specific Payload, see Section 4.6.38 o Vendor Specific Payload, see Section 4.6.39
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.34 Result Code, see Section 4.6.35
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.33 o Radio Operational State, see Section 4.6.34
o Vendor Specific Payload, see Section 4.6.38 o Vendor Specific Payload, see Section 4.6.39
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 120, line 28 skipping to change at page 121, 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.35). Message Element message elements (see Section 4.6.36).
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.33 o Radio Operational State, see Section 4.6.34
o Result Code, see Section 4.6.34 o Result Code, see Section 4.6.35
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.35 o Returned Message Element(s), see Section 4.6.36
o Vendor Specific Payload, see Section 4.6.38 o Vendor Specific Payload, see Section 4.6.39
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.38 o Vendor Specific Payload, see Section 4.6.39
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.38 o Vendor Specific Payload, see Section 4.6.39
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.34 o Result Code, see Section 4.6.35
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.38 o Vendor Specific Payload, see Section 4.6.39
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 128, line 28 skipping to change at page 129, line 28
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 CAPWAP Transport Protocol, see Section 4.6.14 o CAPWAP Transport Protocol, see Section 4.6.14
o Image Data, see Section 4.6.25 o Image Data, see Section 4.6.26
o Vendor Specific Payload, see Section 4.6.38 o Vendor Specific Payload, see Section 4.6.39
The following message elements MAY be included in the Image Data The following message elements MAY be included in the Image Data
Request message when sent by the WTP. Request message when sent by the WTP.
o Image Identifier, see Section 4.6.26 o Image Identifier, see Section 4.6.27
o Initiate Download, see Section 4.6.28 o Initiate Download, see Section 4.6.29
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.34 o Result Code, see Section 4.6.35
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 Vendor Specific Payload, see Section 4.6.38 o Vendor Specific Payload, see Section 4.6.39
The following message elements MAY be included in the Image Data The following message elements MAY be included in the Image Data
Response message when sent by the AC. Response message when sent by the AC.
o Image Information, see Section 4.6.27 o Image Information, see Section 4.6.28
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. If the AC includes the Image Identifier reinitialize its operation. If the AC includes the Image Identifier
message element (see Section 4.6.26), it indicates to the WTP that it message element (see Section 4.6.27), it indicates to the WTP that it
SHOULD use that version of software upon reboot. 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.26 o Image Identifier, see Section 4.6.27
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.38 o Vendor Specific Payload, see Section 4.6.39
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 130, line 21 skipping to change at page 131, 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.34 o Result Code, see Section 4.6.35
o Vendor Specific Payload, see Section 4.6.38 o Vendor Specific Payload, see Section 4.6.39
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
skipping to change at page 131, line 12 skipping to change at page 132, line 12
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.17 o Decryption Error Report, see Section 4.6.17
o Duplicate IPv4 Address, see Section 4.6.22 o Duplicate IPv4 Address, see Section 4.6.22
o Duplicate IPv6 Address, see Section 4.6.23 o Duplicate IPv6 Address, see Section 4.6.23
o WTP Radio Statistics, see Section 4.6.45 o WTP Radio Statistics, see Section 4.6.46
o WTP Reboot Statistics, see Section 4.6.46 o WTP Reboot Statistics, see Section 4.6.47
o Delete Station, see Section 4.6.20 o Delete Station, see Section 4.6.20
o Vendor Specific Payload, see Section 4.6.38 o Vendor Specific Payload, see Section 4.6.39
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.38 o Vendor Specific Payload, see Section 4.6.39
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 133, line 44 skipping to change at page 134, line 44
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.15 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.38 o Vendor Specific Payload, see Section 4.6.39
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.34 o Result Code, see Section 4.6.35
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.38 o Vendor Specific Payload, see Section 4.6.39
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 135, line 32 skipping to change at page 136, line 32
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.20 o Delete Station, see Section 4.6.20
o Vendor Specific Payload, see Section 4.6.38 o Vendor Specific Payload, see Section 4.6.39
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.34 o Result Code, see Section 4.6.35
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.38 o Vendor Specific Payload, see Section 4.6.39
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 140, line 41 skipping to change at page 141, line 41
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 12.1.5. Use of MD5
The Image Information Section 4.6.27) message element makes use of The Image Information Section 4.6.28) message element makes use of
MD5 to compute the hash field. The authenticity and integrity of the 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 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. as a cryptographically secure hash, but just as a basic checksum.
Therefore, the use of MD5 is not considered a security vulnerability, Therefore, the use of MD5 is not considered a security vulnerability,
and no mechanisms for algorithm agility are provided. and no mechanisms for algorithm agility are provided.
12.1.6. CAPWAP Fragmentation 12.1.6. CAPWAP Fragmentation
RFC 4963 [RFC4963] describes a possible security vulnerability where RFC 4963 [RFC4963] describes a possible security vulnerability where
a malicious entity can "corrupt" a flow by injecting fragments. By a malicious entity can "corrupt" a flow by injecting fragments. By
skipping to change at page 148, line 45 skipping to change at page 149, line 45
The lock step nature of the CAPWAP protocol's control channel can The lock step nature of the CAPWAP protocol's control channel can
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.
The CAPWAP protocol supports Explicit Congestion Notification (ECN) The CAPWAP protocol mandates support of the Explicit Congestion
through mode of operation named "limited functionality option", Notification (ECN) through a mode of operation named "limited
detailed in [RFC3168]. Future versions of the CAPWAP protocol should functionality option", detailed in section 9.1.1 of [RFC3168].
consider supporting the "full functionality option", which may Future versions of the CAPWAP protocol should consider mandating
require some explicit signalling within the CAPWAP control protocol. support for the "full functionality option".
15. IANA Considerations 15. IANA Considerations
This section details the actions to be taken by IANA during the This section details the actions to be taken by IANA during the
publication of the specification. There are numerous registries that publication of the specification. There are numerous registries that
need to be created, and the contents, document action (see [RFC5226], need to be created, and the contents, document action (see [RFC5226],
and registry format are all included below. Note that in cases where 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 bit fields are referred to, the bit numbering is left to right, where
the leftmost bit is labelled as bit zero (0). the leftmost bit is labelled as bit zero (0).
skipping to change at page 150, line 22 skipping to change at page 151, line 22
15.4. CAPWAP Message Types 15.4. 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]. of the field containing the IANA Enterprise Number [RFC5226].
IANA will create and maintain the CAPWAP Message Types registry for IANA will create and maintain the CAPWAP Message Types registry for
all message types whose Enterprise Number is set to zero (0). The 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 namespace is 8 bits (0-255), where the value of zero (0) is reserved
reserved and must not be assigned. The values one (1) through 26 are 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. 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 Any new assignments of a CAPWAP Message Type, whose Enterprise Number
is set to zero (0) requires a Expert Review. The format of the is set to zero (0) requires a Expert Review. The format of the
registry to be maintained by IANA has the following format: registry to be maintained by IANA has the following format:
CAPWAP Control Message Message Type Reference CAPWAP Control Message Message Type Reference
Value Value
15.5. CAPWAP Header Flags 15.5. CAPWAP Header Flags
skipping to change at page 151, line 13 skipping to change at page 152, line 13
Expert Review. IANA will create the CAPWAP Control Message Flags Expert Review. IANA will create the CAPWAP Control Message Flags
registry, whose format is: registry, whose format is:
Flag Field Name Bit Position Reference Flag Field Name Bit Position Reference
15.7. CAPWAP Message Element Type 15.7. CAPWAP Message Element Type
The Type field in the CAPWAP Message Element header (see Section 4.6) 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 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 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 be assigned. The values one (1) through 53 are allocated in this
specification, and can be found in Section 4.5.1.1. specification, and can be found in Section 4.5.1.1.
The 16 bit namespace is further divided into blocks of addresses that The 16 bit namespace is further divided into blocks of addresses that
are reserved for specific CAPWAP wireless bindings. The following are reserved for specific CAPWAP wireless bindings. The following
blocks are reserved: blocks are reserved:
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
EPCGlobal Message Elements 3072 - 4095 EPCGlobal Message Elements 3072 - 4095
skipping to change at page 152, line 49 skipping to change at page 153, line 49
one (1) and two (2) are allocated in this specification, and can be 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 found in Section 4.6.14. This namespace is managed by IANA and
assignments require a Expert Review. IANA will create the CAPWAP assignments require a Expert Review. IANA will create the CAPWAP
Transport Protocol Types registry, whose format is: Transport Protocol Types registry, whose format is:
CAPWAP Transport Protocol Type Type Value Reference CAPWAP Transport Protocol Type Type Value Reference
15.13. Data Transfer Type 15.13. 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.15) and Image Data message element (see Section 4.6.25) Section 4.6.15) and Image Data message element (see Section 4.6.26)
is used to provide information about the data being carried. The is used to provide information about the data being carried. The
namespace is 8 bits (0-255), where the value of zero (0) is reserved namespace is 8 bits (0-255), where the value of zero (0) is reserved
and must not be assigned. The values one (1), two (2) and five (5) and must not be assigned. The values one (1), two (2) and five (5)
are allocated in this specification, and can be found in are allocated in this specification, and can be found in
Section 4.6.15. This namespace is managed by IANA and assignments Section 4.6.15. This namespace is managed by IANA and assignments
require a Expert Review. IANA will create the Data Transfer Type require a Expert Review. IANA will create the Data Transfer Type
registry, whose format is: registry, whose format is:
Data Transfer Type Type Value Reference Data Transfer Type Type Value Reference
skipping to change at page 153, line 37 skipping to change at page 154, line 37
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.21) 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. The namespace is 8 bits (0-255). The values zero (0) discovered. The namespace is 8 bits (0-255). The values zero (0)
through four (4) are allocated in this specification, and can be through four (4) are allocated in this specification, and can be
found in Section 4.6.21. This namespace is managed by IANA and found in Section 4.6.21. This namespace is managed by IANA and
assignments require a Expert Review. IANA will create the Discovery assignments require a Expert Review. IANA will create the Discovery
Types registry, whose format is: Types registry, whose format is:
Discovery Types Type Value Reference Discovery Types Type Value Reference
15.16. Radio Admin State 15.16. ECN Support
The ECN Support field in the ECN Support message element (see
Section 4.6.25) is used by the WTP to represent its ECN Support. The
namespace is 8 bits (0-255). The values zero (0) and one (1) are
allocated in this specification, and can be found in Section 4.6.25.
This namespace is managed by IANA and assignments require a Expert
Review. IANA will create the ECN Support registry, whose format is:
ECN Support Type Value Reference
15.17. 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.32) is used by the WTP to represent the element (see Section 4.6.33) is used by the WTP to represent the
state of its radios. The namespace is 8 bits (0-255), where the state of its radios. The namespace is 8 bits (0-255), where the
value of zero (0) is reserved and must not be assigned. The values value of zero (0) is reserved and must not be assigned. The values
one (1) and two (2) are allocated in this specification, and can be 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 found in Section 4.6.33. This namespace is managed by IANA and
assignments require a Expert Review. IANA will create the Radio assignments require a Expert Review. IANA will create the Radio
Admin State registry, whose format is: Admin State registry, whose format is:
Radio Admin State Type Value Reference Radio Admin State Type Value Reference
15.17. Radio Operational State 15.18. 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.33) is used by the WTP to represent the operational state Section 4.6.34) is used by the WTP to represent the operational state
of its radios. The namespace is 8 bits (0-255), where the value of of its radios. The namespace is 8 bits (0-255), where the value of
zero (0) is reserved and must not be assigned. The values one (1) zero (0) is reserved and must not be assigned. The values one (1)
and two (2) are allocated in this specification, and can be found in 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 Section 4.6.34. This namespace is managed by IANA and assignments
require a Expert Review. IANA will create the Radio Operational require a Expert Review. IANA will create the Radio Operational
State registry, whose format is: State registry, whose format is:
Radio Operational State Type Value Reference Radio Operational State Type Value Reference
15.18. Radio Failure Causes 15.19. 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.33) is used by the WTP to represent the reason why a Section 4.6.34) is used by the WTP to represent the reason why a
radio may have failed. The namespace is 8 bits (0-255), where the radio may have failed. The namespace is 8 bits (0-255), where the
value of zero (0) through three (3) are allocated in this value of zero (0) through three (3) are allocated in this
specification, and can be found in Section 4.6.33. This namespace is specification, and can be found in Section 4.6.34. This namespace is
managed by IANA and assignments require a Expert Review. IANA will managed by IANA and assignments require a Expert Review. IANA will
create the Radio Failure Causes registry, whose format is: create the Radio Failure Causes registry, whose format is:
Radio Failure Causes Type Value Reference Radio Failure Causes Type Value Reference
15.19. Result Code 15.20. 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.34) is used to indicate the success, or failure, of a Section 4.6.35) is used to indicate the success, or failure, of a
CAPWAP control message. The namespace is 32 bits (0-4294967295), CAPWAP control message. The namespace is 32 bits (0-4294967295),
where the value of zero (0) through 22 are allocated in this where the value of zero (0) through 22 are allocated in this
specification, and can be found in Section 4.6.34. This namespace is specification, and can be found in Section 4.6.35. This namespace is
managed by IANA and assignments require a Expert Review. IANA will managed by IANA and assignments require a Expert Review. IANA will
create the Result Code registry, whose format is: create the Result Code registry, whose format is:
Result Code Type Value Reference Result Code Type Value Reference
15.20. Returned Message Element Reason 15.21. 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.35) is used to indicate the reason why a message element Section 4.6.36) is used to indicate the reason why a message element
was not processed successfully. The namespace is 8 bits (0-255), was not processed successfully. The namespace is 8 bits (0-255),
where the value of zero (0) is reserved and must not be assigned. where the value of zero (0) is reserved and must not be assigned.
The values one (1) through four (4) are allocated in this The values one (1) through four (4) are allocated in this
specification, and can be found in Section 4.6.35. This namespace is specification, and can be found in Section 4.6.36. This namespace is
managed by IANA and assignments require a Expert Review. IANA will managed by IANA and assignments require a Expert Review. IANA will
create the Returned Message Element Reason registry, whose format is: create the Returned Message Element Reason registry, whose format is:
Returned Message Element Reason Type Value Reference Returned Message Element Reason Type Value Reference
15.21. WTP Board Data Type 15.22. 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.39) is used to represent information about the WTP Section 4.6.40) is used to represent information about the WTP
hardware. The namespace is 16 bits (0-65535). The WTP Board Data hardware. The namespace is 16 bits (0-65535). The WTP Board Data
Type values zero (0) through four (4) are allocated in this Type values zero (0) through four (4) are allocated in this
specification, and can be found in Section 4.6.39. This namespace is specification, and can be found in Section 4.6.40. This namespace is
managed by IANA and assignments require a Expert Review. IANA will managed by IANA and assignments require a Expert Review. IANA will
create the WTP Board Data Type registry, whose format is: create the WTP Board Data Type registry, whose format is:
WTP Board Data Type Type Value Reference WTP Board Data Type Type Value Reference
15.22. WTP Descriptor Type 15.23. 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.40) is used to represent information about the WTP Section 4.6.41) is used to represent information about the WTP
software. The namespace is 16 bits (0-65535). This field, combined software. The namespace is 16 bits (0-65535). This field, combined
with the Descriptor Vendor ID, allows vendors to use a private with the Descriptor Vendor ID, allows vendors to use a private
namespace. This specification defines the WTP Descriptor Type namespace. This specification defines the WTP Descriptor Type
namespace when the Descriptor Vendor ID is set to zero (0), for which namespace when the Descriptor Vendor ID is set to zero (0), for which
the values zero (0) through three (3) are allocated in this the values zero (0) through three (3) are allocated in this
specification, and can be found in Section 4.6.40. This namespace is specification, and can be found in Section 4.6.41. This namespace is
managed by IANA and assignments require a Expert Review. IANA will managed by IANA and assignments require a Expert Review. IANA will
create the WTP Board Data Type registry, whose format is: create the WTP Board Data Type registry, whose format is:
WTP Descriptor Type Type Value Reference WTP Descriptor Type Type Value Reference
15.23. WTP Fallback Mode 15.24. 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.41) is used to indicate to the WTP the type of AC Section 4.6.42) is used to indicate to the WTP the type of AC
fallback mechanism it should employ. The namespace is 8 bits fallback mechanism it should employ. The namespace is 8 bits
(0-255), where the value of zero (0) is reserved and must not be (0-255), where the value of zero (0) is reserved and must not be
assigned. The values one (1) and two (2) are allocated in this 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 specification, and can be found in Section 4.6.42. This namespace is
managed by IANA and assignments require a Expert Review. IANA will managed by IANA and assignments require a Expert Review. IANA will
create the WTP Fallback Mode registry, whose format is: create the WTP Fallback Mode registry, whose format is:
WTP Fallback Mode Type Value Reference WTP Fallback Mode Type Value Reference
15.24. WTP Frame Tunnel Mode 15.25. 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.42) is 8 bits and is used to indicate the type of (see Section 4.6.43) is 8 bits and is used to indicate the type of
tunneling to use between the WTP and the AC. This specification tunneling to use between the WTP and the AC. This specification
defines bits four (4) through six (6), while bits zero (0) through defines bits four (4) through six (6), while bits zero (0) through
four (4) as well as bit seven (7) are reserved and unused. These four (4) as well as bit seven (7) are reserved and unused. These
reserved bits are managed by IANA and assignment requires a Expert reserved bits are managed by IANA and assignment requires a Expert
Review. IANA will create the AC DTLS Policy registry, whose format Review. IANA will create the AC DTLS Policy registry, whose format
is: is:
WTP Frame Tunnel Mode Bit Position Reference WTP Frame Tunnel Mode Bit Position Reference
15.25. WTP MAC Type 15.26. 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.43) is used to indicate the type of MAC to use in Section 4.6.44) is used to indicate the type of MAC to use in
tunneled frames between the WTP and the AC. The namespace is 8 bits tunneled frames between the WTP and the AC. The namespace is 8 bits
(0-255), where the value of zero (0) through two (2) are allocated in (0-255), where the value of zero (0) through two (2) are allocated in
this specification, and can be found in Section 4.6.43. This this specification, and can be found in Section 4.6.44. This
namespace is managed by IANA and assignments require a Expert Review. namespace is managed by IANA and assignments require a Expert Review.
IANA will create the WTP MAC Type registry, whose format is: IANA will create the WTP MAC Type registry, whose format is:
WTP MAC Type Type Value Reference WTP MAC Type Type Value Reference
15.26. WTP Radio Stats Failure Type 15.27. 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.45) is used to indicate the last WTP element (see Section 4.6.46) is used to indicate the last WTP
failure. The namespace is 8 bits (0-255), where the value of zero failure. The namespace is 8 bits (0-255), where the value of zero
(0) through three (3) as well as the value 255 are allocated in this (0) through three (3) as well as the value 255 are allocated in this
specification, and can be found in Section 4.6.45. This namespace is specification, and can be found in Section 4.6.46. This namespace is
managed by IANA and assignments require a Expert Review. IANA will managed by IANA and assignments require a Expert Review. IANA will
create the WTP Radio Stats Failure Type registry, whose format is: create the WTP Radio Stats Failure Type registry, whose format is:
WTP Radio Stats Failure Type Type Value Reference WTP Radio Stats Failure Type Type Value Reference
15.27. WTP Reboot Stats Failure Type 15.28. 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.46) is used to indicate the last reboot element (see Section 4.6.47) is used to indicate the last reboot
reason. The namespace is 8 bits (0-255), where the value of zero (0) reason. The namespace is 8 bits (0-255), where the value of zero (0)
through five (5) as well as the value 255 are allocated in this through five (5) as well as the value 255 are allocated in this
specification, and can be found in Section 4.6.46. This namespace is specification, and can be found in Section 4.6.47. This namespace is
managed by IANA and assignments require a Expert Review. IANA will managed by IANA and assignments require a Expert Review. IANA will
create the WTP Reboot Stats Failure Type registry, whose format is: create the WTP Reboot Stats Failure Type registry, whose format is:
WTP Reboot Stats Failure Type Type Value Reference WTP Reboot Stats Failure Type Type Value Reference
16. Acknowledgments 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, Pasi this protocol specification: Puneet Agarwal, Abhijit Choudhury, Pasi
Eronen, Saravanan Govindan, Peter Nilsson, David Perkins and Yong Eronen, Saravanan Govindan, Peter Nilsson, David Perkins and Yong
skipping to change at page 159, line 42 skipping to change at page 161, line 42
[ISO.9834-1.1993] [ISO.9834-1.1993]
International Organization for Standardization, International Organization for Standardization,
"Procedures for the operation of OSI registration "Procedures for the operation of OSI registration
authorities - part 1: general procedures", ISO Standard authorities - part 1: general procedures", ISO Standard
9834-1, 1993. 9834-1, 1993.
[I-D.ietf-capwap-protocol-binding-ieee80211] [I-D.ietf-capwap-protocol-binding-ieee80211]
Montemurro, M., Stanley, D., and P. Calhoun, "CAPWAP Montemurro, M., Stanley, D., and P. Calhoun, "CAPWAP
Protocol Binding for IEEE 802.11", Protocol Binding for IEEE 802.11",
draft-ietf-capwap-protocol-binding-ieee80211-10 (work in draft-ietf-capwap-protocol-binding-ieee80211-11 (work in
progress), September 2008. progress), October 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-02 (work in progress),
March 2008. October 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
[RFC3232] Reynolds, J., "Assigned Numbers: RFC 1700 is Replaced by [RFC3232] Reynolds, J., "Assigned Numbers: RFC 1700 is Replaced by
an On-line Database", RFC 3232, January 2002. an On-line Database", RFC 3232, January 2002.
[RFC3753] Manner, J. and M. Kojo, "Mobility Related Terminology", [RFC3753] Manner, J. and M. Kojo, "Mobility Related Terminology",
 End of changes. 179 change blocks. 
319 lines changed or deleted 359 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/