[Capwap] FW: Protocol Action: 'CAPWAP Access Controller DHCP Option' to Proposed Standard

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 28 October 2008 20:34 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 DE9863A6C00 for <ietfarch-capwap-archive@core3.amsl.com>; Tue, 28 Oct 2008 13:34:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.027
X-Spam-Level:
X-Spam-Status: No, score=-3.027 tagged_above=-999 required=5 tests=[AWL=0.572, 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 QWmcdCAZ7WJ4 for <ietfarch-capwap-archive@core3.amsl.com>; Tue, 28 Oct 2008 13:34:23 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 06DBD3A6C7F for <capwap-archive@lists.ietf.org>; Tue, 28 Oct 2008 13:34:23 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id A209243028A for <capwap-archive@lists.ietf.org>; Tue, 28 Oct 2008 13:34:22 -0700 (PDT)
Received: from mx3.tigertech.net (mx3.tigertech.net [64.62.209.33]) by mx2.tigertech.net (Postfix) with ESMTP id 16C23440006 for <capwap@lists.tigertech.net>; Tue, 28 Oct 2008 13:34:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx3.tigertech.net (Postfix) with ESMTP id 08EE11CD485 for <capwap@frascone.com>; Tue, 28 Oct 2008 13:34:15 -0700 (PDT)
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 2AFDA1CD489 for <capwap@frascone.com>; Tue, 28 Oct 2008 13:34:14 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low) (P0); Accepted (Neutral)
Received: from nj300815-nj-outbound.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by mx3.tigertech.net (Postfix) with ESMTP for <capwap@frascone.com>; Tue, 28 Oct 2008 13:34:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,501,1220241600"; d="scan'208";a="140171889"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 28 Oct 2008 16:34:12 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 28 Oct 2008 16:34:12 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 28 Oct 2008 21:34:10 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A040109A8C2@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Capwap] Protocol Action: 'CAPWAP Access Controller DHCP Option' to Proposed Standard
Thread-Index: Ack5JSFb5iYGrfsVS9imXTS9ZbwEJwAFzsiw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: capwap@frascone.com
Subject: [Capwap] FW: Protocol Action: 'CAPWAP Access Controller DHCP Option' 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 editor, contributors, chairs and to the whole
Working Group for the approval of this document. 

Regards,

Dan


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

The IESG has approved the following document:

- 'CAPWAP Access Controller DHCP Option '
   <draft-ietf-capwap-dhc-ac-option-02.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-dhc-ac-option-02.t
xt

Technical Summary

   The Control And Provisioning of Wireless Access Points Protocol
   allows a Wireless Termination Point to use DHCP to discover the
   Access Controllers it is to connect to.  This document describes the
   DHCP options to be used by the CAPWAP protocol.

Working Group Summary

  This document is a work item of the CAPWAP WG and respresents
  the consensus of the group.

Document Quality

  This document was reviewed within the CAPWAP WG and no issues
  were raised in WG Last Call. Francis Dupont reviewed it for the GenART
  and Dan Romascanu performed the OPS Area Director review. 

Personnel

   Margaret Wasserman is the document shepherd and Dan Romascanu is the 
   responsible 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