IETF Logo Mail Archive

Re: [Capwap] Editorial nit in the Abstract ofdraft-ietf-capwap-protocol-specification-12.txt

"Pat Calhoun (pacalhou)" <pcalhoun@cisco.com> Wed, 17 September 2008 13:42 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 6737D3A6906 for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 17 Sep 2008 06:42:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.525
X-Spam-Level:
X-Spam-Status: No, score=-3.525 tagged_above=-999 required=5 tests=[AWL=0.074, 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 MYiBVQKdpRb4 for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 17 Sep 2008 06:42:21 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 765B33A6821 for <capwap-archive@lists.ietf.org>; Wed, 17 Sep 2008 06:42:21 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 64A961C4050D for <capwap-archive@lists.ietf.org>; Wed, 17 Sep 2008 06:42:31 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31]) by mx2.tigertech.net (Postfix) with ESMTP id F23C744005D for <capwap@lists.tigertech.net>; Wed, 17 Sep 2008 06:42:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx1.tigertech.net (Postfix) with ESMTP id DFDA434AC117 for <capwap@frascone.com>; Wed, 17 Sep 2008 06:42:26 -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 7DB3734AC10E for <capwap@frascone.com>; Wed, 17 Sep 2008 06:42:26 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 0 (Low); Whitelisted TTSSA (171.71.176.117 whitelisted by list.dnswl.org 9.2)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by mx1.tigertech.net (Postfix) with ESMTP for <capwap@frascone.com>; Wed, 17 Sep 2008 06:42:26 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,415,1217808000"; d="scan'208";a="157153556"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 17 Sep 2008 13:42:26 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m8HDgQnE004471; Wed, 17 Sep 2008 06:42:26 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m8HDgQs0018619; Wed, 17 Sep 2008 13:42:26 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 17 Sep 2008 06:42:25 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 17 Sep 2008 06:42:25 -0700
Message-ID: <4FF84B0BC277FF45AA27FE969DD956A2067860C1@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04FA1EEF@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Capwap] Editorial nit in the Abstract ofdraft-ietf-capwap-protocol-specification-12.txt
Thread-Index: AckYrDpfz8xdXBzjSzOjsmD0mtjCzgAHi6+Q
References: <EDC652A26FB23C4EB6384A4584434A04FA1EEF@307622ANEX5.global.avaya.com>
From: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, capwap@frascone.com
X-OriginalArrivalTime: 17 Sep 2008 13:42:25.0968 (UTC) FILETIME=[385AEB00:01C918CB]
Authentication-Results: sj-dkim-1; header.From=pcalhoun@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Subject: Re: [Capwap] Editorial nit in the Abstract ofdraft-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

Thanks Dan. The reason why it was stated in this manner is that it is
the title of RFC 4564. However, it does look strange, so I am proposing
changing the text to:

<proposed text>
   This specification defines the Control And Provisioning of Wireless
   Access Points (CAPWAP) Protocol, meeting the objectives defined by
   the CAPWAP working group in RFC 4564.  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.
</proposed text>

Created issue 195 to track this.

PatC
-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] 
Sent: Wednesday, September 17, 2008 3:01 AM
To: capwap@frascone.com
Subject: [Capwap] Editorial nit in the Abstract
ofdraft-ietf-capwap-protocol-specification-12.txt

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
_________________________________________________________________
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