draft-ietf-capwap-dhc-ac-option-01.txt   draft-ietf-capwap-dhc-ac-option-02.txt 
Network Working Group P. Calhoun Network Working Group P. Calhoun
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: September 14, 2008 March 13, 2008 Intended status: Standards Track October 15, 2008
Expires: April 18, 2009
CAPWAP Access Controller DHCP Option CAPWAP Access Controller DHCP Option
draft-ietf-capwap-dhc-ac-option-01 draft-ietf-capwap-dhc-ac-option-02
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 33 skipping to change at page 1, line 34
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 September 14, 2008. This Internet-Draft will expire on April 18, 2009.
Abstract Abstract
The Control And Provisioning of Wireless Access Points Protocol The Control And Provisioning of Wireless Access Points Protocol
allows a Wireless Termination Point to use DHCP to discover the allows a Wireless Termination Point to use DHCP to discover the
Access Controllers it is to connect to. This document describes the Access Controllers it is to connect to. This document describes the
DHCP options to be used by the CAPWAP protocol. DHCP options to be used by the CAPWAP protocol.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions used in this document . . . . . . . . . . . . 3 1.1. Conventions used in this document . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. CAPWAP AC DHCPv4 Option . . . . . . . . . . . . . . . . . . . 4 2. CAPWAP AC DHCPv4 Option . . . . . . . . . . . . . . . . . . . 4
3. CAPWAP AC DHCPv6 Option . . . . . . . . . . . . . . . . . . . 5 3. CAPWAP AC DHCPv6 Option . . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
7.1. Normative References . . . . . . . . . . . . . . . . . . . 10 7.1. Normative References . . . . . . . . . . . . . . . . . . . 10
7.2. Informational References . . . . . . . . . . . . . . . . . 10 7.2. Informational References . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 11 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 11
Intellectual Property and Copyright Statements . . . . . . . . . . 12 Intellectual Property and Copyright Statements . . . . . . . . . . 12
1. Introduction 1. Introduction
The Control And Provisioning of Wireless Access Points Protocol The Control And Provisioning of Wireless Access Points Protocol
(CAPWAP) [I-D.ietf-capwap-protocol-specification] allows a Wireless (CAPWAP) [I-D.ietf-capwap-protocol-specification] allows a Wireless
Termination Point (WTP) to use DHCP to discover the Access Termination Point (WTP) to use DHCP to discover the Access
Controllers (AC) it is to connect to. Controllers (AC) it is to connect to.
Prior to the CAPWAP Discovery process, the WTP MAY use one of many Prior to the CAPWAP Discovery process, the WTP may use one of many
methods to identify the proper AC to establish a CAPWAP connection methods to identify the proper AC to establish a CAPWAP connection
with. One of these methods is through the DHCP protocol. This is with. One of these methods is through the DHCP protocol. This is
done through the CAPWAP AC DHCPv4 or CAPWAP AC DHCPv6 Option. done through the CAPWAP AC DHCPv4 or CAPWAP AC DHCPv6 Option.
1.1. Conventions used in this document 1.1. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
1.2. Terminology 1.2. Terminology
This document uses terminology defined in [RFC3753] and This document uses terminology defined in [RFC3753], [RFC2131],
[I-D.ietf-capwap-protocol-specification]. [RFC3315] and [I-D.ietf-capwap-protocol-specification].
2. CAPWAP AC DHCPv4 Option 2. CAPWAP AC DHCPv4 Option
This section defines a DHCPv4 option that carries a list of 32-bit This section defines a DHCPv4 option that carries a list of 32-bit
(binary) IPv4 addresses indicating one or more CAPWAP AC available to (binary) IPv4 addresses indicating one or more CAPWAP AC available to
the WTP. the WTP.
The DHCPv4 option for CAPWAP has the format shown in the following The DHCPv4 option for CAPWAP has the format shown in the following
figure: figure:
skipping to change at page 4, line 34 skipping to change at page 4, line 34
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_CAPWAP_AC_V4 (TBD) option-code: OPTION_CAPWAP_AC_V4 (TBD)
option-length: Length of the 'options' field in octets; MUST be a option-length: Length of the 'options' field in octets; MUST be a
multiple of four (4). multiple of four (4).
AC IPv4 Address: IPv4 address of a CAPWAP AC which the WTP may use. AC IPv4 Address: IPv4 address of a CAPWAP AC which the WTP may use.
The ACs are listed in the order of preference for use by the WTP. The ACs are listed in the order of preference for use by the WTP.
A CAPWAP WTP, acting as a DHCPv4 client, SHOULD request the CAPWAP AC A DHCPv4 client, acting on behalf of a CAPWAP WTP, MUST request the
DHCPv4 Option in a Parameter Request List as described in [RFC2131] CAPWAP AC DHCPv4 Option in a Parameter Request List Option, as
and [RFC2132]. described in [RFC2131] and [RFC2132].
If configured with a (list of) CAPWAP AC address(es), a DHCPv4 server A DHCPv4 server returns the CAPWAP AC Option to the client if the
SHOULD send the client the CAPWAP AC DHCPv4 option, even if this server policy is configured appropriately and the server is
option is not explicitly requested by the client. configured with a list of CAPWAP AC addresses.
A CAPWAP WTP, acting as a DHCPv4 client, receiving the CAPWAP AC A CAPWAP WTP, acting as a DHCPv4 client, receiving the CAPWAP AC
DHCPv4 option MAY use the (list of) IP address(es) to locate AC. The DHCPv4 option MAY use the (list of) IP address(es) to locate AC. The
CAPWAP protocol [I-D.ietf-capwap-protocol-specification] provides CAPWAP protocol [I-D.ietf-capwap-protocol-specification] provides
guidance on the WTP's discovery process. guidance on the WTP's discovery process.
The WTP, acting as a DHCPv4 client, SHOULD try the records in the The WTP, acting as a DHCPv4 client, SHOULD try the records in the
order listed in the CAPWAP AC DHCPv4 option received from the DHCPv4 order listed in the CAPWAP AC DHCPv4 option received from the DHCPv4
server. server.
skipping to change at page 5, line 38 skipping to change at page 5, line 38
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_CAPWAP_AC_V6 (TBD) option-code: OPTION_CAPWAP_AC_V6 (TBD)
option-length: Length of the 'options' field in octets; MUST be a option-length: Length of the 'options' field in octets; MUST be a
multiple of sixteen (16). multiple of sixteen (16).
AC IPv6 Address: IPv6 address of a CAPWAP AC which the WTP may use. AC IPv6 Address: IPv6 address of a CAPWAP AC which the WTP may use.
The ACs are listed in the order of preference for use by the WTP. The ACs are listed in the order of preference for use by the WTP.
A CAPWAP WTP, acting as a DHCPv6 client, SHOULD request the CAPWAP AC A DHCPv6 client, acting on behalf of a CAPWAP WTP, MUST request the
DHCPv6 Option in a Parameter Request List as described in [RFC2131] CAPWAP AC DHCPv6 Option in a Parameter Request List Option, as
and [RFC2132]. described in [RFC3315].
If configured with a (list of) CAPWAP AC address(es), a DHCPv6 server A DHCPv6 server returns the CAPWAP AC Option to the client if the
SHOULD send the client the CAPWAP AC DHCPv6 option, even if this server policy is configured appropriately and the server is
option is not explicitly requested by the client. configured with a list of CAPWAP AC addresses.
A CAPWAP WTP, acting as a DHCPv6 client, receiving the CAPWAP AC A CAPWAP WTP, acting as a DHCPv6 client, receiving the CAPWAP AC
DHCPv6 option MAY use the (list of) IP address(es) to locate AC. The DHCPv6 option MAY use the (list of) IP address(es) to locate AC. The
CAPWAP protocol [I-D.ietf-capwap-protocol-specification] provides CAPWAP protocol [I-D.ietf-capwap-protocol-specification] provides
guidance on the WTP's discovery process. guidance on the WTP's discovery process.
The WTP, acting as a DHCPv6 client, SHOULD try the records in the The WTP, acting as a DHCPv6 client, SHOULD try the records in the
order listed in the CAPWAP AC DHCPv6 option received from the DHCPv6 order listed in the CAPWAP AC DHCPv6 option received from the DHCPv6
server. server.
4. IANA Considerations 4. IANA Considerations
The following DHCPv4 option code for CAPWAP AC option MUST be The following DHCPv4 option code for CAPWAP AC option must be
assigned by IANA: assigned by IANA:
Option Name Value Described in Option Name Value Described in
----------------------------------------------- -----------------------------------------------
OPTION_CAPWAP_AC_V4 TBD Section 2 OPTION_CAPWAP_AC_V4 TBD Section 2
The following DHCPv6 option code for CAPWAP AC options MUST be The following DHCPv6 option code for CAPWAP AC options MUST be
assigned by IANA: assigned by IANA:
Option Name Value Described in Option Name Value Described in
skipping to change at page 8, line 16 skipping to change at page 8, line 16
The security considerations in [RFC2131], [RFC2132] and [RFC3315] The security considerations in [RFC2131], [RFC2132] and [RFC3315]
apply. If an adversary manages to modify the response from a DHCP apply. If an adversary manages to modify the response from a DHCP
server or insert its own response, a WTP could be led to contact a server or insert its own response, a WTP could be led to contact a
rogue CAPWAP AC, possibly one that then intercepts call requests or rogue CAPWAP AC, possibly one that then intercepts call requests or
denies service. CAPWAP's use of DTLS MUST be used to authenticate denies service. CAPWAP's use of DTLS MUST be used to authenticate
the CAPWAP peers in the establishment of the session. the CAPWAP peers in the establishment of the session.
In most of the networks, the DHCP exchange that delivers the options In most of the networks, the DHCP exchange that delivers the options
prior to network access authentication is neither integrity protected prior to network access authentication is neither integrity protected
nor origin authenticated. Therefore, the options defined in this nor origin authenticated. Therefore, in security sensitive
document are not the only methods used to determine which AC a WTP environments the options defined in this document SHOULD NOT be the
should connect to. The CAPWAP protocol only methods used to determine which AC a WTP should connect to. The
[I-D.ietf-capwap-protocol-specification] defines other AC discovery CAPWAP protocol [I-D.ietf-capwap-protocol-specification] defines
procedures a WTP MAY utilize. other AC discovery procedures a WTP MAY utilize.
6. Acknowledgements 6. Acknowledgments
The following individuals are acknowledged for their contributions to The following individuals are acknowledged for their contributions to
this protocol specification: Ralph Droms, Margaret Wasserman. this protocol specification: Ralph Droms, Margaret Wasserman.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
skipping to change at page 10, line 23 skipping to change at page 10, line 23
RFC 2131, March 1997. RFC 2131, March 1997.
[RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor [RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
Extensions", RFC 2132, March 1997. Extensions", RFC 2132, March 1997.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
[I-D.ietf-capwap-protocol-specification] [I-D.ietf-capwap-protocol-specification]
Calhoun, P., "CAPWAP Protocol Specification", Montemurro, M., Stanley, D., and P. Calhoun, "CAPWAP
draft-ietf-capwap-protocol-specification-10 (work in Protocol Specification",
progress), March 2008. draft-ietf-capwap-protocol-specification-13 (work in
progress), September 2008.
7.2. Informational References 7.2. Informational References
[RFC3753] Manner, J. and M. Kojo, "Mobility Related Terminology", [RFC3753] Manner, J. and M. Kojo, "Mobility Related Terminology",
RFC 3753, June 2004. RFC 3753, June 2004.
Author's Address Author's Address
Pat R. Calhoun Pat R. Calhoun
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
Phone: +1 408-853-5269 Phone: +1 408-902-3240
Email: pcalhoun@cisco.com Email: pcalhoun@cisco.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
 End of changes. 15 change blocks. 
30 lines changed or deleted 32 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/