Browse Prior Art Database

Control And Provisioning of Wireless Access Points (CAPWAP) Threat Analysis for IEEE 802.11 Deployments (RFC5418)

IP.com Disclosure Number: IPCOM000180291D
Original Publication Date: 2009-Mar-01
Included in the Prior Art Database: 2009-Mar-06
Document File: 35 page(s) / 74K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Kelly: AUTHOR [+2]

Abstract

Early Wireless Local Area Network (WLAN) deployments feature a "fat" Access Point (AP), which serves as a stand-alone interface between the wired and wireless network segments. However, this model raises scaling, mobility, and manageability issues, and the Control and Provisioning of Wireless Access Points (CAPWAP) protocol is meant to address these issues. 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 IEEE 802.11-based CAPWAP implementations and deployments.

This text was extracted from an ASCII text file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 4% of the total text.

Network Working Group                                           S. Kelly Request for Comments: 5418                               

Aruba

Networks Category: Informational                                        T. Clancy                                                                      LTS                                                               March 2009

       Control And Provisioning of Wireless Access Points (CAPWAP)               Threat Analysis for IEEE 802.11 Deployments

Status of This Memo

   This memo provides information for the Internet community.  It does    not specify an Internet standard of any kind.  Distribution of this    memo is unlimited.

Copyright Notice

   Copyright (c) 2009 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents in effect on the date of    publication of this document (http://trustee.ietf.org/license-info).    Please review these documents carefully, as they describe your rights    and restrictions with respect to this document.

   This document may contain material from IETF Documents or IETF    Contributions published or made publicly available before November    10, 2008.  The person(s) controlling the copyright in some of this    material may not have granted the IETF Trust the right to allow    modifications of such material outside the IETF Standards Process.    Without obtaining an adequate license from the person(s) controlling    the copyright in such materials, this document may not be modified    outside the IETF Standards Process, and derivative works of it may    not be created outside the IETF Standards Process, except to format    it for publication as an RFC or to translate it into languages other    than English.

Kelly & Clancy               Informational                      [Page 1]
 RFC 5418             CAPWAP 802.11 Threat Analysis            March 2009

 Abstract

   Early Wireless Local Area Network (WLAN) deployments feature a "fat"    Access Point (AP), which serves as a stand-alone interface between    the wired and wireless network segments.  However, this model raises    scaling, mobility, and manageability issues, and the Control and    Provisioning of Wireless Access Points (CAPWAP) protocol is meant to    address these issues.  CAPWAP effectively splits the fat AP    functionality into two network elements...