RFC 5412 on Lightweight Access Point Protocol

rfc-editor@rfc-editor.org Tue, 23 February 2010 01:44 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 7F01D28C4CF for <ietf-announce@core3.amsl.com>; Mon, 22 Feb 2010 17:44:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.565
X-Spam-Status: No, score=-2.565 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id OZLvpQ6a+YRg for <ietf-announce@core3.amsl.com>; Mon, 22 Feb 2010 17:44:19 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 89D3E28C17F for <ietf-announce@ietf.org>; Mon, 22 Feb 2010 17:44:19 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4A468130002; Mon, 22 Feb 2010 17:46:20 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5412 on Lightweight Access Point Protocol
From: rfc-editor@rfc-editor.org
Message-Id: <20100223014620.4A468130002@rfc-editor.org>
Date: Mon, 22 Feb 2010 17:46:20 -0800
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Feb 2010 01:44:20 -0000

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

        RFC 5412

        Title:      Lightweight Access Point Protocol 
        Author:     P. Calhoun, R. Suri,
                    N. Cam Winget, M. Williams,
                    S. Hares, B. O'Hara,
                    S. Kelly
        Status:     Historic
        Date:       February 2010
        Mailbox:    pcalhoun@cisco.com, 
                    ncamwing@cisco.com,  gwhiz@gwhiz.com, 
                    shares@ndzh.com,  bob.ohara@computer.org, 
        Pages:      125
        Characters: 262297
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ohara-capwap-lwapp-04.txt

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

In recent years, there has been a shift in wireless LAN (WLAN) product
architectures from autonomous access points to centralized control of
lightweight access points.  The general goal has been to move most
of the traditional wireless functionality such as access control
(user authentication and authorization), mobility, and radio
management out of the access point into a centralized controller.

The IETF's CAPWAP (Control and Provisioning of Wireless Access Points)
WG has identified that a standards-based protocol is necessary between
a wireless Access Controller and Wireless Termination Points (the
latter are also commonly referred to as Lightweight Access Points).
This specification defines the Lightweight Access Point Protocol
(LWAPP), which addresses the CAPWAP's (Control and Provisioning of
Wireless Access Points) protocol requirements.  Although the LWAPP
protocol is designed to be flexible enough to be used for a variety of
wireless technologies, this specific document describes the base
protocol and an extension that allows it to be used with the IEEE's
802.11 wireless LAN protocol.  This document defines a Historic Document
for the Internet community.

This document is a product of the Independent Submissions stream.

HISTORIC: This memo defines a Historic Document 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@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