draft-ietf-capwap-protocol-specification-12.txt   draft-ietf-capwap-protocol-specification-13.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: March 13, 2009 Research In Motion Expires: March 23, 2009 Research In Motion
D. Stanley, Editor D. Stanley, Editor
Aruba Networks Aruba Networks
September 9, 2008 September 19, 2008
CAPWAP Protocol Specification CAPWAP Protocol Specification
draft-ietf-capwap-protocol-specification-12 draft-ietf-capwap-protocol-specification-13
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 March 13, 2009. This Internet-Draft will expire on March 23, 2009.
Abstract Abstract
This specification defines the Control And Provisioning of Wireless This specification defines the Control And Provisioning of Wireless
Access Points (CAPWAP) Protocol. The CAPWAP protocol meets the Access Points (CAPWAP) Protocol, meeting the objectives defined by
Objectives for Control and Provisioning of Wireless Access Points the CAPWAP working group in RFC 4564. The CAPWAP protocol is
(CAPWAP). The CAPWAP protocol is designed to be flexible, allowing designed to be flexible, allowing it to be used for a variety of
it to be used for a variety of wireless technologies. This document wireless technologies. This document describes the base CAPWAP
describes the base CAPWAP protocol, while separate binding extensions protocol, while separate binding extensions will enable its use with
will enable its use with additional wireless technologies. additional wireless technologies.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 7 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2. Conventions used in this document . . . . . . . . . . . 9 1.2. Conventions used in this document . . . . . . . . . . . 9
1.3. Contributing Authors . . . . . . . . . . . . . . . . . . 9 1.3. Contributing Authors . . . . . . . . . . . . . . . . . . 9
1.4. Terminology . . . . . . . . . . . . . . . . . . . . . . 10 1.4. Terminology . . . . . . . . . . . . . . . . . . . . . . 10
2. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 12 2. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 12
2.1. Wireless Binding Definition . . . . . . . . . . . . . . 13 2.1. Wireless Binding Definition . . . . . . . . . . . . . . 13
skipping to change at page 3, line 8 skipping to change at page 3, line 8
4.4.3. Establishment of a DTLS Data Channel . . . . . . . . 53 4.4.3. Establishment of a DTLS Data Channel . . . . . . . . 53
4.5. CAPWAP Control Messages . . . . . . . . . . . . . . . . 53 4.5. CAPWAP Control Messages . . . . . . . . . . . . . . . . 53
4.5.1. Control Message Format . . . . . . . . . . . . . . . 54 4.5.1. Control Message Format . . . . . . . . . . . . . . . 54
4.5.2. Control Message Quality of Service . . . . . . . . . 57 4.5.2. Control Message Quality of Service . . . . . . . . . 57
4.5.3. Retransmissions . . . . . . . . . . . . . . . . . . . 57 4.5.3. Retransmissions . . . . . . . . . . . . . . . . . . . 57
4.6. CAPWAP Protocol Message Elements . . . . . . . . . . . . 59 4.6. CAPWAP Protocol Message Elements . . . . . . . . . . . . 59
4.6.1. AC Descriptor . . . . . . . . . . . . . . . . . . . . 61 4.6.1. AC Descriptor . . . . . . . . . . . . . . . . . . . . 61
4.6.2. AC IPv4 List . . . . . . . . . . . . . . . . . . . . 64 4.6.2. AC IPv4 List . . . . . . . . . . . . . . . . . . . . 64
4.6.3. AC IPv6 List . . . . . . . . . . . . . . . . . . . . 64 4.6.3. AC IPv6 List . . . . . . . . . . . . . . . . . . . . 64
4.6.4. AC Name . . . . . . . . . . . . . . . . . . . . . . . 65 4.6.4. AC Name . . . . . . . . . . . . . . . . . . . . . . . 65
4.6.5. AC Name with Index . . . . . . . . . . . . . . . . . 65 4.6.5. AC Name with Priority . . . . . . . . . . . . . . . . 65
4.6.6. AC Timestamp . . . . . . . . . . . . . . . . . . . . 66 4.6.6. AC Timestamp . . . . . . . . . . . . . . . . . . . . 66
4.6.7. Add MAC ACL Entry . . . . . . . . . . . . . . . . . . 66 4.6.7. Add MAC ACL Entry . . . . . . . . . . . . . . . . . . 66
4.6.8. Add Station . . . . . . . . . . . . . . . . . . . . . 67 4.6.8. Add Station . . . . . . . . . . . . . . . . . . . . . 67
4.6.9. CAPWAP Control IPv4 Address . . . . . . . . . . . . . 68 4.6.9. CAPWAP Control IPv4 Address . . . . . . . . . . . . . 68
4.6.10. CAPWAP Control IPv6 Address . . . . . . . . . . . . . 68 4.6.10. CAPWAP Control IPv6 Address . . . . . . . . . . . . . 68
4.6.11. CAPWAP Local IPv4 Address . . . . . . . . . . . . . . 69 4.6.11. CAPWAP Local IPv4 Address . . . . . . . . . . . . . . 69
4.6.12. CAPWAP Local IPv6 Address . . . . . . . . . . . . . . 69 4.6.12. CAPWAP Local IPv6 Address . . . . . . . . . . . . . . 70
4.6.13. CAPWAP Timers . . . . . . . . . . . . . . . . . . . . 70 4.6.13. CAPWAP Timers . . . . . . . . . . . . . . . . . . . . 70
4.6.14. CAPWAP Transport Protocol . . . . . . . . . . . . . . 70 4.6.14. CAPWAP Transport Protocol . . . . . . . . . . . . . . 71
4.6.15. Data Transfer Data . . . . . . . . . . . . . . . . . 71 4.6.15. Data Transfer Data . . . . . . . . . . . . . . . . . 72
4.6.16. Data Transfer Mode . . . . . . . . . . . . . . . . . 72 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 . . . . . . . . . . . 73 4.6.18. Decryption Error Report Period . . . . . . . . . . . 74
4.6.19. Delete MAC ACL Entry . . . . . . . . . . . . . . . . 74 4.6.19. Delete MAC ACL Entry . . . . . . . . . . . . . . . . 74
4.6.20. Delete Station . . . . . . . . . . . . . . . . . . . 74 4.6.20. Delete Station . . . . . . . . . . . . . . . . . . . 75
4.6.21. Discovery Type . . . . . . . . . . . . . . . . . . . 75 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 . . . . . . . . . . . . . . . . . . . . 77 4.6.24. Idle Timeout . . . . . . . . . . . . . . . . . . . . 78
4.6.25. Image Data . . . . . . . . . . . . . . . . . . . . . 78 4.6.25. Image Data . . . . . . . . . . . . . . . . . . . . . 78
4.6.26. Image Identifier . . . . . . . . . . . . . . . . . . 79 4.6.26. Image Identifier . . . . . . . . . . . . . . . . . . 79
4.6.27. Image Information . . . . . . . . . . . . . . . . . . 79 4.6.27. Image Information . . . . . . . . . . . . . . . . . . 79
4.6.28. Initiate Download . . . . . . . . . . . . . . . . . . 80 4.6.28. Initiate Download . . . . . . . . . . . . . . . . . . 80
4.6.29. Location Data . . . . . . . . . . . . . . . . . . . . 80 4.6.29. Location Data . . . . . . . . . . . . . . . . . . . . 80
4.6.30. Maximum Message Length . . . . . . . . . . . . . . . 81 4.6.30. Maximum Message Length . . . . . . . . . . . . . . . 81
4.6.31. MTU Discovery Padding . . . . . . . . . . . . . . . . 81 4.6.31. MTU Discovery Padding . . . . . . . . . . . . . . . . 81
4.6.32. Radio Administrative State . . . . . . . . . . . . . 81 4.6.32. Radio Administrative State . . . . . . . . . . . . . 82
4.6.33. Radio Operational State . . . . . . . . . . . . . . . 82 4.6.33. Radio Operational State . . . . . . . . . . . . . . . 82
4.6.34. Result Code . . . . . . . . . . . . . . . . . . . . . 83 4.6.34. Result Code . . . . . . . . . . . . . . . . . . . . . 83
4.6.35. Returned Message Element . . . . . . . . . . . . . . 85 4.6.35. Returned Message Element . . . . . . . . . . . . . . 85
4.6.36. Session ID . . . . . . . . . . . . . . . . . . . . . 86 4.6.36. Session ID . . . . . . . . . . . . . . . . . . . . . 86
4.6.37. Statistics Timer . . . . . . . . . . . . . . . . . . 86 4.6.37. Statistics Timer . . . . . . . . . . . . . . . . . . 86
4.6.38. Vendor Specific Payload . . . . . . . . . . . . . . . 87 4.6.38. Vendor Specific Payload . . . . . . . . . . . . . . . 87
4.6.39. WTP Board Data . . . . . . . . . . . . . . . . . . . 87 4.6.39. WTP Board Data . . . . . . . . . . . . . . . . . . . 87
4.6.40. WTP Descriptor . . . . . . . . . . . . . . . . . . . 89 4.6.40. WTP Descriptor . . . . . . . . . . . . . . . . . . . 89
4.6.41. WTP Fallback . . . . . . . . . . . . . . . . . . . . 91 4.6.41. WTP Fallback . . . . . . . . . . . . . . . . . . . . 91
4.6.42. WTP Frame Tunnel Mode . . . . . . . . . . . . . . . . 91 4.6.42. WTP Frame Tunnel Mode . . . . . . . . . . . . . . . . 92
4.6.43. WTP MAC Type . . . . . . . . . . . . . . . . . . . . 92 4.6.43. WTP MAC Type . . . . . . . . . . . . . . . . . . . . 93
4.6.44. WTP Name . . . . . . . . . . . . . . . . . . . . . . 93 4.6.44. WTP Name . . . . . . . . . . . . . . . . . . . . . . 93
4.6.45. WTP Radio Statistics . . . . . . . . . . . . . . . . 93 4.6.45. WTP Radio Statistics . . . . . . . . . . . . . . . . 94
4.6.46. WTP Reboot Statistics . . . . . . . . . . . . . . . . 95 4.6.46. WTP Reboot Statistics . . . . . . . . . . . . . . . . 95
4.6.47. WTP Static IP Address Information . . . . . . . . . . 96 4.6.47. WTP Static IP Address Information . . . . . . . . . . 97
4.7. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . 97 4.7. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . 97
4.7.1. ChangeStatePendingTimer . . . . . . . . . . . . . . . 97 4.7.1. ChangeStatePendingTimer . . . . . . . . . . . . . . . 97
4.7.2. DataChannelKeepAlive . . . . . . . . . . . . . . . . 97 4.7.2. DataChannelKeepAlive . . . . . . . . . . . . . . . . 98
4.7.3. DataChannelDeadInterval . . . . . . . . . . . . . . . 98 4.7.3. DataChannelDeadInterval . . . . . . . . . . . . . . . 98
4.7.4. DataCheckTimer . . . . . . . . . . . . . . . . . . . 98 4.7.4. DataCheckTimer . . . . . . . . . . . . . . . . . . . 98
4.7.5. DiscoveryInterval . . . . . . . . . . . . . . . . . . 98 4.7.5. DiscoveryInterval . . . . . . . . . . . . . . . . . . 98
4.7.6. DTLSSessionDelete . . . . . . . . . . . . . . . . . . 98 4.7.6. DTLSSessionDelete . . . . . . . . . . . . . . . . . . 98
4.7.7. EchoInterval . . . . . . . . . . . . . . . . . . . . 98 4.7.7. EchoInterval . . . . . . . . . . . . . . . . . . . . 98
4.7.8. IdleTimeout . . . . . . . . . . . . . . . . . . . . . 98 4.7.8. IdleTimeout . . . . . . . . . . . . . . . . . . . . . 99
4.7.9. ImageDataStartTimer . . . . . . . . . . . . . . . . . 98 4.7.9. ImageDataStartTimer . . . . . . . . . . . . . . . . . 99
4.7.10. MaxDiscoveryInterval . . . . . . . . . . . . . . . . 99 4.7.10. MaxDiscoveryInterval . . . . . . . . . . . . . . . . 99
4.7.11. ReportInterval . . . . . . . . . . . . . . . . . . . 99 4.7.11. ReportInterval . . . . . . . . . . . . . . . . . . . 99
4.7.12. RetransmitInterval . . . . . . . . . . . . . . . . . 99 4.7.12. RetransmitInterval . . . . . . . . . . . . . . . . . 99
4.7.13. SilentInterval . . . . . . . . . . . . . . . . . . . 99 4.7.13. SilentInterval . . . . . . . . . . . . . . . . . . . 99
4.7.14. StatisticsTimer . . . . . . . . . . . . . . . . . . . 99 4.7.14. StatisticsTimer . . . . . . . . . . . . . . . . . . . 100
4.7.15. WaitDTLS . . . . . . . . . . . . . . . . . . . . . . 99 4.7.15. WaitDTLS . . . . . . . . . . . . . . . . . . . . . . 100
4.7.16. WaitJoin . . . . . . . . . . . . . . . . . . . . . . 100 4.7.16. WaitJoin . . . . . . . . . . . . . . . . . . . . . . 100
4.8. CAPWAP Protocol Variables . . . . . . . . . . . . . . . 100 4.8. CAPWAP Protocol Variables . . . . . . . . . . . . . . . 100
4.8.1. AdminState . . . . . . . . . . . . . . . . . . . . . 100 4.8.1. AdminState . . . . . . . . . . . . . . . . . . . . . 100
4.8.2. DiscoveryCount . . . . . . . . . . . . . . . . . . . 100 4.8.2. DiscoveryCount . . . . . . . . . . . . . . . . . . . 100
4.8.3. FailedDTLSAuthFailCount . . . . . . . . . . . . . . . 100 4.8.3. FailedDTLSAuthFailCount . . . . . . . . . . . . . . . 100
4.8.4. FailedDTLSSessionCount . . . . . . . . . . . . . . . 100 4.8.4. FailedDTLSSessionCount . . . . . . . . . . . . . . . 101
4.8.5. MaxDiscoveries . . . . . . . . . . . . . . . . . . . 100 4.8.5. MaxDiscoveries . . . . . . . . . . . . . . . . . . . 101
4.8.6. MaxFailedDTLSSessionRetry . . . . . . . . . . . . . . 100 4.8.6. MaxFailedDTLSSessionRetry . . . . . . . . . . . . . . 101
4.8.7. MaxRetransmit . . . . . . . . . . . . . . . . . . . . 101 4.8.7. MaxRetransmit . . . . . . . . . . . . . . . . . . . . 101
4.8.8. RetransmitCount . . . . . . . . . . . . . . . . . . . 101 4.8.8. RetransmitCount . . . . . . . . . . . . . . . . . . . 101
4.8.9. WTPFallBack . . . . . . . . . . . . . . . . . . . . . 101 4.8.9. WTPFallBack . . . . . . . . . . . . . . . . . . . . . 101
4.9. WTP Saved Variables . . . . . . . . . . . . . . . . . . 101 4.9. WTP Saved Variables . . . . . . . . . . . . . . . . . . 101
4.9.1. AdminRebootCount . . . . . . . . . . . . . . . . . . 101 4.9.1. AdminRebootCount . . . . . . . . . . . . . . . . . . 101
4.9.2. FrameEncapType . . . . . . . . . . . . . . . . . . . 101 4.9.2. FrameEncapType . . . . . . . . . . . . . . . . . . . 102
4.9.3. LastRebootReason . . . . . . . . . . . . . . . . . . 101 4.9.3. LastRebootReason . . . . . . . . . . . . . . . . . . 102
4.9.4. MacType . . . . . . . . . . . . . . . . . . . . . . . 101 4.9.4. MacType . . . . . . . . . . . . . . . . . . . . . . . 102
4.9.5. PreferredACs . . . . . . . . . . . . . . . . . . . . 102 4.9.5. PreferredACs . . . . . . . . . . . . . . . . . . . . 102
4.9.6. RebootCount . . . . . . . . . . . . . . . . . . . . . 102 4.9.6. RebootCount . . . . . . . . . . . . . . . . . . . . . 102
4.9.7. Static IP Address . . . . . . . . . . . . . . . . . . 102 4.9.7. Static IP Address . . . . . . . . . . . . . . . . . . 102
4.9.8. WTPLinkFailureCount . . . . . . . . . . . . . . . . . 102 4.9.8. WTPLinkFailureCount . . . . . . . . . . . . . . . . . 102
4.9.9. WTPLocation . . . . . . . . . . . . . . . . . . . . . 102 4.9.9. WTPLocation . . . . . . . . . . . . . . . . . . . . . 102
4.9.10. WTPName . . . . . . . . . . . . . . . . . . . . . . . 102 4.9.10. WTPName . . . . . . . . . . . . . . . . . . . . . . . 102
5. CAPWAP Discovery Operations . . . . . . . . . . . . . . . . . 103 5. CAPWAP Discovery Operations . . . . . . . . . . . . . . . . . 103
5.1. Discovery Request Message . . . . . . . . . . . . . . . 103 5.1. Discovery Request Message . . . . . . . . . . . . . . . 103
5.2. Discovery Response Message . . . . . . . . . . . . . . . 104 5.2. Discovery Response Message . . . . . . . . . . . . . . . 104
5.3. Primary Discovery Request Message . . . . . . . . . . . 105 5.3. Primary Discovery Request Message . . . . . . . . . . . 105
skipping to change at page 6, line 9 skipping to change at page 6, line 9
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 147 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 147
15.1. Multicast Address . . . . . . . . . . . . . . . . . . . 147 15.1. Multicast Address . . . . . . . . . . . . . . . . . . . 147
15.2. UDP Port . . . . . . . . . . . . . . . . . . . . . . . . 147 15.2. UDP Port . . . . . . . . . . . . . . . . . . . . . . . . 147
15.3. CAPWAP Message Types . . . . . . . . . . . . . . . . . . 148 15.3. CAPWAP Message Types . . . . . . . . . . . . . . . . . . 148
15.4. CAPWAP Header Flags . . . . . . . . . . . . . . . . . . 148 15.4. CAPWAP Header Flags . . . . . . . . . . . . . . . . . . 148
15.5. CAPWAP Control Message Flags . . . . . . . . . . . . . . 148 15.5. CAPWAP Control Message Flags . . . . . . . . . . . . . . 148
15.6. CAPWAP Message Element Type . . . . . . . . . . . . . . 148 15.6. CAPWAP Message Element Type . . . . . . . . . . . . . . 148
15.7. Wireless Binding Identifiers . . . . . . . . . . . . . . 149 15.7. Wireless Binding Identifiers . . . . . . . . . . . . . . 149
15.8. AC Security Types . . . . . . . . . . . . . . . . . . . 149 15.8. AC Security Types . . . . . . . . . . . . . . . . . . . 149
15.9. AC DTLS Policy . . . . . . . . . . . . . . . . . . . . . 149 15.9. AC DTLS Policy . . . . . . . . . . . . . . . . . . . . . 149
15.10. AC Information Type . . . . . . . . . . . . . . . . . . 149 15.10. AC Information Type . . . . . . . . . . . . . . . . . . 150
15.11. CAPWAP Transport Protocol Types . . . . . . . . . . . . 150 15.11. CAPWAP Transport Protocol Types . . . . . . . . . . . . 150
15.12. Data Transfer Type . . . . . . . . . . . . . . . . . . . 150 15.12. Data Transfer Type . . . . . . . . . . . . . . . . . . . 150
15.13. Data Transfer Mode . . . . . . . . . . . . . . . . . . . 150 15.13. Data Transfer Mode . . . . . . . . . . . . . . . . . . . 151
15.14. Discovery Types . . . . . . . . . . . . . . . . . . . . 151 15.14. Discovery Types . . . . . . . . . . . . . . . . . . . . 151
15.15. Radio Admin State . . . . . . . . . . . . . . . . . . . 151 15.15. Radio Admin State . . . . . . . . . . . . . . . . . . . 151
15.16. Radio Operational State . . . . . . . . . . . . . . . . 151 15.16. Radio Operational State . . . . . . . . . . . . . . . . 151
15.17. Radio Failure Causes . . . . . . . . . . . . . . . . . . 151 15.17. Radio Failure Causes . . . . . . . . . . . . . . . . . . 152
15.18. Result Code . . . . . . . . . . . . . . . . . . . . . . 152 15.18. Result Code . . . . . . . . . . . . . . . . . . . . . . 152
15.19. Returned Message Element Reason . . . . . . . . . . . . 152 15.19. Returned Message Element Reason . . . . . . . . . . . . 152
15.20. WTP Board Data Type . . . . . . . . . . . . . . . . . . 152 15.20. WTP Board Data Type . . . . . . . . . . . . . . . . . . 152
15.21. WTP Descriptor Type . . . . . . . . . . . . . . . . . . 152 15.21. WTP Descriptor Type . . . . . . . . . . . . . . . . . . 153
15.22. WTP Fallback Mode . . . . . . . . . . . . . . . . . . . 153 15.22. WTP Fallback Mode . . . . . . . . . . . . . . . . . . . 153
15.23. WTP Frame Tunnel Mode . . . . . . . . . . . . . . . . . 153 15.23. WTP Frame Tunnel Mode . . . . . . . . . . . . . . . . . 153
15.24. WTP MAC Type . . . . . . . . . . . . . . . . . . . . . . 153 15.24. WTP MAC Type . . . . . . . . . . . . . . . . . . . . . . 154
15.25. WTP Radio Stats Failure Type . . . . . . . . . . . . . . 154 15.25. WTP Radio Stats Failure Type . . . . . . . . . . . . . . 154
15.26. WTP Reboot Stats Failure Type . . . . . . . . . . . . . 154 15.26. WTP Reboot Stats Failure Type . . . . . . . . . . . . . 154
16. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 155 16. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 155
17. References . . . . . . . . . . . . . . . . . . . . . . . . . 156 17. References . . . . . . . . . . . . . . . . . . . . . . . . . 156
17.1. Normative References . . . . . . . . . . . . . . . . . . 156 17.1. Normative References . . . . . . . . . . . . . . . . . . 156
17.2. Informational References . . . . . . . . . . . . . . . . 157 17.2. Informational References . . . . . . . . . . . . . . . . 157
Editors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 159 Editors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 159
Intellectual Property and Copyright Statements . . . . . . . . . 160 Intellectual Property and Copyright Statements . . . . . . . . . 160
1. Introduction 1. Introduction
skipping to change at page 25, line 10 skipping to change at page 25, line 10
description of the firmware download process). The WTP description of the firmware download process). The WTP
initializes the EchoInterval timer (see Section 4.7), and initializes the EchoInterval timer (see Section 4.7), and
transmits the Image Data Request message (see Section 9.1.1) transmits the Image Data Request message (see Section 9.1.1)
requesting the start of the firmware download. requesting the start of the firmware download.
AC: This state transition occurs when the AC receives the Image AC: This state transition occurs when the AC receives the Image
Data Request message from the WTP, after having sent its Join Data Request message from the WTP, after having sent its Join
Response to the WTP. The AC stops the WaitJoin timer. The AC Response to the WTP. The AC stops the WaitJoin timer. The AC
MUST transmit an Image Data Response message (see MUST transmit an Image Data Response message (see
Section 9.1.2) to the WTP, which includes a portion of the Section 9.1.2) to the WTP, which includes a portion of the
firmware. The AC MUST start the ImageDataStartTimer timer (see firmware.
Section 4.7).
Join to Configure (g): This state transition is used by the WTP and Join to Configure (g): This state transition is used by the WTP and
the AC to exchange configuration information. the AC to exchange configuration information.
WTP: The WTP enters the Configure state when it receives a WTP: The WTP enters the Configure state when it receives a
successful Join Response message, and determines that the successful Join Response message, and determines that the
included Image Identifier message element is the same as its included Image Identifier message element is the same as its
currently running image. The WTP transmits the Configuration currently running image. The WTP transmits the Configuration
Status Request message (see Section 8.2) to the AC with message Status Request message (see Section 8.2) to the AC with message
elements describing its current configuration. elements describing its current configuration.
skipping to change at page 26, line 31 skipping to change at page 26, line 31
WTP: The WTP enters the Image Data state when it receives an WTP: The WTP enters the Image Data state when it receives an
Image Data Response message indicating that the AC has more Image Data Response message indicating that the AC has more
data to send. This state transition also occurs when the WTP data to send. This state transition also occurs when the WTP
receives the subsequent Image Data Requests, at which time it receives the subsequent Image Data Requests, at which time it
resets the ImageDataStartTimer time to ensure it receives the resets the ImageDataStartTimer time to ensure it receives the
next expected Image Data Request from the AC. next expected Image Data Request from the AC.
AC: This state transition occurs when the AC receives the Image AC: This state transition occurs when the AC receives the Image
Data Response message from the WTP while already in the Image Data Response message from the WTP while already in the Image
Data state. The AC disables the ImageDataStartTimer timer. Data state.
Image Data to Reset (k): This state transition is used to reset the Image Data to Reset (k): This state transition is used to reset the
DTLS connection prior to restarting the WTP after an image DTLS connection prior to restarting the WTP after an image
download. download.
WTP: When an image download completes, or if the WTP: When an image download completes, or if the
ImageDataStartTimer timer expires, the WTP enters the Reset ImageDataStartTimer timer expires, the WTP enters the Reset
state. The WTP MAY also transition to this state upon state. The WTP MAY also transition to this state upon
receiving an Image Data Response message from the AC (see receiving an Image Data Response message from the AC (see
Section 9.1.2) indicating a failure. Section 9.1.2) indicating a failure.
AC: The AC enters the Reset state either when the image transfer AC: The AC enters the Reset state either when the image transfer
has successfully completed, an error occurs during the image has successfully completed or an error occurs during the image
download process or if the ImageDataStartTimer timer expires. download process.
Image Data to DTLS Teardown (l): This transition occurs when the Image Data to DTLS Teardown (l): This transition occurs when the
firmware download process aborts due to a DTLS error. firmware download process aborts due to a DTLS error.
WTP: The WTP enters this state when it receives one of the WTP: The WTP enters this state when it receives one of the
following DTLS notifications: DTLSAborted, following DTLS notifications: DTLSAborted,
DTLSReassemblyFailure or DTLSPeerDisconnect (see DTLSReassemblyFailure or DTLSPeerDisconnect (see
Section 2.3.2.2). The WTP MAY tear down the DTLS session if it Section 2.3.2.2). The WTP MAY tear down the DTLS session if it
receives frequent DTLSDecapFailure notifications. The WTP receives frequent DTLSDecapFailure notifications. The WTP
starts the DTLSSessionDelete timer (see Section 4.7.6). starts the DTLSSessionDelete timer (see Section 4.7.6).
skipping to change at page 35, line 41 skipping to change at page 35, line 41
<------ Finished <------ Finished
Figure 5: DTLS Handshake Figure 5: DTLS Handshake
DTLS, as specified, provides its own retransmit timers with an DTLS, as specified, provides its own retransmit timers with an
exponential back-off. [RFC4347] does not specify how long exponential back-off. [RFC4347] does not specify how long
retransmissions should continue. Consequently, timing out incomplete retransmissions should continue. Consequently, timing out incomplete
DTLS handshakes is entirely the responsibility of the CAPWAP module. DTLS handshakes is entirely the responsibility of the CAPWAP module.
The DTLS implementation used by CAPWAP MUST support TLS Session The DTLS implementation used by CAPWAP MUST support TLS Session
Resumption. Session resumption is used to establish the DTLS session Resumption. Session resumption is typically used to establish the
used for the data channel. The DTLS implementation on the WTP MUST DTLS session used for the data channel. Since the data channel uses
return some unique identifier to the CAPWAP module to enable different port numbers than the control channel, the DTLS
subsequent establishment of a DTLS-encrypted data channel, if implementation on the WTP MUST provide an interface that allows the
necessary. CAPWAP module to request session resumption despite the use of the
different port numbers (TLS implementations usually attempt session
resumption only when connecting to the same IP address and port
number). Note that session resumption is not guaranteed to occur,
and a full DTLS handshake may occur instead.
The DTLS implementation used by CAPWAP MUST use replay detection, per The DTLS implementation used by CAPWAP MUST use replay detection, per
Section 3.3 of [RFC4347]. Since the CAPWAP protocol handles Section 3.3 of [RFC4347]. Since the CAPWAP protocol handles
retransmissions by re-encrypting lost frames, any duplicate DTLS retransmissions by re-encrypting lost frames, any duplicate DTLS
frames are either unintentional or malicious, and should be silently frames are either unintentional or malicious, and should be silently
discarded. discarded.
2.4.2. DTLS Session Establishment 2.4.2. DTLS Session Establishment
The WTP, either through the Discovery process, or through pre- The WTP, either through the Discovery process, or through pre-
skipping to change at page 41, line 29 skipping to change at page 41, line 29
UDP/UDP-Lite transport protocols. The CAPWAP Transport Protocol UDP/UDP-Lite transport protocols. The CAPWAP Transport Protocol
message element Section 4.6.14 describes the rules to use in message element Section 4.6.14 describes the rules to use in
determining which transport protocol is to be used. determining which transport protocol is to be used.
3.1. UDP Transport 3.1. UDP Transport
One of the CAPWAP protocol requirements is to allow a WTP to reside One of the CAPWAP protocol requirements is to allow a WTP to reside
behind a middlebox, firewall and/or Network Address Translation (NAT) behind a middlebox, firewall and/or Network Address Translation (NAT)
device. Since a CAPWAP session is initiated by the WTP (client) to device. Since a CAPWAP session is initiated by the WTP (client) to
the well-known UDP port of the AC (server), the use of UDP is a the well-known UDP port of the AC (server), the use of UDP is a
logical choice. The UDP checksum field in CAPWAP packets MUST be set logical choice. When CAPWAP is run over IPv4, the UDP checksum field
to zero. in CAPWAP packets MUST be set to zero.
CAPWAP protocol control packets sent from the WTP to the AC use the CAPWAP protocol control packets sent from the WTP to the AC use the
CAPWAP control channel, as defined in Section 1.4. The CAPWAP CAPWAP control channel, as defined in Section 1.4. The CAPWAP
control port at the AC is the well known UDP port 5246. The CAPWAP control port at the AC is the well known UDP port 5246. The CAPWAP
control port at the WTP can be any port selected by the WTP. control port at the WTP can be any port selected by the WTP.
CAPWAP protocol data packets sent from the WTP to the AC use the CAPWAP protocol data packets sent from the WTP to the AC use the
CAPWAP data channel, as defined in Section 1.4. The CAPWAP data port CAPWAP data channel, as defined in Section 1.4. The CAPWAP data port
at the AC is the well known UDP port 5247. If an AC permits the at the AC is the well known UDP port 5247. If an AC permits the
administrator to change the CAPWAP control port, the CAPWAP data port administrator to change the CAPWAP control port, the CAPWAP data port
skipping to change at page 43, line 11 skipping to change at page 43, line 11
SRV record MAY specify a non-default port number for the control SRV record MAY specify a non-default port number for the control
channel; the port number for the data channel is the next port channel; the port number for the data channel is the next port
number (control channel port + 1). number (control channel port + 1).
An AC MAY also communicate alternative ACs to the WTP within the An AC MAY also communicate alternative ACs to the WTP within the
Discovery Response message through the AC IPv4 List (see Discovery Response message through the AC IPv4 List (see
Section 4.6.2) and AC IPv6 List (see Section 4.6.2). The addresses Section 4.6.2) and AC IPv6 List (see Section 4.6.2). The addresses
provided in these two message elements are intended to help the WTP provided in these two message elements are intended to help the WTP
discover additional ACs through means other than those listed above. discover additional ACs through means other than those listed above.
The AC Name with Index message element (see Section 4.6.5), is used The AC Name with Priority message element (see Section 4.6.5), is
to communicate a list of preferred ACs to the WTP. The WTP SHOULD used to communicate a list of preferred ACs to the WTP. The WTP
attempt to utilize the ACs listed in the order provided by the AC. SHOULD attempt to utilize the ACs listed in the order provided by the
The Name to IP Address mapping is handled via the Discovery message AC. The Name to IP Address mapping is handled via the Discovery
exchange, in which the ACs provide their identity in the AC Name (see message exchange, in which the ACs provide their identity in the AC
Section 4.6.4) message element in the Discovery Response message. Name (see Section 4.6.4) message element in the Discovery Response
message.
Once the WTP has received Discovery Response messages from the Once the WTP has received Discovery Response messages from the
candidate ACs, it MAY use other factors to determine the preferred candidate ACs, it MAY use other factors to determine the preferred
AC. For instance, each binding defines a WTP Radio Information AC. For instance, each binding defines a WTP Radio Information
message element (see Section 2.1), which the AC includes in Discovery message element (see Section 2.1), which the AC includes in Discovery
Response messages. The presence of one or more of these message Response messages. The presence of one or more of these message
elements is used to identify the CAPWAP bindings supported by the AC. elements is used to identify the CAPWAP bindings supported by the AC.
A WTP MAY connect to an AC based on the supported bindings A WTP MAY connect to an AC based on the supported bindings
advertised. advertised.
skipping to change at page 60, line 22 skipping to change at page 60, line 22
The table below lists the CAPWAP protocol Message Elements and their The table below lists the CAPWAP protocol Message Elements and their
Type values. Type values.
CAPWAP Message Element Type Value CAPWAP Message Element Type Value
AC Descriptor 1 AC Descriptor 1
AC IPv4 List 2 AC IPv4 List 2
AC IPv6 List 3 AC IPv6 List 3
AC Name 4 AC Name 4
AC Name with Index 5 AC Name with Priority 5
AC Timestamp 6 AC Timestamp 6
Add MAC ACL Entry 7 Add MAC ACL Entry 7
Add Station 8 Add Station 8
Reserved 9 Reserved 9
CAPWAP Control IPV4 Address 10 CAPWAP Control IPV4 Address 10
CAPWAP Control IPV6 Address 11 CAPWAP Control IPV6 Address 11
CAPWAP Local IPV4 Address 30 CAPWAP Local IPV4 Address 30
CAPWAP Local IPV6 Address 50 CAPWAP Local IPV6 Address 50
CAPWAP Timers 12 CAPWAP Timers 12
CAPWAP Transport Protocol 51 CAPWAP Transport Protocol 51
skipping to change at page 62, line 12 skipping to change at page 62, line 12
Active WTPs: The number of WTPs currently attached to the AC Active WTPs: The number of WTPs currently attached to the AC
Max WTPs: The maximum number of WTPs supported by the AC Max WTPs: The maximum number of WTPs supported by the AC
Security: A 8 bit mask specifying the authentication credential Security: A 8 bit mask specifying the authentication credential
type supported by the AC (See Section 2.4.4). The field has the type supported by the AC (See Section 2.4.4). The field has the
following format: following format:
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Reserved |S|X|U| |Reserved |S|X|R|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Reserved: A set of reserved bits for future use. All Reserved: A set of reserved bits for future use. All
implementations complying with this protocol MUST set to zero implementations complying with this protocol MUST set to zero
any bits that are reserved in the version of the protocol any bits that are reserved in the version of the protocol
supported by that implementation. Receivers MUST ignore all supported by that implementation. Receivers MUST ignore all
bits not defined for the version of the protocol they support. bits not defined for the version of the protocol they support.
S: The AC supports the pre-shared secret authentication, as S: The AC supports the pre-shared secret authentication, as
described in Section 12.6. described in Section 12.6.
X: The AC supports X.509 Certificate authentication, as X: The AC supports X.509 Certificate authentication, as
described in Section 12.7. described in Section 12.7.
U: This bit is set to zero and is unused. R: A reserved bit for future use. All implementations complying
with this protocol MUST set to zero any bits that are reserved
in the version of the protocol supported by that
implementation. Receivers MUST ignore all bits not defined for
the version of the protocol they support.
R-MAC Field: The AC supports the optional Radio MAC Address field R-MAC Field: The AC supports the optional Radio MAC Address field
in the CAPWAP transport Header (see Section 4.3). The following in the CAPWAP transport Header (see Section 4.3). The following
enumerated values are supported: enumerated values are supported:
0 - Reserved 0 - Reserved
1 - Supported 1 - Supported
2 - Not Supported 2 - Not Supported
skipping to change at page 63, line 7 skipping to change at page 63, line 13
for the version of the protocol they support. for the version of the protocol they support.
DTLS Policy: The AC communicates its policy on the use of DTLS for DTLS Policy: The AC communicates its policy on the use of DTLS for
the CAPWAP data channel. The AC MAY communicate more than one the CAPWAP data channel. The AC MAY communicate more than one
supported option, represented by the bit field below. The WTP supported option, represented by the bit field below. The WTP
MUST abide by one of the options communicated by AC. The field MUST abide by one of the options communicated by AC. The field
has the following format: has the following format:
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Reserved |D|C|U| |Reserved |D|C|R|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Reserved: A set of reserved bits for future use. All Reserved: A set of reserved bits for future use. All
implementations complying with this protocol MUST set to zero implementations complying with this protocol MUST set to zero
any bits that are reserved in the version of the protocol any bits that are reserved in the version of the protocol
supported by that implementation. Receivers MUST ignore all supported by that implementation. Receivers MUST ignore all
bits not defined for the version of the protocol they support. bits not defined for the version of the protocol they support.
D: DTLS Enabled Data Channel Supported D: DTLS Enabled Data Channel Supported
C: Clear Text Data Channel Supported C: Clear Text Data Channel Supported
U: This bit is set to zero and is unused. R: A reserved bit for future use. All implementations complying
with this protocol MUST set to zero any bits that are reserved
in the version of the protocol supported by that
implementation. Receivers MUST ignore all bits not defined for
the version of the protocol they support.
AC Information Sub-Element: The AC Descriptor message element AC Information Sub-Element: The AC Descriptor message element
contains multiple AC Information sub-elements, and defines two contains multiple AC Information sub-elements, and defines two
sub-types, each of which MUST be present. The AC Information sub- sub-types, each of which MUST be present. The AC Information sub-
element has the following format: element has the following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AC Information Vendor Identifier | | AC Information Vendor Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AC Information Type | AC Information Length | | AC Information Type | AC Information Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AC Information Data... | AC Information Data...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AC Information Vendor Identifier: A 32-bit value containing the AC Information Vendor Identifier: A 32-bit value containing the
IANA assigned "SMI Network Management Private Enterprise Codes" IANA assigned "SMI Network Management Private Enterprise Codes"
AC Information Type: Vendor specific encoding of AC information
AC Information Type: Vendor specific encoding of AC information. in the UTF-8 format [RFC3629]. The following enumerated values
The following enumerated values are supported. Both the are supported. Both the Hardware and Software Version sub-
Hardware and Software Version sub-elements MUST be included in elements MUST be included in the AC Descriptor message element.
the AC Descriptor message element. The values listed below are The values listed below are used in conjunction with the AC
used in conjunction with the AC Information Vendor Identifier Information Vendor Identifier field, whose value MUST be set to
field, whose value MUST be set to zero (0). zero (0). This field, combined with the AC Information Vendor
Identifier set to a non-zero (0) value, allows vendors to use a
private namespace.
4 - Hardware Version: The AC's hardware version number. 4 - Hardware Version: The AC's hardware version number.
5 - Software Version: The AC's Software (firmware) version 5 - Software Version: The AC's Software (firmware) version
number. number.
AC Information Length: Length of vendor specific encoding of AC AC Information Length: Length of vendor specific encoding of AC
information, with a maximum size of 1024. information, with a maximum size of 1024.
AC Information Data: Vendor specific encoding of AC information. AC Information Data: Vendor specific encoding of AC information.
skipping to change at page 65, line 28 skipping to change at page 65, line 43
| Name ... | Name ...
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Type: 4 for AC Name Type: 4 for AC Name
Length: >= 1 Length: >= 1
Name: A variable length UTF-8 encoded string [RFC3629] containing Name: A variable length UTF-8 encoded string [RFC3629] containing
the AC's name, whose maximum size MUST NOT exceed 512 bytes. the AC's name, whose maximum size MUST NOT exceed 512 bytes.
4.6.5. AC Name with Index 4.6.5. AC Name with Priority
The AC Name with Index message element is sent by the AC to the WTP The AC Name with Priority message element is sent by the AC to the
to configure preferred ACs. The number of instances of this message WTP to configure preferred ACs. The number of instances of this
element is equal to the number of ACs configured on the WTP. The WTP message element is equal to the number of ACs configured on the WTP.
also uses this message element to send its configuration to the AC. The WTP also uses this message element to send its configuration to
the AC.
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Priority | AC Name... | Priority | AC Name...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 5 for AC Name with Index Type: 5 for AC Name with Priority
Length: >= 2 Length: >= 2
Priority: A value between 1 and 255 specifying the priority order Priority: A value between 1 and 255 specifying the priority order
of the preferred AC. For instance, the value of one (1) is used of the preferred AC. For instance, the value of one (1) is used
to set the primary AC, the value of two (2) is used to set the to set the primary AC, the value of two (2) is used to set the
secondary, etc. secondary, etc.
AC Name: A variable length UTF-8 encoded string [RFC3629] AC Name: A variable length UTF-8 encoded string [RFC3629]
containing the AC name, whose maximum size MUST NOT exceed 512 containing the AC name, whose maximum size MUST NOT exceed 512
skipping to change at page 78, line 45 skipping to change at page 79, line 13
following enumerated values are supported: following enumerated values are supported:
1 - Image data is included 1 - Image data is included
2 - Last Image Data Block is included (EOF) 2 - Last Image Data Block is included (EOF)
5 - An error occurred. Transfer is aborted 5 - An error occurred. Transfer is aborted
Data: The Image Data field contains up to 1024 characters, and its Data: The Image Data field contains up to 1024 characters, and its
length is inferred from this message element's length field. If length is inferred from this message element's length field. If
the block being sent is the last one, the Opcode is set to 2. The the block being sent is the last one, the Data Type field is set
AC MAY opt to abort the data transfer by setting the Opcode to 5. to 2. The AC MAY opt to abort the data transfer by setting the
When the Opcode is 5, the Value field has a zero length. Data Type field to 5. When the Data Type field is 5, the Value
field has a zero length.
4.6.26. Image Identifier 4.6.26. 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.
skipping to change at page 85, line 40 skipping to change at page 86, line 4
element could not be applied by the WTP. The following enumerated element could not be applied by the WTP. The following enumerated
values are supported: values are supported:
0 - Reserved 0 - Reserved
1 - Unknown Message Element 1 - Unknown Message Element
2 - Unsupported Message Element 2 - Unsupported Message Element
3 - Unknown Message Element Value 3 - Unknown Message Element Value
4 - Unsupported Message Element Value 4 - Unsupported Message Element Value
Length: The length of the Message Element field, which MUST NOT Length: The length of the Message Element field, which MUST NOT
exceed 65535 octets. exceed 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.36. Session ID
The Session ID message element value contains a randomly generated The Session ID message element value contains a randomly generated
unsigned 32-bit integer. unsigned 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session ID | | Session ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session ID | | Session ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 35 for Session ID Type: 35 for Session ID
Length: 32 Length: 32
Session ID: A 32-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.37. Statistics Timer
The Statistics Timer message element value is used by the AC to The Statistics Timer message element value is used by the AC to
inform the WTP of the frequency with which it expects to receive inform the WTP of the frequency with which it expects to receive
updated statistics. updated statistics.
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
skipping to change at page 87, line 45 skipping to change at page 88, line 4
The WTP Board Data message element is sent by the WTP to the AC and The WTP Board Data message element is sent by the WTP to the AC and
contains information about the hardware present. contains information about the hardware present.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor Identifier | | Vendor Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Board Data Sub-Element... | Board Data Sub-Element...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 38 for WTP Board Data Type: 38 for WTP Board Data
Length: >=14 Length: >=14
Vendor Identifier: A 32-bit value containing the IANA assigned "SMI Vendor Identifier: A 32-bit value containing the IANA assigned "SMI
Network Management Private Enterprise Codes", identifying the WTP Network Management Private Enterprise Codes", identifying the WTP
hardware manufacturer. hardware manufacturer. The Vendor Identifier field MUST NOT be
set to zero.
Board Data Sub-Element: The WTP Board Data message element contains Board Data Sub-Element: The WTP Board Data message element contains
multiple Board Data sub-elements, some of which are mandatory and multiple Board Data sub-elements, some of which are mandatory and
some are optional, as described below. The Board Data sub-element some are optional, as described below. The Board Data Type values
has the following format: are not extensible by vendors, and is therefore not coupled along
with the Vendor Identifier field. The Board Data sub-element has
the following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Board Data Type | Board Data Length | | Board Data Type | Board Data Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Board Data Value... | Board Data Value...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Board Data Type: The Board Data Type field identifies the data Board Data Type: The Board Data Type field identifies the data
skipping to change at page 89, line 14 skipping to change at page 89, line 20
4.6.40. WTP Descriptor 4.6.40. WTP Descriptor
The WTP Descriptor message element is used by a WTP to communicate The WTP Descriptor message element is used by a WTP to communicate
its current hardware and software (firmware) configuration. The its current hardware and software (firmware) configuration. The
value contains the following fields. value contains the following fields.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max Radios | Radios in use | Encryption Sub-Element | | Max Radios | Radios in use | Num Encrypt |Encryp Sub-Elmt|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Descriptor Sub-Element... | Encryption Sub-Element | Descriptor Sub-Element...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 39 for WTP Descriptor Type: 39 for WTP Descriptor
Length: >= 31 Length: >= 31
Max Radios: An 8-bit value representing the number of radios (where Max Radios: An 8-bit value representing the number of radios (where
each radio is identified via the Radio ID field) supported by the each radio is identified via the Radio ID field) supported by the
WTP. WTP.
Radios in use: An 8-bit value representing the number of radios in Radios in use: An 8-bit value representing the number of radios in
use in the WTP. use in the WTP.
Num Encrypt: The number of 3 byte Encryption Sub-Elements that
follow this field. The value of the Num Encrypt field MUST be
between one (1) and 255.
Encryption Sub-Element: The WTP Descriptor message element MUST Encryption Sub-Element: The WTP Descriptor message element MUST
contain at least one Encryption sub-element. One sub-element is contain at least one Encryption sub-element. One sub-element is
present for each binding supported by the WTP. The Encryption present for each binding supported by the WTP. The Encryption
sub-element has the following format: sub-element has the following format:
0 1 2 0 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Resvd| WBID | Encryption Capabilities | |Resvd| WBID | Encryption Capabilities |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 90, line 29 skipping to change at page 90, line 40
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Descriptor Type | Descriptor Length | | Descriptor Type | Descriptor Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Descriptor Data... | Descriptor Data...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Descriptor Vendor Identifier: A 32-bit value containing the IANA Descriptor Vendor Identifier: A 32-bit value containing the IANA
assigned "SMI Network Management Private Enterprise Codes". assigned "SMI Network Management Private Enterprise Codes".
Descriptor Type: The Descriptor Type field identifies the data Descriptor Type: The Descriptor Type field identifies the data
being encoded. The CAPWAP protocol defines the following being encoded. The format of the data is vendor specific
values, and each of these types identify whether their presence encoded in the UTF-8 format [RFC3629]. The CAPWAP protocol
is mandatory or optional. The values listed below are used in defines the following values, and each of these types identify
conjunction with the Descriptor Vendor Identifier field, whose whether their presence is mandatory or optional. The values
value MUST be set to zero (0). listed below are used in conjunction with the Descriptor Vendor
Identifier field, whose value MUST be set to zero (0). This
field, combined with the Descriptor Vendor Identifier set to a
non-zero (0) value, allows vendors to use a private namespace.
0 - Hardware Version: The WTP hardware version number MUST be 0 - Hardware Version: The WTP hardware version number MUST be
present. present.
1 - Active Software Version: The WTP running software version 1 - Active Software Version: The WTP running software version
number MUST be present. number MUST be present.
2 - Boot Version: The WTP boot loader version number MUST be 2 - Boot Version: The WTP boot loader version number MUST be
present. present.
skipping to change at page 92, line 34 skipping to change at page 92, line 47
E: The 802.3 Frame Tunnel Mode requires the WTP and AC to E: The 802.3 Frame Tunnel Mode requires the WTP and AC to
encapsulate all user payload as native IEEE 802.3 frames (see encapsulate all user payload as native IEEE 802.3 frames (see
Section 4.4). All user traffic is tunneled to the AC. This value Section 4.4). All user traffic is tunneled to the AC. This value
MUST NOT be used when the WTP MAC Type is set to Split-MAC. MUST NOT be used when the WTP MAC Type is set to Split-MAC.
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.
U: This bit is set to zero and is unused. R: A reserved bit for future use. All implementations complying
with this protocol MUST set to zero any bits that are reserved in
the version of the protocol supported by that implementation.
Receivers MUST ignore all bits not defined for the version of the
protocol they support.
4.6.43. WTP MAC Type 4.6.43. WTP MAC Type
The WTP MAC-Type message element allows the WTP to communicate its The WTP MAC-Type message element allows the WTP to communicate its
mode of operation to the AC. A WTP that advertises support for both mode of operation to the AC. A WTP that advertises support for both
modes allows the AC to select the mode to use, based on local policy. modes allows the AC to select the mode to use, based on local policy.
0 0
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
skipping to change at page 98, line 51 skipping to change at page 99, line 13
to the AC with which the WTP has joined. to the AC with which the WTP has joined.
Default: 30 Default: 30
4.7.8. IdleTimeout 4.7.8. IdleTimeout
The default Idle Timeout is 300 seconds. The default Idle Timeout is 300 seconds.
4.7.9. ImageDataStartTimer 4.7.9. ImageDataStartTimer
The number of seconds the AC or WTP will wait for its peer to The number of seconds the WTP will wait for its peer to transmit the
transmit the Image Data Request. Image Data Request.
Default: 30 Default: 30
4.7.10. MaxDiscoveryInterval 4.7.10. MaxDiscoveryInterval
The maximum time allowed between sending Discovery Request messages, The maximum time allowed between sending Discovery Request messages,
in seconds. This value MUST be no less than 2 seconds and no greater in seconds. This value MUST be no less than 2 seconds and no greater
than 180 seconds. than 180 seconds.
Default: 20 seconds. Default: 20 seconds.
4.7.11. ReportInterval 4.7.11. ReportInterval
The ReportInterval is used by the WTP to determine the interval the The ReportInterval is used by the WTP to determine the interval the
WTP uses between sending the Decryption Error message elements to the WTP uses between sending the Decryption Error message elements to
AC to decryption errors, in seconds. inform the AC of decryption errors, in seconds.
The default Report Interval is 120 seconds. The default Report Interval is 120 seconds.
4.7.12. RetransmitInterval 4.7.12. RetransmitInterval
The minimum time, in seconds, in which a non-acknowledged CAPWAP The minimum time, in seconds, in which a non-acknowledged CAPWAP
packet will be retransmitted. packet will be retransmitted.
Default: 3 Default: 3
skipping to change at page 116, line 5 skipping to change at page 116, line 5
o Radio Administrative State, see Section 4.6.32 o Radio Administrative State, see Section 4.6.32
o Statistics Timer, see Section 4.6.37 o Statistics Timer, see Section 4.6.37
o WTP Reboot Statistics, see Section 4.6.46 o WTP Reboot Statistics, see Section 4.6.46
The following message elements MAY be included in the Configuration The following message elements MAY be included in the Configuration
Status Request message. Status Request message.
o AC Name with Index, 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.47
o Vendor Specific Payload, see Section 4.6.38 o Vendor Specific Payload, see Section 4.6.38
8.3. Configuration Status Response 8.3. Configuration Status Response
The Configuration Status Response message is sent by an AC and The Configuration Status Response message is sent by an AC and
skipping to change at page 117, line 38 skipping to change at page 117, line 38
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.28).
The Configuration Update Request is sent by the AC when in the Run The Configuration Update Request is sent by the AC when in the Run
State. The WTP does not transmit this message. State. The WTP does not transmit this message.
One or more of the following message elements MAY be included in the One or more of the following message elements MAY be included in the
Configuration Update message. Configuration Update message.
o AC Name with Index, see Section 4.6.5 o AC Name with 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
skipping to change at page 140, line 17 skipping to change at page 140, line 17
done based on which DTLS session decrypted the packet. Otherwise one done based on which DTLS session decrypted the packet. Otherwise one
authenticated WTP could spoof another authenticated WTP by altering authenticated WTP could spoof another authenticated WTP by altering
the Session ID in the encrypted CAPWAP header. the Session ID in the encrypted CAPWAP header.
It should be noted that when the CAPWAP data channel is unencrypted, It should be noted that when the CAPWAP data channel is unencrypted,
the WTP Session ID is exposed and possibly known to adversaries and the WTP Session ID is exposed and possibly known to adversaries and
other WTPs. This would allow the forgery of the source of data- other WTPs. This would allow the forgery of the source of data-
channel traffic. This, however, should not be a surprise for channel traffic. This, however, should not be a surprise for
unencrypted data channels. When the data channel is encrypted, the unencrypted data channels. When the data channel is encrypted, the
Session ID is not exposed, and therefore can safely be used to Session ID is not exposed, and therefore can safely be used to
associate a data and control channel. The 64-bit length of the associate a data and control channel. The 128-bit length of the
Session ID mitigates online guessing attacks where an adversarial, Session ID mitigates online guessing attacks where an adversarial,
authenticated WTP tries to correlate his own data channel with authenticated WTP tries to correlate his own data channel with
another WTP's control channel. Note that for encrypted data another WTP's control channel. Note that for encrypted data
channels, the Session ID should only be used for correlation for the channels, the Session ID should only be used for correlation for the
first packet immediately after the initial DTLS handshake. Future first packet immediately after the initial DTLS handshake. Future
correlation should instead be done via identification of a packet's correlation should instead be done via identification of a packet's
DTLS session. DTLS session.
12.3. Discovery or DTLS Setup Attacks 12.3. Discovery or DTLS Setup Attacks
skipping to change at page 149, line 4 skipping to change at page 149, line 4
registry, whose format is: registry, whose format is:
Flag Field Name Bit Position Reference Flag Field Name Bit Position Reference
15.6. CAPWAP Message Element Type 15.6. 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 52 are allocated in this
specification, and can be found in Section 4.5.1.1. This namespace specification, and can be found in Section 4.5.1.1.
is managed by IANA and assignments require a Expert Review. IANA
will create the CAPWAP Message Element Type registry, whose format The 16 bit namespace is further divided into blocks of addresses that
is: are reserved for specific CAPWAP wireless bindings. The following
blocks are reserved:
CAPWAP Protocol Message Elements 1 - 1023
IEEE 802.11 Message Elements 1024 - 2047
EPCGlobal Message Elements 3072 - 4095
This namespace is managed by IANA and assignments require a Expert
Review. IANA will create the CAPWAP Message Element Type registry,
whose format is:
CAPWAP Message Element Type Value Reference CAPWAP Message Element Type Value Reference
15.7. Wireless Binding Identifiers 15.7. Wireless Binding Identifiers
The Wireless Binding Identifier (WBID) field in the CAPWAP header The Wireless Binding Identifier (WBID) field in the CAPWAP header
(see Section 4.3) is used to identify the wireless technology (see Section 4.3) is used to identify the wireless technology
associated with the packet. This specification allocates the values associated with the packet. This specification allocates the values
one (1) and three (3). Due to the limited address space available, a one (1) and three (3). Due to the limited address space available, a
new WBID request requires Expert Review. IANA will create the CAPWAP new WBID request requires Expert Review. IANA will create the CAPWAP
skipping to change at page 157, line 19 skipping to change at page 157, line 19
for IP version 6", RFC 1981, August 1996. for IP version 6", RFC 1981, August 1996.
[RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for [RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for
specifying the location of services (DNS SRV)", RFC 2782, specifying the location of services (DNS SRV)", RFC 2782,
February 2000. February 2000.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003. 10646", STD 63, RFC 3629, November 2003.
[I-D.ietf-capwap-protocol-binding-ieee80211] [I-D.ietf-capwap-protocol-binding-ieee80211]
Calhoun, P., "CAPWAP Protocol Binding for IEEE 802.11", Montemurro, M., Stanley, D., and P. Calhoun, "CAPWAP
draft-ietf-capwap-protocol-binding-ieee80211-07 (work in Protocol Binding for IEEE 802.11",
progress), July 2008. draft-ietf-capwap-protocol-binding-ieee80211-08 (work in
progress), September 2008.
[I-D.ietf-capwap-dhc-ac-option] [I-D.ietf-capwap-dhc-ac-option]
Calhoun, P., "CAPWAP Access Controller DHCP Option", Calhoun, P., "CAPWAP Access Controller DHCP Option",
draft-ietf-capwap-dhc-ac-option-01 (work in progress), draft-ietf-capwap-dhc-ac-option-01 (work in progress),
March 2008. March 2008.
[FRAME-EXT] [FRAME-EXT]
IEEE, "IEEE Standard 802.3as-2006", 2005. IEEE, "IEEE Standard 802.3as-2006", 2005.
17.2. Informational References 17.2. Informational References
 End of changes. 61 change blocks. 
108 lines changed or deleted 149 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/