A new Request for Comments is now available in online RFC libraries.
RFC 5418
Title: Control And Provisioning of Wireless
Access Points (CAPWAP) Threat Analysis for
IEEE 802.11 Deployments
Author: S. Kelly, T. Clancy
Status: Informational
Date: March 2009
Mailbox: scott@hyperthought.com,
clancy@LTSnet.net
Pages: 34
Characters: 74169
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-capwap-threat-analysis-04.txt
URL: http://www.rfc-editor.org/rfc/rfc5418.txt
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 memo provides information for the Internet community.
This document is a product of the Control And Provisioning of Wireless Access Points Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
USC/Information Sciences Institute
_______________________________________________
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce
