IETF Logo Mail Archive

[Capwap] Editorial nit in the Abstract of draft-ietf-capwap-protocol-specification-12.txt

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 17 September 2008 10:00 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 4C7C328C29A for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 17 Sep 2008 03:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.857
X-Spam-Level:
X-Spam-Status: No, score=-2.857 tagged_above=-999 required=5 tests=[AWL=0.742, 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 foGkXP3JdGU2 for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 17 Sep 2008 03:00:31 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 9167128C1A9 for <capwap-archive@lists.ietf.org>; Wed, 17 Sep 2008 03:00:31 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id A81E74305A9 for <capwap-archive@lists.ietf.org>; Wed, 17 Sep 2008 03:00:42 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31]) by mx2.tigertech.net (Postfix) with ESMTP id DA45C44005B for <capwap@lists.tigertech.net>; Wed, 17 Sep 2008 03:00:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx1.tigertech.net (Postfix) with ESMTP id CBFA034AC0B7 for <capwap@frascone.com>; Wed, 17 Sep 2008 03:00:38 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from mx1.tigertech.net (localhost [127.0.0.1]) by mx1.tigertech.net (Postfix) with ESMTP id 55A0734AC0E0 for <capwap@frascone.com>; Wed, 17 Sep 2008 03:00:38 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low); Accepted (Neutral)
Received: from co300216-co-outbound.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by mx1.tigertech.net (Postfix) with ESMTP for <capwap@frascone.com>; Wed, 17 Sep 2008 03:00:38 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,414,1217822400"; d="scan'208";a="143911795"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.avaya.com with ESMTP; 17 Sep 2008 06:00:37 -0400
X-IronPort-AV: E=Sophos;i="4.32,414,1217822400"; d="scan'208";a="280629100"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 17 Sep 2008 06:00:36 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 17 Sep 2008 12:00:35 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04FA1EEF@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Editorial nit in the Abstract of draft-ietf-capwap-protocol-specification-12.txt
Thread-Index: AckYrDpfz8xdXBzjSzOjsmD0mtjCzg==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: capwap@frascone.com
Subject: [Capwap] Editorial nit in the Abstract of draft-ietf-capwap-protocol-specification-12.txt
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

While preparing the ballot write-up for the IESG telechat for
draft-ietf-capwap-protocol-specification-12.txt I observed an editorial
nit in the Abstract section. 

   This specification defines the Control And Provisioning of Wireless
   Access Points (CAPWAP) Protocol.  The CAPWAP protocol meets the
   Objectives for Control and Provisioning of Wireless Access Points
   (CAPWAP).  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.

CAPWAP is expanded twice which seems unnecessary. 

Please correct this with the RFC Editor or in the next version of the
document if there will be one. 

Thanks and Regards,

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

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

v2.23.0 | Report a Bug | By Email