[Capwap] 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: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3079028C151 for <ietfarch-capwap-archive@core3.amsl.com>; Thu, 5 Mar 2009 16:56:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.333
X-Spam-Level:
X-Spam-Status: No, score=-2.333 tagged_above=-999 required=5 tests=[AWL=0.666, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_LOW=-1]
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 NAEouhnLUjMt for <ietfarch-capwap-archive@core3.amsl.com>; Thu, 5 Mar 2009 16:56:05 -0800 (PST)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 24EE628C11B for <capwap-archive@lists.ietf.org>; Thu, 5 Mar 2009 16:56:05 -0800 (PST)
Received: from hermes.tigertech.net (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 55F5B4306A2 for <capwap-archive@lists.ietf.org>; Thu, 5 Mar 2009 16:56:35 -0800 (PST)
Received: from mx3.tigertech.net (morbo.tigertech.net [67.131.251.53]) by mx2.tigertech.net (Postfix) with ESMTP id 622ACD0404A for <capwap@lists.tigertech.net>; Thu, 5 Mar 2009 16:56:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx3.tigertech.net (Postfix) with ESMTP id 4028A1CD490 for <capwap@frascone.com>; Thu, 5 Mar 2009 16:56:30 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at morbo.tigertech.net
Received: from mx3.tigertech.net (localhost [127.0.0.1]) by mx3.tigertech.net (Postfix) with ESMTP id EF1421CD48E for <capwap@frascone.com>; Thu, 5 Mar 2009 16:56:29 -0800 (PST)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (High) (P0); Whitelisted TTSSA (rfc-editor@rfc-editor.org whitelisted)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by mx3.tigertech.net (Postfix) with ESMTP for <capwap@frascone.com>; Thu, 5 Mar 2009 16:56:29 -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
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
Subject: [Capwap] RFC 5415 on Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>, <mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>, <mailto:capwap-request@frascone.com?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com
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
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap
Archives: http://lists.frascone.com/pipermail/capwap