Re: [ipcdn] idnits and smilint on Cable Device MIB Draft 09

"Randy Presuhn" <randy_presuhn@mindspring.com> Mon, 27 June 2005 21:03 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dn0lD-0001BM-1D; Mon, 27 Jun 2005 17:03:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dn0lA-0001BF-Im for ipcdn@megatron.ietf.org; Mon, 27 Jun 2005 17:03:16 -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 RAA19000 for <ipcdn@ietf.org>; Mon, 27 Jun 2005 17:03:13 -0400 (EDT)
Received: from pop-scotia.atl.sa.earthlink.net ([207.69.195.65]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dn1AM-00045X-Lw for ipcdn@ietf.org; Mon, 27 Jun 2005 17:29:19 -0400
Received: from h-64-105-137-71.snvacaid.dynamic.covad.net ([64.105.137.71] helo=oemcomputer) by pop-scotia.atl.sa.earthlink.net with smtp (Exim 3.36 #10) id 1Dn0l7-0001Mm-00 for ipcdn@ietf.org; Mon, 27 Jun 2005 17:03:13 -0400
Message-ID: <007601c57b5c$2a5a5d20$7f1afea9@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: "Ipcdn (E-mail)" <ipcdn@ietf.org>
References: <D5A7E45D575DD61180130002A5DB377C12F98F3D@ca25exm01>
Subject: Re: [ipcdn] idnits and smilint on Cable Device MIB Draft 09
Date: Mon, 27 Jun 2005 14:07:01 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
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

Hi -

> From: "Marez Kevin-MGI1375" <Kevin.Marez@motorola.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>; "Ipcdn \(E-mail\)" <ipcdn@ietf.org>
> Sent: Monday, June 27, 2005 12:26 PM
> Subject: RE: [ipcdn] idnits and smilint on Cable Device MIB Draft 09
...
> 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,
...

It's ok with me if it's really the case that the WG wants to "encourage
continued implementation of the deprecated groups".  When I look at what
has actaully been deprecated, it's seems to me that that is not the intent.

Randy




_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn