[storm] idnits review of draft-ietf-storm-ifcpmib-00.txt
"David Harrington" <ietfdbh@comcast.net> Thu, 04 February 2010 17:48 UTC
Return-Path: <ietfdbh@comcast.net>
X-Original-To: storm@core3.amsl.com
Delivered-To: storm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F79D3A6C7F for <storm@core3.amsl.com>; Thu, 4 Feb 2010 09:48:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 8pW+GJaWdhF4 for <storm@core3.amsl.com>; Thu, 4 Feb 2010 09:48:56 -0800 (PST)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by core3.amsl.com (Postfix) with ESMTP id 9B5833A68F9 for <storm@ietf.org>; Thu, 4 Feb 2010 09:48:55 -0800 (PST)
Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta12.westchester.pa.mail.comcast.net with comcast id dqwn1d0010SCNGk5Ctpj8k; Thu, 04 Feb 2010 17:49:43 +0000
Received: from Harrington73653 ([24.147.240.98]) by omta09.westchester.pa.mail.comcast.net with comcast id dtpj1d00D284sdk3Vtpj24; Thu, 04 Feb 2010 17:49:43 +0000
From: David Harrington <ietfdbh@comcast.net>
To: storm@ietf.org
Date: Thu, 04 Feb 2010 12:49:42 -0500
Message-ID: <02d401caa5c2$6e2b2440$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acqlwm3H51u5v0C/ReqVZHLSFUL+fQ==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: [storm] idnits review of draft-ietf-storm-ifcpmib-00.txt
X-BeenThere: storm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Storage Maintenance WG <storm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/storm>
List-Post: <mailto:storm@ietf.org>
List-Help: <mailto:storm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2010 17:48:57 -0000
Hi, idnits 2.12.00 reports a number of problems that will need to be fixed. tmp/draft-ietf-storm-ifcpmib-00.txt: tmp/draft-ietf-storm-ifcpmib-00.txt(201): Line is too long: the offending characters are 'precated.' tmp/draft-ietf-storm-ifcpmib-00.txt(288): Line is too long: the offending characters are 'ft; see' tmp/draft-ietf-storm-ifcpmib-00.txt(340): Line is too long: the offending characters are '."' tmp/draft-ietf-storm-ifcpmib-00.txt(1485): RFC 2119 keyword: It is RECOMMENDED that implementers consider the security features as. tmp/draft-ietf-storm-ifcpmib-00.txt(1491): RFC 2119 keyword: RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to. tmp/draft-ietf-storm-ifcpmib-00.txt(1575): Line is too long: the offending characters are 'ng and' tmp/draft-ietf-storm-ifcpmib-00.txt(1576): Line is too long: the offending characters are ' wish to' Checking boilerplate required by RFC 5378 and the IETF Trust (see http://trustee.ietf.org/license-info): ---------------------------------------------------------------------- ------ ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: "This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License." ... text found in draft: "This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of .................................^ this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document." (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See http://trustee.ietf.org/license-info/.) Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt: ---------------------------------------------------------------------- ------ No issues found here. Checking nits according to http://www.ietf.org/ID-Checklist.html: ---------------------------------------------------------------------- ------ ** There are 5 instances of too long lines in the document, the longest one being 9 characters in excess of 72. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119, paragraph 2: "The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119." Miscellaneous warnings: ---------------------------------------------------------------------- ------ == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document has a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. Does it really need the disclaimer? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------- ------ (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC4172' is defined on line 1336, but no explicit reference was found in the text '[RFC4172] Monia, C., Mullendore, R., Travostino, F., Jeong, W., and...' ** Obsolete normative reference: RFC 2021 (Obsoleted by RFC 4502) Summary: 4 errors (**), 2 warnings (==), 1 comment (--). David Harrington dbharrington@comcast.net ietfdbh@comcast.net dharrington@huawei.com
- [storm] idnits review of draft-ietf-storm-ifcpmib… David Harrington