RFC 5415 on Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification

rfc-editor@rfc-editor.org Fri, 06 March 2009 00:56 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6BFCB3A69B0 for <ietf-announce@core3.amsl.com>; Thu, 5 Mar 2009 16:56:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.83
X-Spam-Level:
X-Spam-Status: No, score=-16.83 tagged_above=-999 required=5 tests=[AWL=0.169, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wTuJlJ8f8RiP for <ietf-announce@core3.amsl.com>; Thu, 5 Mar 2009 16:55:59 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 83D243A693C for <ietf-announce@ietf.org>; Thu, 5 Mar 2009 16:55:59 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 0FB9624055B; Thu, 5 Mar 2009 16:54:58 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5415 on Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification
From: rfc-editor@rfc-editor.org
Message-Id: <20090306005458.0FB9624055B@bosco.isi.edu>
Date: Thu, 05 Mar 2009 16:54:58 -0800
Cc: capwap@frascone.com, 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: Fri, 06 Mar 2009 00:56:00 -0000

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

        
        RFC 5415

        Title:      Control And Provisioning of Wireless 
                    Access Points (CAPWAP) Protocol Specification 
        Author:     P. Calhoun, Ed.,
                    M. Montemurro, Ed.,
                    D. Stanley, Ed.
        Status:     Standards Track
        Date:       March 2009
        Mailbox:    pcalhoun@cisco.com, 
                    mmontemurro@rim.com, 
                    dstanley@arubanetworks.com
        Pages:      155
        Characters: 345381
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-capwap-protocol-specification-15.txt

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

This specification defines the Control And Provisioning of Wireless
Access Points (CAPWAP) Protocol, meeting the objectives defined by
the CAPWAP Working Group in RFC 4564.  The CAPWAP protocol is
designed to be flexible, allowing it to be used for a variety of
wireless technologies.  This document describes the base CAPWAP
protocol, while separate binding extensions will enable its use with
additional wireless technologies.  [STANDARDS TRACK]

This document is a product of the Control And Provisioning of Wireless Access Points Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  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