draft-ietf-capwap-protocol-binding-ieee80211-11.txt   draft-ietf-capwap-protocol-binding-ieee80211-12.txt 
Network Working Group P. Calhoun, Editor Network Working Group P. Calhoun, Editor
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track M. Montemurro, Editor Intended status: Standards Track M. Montemurro, Editor
Expires: 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 Binding for IEEE 802.11 CAPWAP Protocol Binding for IEEE 802.11
draft-ietf-capwap-protocol-binding-ieee80211-11 draft-ietf-capwap-protocol-binding-ieee80211-12
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 37 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 17, 2009. This Internet-Draft will expire on May 4, 2009.
Abstract Abstract
Wireless LAN product architectures have evolved from single Wireless LAN product architectures have evolved from single
autonomous access points to systems consisting of a centralized autonomous access points to systems consisting of a centralized
Access Controller (AC) and Wireless Termination Points (WTPs). The Access Controller (AC) and Wireless Termination Points (WTPs). The
general goal of centralized control architectures is to move access general goal of centralized control architectures is to move access
control, including user authentication and authorization, mobility control, including user authentication and authorization, mobility
management and radio management from the single access point to a management and radio management from the single access point to a
centralized controller. centralized controller.
skipping to change at page 4, line 11 skipping to change at page 4, line 11
10.3. CAPWAP Message Element Type . . . . . . . . . . . . . . . 75 10.3. CAPWAP Message Element Type . . . . . . . . . . . . . . . 75
10.4. IEEE 802.11 Key Status . . . . . . . . . . . . . . . . . 75 10.4. IEEE 802.11 Key Status . . . . . . . . . . . . . . . . . 75
10.5. IEEE 802.11 QoS . . . . . . . . . . . . . . . . . . . . . 76 10.5. IEEE 802.11 QoS . . . . . . . . . . . . . . . . . . . . . 76
10.6. IEEE 802.11 Auth Type . . . . . . . . . . . . . . . . . . 76 10.6. IEEE 802.11 Auth Type . . . . . . . . . . . . . . . . . . 76
10.7. IEEE 802.11 Antenna Combiner . . . . . . . . . . . . . . 76 10.7. IEEE 802.11 Antenna Combiner . . . . . . . . . . . . . . 76
10.8. IEEE 802.11 Antenna Selection . . . . . . . . . . . . . . 76 10.8. IEEE 802.11 Antenna Selection . . . . . . . . . . . . . . 76
10.9. IEEE 802.11 Session Key Flags . . . . . . . . . . . . . . 77 10.9. IEEE 802.11 Session Key Flags . . . . . . . . . . . . . . 77
10.10. IEEE 802.11 Tagging Policy . . . . . . . . . . . . . . . 77 10.10. IEEE 802.11 Tagging Policy . . . . . . . . . . . . . . . 77
10.11. IEEE 802.11 WTP Radio Fail . . . . . . . . . . . . . . . 77 10.11. IEEE 802.11 WTP Radio Fail . . . . . . . . . . . . . . . 77
10.12. IEEE 802.11 WTP Radio Type . . . . . . . . . . . . . . . 77 10.12. IEEE 802.11 WTP Radio Type . . . . . . . . . . . . . . . 77
10.13. WTP Encryption Capabilities . . . . . . . . . . . . . . . 78
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 79 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 79
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 80 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 80
12.1. Normative References . . . . . . . . . . . . . . . . . . 80 12.1. Normative References . . . . . . . . . . . . . . . . . . 80
12.2. Informational References . . . . . . . . . . . . . . . . 81 12.2. Informational References . . . . . . . . . . . . . . . . 81
Editors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 82 Editors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 82
Intellectual Property and Copyright Statements . . . . . . . . . . 83 Intellectual Property and Copyright Statements . . . . . . . . . . 83
1. Introduction 1. Introduction
The CAPWAP protocol [I-D.ietf-capwap-protocol-specification] defines The CAPWAP protocol [I-D.ietf-capwap-protocol-specification] defines
skipping to change at page 51, line 8 skipping to change at page 51, line 8
supported by that implementation. Receivers MUST ignore all bits supported by that implementation. Receivers MUST ignore all bits
not defined for the version of the protocol they support. not defined for the version of the protocol they support.
8021p: The maximum 802.1p priority value that the WTP will allow in 8021p: The maximum 802.1p priority value that the WTP will allow in
the Traffic Identifier (TID) field in the extended 802.11e QOS the Traffic Identifier (TID) field in the extended 802.11e QOS
Data header. Data header.
6.15. IEEE 802.11 Station Session Key 6.15. IEEE 802.11 Station Session Key
The IEEE 802.11 Station Session Key message element is sent when the The IEEE 802.11 Station Session Key message element is sent when the
AC determines that encryption of a station must be performed in the AC by the AC to provision encryption keys, or to configure an access
WTP. This message element MUST NOT be present without the IEEE policy, on the WTP. This message element MUST NOT be present without
802.11 Station (see Section 6.13) message element, and MUST NOT be the IEEE 802.11 Station (see Section 6.13) message element, and MUST
sent if the WTP had not specifically advertised support for the NOT be sent if the WTP had not specifically advertised support for
requested encryption scheme, through the WTP Descriptor Message the requested encryption scheme, through the WTP Descriptor Message
Element's Encryption Capabilities Field (see Section 8.1). Element's Encryption Capabilities Field (see Section 8.1).
When the Key field is non-zero in length, the RSN information element When the Key field is non-zero in length, the RSN information element
MUST be sent along with the IEEE 802.11 Station Session Key in order MUST be sent along with the IEEE 802.11 Station Session Key in order
to instruct the WTP on the usage of the Key field. The WTP MUST to instruct the WTP on the usage of the Key field. The WTP MUST
observe the AKM field of the RSN information element in order to observe the AKM field of the RSN information element in order to
identify the authentication protocol to be enforced with the station. identify the authentication protocol to be enforced with the station.
If cryptographic services are provided at the WTP, the WTP MUST If cryptographic services are provided at the WTP, the WTP MUST
observe the algorithm dictated in the Pairwise Cipher Suite field of observe the algorithm dictated in the Pairwise Cipher Suite field of
skipping to change at page 72, line 16 skipping to change at page 72, line 16
This section lists IEEE 802.11 specific values for the generic CAPWAP This section lists IEEE 802.11 specific values for the generic CAPWAP
message elements which include fields whose values are technology message elements which include fields whose values are technology
specific. specific.
8.1. WTP Descriptor Message Element, Encryption Capabilities Field: 8.1. WTP Descriptor Message Element, Encryption Capabilities Field:
This specification defines two new bits for the WTP Descriptor's This specification defines two new bits for the WTP Descriptor's
Encryption Capabilities field, as defined in Encryption Capabilities field, as defined in
[I-D.ietf-capwap-protocol-specification]. Note that only the bits [I-D.ietf-capwap-protocol-specification]. Note that only the bits
defined in this specification are described below. The format of the defined in this specification are described below. WEP is not
explicitely advertised as a WTP capability since all WTPs are
expected to support the encryption cipher. The format of the
Encryption Capabilities Field is: Encryption Capabilities Field is:
1 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |A|T| | | |A|T| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
A: WTP supports AES-CCMP, as defined in [IEEE.802-11.2007]. A: WTP supports AES-CCMP, as defined in [IEEE.802-11.2007].
skipping to change at page 75, line 30 skipping to change at page 75, line 30
as it is used in implementations. as it is used in implementations.
10.2. CAPWAP IEEE 802.11 Message Types 10.2. CAPWAP IEEE 802.11 Message Types
This document creates a new sub-registry to the existing CAPWAP This document creates a new sub-registry to the existing CAPWAP
Message Type registry, which is defined in Message Type registry, which is defined in
[I-D.ietf-capwap-protocol-specification]. [I-D.ietf-capwap-protocol-specification].
IANA will create and maintain the CAPWAP IEEE 802.11 Message Types IANA will create and maintain the CAPWAP IEEE 802.11 Message Types
sub-registry for all message types whose Enterprise Number is set to sub-registry for all message types whose Enterprise Number is set to
13277. The namespace is 32 bits (0-4294967295), where the values 13277. The namespace is 8 bits (3398912-3399167), where the value
3398911 and 3398912 are reserved and must not be assigned. The 3398912 is reserved and must not be assigned. The values 3398913 and
values 3398913 and 3398914 are allocated in this specification, and 3398914 are allocated in this specification, and can be found in
can be found in Section 3. Any new assignments of a CAPWAP IEEE Section 3. Any new assignments of a CAPWAP IEEE 802.11 Message Type,
802.11 Message Type, whose Enterprise Number is set to 13277) whose Enterprise Number is set to 13277) requires a Expert Review.
requires a Expert Review. The format of the registry to be The format of the registry to be maintained by IANA has the following
maintained by IANA has the following format: format:
CAPWAP IEEE 802.11 Message Type Reference CAPWAP IEEE 802.11 Message Type Reference
Control Message Value Control Message Value
10.3. CAPWAP Message Element Type 10.3. CAPWAP Message Element Type
This specification defines new values to be registered to the This specification defines new values to be registered to the
existing CAPWAP Message Element Type registry, defined in existing CAPWAP Message Element Type registry, defined in
[I-D.ietf-capwap-protocol-specification]. The values used in this [I-D.ietf-capwap-protocol-specification]. The values used in this
document, 1024 through 1048, as listed in Figure 8 are recommended as document, 1024 through 1048, as listed in Figure 8 are recommended as
skipping to change at page 76, line 13 skipping to change at page 76, line 13
Section 6.1) and IEEE 802.11 Update WLAN message element (see Section 6.1) and IEEE 802.11 Update WLAN message element (see
Section 6.21) is used to provide information about the status of the Section 6.21) is used to provide information about the status of the
keying exchange. This document defines four values, and the keying exchange. This document defines four values, and the
remaining values are controlled and maintained by IANA and requires a remaining values are controlled and maintained by IANA and requires a
Expert Review. Expert Review.
10.5. IEEE 802.11 QoS 10.5. IEEE 802.11 QoS
The QoS field in the IEEE 802.11 Add WLAN message element (see The QoS field in the IEEE 802.11 Add WLAN message element (see
Section 6.1) is used to configure a QoS policy for the WLAN. The Section 6.1) is used to configure a QoS policy for the WLAN. The
namespace is 8 bits (0-255), where the values zero (0) through four namespace is 8 bits (0-255), where the values zero (0) through three
(4) are allocated in this specification, and can be found in (3) are allocated in this specification, and can be found in
Section 6.1. This namespace is managed by IANA and assignments Section 6.1. This namespace is managed by IANA and assignments
require a Expert Review. IANA will create the IEEE 802.11 QoS require a Expert Review. IANA will create the IEEE 802.11 QoS
registry, whose format is: registry, whose format is:
IEEE 802.11 QoS Type Value Reference IEEE 802.11 QoS Type Value Reference
10.6. IEEE 802.11 Auth Type 10.6. IEEE 802.11 Auth Type
The Auth Type field in the IEEE 802.11 Add WLAN message element (see The Auth Type field in the IEEE 802.11 Add WLAN message element (see
Section 6.1) is 8 bits and is used to configure the IEEE 802.11 Section 6.1) is 8 bits and is used to configure the IEEE 802.11
skipping to change at page 76, line 37 skipping to change at page 76, line 37
specification, and can be found in Section 6.1. This namespace is specification, and can be found in Section 6.1. 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 IEEE 802.11 Auth Type registry, whose format is: create the IEEE 802.11 Auth Type registry, whose format is:
IEEE 802.11 Auth Type Type Value Reference IEEE 802.11 Auth Type Type Value Reference
10.7. IEEE 802.11 Antenna Combiner 10.7. IEEE 802.11 Antenna Combiner
The Combiner field in the IEEE 802.11 Antenna message element (see The Combiner field in the IEEE 802.11 Antenna message element (see
Section 6.2) is used to provide information about the WTP's antennas. Section 6.2) is used to provide information about the WTP's antennas.
The namespace is 8 bits (0-255), where the values zero (0) and one The namespace is 8 bits (0-255), where the values zero (0) and four
(1) are allocated in this specification, and can be found in (4) are allocated in this specification, and can be found in
Section 6.2. This namespace is managed by IANA and assignments Section 6.2. This namespace is managed by IANA and assignments
require a Expert Review. IANA will create the IEEE 802.11 Antenna require a Expert Review. IANA will create the IEEE 802.11 Antenna
Combiner registry, whose format is: Combiner registry, whose format is:
IEEE 802.11 Antenna Combiner Type Value Reference IEEE 802.11 Antenna Combiner Type Value Reference
10.8. IEEE 802.11 Antenna Selection 10.8. IEEE 802.11 Antenna Selection
The Antenna Selection field in the IEEE 802.11 Antenna message The Antenna Selection field in the IEEE 802.11 Antenna message
element (see Section 6.2) is used to provide information about the element (see Section 6.2) is used to provide information about the
WTP's antennas. The namespace is 8 bits (0-255), where the values WTP's antennas. The namespace is 8 bits (0-255), where the values
zero (0) is reserved and used and the values one (1) through four (4) zero (0) is reserved and used and the values one (1) through two (2)
are allocated in this specification, and can be found in Section 6.2. are allocated in this specification, and can be found in Section 6.2.
This namespace is managed by IANA and assignments require a Expert This namespace is managed by IANA and assignments require a Expert
Review. IANA will create the IEEE 802.11 Antenna Selection registry, Review. IANA will create the IEEE 802.11 Antenna Selection registry,
whose format is: whose format is:
IEEE 802.11 Antenna Selection Type Value Reference IEEE 802.11 Antenna Selection Type Value Reference
10.9. IEEE 802.11 Session Key Flags 10.9. IEEE 802.11 Session Key Flags
The Flags field in the IEEE 802.11 Station Session Key message The Flags field in the IEEE 802.11 Station Session Key message
element (see Section 6.15) is 16 bits and is used to configure the element (see Section 6.15) is 16 bits and is used to configure the
session key association with the mobile device. This specification session key association with the mobile device. This specification
defines bits zero (0) and one (1), while bits two (2) through sixteen defines bits zero (0) and one (1), while bits two (2) through fifteen
are reserved. The reserved bits are managed by IANA and whose are reserved. The reserved bits are managed by IANA and whose
assignment requires a Expert Review. IANA will create the IEEE assignment requires a Expert Review. IANA will create the IEEE
802.11 Session Key Flags registry, whose format is: 802.11 Session Key Flags registry, whose format is:
IEEE 802.11 Station Session Key Bit Position Reference IEEE 802.11 Station Session Key Bit Position Reference
10.10. IEEE 802.11 Tagging Policy 10.10. IEEE 802.11 Tagging Policy
The Tagging Policy field in the IEEE 802.11 WTP Quality of Service The Tagging Policy field in the IEEE 802.11 WTP Quality of Service
message element (see Section 6.22) is 8 bits and is used to specify message element (see Section 6.22) is 8 bits and is used to specify
how the CAPWAP Data Channel packets are to be tagged. This how the CAPWAP Data Channel packets are to be tagged. This
specification defines bits five (5) through seven (7). The remaining specification defines bits three (3) through seven (7). The
bits are managed by IANA and whose assignment requires a Expert remaining bits are managed by IANA and whose assignment requires a
Review. IANA will create the IEEE 802.11 Tagging Policy registry, Expert Review. IANA will create the IEEE 802.11 Tagging Policy
whose format is: registry, whose format is:
IEEE 802.11 Tagging Policy Bit Position Reference IEEE 802.11 Tagging Policy Bit Position Reference
10.11. IEEE 802.11 WTP Radio Fail 10.11. IEEE 802.11 WTP Radio Fail
The Type field in the IEEE 802.11 WTP Radio Fail Alarm Indication The Type field in the IEEE 802.11 WTP Radio Fail Alarm Indication
message element (see Section 6.24) is used to provide information on message element (see Section 6.24) is used to provide information on
why a WTP's radio has failed. The namespace is 8 bits (0-255), where why a WTP's radio has failed. The namespace is 8 bits (0-255), where
the values zero (0) is reserved and unused, while the values one (1) the values zero (0) is reserved and unused, while 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
skipping to change at page 78, line 4 skipping to change at page 78, line 4
require a Expert Review. IANA will create the IEEE 802.11 WTP Radio require a Expert Review. IANA will create the IEEE 802.11 WTP Radio
Fail registry, whose format is: Fail registry, whose format is:
IEEE 802.11 WTP Radio Fail Type Value Reference IEEE 802.11 WTP Radio Fail Type Value Reference
10.12. IEEE 802.11 WTP Radio Type 10.12. IEEE 802.11 WTP Radio Type
The Radio Type field in the IEEE 802.11 WTP Radio Information message The Radio Type field in the IEEE 802.11 WTP Radio Information message
element (see Section 6.25) is 8 bits and is used to provide element (see Section 6.25) is 8 bits and is used to provide
information about the WTP's radio type. This specification defines information about the WTP's radio type. This specification defines
bits five (5) through seven (7). The remaining bits are managed by bits four (4) through seven (7). The remaining bits are managed by
IANA and whose assignment requires a Expert Review. IANA will create IANA and whose assignment requires a Expert Review. IANA will create
the IEEE 802.11 WTP Radio Type registry, whose format is: the IEEE 802.11 WTP Radio Type registry, whose format is:
IEEE 802.11 WTP Radio Type Bit Position Reference IEEE 802.11 WTP Radio Type Bit Position Reference
10.13. WTP Encryption Capabilities
The WTP Encryption Capabilities field in the WTP Descriptor message
element (see Section 8.1) is 16 bits and is used by the WTP to
indicate its IEEE 802.11 encryption capabilities. This specification
defines bits 12 and 13. The reserved bits are managed by IANA and
whose assignment requires a Expert Review. IANA will create the IEEE
802.11 Encryption Capabilities registry, whose format is:
IEEE 802.11 Encryption Capabilities Bit Position Reference
11. Acknowledgments 11. Acknowledgments
The following individuals are acknowledged for their contributions to The following individuals are acknowledged for their contributions to
this binding specification: Puneet Agarwal, Charles Clancy, Pasi this binding specification: Puneet Agarwal, Charles Clancy, Pasi
Eronen, Saravanan Govindan, Scott Kelly, Peter Nilsson, Bob O'Hara, Eronen, Saravanan Govindan, Scott Kelly, Peter Nilsson, Bob O'Hara,
David Perkins, Margaret Wasserman and Yong Zhang. David Perkins, Margaret Wasserman and Yong Zhang.
12. References 12. References
12.1. Normative References 12.1. Normative References
skipping to change at page 81, line 10 skipping to change at page 81, line 10
information exchange between systems - Local and information exchange between systems - Local and
metropolitan area networks - Specific requirements - Part metropolitan area networks - Specific requirements - Part
11: Wireless LAN Medium Access Control (MAC) and Physical 11: Wireless LAN Medium Access Control (MAC) and Physical
Layer (PHY) specifications", IEEE Standard 802.11, 2007, < Layer (PHY) specifications", IEEE Standard 802.11, 2007, <
http://standards.ieee.org/getieee802/download/ http://standards.ieee.org/getieee802/download/
802.11-2007.pdf>. 802.11-2007.pdf>.
[I-D.ietf-capwap-protocol-specification] [I-D.ietf-capwap-protocol-specification]
Montemurro, M., Stanley, D., and P. Calhoun, "CAPWAP Montemurro, M., Stanley, D., and P. Calhoun, "CAPWAP
Protocol Specification", Protocol Specification",
draft-ietf-capwap-protocol-specification-13 (work in draft-ietf-capwap-protocol-specification-14 (work in
progress), September 2008. progress), October 2008.
[IEEE.802-1X.2004] [IEEE.802-1X.2004]
"Information technology - Telecommunications and "Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan area networks - Specific requirements - Port- metropolitan area networks - Specific requirements - Port-
Based Network Access Control", IEEE Standard 802.1X, 2004, Based Network Access Control", IEEE Standard 802.1X, 2004,
<http://standards.ieee.org/getieee802/download/ <http://standards.ieee.org/getieee802/download/
802.1X-2004.pdf>. 802.1X-2004.pdf>.
[IEEE.802-1Q.2005] [IEEE.802-1Q.2005]
 End of changes. 16 change blocks. 
30 lines changed or deleted 44 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/