draft-ietf-opsawg-capwap-hybridmac-05.txt   draft-ietf-opsawg-capwap-hybridmac-06.txt 
Network Working Group C. Shao Network Working Group C. Shao
Internet-Draft H. Deng Internet-Draft H. Deng
Intended status: Standards Track China Mobile Intended status: Standards Track China Mobile
Expires: January 17, 2015 R. Pazhyannur Expires: February 12, 2015 R. Pazhyannur
Cisco Systems Cisco Systems
F. Bari F. Bari
AT&T AT&T
R. Zhang R. Zhang
China Telecom China Telecom
S. Matsushima S. Matsushima
SoftBank Telecom SoftBank Telecom
July 16, 2014 August 11, 2014
IEEE 802.11 MAC Profile for CAPWAP IEEE 802.11 MAC Profile for CAPWAP
draft-ietf-opsawg-capwap-hybridmac-05 draft-ietf-opsawg-capwap-hybridmac-06
Abstract Abstract
The CAPWAP protocol defines two entities: a Wireless Transmission The CAPWAP protocol defines two entities: a Wireless Transmission
Point (WTP) and an Access Controller (AC). The CAPWAP protocol Point (WTP) and an Access Controller (AC). The CAPWAP protocol
binding for IEEE 802.11 defines two MAC (Medium Access Control) modes binding for IEEE 802.11 defines two MAC (Medium Access Control) modes
for IEEE 802.11 WTP: Split and Local MAC, and describes the required for IEEE 802.11 WTP: Split and Local MAC, and describes the required
functionality split between the WTP and AC for each mode. However, functionality split between the WTP and AC for each mode. However,
in the split MAC mode, the partitioning of encryption/decryption in the split MAC mode, the partitioning of encryption/decryption
functions are not been clearly clearly defined. In the Split MAC functions are not been clearly clearly defined. In the Split MAC
skipping to change at page 2, line 10 skipping to change at page 2, line 10
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on January 17, 2015. This Internet-Draft will expire on February 12, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions used in this document . . . . . . . . . . . . . . 4 2. IEEE MAC Profile Descriptions . . . . . . . . . . . . . . . . 4
3. IEEE MAC Profile Descriptions . . . . . . . . . . . . . . . . 5 2.1. Split MAC with WTP encryption . . . . . . . . . . . . . . 4
3.1. Split MAC with WTP encryption . . . . . . . . . . . . . . 5 2.2. Split MAC with AC encryption . . . . . . . . . . . . . . 5
3.2. Split MAC with AC encryption . . . . . . . . . . . . . . 6 2.3. IEEE 802.11 MAC Profile Frame Exchange . . . . . . . . . 6
3.3. IEEE 802.11 MAC Profile Frame Exchange . . . . . . . . . 7 3. MAC Profile Message Element Definitions . . . . . . . . . . . 7
4. MAC Profile Message Element Definitions . . . . . . . . . . . 8 3.1. IEEE 802.11 Supported MAC Profiles . . . . . . . . . . . 7
4.1. IEEE 802.11 Supported MAC Profiles . . . . . . . . . . . 8 3.2. IEEE 802.11 MAC Profile . . . . . . . . . . . . . . . . . 8
4.2. IEEE 802.11 MAC Profile . . . . . . . . . . . . . . . . . 9 4. Security Considerations . . . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 9
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 8. Normative References . . . . . . . . . . . . . . . . . . . . 9
9. Normative References . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
The CAPWAP protocol supports two MAC modes of operation: Split and The CAPWAP protocol supports two MAC modes of operation: Split and
Local MAC, as described in [RFC5415], [RFC5416]. However, there are Local MAC, as described in [RFC5415], [RFC5416]. However, there are
MAC functions that have not been clearly defined. For example IEEE MAC functions that have not been clearly defined. For example IEEE
802.11 encryption is specified as located in either in the AC or the 802.11 encryption is specified as located in either in the AC or the
WTP with no clear way to negotiate where it should be located. WTP with no clear way to negotiate where it should be located.
Because different vendors have different definitions of the MAC mode, Because different vendors have different definitions of the MAC mode,
many MAC layer functions are mapped differently to either the WTP or many MAC layer functions are mapped differently to either the WTP or
skipping to change at page 4, line 44 skipping to change at page 4, line 9
| |IEEE 802.11 | WTP | WTP/AC | | |IEEE 802.11 | WTP | WTP/AC |
+ |Encryption/Decryption | | | + |Encryption/Decryption | | |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Functions in Local MAC and Split MAC Figure 1: Functions in Local MAC and Split MAC
To solve this problem, this specification introduces IEEE 802.11 MAC To solve this problem, this specification introduces IEEE 802.11 MAC
profile. The MAC profile unambiguously specifies where the various profile. The MAC profile unambiguously specifies where the various
MAC functionality should be located. MAC functionality should be located.
2. Conventions used in this document 2. IEEE MAC Profile Descriptions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL","SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
3. IEEE MAC Profile Descriptions
A IEEE MAC Profile refers to a description of how the MAC A IEEE MAC Profile refers to a description of how the MAC
functionality is split between the WTP and AC shown in Figure 1. functionality is split between the WTP and AC shown in Figure 1.
3.1. Split MAC with WTP encryption 2.1. Split MAC with WTP encryption
The functional split for the Split MAC with WTP encryption is The functional split for the Split MAC with WTP encryption is
provided in Figure 2. This profile is similar to the Split MAC provided in Figure 2. This profile is similar to the Split MAC
description in [RFC5416], except that IEEE 802.11 encryption/ description in [RFC5416], except that IEEE 802.11 encryption/
decryption is at the WTP. Note that fragmentation is always done at decryption is at the WTP. Note that fragmentation is always done at
the same entity as the encryption. Consequently, in this profile the same entity as the encryption. Consequently, in this profile
fragmentation/defragmentation is also done only at the WTP. Note fragmentation/defragmentation is also done only at the WTP. Note
that scheduling functionality is denoted as WTP/AC. As explained in that scheduling functionality is denoted as WTP/AC. As explained in
[RFC5416], this means that the admission control component of IEEE [RFC5416], this means that the admission control component of IEEE
802.11 resides on the AC, the real-time scheduling and queuing 802.11 resides on the AC, the real-time scheduling and queuing
skipping to change at page 6, line 41 skipping to change at page 5, line 41
| |IEEE 802.1X/EAP | AC | | |IEEE 802.1X/EAP | AC |
+ IEEE +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + IEEE +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 802.11 RSN |RSNA Key Management | AC | | 802.11 RSN |RSNA Key Management | AC |
+ (WPA2) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + (WPA2) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |IEEE 802.11 | WTP | | |IEEE 802.11 | WTP |
+ |Encryption/Decryption | | + |Encryption/Decryption | |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Functions in Split MAC with WTP Encryption Figure 2: Functions in Split MAC with WTP Encryption
3.2. Split MAC with AC encryption 2.2. Split MAC with AC encryption
The functional split for the Split MAC with AC encryption is provided The functional split for the Split MAC with AC encryption is provided
in Figure 3. This profile is similar to the Split MAC in [RFC5416] in Figure 3. This profile is similar to the Split MAC in [RFC5416]
except that IEEE 802.11 encryption/decryption is at the AC. Since except that IEEE 802.11 encryption/decryption is at the AC. Since
fragmentation is always done at the same entity as the encryption, in fragmentation is always done at the same entity as the encryption, in
this profile, AC does fragmentation/defragmentation. this profile, AC does fragmentation/defragmentation.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Functions | Profile | | Functions | Profile |
| | 1 | | | 1 |
skipping to change at page 7, line 41 skipping to change at page 6, line 41
| |IEEE 802.1X/EAP | AC | | |IEEE 802.1X/EAP | AC |
+ IEEE +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + IEEE +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 802.11 RSN |RSNA Key Management | AC | | 802.11 RSN |RSNA Key Management | AC |
+ (WPA2) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + (WPA2) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |IEEE 802.11 | AC | | |IEEE 802.11 | AC |
+ |Encryption/Decryption | | + |Encryption/Decryption | |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Functions in Split MAC with AC encryption Figure 3: Functions in Split MAC with AC encryption
3.3. IEEE 802.11 MAC Profile Frame Exchange 2.3. IEEE 802.11 MAC Profile Frame Exchange
An example of message exchange using the IEEE 802.11 MAC Profile An example of message exchange using the IEEE 802.11 MAC Profile
message element is shown in Figure 4. The WTP informs the AC of the message element is shown in Figure 4. The WTP informs the AC of the
various MAC profiles it supports. This happens either in a Discovery various MAC profiles it supports. This happens either in a Discovery
Request message or the Join Request message. The AC determines the Request message or the Join Request message. The AC determines the
appropriate profile and configures the WTP with the profile while appropriate profile and configures the WTP with the profile while
configuring the WLAN. configuring the WLAN.
+-+-+-+-+-+-+ +-+-+-+-+-+-+ +-+-+-+-+-+-+ +-+-+-+-+-+-+
| WTP | | AC | | WTP | | AC |
skipping to change at page 8, line 26 skipping to change at page 7, line 26
| IEEE 802.11 Add WLAN, | | IEEE 802.11 Add WLAN, |
| IEEE 802.11 MAC Profile | | IEEE 802.11 MAC Profile |
| ] | | ] |
|<----------------------------------------| |<----------------------------------------|
| | | |
|IEEE 802.11 WLAN Config. Response | |IEEE 802.11 WLAN Config. Response |
|---------------------------------------->| |---------------------------------------->|
Figure 4: Message Exchange For Negotiating MAC Profile Figure 4: Message Exchange For Negotiating MAC Profile
4. MAC Profile Message Element Definitions 3. MAC Profile Message Element Definitions
4.1. IEEE 802.11 Supported MAC Profiles 3.1. IEEE 802.11 Supported MAC Profiles
The IEEE 802.11 Supported MAC Profile message element allows the WTP The IEEE 802.11 Supported MAC Profile message element allows the WTP
to communicate the profiles it supports. The Discovery Request to communicate the profiles it supports. The Discovery Request
message, Primary Discovery Request message, and Join Request message message, Primary Discovery Request message, and Join Request message
may include one such message element. may include one such message element.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0
+=+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- +=+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
| Num_Profiles | Profile_1 | Profile_[2..N].. | Num_Profiles | Profile_1 | Profile_[2..N]..
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Figure 5: IEEE 802.11 Supported MAC Profiles Figure 5: IEEE 802.11 Supported MAC Profiles
o Type: TBD for IEEE 802.11 Supported MAC Profiles o Type: TBD for IEEE 802.11 Supported MAC Profiles
o Num_Profiles >=1: This refers to number of profiles present in o Num_Profiles >=1: This refers to number of profiles present in
this message element. There must be at least one profile. this message element. There must be at least one profile.
o Profile: Each profile is idnentified by a value specified in o Profile: Each profile is identified by a value specified in
Section 4.2. Section 3.2.
4.2. IEEE 802.11 MAC Profile 3.2. IEEE 802.11 MAC Profile
The IEEE 802.11 MAC Profile message element allows the AC to select a The IEEE 802.11 MAC Profile message element allows the AC to select a
profile. This message element may be provided along with the IEEE profile. This message element may be provided along with the IEEE
802.11 ADD WLAN message element while configuring a WLAN on the WTP. 802.11 ADD WLAN message element while configuring a WLAN on the WTP.
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+=+-+-+-+-+-+-+-+ +=+-+-+-+-+-+-+-+
| Profile | | Profile |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Figure 6: IEEE 802.11 MAC Profile Figure 6: IEEE 802.11 MAC Profile
o Type: TBD for IEEE 802.11 MAC Profile o Type: TBD for IEEE 802.11 MAC Profile
o Profile: The profile is identified by a value as given below o Profile: The profile is identified by a value as given below
* 0: This refers to the Split MAC Profile with WTP encryption * 0: This refers to the Split MAC Profile with WTP encryption
* 1: This refers to the Split MAC Profile with AC encryption * 1: This refers to the Split MAC Profile with AC encryption
5. Security Considerations 4. Security Considerations
This document does not introduce any new security risks compared to This document does not introduce any new security risks compared to
[RFC5416]. The security considerations described in [RFC5416] apply [RFC5416]. The security considerations described in [RFC5416] apply
here as well. here as well.
6. IANA Considerations 5. IANA Considerations
This document requires the following IANA actions: This document requires the following IANA actions:
o This specification defines two new message elements, IEEE 802.11 o This specification defines two new message elements, IEEE 802.11
Supported MAC Profiles (described in Section 4.1) and IEEE 802.11 Supported MAC Profiles (described in Section 3.1) and IEEE 802.11
MAC Profile (described in Section 4.2). These elements needs to MAC Profile (described in Section 3.2). These elements needs to
be registered in the existing CAPWAP Message Element Type be registered in the existing CAPWAP Message Element Type
registry, defined in [RFC5415]. The values for these elements registry, defined in [RFC5415]. The values for these elements
needs to be between 1024 and 2047 (see Section 15.7 in [RFC5415]). needs to be between 1024 and 2047 (see Section 15.7 in [RFC5415]).
CAPWAP Protocol Message Element Type Value CAPWAP Protocol Message Element Type Value
IEEE 802.11 Supported MAC Profiles TBD1 IEEE 802.11 Supported MAC Profiles TBD1
IEEE 802.11 MAC Profile TBD2 IEEE 802.11 MAC Profile TBD2
o The IEEE 802.11 Supported MAC Profiles message element and IEEE o The IEEE 802.11 Supported MAC Profiles message element and IEEE
802.11 MAC Profile message element include a Profile Field (as 802.11 MAC Profile message element include a Profile Field (as
defined in Section 4.2). The Profile field in the IEEE 802.11 defined in Section 3.2). The Profile field in the IEEE 802.11
Supported MAC Profiles denotes the MAC profiles supported by the Supported MAC Profiles denotes the MAC profiles supported by the
WTP. The profile field in the IEEE MAC profile denotes MAC WTP. The profile field in the IEEE MAC profile denotes MAC
profile assigned to the WTP. The namespace for the field is 8 profile assigned to the WTP. The namespace for the field is 8
bits (0-255). This specification defines two values, zero (0) and bits (0-255). This specification defines two values, zero (0) and
one (1) as described below. The remaining values (2-255) are one (1) as described below. The remaining values (2-255) are
controlled and maintained by IANA and require an Expert Review. controlled and maintained by IANA and require an Expert Review.
IANA needs to create a registry whose format is given below. IANA needs to create a registry called CAPWAP IEEE 802.11 Split
MAC Profile. The registry format is given below.
Profile Type Value Reference Profile Type Value Reference
Split MAC with WTP encryption 0 Split MAC with WTP encryption 0
Split MAC with AC encryption 1 Split MAC with AC encryption 1
7. Contributors 6. Contributors
Yifan Chen chenyifan@chinamobile.com Yifan Chen chenyifan@chinamobile.com
Naibao Zhou zhounaibao@chinamobile.com Naibao Zhou zhounaibao@chinamobile.com
8. Acknowledgments 7. Acknowledgments
The authors are grateful for extremely valuable suggestions from The authors are grateful for extremely valuable suggestions from
Dorothy Stanley in developing this specification. Dorothy Stanley in developing this specification.
Guidance from management team: Melinda Shore, Scott Bradner, Chris Guidance from management team: Melinda Shore, Scott Bradner, Chris
Liljenstolpe, Benoit Claise, Joel Jaeggli, Dan Romascanu are highly Liljenstolpe, Benoit Claise, Joel Jaeggli, Dan Romascanu are highly
appreciated. appreciated.
9. Normative References 8. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5415] Calhoun, P., Montemurro, M., and D. Stanley, "Control And [RFC5415] Calhoun, P., Montemurro, M., and D. Stanley, "Control And
Provisioning of Wireless Access Points (CAPWAP) Protocol Provisioning of Wireless Access Points (CAPWAP) Protocol
Specification", RFC 5415, March 2009. Specification", RFC 5415, March 2009.
[RFC5416] Calhoun, P., Montemurro, M., and D. Stanley, "Control and [RFC5416] Calhoun, P., Montemurro, M., and D. Stanley, "Control and
Provisioning of Wireless Access Points (CAPWAP) Protocol Provisioning of Wireless Access Points (CAPWAP) Protocol
Binding for IEEE 802.11", RFC 5416, March 2009. Binding for IEEE 802.11", RFC 5416, March 2009.
Authors' Addresses Authors' Addresses
 End of changes. 21 change blocks. 
45 lines changed or deleted 36 lines changed or added

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