Re: MIB Doctor review: publish draft-ietf-disman-remops-mib-v2-0 6.txt

Juergen Quittek <[email protected]> Mon, 20 Feb 2006 01:59:23 +0100
Newsgroups gmane.ietf.disman
Message-ID <CF33A0568F296127BCC81579@[192.168.1.128]>
Hi Juergen,

Thanks for the review.
I posted a new version incorporating the changes described inline below.

--On 2/17/06 9:09 AM +0100 Juergen Schoenwaelder wrote:

> On Fri, Feb 10, 2006 at 12:28:11AM +0100, Wijnen, Bert (Bert) wrote:
>
>> So did you check rev 7 to make sure you are happy.
>> I am assuming so, but would appreciate an ack.
>>
>> In your MIB doctor review, did you also do a smidiff
>> with the RFC versions, and are we OK on those?
>
> Bert,
>
> I did an smidiff and I actually wrote a compliance statement output
> driver for smidump to be able to check the differences between
> compliance statements.
>
> I just took a quick look at the latest version (which is -08 I think)
> and I found a few more nits that you might want to get fixed if still
> possible and JQ can turn things around things quickly:
>
> 1) In the pingMIB MODULE-IDENTITY, it says twice:
>
>                 - changed DEFVAL of object pingCtlDescr from
>                   DEFVAL { '00'H } to DEFVAL { ''H }
>
>    I think saying this once should be good enough.

Agreed and fixed.

> 2) pingCompliancy -> pingCompliance

Fixed.

> 3) pingFullCompliancy -> pingFullCompliance

Fixed.

> 4) traceRoutecompliancy -> traceRouteCompliance

Fixed.

> 5) traceRouteFullCompliancy -> traceRouteFullCompliance

Fixed.

> 6) I would have liked to see text in the deprecated compliance that
>    says why these were deprecated and what implementors should do
>    about it (since comparing compliance statements is really a tedious
>    task). I know this is mentioned in section 3.4 but you know that
>    extracted MIB modules often have a life of their own.
>
>     pingCompliance MODULE-COMPLIANCE
>        STATUS  deprecated
>        DESCRIPTION
>                "The compliance statement for the DISMAN-PING-MIB. This
> 		compliance statement has been deprecated because the
> 		group pingGroup and the pingTimeStampGroup have been
> 		split and deprecated. The pingFullCompliance statement
> 		is semantically identical to the deprecated pingCompliance
> 		statement".

Done.

>     traceRouteCompliance MODULE-COMPLIANCE
>        STATUS  deprecated
>        DESCRIPTION
>                "The compliance statement for the DISMAN-TRACEROUTE-MIB.
> 		This compliance statement has been deprecated because
> 		the traceRouteGroup and the traceRouteTimeStampGroup
> 		have been split and deprecated. The traceRouteFullCompliance
> 		is semantically identical to the deprecated
> 		traceRouteCompliance statement."

Done.

Thank you for the constructive comments.

    Juergen Q.
-- 
Juergen Quittek        [email protected]       Tel: +49 6221 90511-15
NEC Europe Ltd.,       Network Laboratories        Fax: +49 6221 90511-55
Kurfuersten-Anlage 36, 69115 Heidelberg, Germany   http://www.netlab.nec.de