Re: [Capwap] FW: review of draft-ietf-capwap-dhc-ac-option-01.txt
"Pat Calhoun (pacalhou)" <pcalhoun@cisco.com> Wed, 17 September 2008 13:18 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 4FB5F28C25B for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 17 Sep 2008 06:18:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.523
X-Spam-Level:
X-Spam-Status: No, score=-3.523 tagged_above=-999 required=5 tests=[AWL=0.076, 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 L5a63YxC+A20 for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 17 Sep 2008 06:18:40 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 6379028C148 for <capwap-archive@lists.ietf.org>; Wed, 17 Sep 2008 06:18:40 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id CB2EF430B8F for <capwap-archive@lists.ietf.org>; Wed, 17 Sep 2008 06:18:53 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31]) by mx2.tigertech.net (Postfix) with ESMTP id BB04244005D for <capwap@lists.tigertech.net>; Wed, 17 Sep 2008 06:18:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx1.tigertech.net (Postfix) with ESMTP id A70C634AC117 for <capwap@frascone.com>; Wed, 17 Sep 2008 06:18:48 -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 459EF34AC110 for <capwap@frascone.com>; Wed, 17 Sep 2008 06:18:48 -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:18:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,415,1217808000"; d="scan'208";a="157139572"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 17 Sep 2008 13:18:39 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m8HDIdLi025625; Wed, 17 Sep 2008 06:18:39 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m8HDIdXH001387; Wed, 17 Sep 2008 13:18:39 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:18:37 -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:18:37 -0700
Message-ID: <4FF84B0BC277FF45AA27FE969DD956A2067860BB@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04FA1EF9@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Capwap] FW: review of draft-ietf-capwap-dhc-ac-option-01.txt
Thread-Index: AcjjL+OmnJqDk5TSRym/pRJSPYsq5Q1fj6EgAAZUqdA=
References: <EDC652A26FB23C4EB6384A4584434A04FA1EF9@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:18:37.0333 (UTC) FILETIME=[E4D28450:01C918C7]
Authentication-Results: sj-dkim-1; header.From=pcalhoun@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Subject: Re: [Capwap] FW: review of draft-ietf-capwap-dhc-ac-option-01.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
Here is what I did with Francis' comments: > - the first general question is about references to DHCP: > * the whole document, including the Abstract, assumes the reader > already knows what is DHCP. I have no concern about this but perhaps > I should? I propose to keep this point closed until someone else raises it > (so it could enter into the any other LC comments) I did not address this given no one else raised it during LC. > > * 1.2 (Terminology) is only about CAPWAP, IMHO even you don't abuse of > DHCP specific terms it is a good place to add DHCP references (the > three at the beginning of the Security Considerations for instance). I added a pointer to RFC 2131 and RFC 3735 in the Terminology section > > - the second question is about the use (or abuse) of 2119 keywords at > unusual places, namely in the Introduction (i.e., before the 2119 > reference) and in the IANA Considerations. But it is only a question > of usage/style... Yes, this was addressed > > - in TOC and section 6: Acknowledgements -> Acknowledgments After figuring out that I have been misspelling the word all this time (well, maybe I should say I never realized Canadians spelled it differently from US, even after being here for over 10 years), yes I fixed it. PatC > -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Wednesday, September 17, 2008 3:15 AM To: capwap@frascone.com Subject: [Capwap] FW: review of draft-ietf-capwap-dhc-ac-option-01.txt Have Francis' comments been answered? Dan -----Original Message----- From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr] Sent: Friday, July 11, 2008 11:27 AM To: gen-art@ietf.org Cc: pcalhoun@cisco.com; Romascanu, Dan (Dan) Subject: review of draft-ietf-capwap-dhc-ac-option-01.txt I have been selected as the General Area Review Team (Gen-ART) reviewer for this draft (for background on Gen-ART, please see http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html). Please resolve these comments along with any other Last Call comments you may receive. Document: draft-ietf-capwap-dhc-ac-option-01.txt Reviewer: Francis Dupont Review Date: 2008-07-10 IETF LC End Date: 2008-07-14 IESG Telechat date: unknown Summary: Ready with nits Comments: I have two general questions and the usual editioral things (here editorial means they can be handled by the RFC Editor): - the first general question is about references to DHCP: * the whole document, including the Abstract, assumes the reader already knows what is DHCP. I have no concern about this but perhaps I should? I propose to keep this point closed until someone else raises it (so it could enter into the any other LC comments) * 1.2 (Terminology) is only about CAPWAP, IMHO even you don't abuse of DHCP specific terms it is a good place to add DHCP references (the three at the beginning of the Security Considerations for instance). - the second question is about the use (or abuse) of 2119 keywords at unusual places, namely in the Introduction (i.e., before the 2119 reference) and in the IANA Considerations. But it is only a question of usage/style... - in TOC and section 6: Acknowledgements -> Acknowledgments Regards Francis.Dupont@fdupont.fr _________________________________________________________________ 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
- [Capwap] FW: review of draft-ietf-capwap-dhc-ac-o… Romascanu, Dan (Dan)
- Re: [Capwap] FW: review of draft-ietf-capwap-dhc-… Pat Calhoun (pacalhou)
- Re: [Capwap] FW: review of draft-ietf-capwap-dhc-… Romascanu, Dan (Dan)
- Re: [Capwap] FW: review of draft-ietf-capwap-dhc-… Pat Calhoun (pacalhou)
- Re: [Capwap] FW: review of draft-ietf-capwap-dhc-… Romascanu, Dan (Dan)