[rfc-dist] RFC 5413 on SLAPP: Secure Light Access Point Protocol

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Mon Feb 22 17:46:32 PST 2010

A new Request for Comments is now available in online RFC libraries.

        RFC 5413

        Title:      SLAPP: Secure Light Access Point 
        Author:     P. Narasimhan, D. Harkins,
                    S. Ponnuswamy
        Status:     Informational
        Date:       February 2010
        Mailbox:    partha at arubanetworks.com, 
                    dharkins at arubanetworks.com, 
                    subbu at arubanetworks.com
        Pages:      75
        Characters: 147426
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-narasimhan-ietf-slapp-01.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5413.txt

The Control and Provisioning of Wireless Access Points (CAPWAP)
problem statement describes a problem that needs to be
addressed before a wireless LAN (WLAN) network designer can construct
a solution composed of Wireless Termination Points (WTP) and Access
Controllers (AC) from multiple, different vendors.  One of the
primary goals is to find a solution that solves the interoperability
between the two classes of devices (WTPs and ACs) that then enables
an AC from one vendor to control and manage a WTP from another.

In this document, we present a protocol that forms the common
technology-independent framework and the ability to negotiate and
add, on top of this framework, a control protocol that contains a
technology-dependent component to arrive at a complete solution.  We
have also presented two such control protocols -- an 802.11 Control
protocol, and another, more generic image download protocol, in this

Even though the text in this document is written to specifically address
the problem stated in RFC 3990, the solution can be applied to any problem
that has a controller (equivalent to the AC) managing one or more
network elements (equivalent to the WTP).  This document defines a 
Historic Document for the Internet community.

This document is a product of the Independent Submissions stream.

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

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 at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC

More information about the rfc-dist mailing list