Re: [Capwap] FW: review of draft-ietf-capwap-dhc-ac-option-01.txt
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 17 September 2008 13:46 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 ACC463A689C for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 17 Sep 2008 06:46:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.886
X-Spam-Level:
X-Spam-Status: No, score=-2.886 tagged_above=-999 required=5 tests=[AWL=0.713, 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 ToqJxeBAB2aj for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 17 Sep 2008 06:46:08 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id BA8243A6810 for <capwap-archive@lists.ietf.org>; Wed, 17 Sep 2008 06:46:08 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 434FE430D62 for <capwap-archive@lists.ietf.org>; Wed, 17 Sep 2008 06:46:22 -0700 (PDT)
Received: from mx3.tigertech.net (mx3.tigertech.net [64.62.209.33]) by mx2.tigertech.net (Postfix) with ESMTP id 86BFA44005D for <capwap@lists.tigertech.net>; Wed, 17 Sep 2008 06:46:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx3.tigertech.net (Postfix) with ESMTP id 67B9F19F71C for <capwap@frascone.com>; Wed, 17 Sep 2008 06:46:16 -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 9811519F725 for <capwap@frascone.com>; Wed, 17 Sep 2008 06:46:14 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low); Accepted (Sender first seen 3 mons 19:42:37 ago / 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>; Wed, 17 Sep 2008 06:46:14 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,415,1217822400"; d="scan'208";a="121991147"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 17 Sep 2008 09:46:12 -0400
X-IronPort-AV: E=Sophos;i="4.32,415,1217822400"; d="scan'208";a="280740143"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 17 Sep 2008 09:46:10 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 17 Sep 2008 15:45:33 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04FA2051@307622ANEX5.global.avaya.com>
In-Reply-To: <4FF84B0BC277FF45AA27FE969DD956A2067860BB@xmb-sjc-235.amer.cisco.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/pRJSPYsq5Q1fj6EgAAZUqdAAAPPJ8A==
References: <EDC652A26FB23C4EB6384A4584434A04FA1EF9@307622ANEX5.global.avaya.com> <4FF84B0BC277FF45AA27FE969DD956A2067860BB@xmb-sjc-235.amer.cisco.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Pat Calhoun (pacalhou)" <pcalhoun@cisco.com>, capwap@frascone.com
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
Pat, There was no new version since then, and the document is now in IESG review. I suggest that we include these in the notes to the RFC Editor - can you let me know exactly where the pointers to 2131 and 3735 would fit? Thanks and Regards, Dan > -----Original Message----- > From: Pat Calhoun (pacalhou) [mailto:pcalhoun@cisco.com] > Sent: Wednesday, September 17, 2008 4:19 PM > To: Romascanu, Dan (Dan); capwap@frascone.com > Subject: RE: [Capwap] FW: review of > draft-ietf-capwap-dhc-ac-option-01.txt > > 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)