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

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 11 November 2008 17:29 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 5C9B228C205 for <ietfarch-capwap-archive@core3.amsl.com>; Tue, 11 Nov 2008 09:29:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.046
X-Spam-Level:
X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[AWL=1.553, BAYES_00=-2.599, 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 XGAAJvJoI5I3 for <ietfarch-capwap-archive@core3.amsl.com>; Tue, 11 Nov 2008 09:29:46 -0800 (PST)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 67A4A28C1F2 for <capwap-archive@lists.ietf.org>; Tue, 11 Nov 2008 09:29:46 -0800 (PST)
Received: from hermes.tigertech.net (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id B04D3430268 for <capwap-archive@lists.ietf.org>; Tue, 11 Nov 2008 09:29:47 -0800 (PST)
Received: from mx3.tigertech.net (morbo.tigertech.net [67.131.251.53]) by mx2.tigertech.net (Postfix) with ESMTP id A8810440056 for <capwap@lists.tigertech.net>; Tue, 11 Nov 2008 09:29:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx3.tigertech.net (Postfix) with ESMTP id E0B821A04F9 for <capwap@frascone.com>; Tue, 11 Nov 2008 09:29:40 -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 3A8751A04F1 for <capwap@frascone.com>; Tue, 11 Nov 2008 09:29:37 -0800 (PST)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low) (P0); Accepted (dynamic or unknown reverse DNS)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by mx3.tigertech.net (Postfix) with ESMTP for <capwap@frascone.com>; Tue, 11 Nov 2008 09:29:34 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,584,1220241600"; d="scan'208";a="127967812"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 11 Nov 2008 12:29:32 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 11 Nov 2008 12:29:32 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 11 Nov 2008 18:29:30 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A040111351A@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Capwap] Protocol Action: 'CAPWAP Protocol Specification' to Proposed Standard
Thread-Index: AclEIgE4cGk61BNVTGeKVbKDrwupegAAMDwg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: capwap@frascone.com
Cc: "ext Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Subject: [Capwap] FW: 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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

Congratulations to the editors, chairs and the whole working group for
meeting this major milestone. 

Special thanks also to Bert Wijnen, who was the Area Director by the
time the WG was initiated. 

Dan

-----Original Message-----
From: The IESG [mailto:iesg-secretary@ietf.org] 
Sent: Tuesday, November 11, 2008 7:21 PM
To: IETF-Announce
Cc: capwap chair; Internet Architecture Board; capwap mailing list; RFC
Editor
Subject: [Capwap] Protocol Action: 'CAPWAP Protocol Specification' to
Proposed Standard

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-specifica
tion-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
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

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