[Capwap] Protocol Action: 'CAPWAP Protocol Specification' to Proposed Standard

The IESG <iesg-secretary@ietf.org> Tue, 11 November 2008 17:22 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 E880F28C0F1 for <ietfarch-capwap-archive@core3.amsl.com>; Tue, 11 Nov 2008 09:22:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 xclQtpOqbLUR for <ietfarch-capwap-archive@core3.amsl.com>; Tue, 11 Nov 2008 09:22:01 -0800 (PST)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 773903A68C5 for <capwap-archive@lists.ietf.org>; Tue, 11 Nov 2008 09:21:55 -0800 (PST)
Received: from hermes.tigertech.net (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 9FBE243025D for <capwap-archive@lists.ietf.org>; Tue, 11 Nov 2008 09:21:56 -0800 (PST)
Received: from mx3.tigertech.net (morbo.tigertech.net [67.131.251.53]) by mx2.tigertech.net (Postfix) with ESMTP id 62615440056 for <capwap@lists.tigertech.net>; Tue, 11 Nov 2008 09:21:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx3.tigertech.net (Postfix) with ESMTP id 778F91A0429 for <capwap@frascone.com>; Tue, 11 Nov 2008 09:21:50 -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 E6B521A0487 for <capwap@frascone.com>; Tue, 11 Nov 2008 09:21:48 -0800 (PST)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (Low) (P0); Whitelisted TTSSA (64.170.98.32 whitelisted by list.dnswl.org 9.2)
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by mx3.tigertech.net (Postfix) with ESMTP for <capwap@frascone.com>; Tue, 11 Nov 2008 09:21:45 -0800 (PST)
Received: by core3.amsl.com (Postfix, from userid 30) id 34D0328C1F2; Tue, 11 Nov 2008 09:20:37 -0800 (PST)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20081111172037.34D0328C1F2@core3.amsl.com>
Date: Tue, 11 Nov 2008 09:20:37 -0800
Cc: capwap chair <capwap-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.org>, capwap mailing list <capwap@frascone.com>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Capwap] Protocol Action: 'CAPWAP Protocol Specification' to Proposed Standard
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

The IESG has approved the following document:

- 'CAPWAP Protocol Specification '
   <draft-ietf-capwap-protocol-specification-15.txt> as a Proposed Standard

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

The IESG contact persons are Dan Romascanu and Ron Bonica.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-specification-15.txt

Technical Summary

  This specification defines the Control And Provisioning of Wireless
  Access Points (CAPWAP) Protocol.  This is a protocol to allow an
  Access Controller (AC) to securely manage the firmware and
  configuration of a set of Wireless Termination Points (WTPs).

  The CAPWAP protocol meets the IETF CAPWAP working group protocol
  requirements.  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.  The CAPWAP
  protocol binding which defines extensions for use with the IEEE
  802.11 wireless LAN protocol is available in a separate document. 
  Extensions are expected to be defined to enable use of the CAPWAP 
  protocol with additional wireless technologies.

Working Group Summary

   This document represents a very strong consensus of the WG.  Earlier
   there was a lot of contention about different aspects of this
   protocol, including (but not limited to) the security model, the basic
   operational model, and what parts of the functionality should be
   mandatory or optional.  However,  consensus was reached
   on all of those points and that consensus is properly reflected in the
   current document.

Document Quality

  The CAPWAP protocol has been extensively reviewed and has been
  updated to address issues raised in those reviewes.  Technical 
  advisors were Charles Clancy, Scott Kelly, Bob O'Hara and David 
  Borman.  Joe Salowey provided an early secdir review, and  
  Pasi Eronen reviewed again at IETF Last Call. Magnus Westerlund and
  Lars Eggert performed an early transport area review. Dan Romascanu 
  performed the OPS Area Review. The document was also reviewed by 
  IEEE 802.11. 

Personnel

  Margaret Wasserman is PROTO-shepherd and Dan Romascanu is shepherding
  AD.

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap