Re: [Capwap] CAPWAP IESG Review Comment E2
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 18 June 2008 12:59 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 4BB9528C197 for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 18 Jun 2008 05:59:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.441
X-Spam-Level:
X-Spam-Status: No, score=-1.441 tagged_above=-999 required=5 tests=[AWL=-1.142, BAYES_00=-2.599, MANGLED_ONLINE=2.3]
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 Kv3-7OLJeXth for <ietfarch-capwap-archive@core3.amsl.com>; Wed, 18 Jun 2008 05:59:26 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 3A8BF28C109 for <capwap-archive@lists.ietf.org>; Wed, 18 Jun 2008 05:59:26 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 24AFB4332C3 for <capwap-archive@lists.ietf.org>; Wed, 18 Jun 2008 06:00:14 -0700 (PDT)
Received: from hgblob.mail.tigertech.net (mx1.tigertech.net [64.62.209.31]) by mx2.tigertech.net (Postfix) with ESMTP id 48CE14400C5 for <capwap@lists.tigertech.net>; Wed, 18 Jun 2008 06:00:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx1.tigertech.net (Postfix) with ESMTP id B87AB34AC1FC for <capwap@frascone.com>; Wed, 18 Jun 2008 06:00:04 -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 C6AFF34AC38C for <capwap@frascone.com>; Wed, 18 Jun 2008 06:00:01 -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, 18 Jun 2008 06:00:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,664,1204520400"; d="scan'208";a="131769770"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.avaya.com with ESMTP; 18 Jun 2008 08:59:59 -0400
X-IronPort-AV: E=Sophos;i="4.27,664,1204520400"; d="scan'208";a="220302556"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 18 Jun 2008 08:59:58 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 18 Jun 2008 14:59:25 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04D21241@307622ANEX5.global.avaya.com>
In-Reply-To: <4FF84B0BC277FF45AA27FE969DD956A205EFE0B7@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Capwap] CAPWAP IESG Review Comment E2
Thread-Index: AcjRQp62pChK8mmsRBe/zh+koYDKfwAAHRCQ
References: <4FF84B0BC277FF45AA27FE969DD956A205EFE0B7@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] CAPWAP IESG Review Comment E2
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
OK with me, pending on the respective changes being having been made correctly. Dan > -----Original Message----- > From: Pat Calhoun (pacalhou) [mailto:pcalhoun@cisco.com] > Sent: Wednesday, June 18, 2008 3:56 PM > To: capwap@frascone.com > Subject: [Capwap] CAPWAP IESG Review Comment E2 > > All, > > The IESG Comment is as follows: > > E2 - A number of editorial problems have been detected when > running idnits. Please fix them: > > ------------------ > > Checking nits according to > http://www.ietf.org/ietf/1id-guidelines.txt: > > -------------------------------------------------------------- > ---------- > ---- > > == No 'Intended status' indicated for this document; > assuming Proposed > Standard > > > Checking nits according to http://www.ietf.org/ID-Checklist.html: > > -------------------------------------------------------------- > ---------- > ---- > > No issues found here. > > Miscellaneous warnings: > > -------------------------------------------------------------- > ---------- > ---- > > == Using lowercase 'not' together with uppercase 'MUST' is > not an accepted > usage according to RFC 2119. Please use 'MUST NOT' (if > that is what you > mean). > > Found 'MUST not' in this paragraph: > > Unless otherwise specified, a control message that lists a set of > supported (or expected) message elements MUST not expect > the message > elements to be in any specific order. The sender MAY > include the message > elements in any order. Unless otherwise noted, one > message element of > each type is present in a given control message. > > > Checking references for intended status: Proposed Standard > > -------------------------------------------------------------- > ---------- > ---- > > (See RFCs 3967 and 4897 for information about using > normative references > to lower-maturity documents in RFCs) > > == Missing Reference: 'ChangeCipherSpec' is mentioned on > line 1456, but not > defined > '[ChangeCipherSpec]...' > > == Unused Reference: 'RFC2132' is defined on line 6048, but > no explicit > reference was found in the text > '[RFC2132] Alexander, S. and R. Droms, "DHCP Options > and BOOTP Vendo...' > > ** Obsolete normative reference: RFC 3280 (Obsoleted by RFC 5280) > > ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) > > ** Obsolete normative reference: RFC 1883 (Obsoleted by RFC 2460) > > -- Unexpected draft version: The latest known version of > draft-calhoun-dhc-capwap-ac-option is -00, but you're > referring to -02. > > -- Possible downref: Normative reference to a draft: ref. > 'I-D.calhoun-dhc-capwap-ac-option' (No intended status > found in state > file of draft-calhoun-dhc-capwap-ac-option) > > == Outdated reference: draft-housley-aaa-key-mgmt has been > published as RFC > 4962 > ---------------------------- > > I have made the necessary changes to address all of the issues. > > PatC > _________________________________________________________________ > 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] CAPWAP IESG Review Comment E2 Pat Calhoun (pacalhou)
- Re: [Capwap] CAPWAP IESG Review Comment E2 Romascanu, Dan (Dan)
- Re: [Capwap] CAPWAP IESG Review Comment E2 Pat Calhoun (pacalhou)