RFC 5414 on Wireless LAN Control Protocol (WiCoP)

rfc-editor@rfc-editor.org Thu, 04 February 2010 01:46 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 [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BA52B3A695C for <ietf-announce@core3.amsl.com>; Wed, 3 Feb 2010 17:46:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.557
X-Spam-Level:
X-Spam-Status: No, score=-2.557 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 GzuFAP+R6RZg for <ietf-announce@core3.amsl.com>; Wed, 3 Feb 2010 17:46:18 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 10BAA3A685D for <ietf-announce@ietf.org>; Wed, 3 Feb 2010 17:46:18 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 80F54130001; Wed, 3 Feb 2010 17:47:02 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5414 on Wireless LAN Control Protocol (WiCoP)
From: rfc-editor@rfc-editor.org
Message-Id: <20100204014702.80F54130001@rfc-editor.org>
Date: Wed, 03 Feb 2010 17:47:02 -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: Thu, 04 Feb 2010 01:46:18 -0000

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

        
        RFC 5414

        Title:      Wireless LAN Control Protocol (WiCoP) 
        Author:     S. Iino, S. Govindan,
                    M. Sugiura, H. Cheng
        Status:     Informational
        Date:       February 2010
        Mailbox:    iino.satoshi@jp.panasonic.com, 
                    saravanan.govindan@sg.panasonic.com, 
                    sugiura.mikihito@jp.panasonic.com,     
                    hong.cheng@sg.panasonic.com
        Pages:      54
        Characters: 118969
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iino-capwap-wicop-02.txt

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

The popularity of wireless local area networks (WLANs) has led to
widespread deployments across different establishments.  It has also
translated into an increasing scale of the WLANs.  Large-scale
deployments made of large numbers of wireless termination points
(WTPs) and covering substantial areas are increasingly common.

The Wireless LAN Control Protocol (WiCoP) described in this document
allows for the control and provisioning of large-scale WLANs.  It
enables central management of these networks and realizes the
objectives set forth for the Control And Provisioning of Wireless
Access Points (CAPWAP).  This document defines a Historic Document for 
the Internet community.


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
Association Management Solutions, LLC