RE: [ipcdn] idnits and smilint on Cable Device MIB Draft 09
Marez Kevin-MGI1375 <Kevin.Marez@motorola.com> Mon, 27 June 2005 19:26 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DmzFR-0001Ym-8i; Mon, 27 Jun 2005 15:26:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DmzFO-0001Yh-9S for ipcdn@megatron.ietf.org; Mon, 27 Jun 2005 15:26:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27493 for <ipcdn@ietf.org>; Mon, 27 Jun 2005 15:26:20 -0400 (EDT)
Received: from motgate2.mot.com ([144.189.100.101]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DmzeZ-0006TQ-Ij for ipcdn@ietf.org; Mon, 27 Jun 2005 15:52:25 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234]) by motgate2.mot.com (8.12.11/Motgate2) with ESMTP id j5RJbHk1006608 for <ipcdn@ietf.org>; Mon, 27 Jun 2005 12:37:17 -0700 (MST)
Received: from ca25exm01.GI.COM (ca25exm01.w1.bcs.mot.com [168.84.84.121]) by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id j5RJTdR7016468 for <ipcdn@ietf.org>; Mon, 27 Jun 2005 14:29:39 -0500 (CDT)
Received: by ca25exm01 with Internet Mail Service (5.5.2657.72) id <K022LBKV>; Mon, 27 Jun 2005 12:26:08 -0700
Message-ID: <D5A7E45D575DD61180130002A5DB377C12F98F3D@ca25exm01>
From: Marez Kevin-MGI1375 <Kevin.Marez@motorola.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>, "Ipcdn \\(E-mail\\)" <ipcdn@ietf.org>
Subject: RE: [ipcdn] idnits and smilint on Cable Device MIB Draft 09
Date: Mon, 27 Jun 2005 12:26:05 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc:
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>, <mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>, <mailto:ipcdn-request@ietf.org?subject=subscribe>
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org
Randy, Thanks very much for the speedy review! Regarding your 'not-so-good news', I think what you wanted to say was that the old docsDevCmCompliance should be deprecated, and that there will be a docDevCmComplianceRev1 (or whatever a good name would be) that has only the "current" stuff from docsDevCmCompliance. Alternatively, you could keep the old compliance stuff as-is, and just add a docDevCmComplianceRev1. It depends on the message you want to send. we had actually discussed this previously and reached the following conclusion (this was per an "internal" discussion with Rich Woundy and others in response to the question of having compliance statements contain deprecated objects): Hopefully the MIB doctors are OK with these compliance statements as-is. Note the following text from the MIB guidelines, page 30 of <http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-03 .txt>: - The status of a compliance statement is independent of the status of its members. Thus, a current compliance statement MAY refer to deprecated object groups or notification groups. This may be desirable in certain cases, e.g., a set of widely-deployed object or notification groups may be deprecated when they are replaced by a more up-to-date set of definitions, but compliance statements that refer to them may remain current in order to encourage continued implementation of the deprecated groups. Please let me know if this is acceptable. Thanks very much, Kevin Marez Motorola -----Original Message----- From: ipcdn-bounces@ietf.org [mailto:ipcdn-bounces@ietf.org] On Behalf Of Randy Presuhn Sent: Friday, June 24, 2005 10:51 PM To: Ipcdn \(E-mail\) Subject: [ipcdn] idnits and smilint on Cable Device MIB Draft 09 Hi - Good news and not-so-good news. On ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mibv2-09.txt, I ran http://ietf.levkowetz.com/tools/idnits/idnits.pyht, and it gave the -09 a clean bill of health: idnits 1.74 tmp/draft-ietf-ipcdn-device-mibv2-09.txt: Checking nits according to http://www.ietf.org/ID-Checklist.html: Checking conformance with RFC 3978/3979 boilerplate... the boilerplate looks good. No nits found. Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt: Nothing found here (but these checks do not cover all of 1id-guidelines.txt yet). Miscellaneous warnings: None. No nits found. When I ran smilint 0.4.3, things were a bit more interesting. (I used the smilint@ibr.cs.tu-bs.de service) It identified two issues. mailbody:2489: [5] {index-exceeds-too-large} warning: index of row `docsDevCpeInetEntry' can exceed OID size limit by 141 subidentifier(s) This is OK, the DESCRIPTION of docsDevCpeInetAddr explains the situation in the spirit of the MBI review guidelines section 4.6.6 mailbody:3013: [4] {compliance-group-status} warning: current compliance statement `docsDevCmCompliance' includes deprecated group `docsDevNmAccessGroup' mailbody:3031: [4] {compliance-group-status} warning: current compliance statement `docsDevCmCompliance' includes deprecated group `docsDevNmAccessExtGroup' mailbody:3044: [4] {compliance-group-status} warning: current compliance statement `docsDevCmCompliance' includes deprecated group `docsDevFilterGroup' mailbody:3195: [4] {compliance-group-status} warning: current compliance statement `docsDevCmtsCompliance' includes deprecated group `docsDevNmAccessGroup' mailbody:3206: [4] {compliance-group-status} warning: current compliance statement `docsDevCmtsCompliance' includes deprecated group `docsDevNmAccessExtGroup' mailbody:3235: [4] {compliance-group-status} warning: current compliance statement `docsDevCmtsCompliance' includes deprecated group `docsDevFilterGroup' mailbody:3247: [4] {compliance-group-status} warning: current compliance statement `docsDevCmtsCompliance' includes deprecated group `docsDevCpeGroup' This doesn't look OK. I think what you wanted to say was that the old docsDevCmCompliance should be deprecated, and that there will be a docDevCmComplianceRev1 (or whatever a good name would be) that has only the "current" stuff from docsDevCmCompliance. Alternatively, you could keep the old compliance stuff as-is, and just add a docDevCmComplianceRev1. It depends on the message you want to send. I'll look at the smidiff output separately. Randy _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn
- RE: [ipcdn] idnits and smilint on Cable Device MI… Marez Kevin-MGI1375
- Re: [ipcdn] idnits and smilint on Cable Device MI… Randy Presuhn
- RE: [ipcdn] idnits and smilint on Cable Device MI… Woundy, Richard
- RE: [ipcdn] idnits and smilint on Cable Device MI… Woundy, Richard
- Re: [ipcdn] idnits and smilint on Cable Device MI… Randy Presuhn
- Re: [ipcdn] idnits and smilint on Cable Device MI… Randy Presuhn