CAPWAP Threat Analysis for 802.11 Deployments

Document Type Replaced Internet-Draft (individual)
Last updated 2008-04-16 (latest revision 2006-10-17)
Replaced by draft-ietf-capwap-threat-analysis
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-capwap-threat-analysis
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Early Wireless LAN (WLAN) deployments feature a "fat" Access Point (AP) which serves as a standalone interface between the wired and wireless network segments. However, this model raises scaling, mobility, and manageability issues, and the CAPWAP protocol [CAPWAP] is being developed in reponse. CAPWAP effectively splits the fat AP functionality into two network elements, and the communication channel between these components may traverse potentially hostile hops. This document analyzes the security exposure resulting from the introduction of CAPWAP, and summarizes the associated security considerations for CAPWAP implementations and deployments.


Scott Kelly (
Charles Clancy (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)