Re: RE: [Disman] Disman WG last callondraft-ietf-disman-remops-mib-v2-02.txt

Hi -

> From: "Romascanu, Dan (Dan)" <[email protected]>
> To: "Randy Presuhn" <[email protected]>; <[email protected]>
> Cc: <[email protected]>
> Sent: Thursday, June 17, 2004 12:41 PM
> Subject: [ipcdn] RE: [Disman] Disman WG last callondraft-ietf-disman-remops-mib-v2-02.txt
>

> Randy,
>
> Would it be possible for the authors to provide a log of changes relative to RFC 2925?
...

Juergen Quittek's summary of June 16 appears below.
Do you need more detail?  Please send any followup
discussion to the disman WG mailing list.

Randy
---------------------------------------------------
Dear all,

I just posted a new version of the remote operation MIB modules.
Following Eduardo's suggestion I added Minimum Compliancy statements
in addition to the existing full compliancy statements to each of the
three MIB modules.

I also had to (syntactically) modify the existing compliancy
statements.  Please have a close look at all six MODULE-COMPLIANCE
macros.  Until the document becomes available at the I-D repository,
you can preview it at
ftp://ftp.ccrle.nec.de/pub/internet-drafts/draft-ietf-disman-remops-mib-v2-02.txt

There was not much response on my questions on how to define the
minimum compliance statements.  I preferred leaving read-only
objects in place to creating non-consecutive numbering of objects
in table entries.  I am not dogmatic about this and suggestions
for changes are very welcome.

For simplifying the review here is a list of objects and groups
for which the full and minimum compliance statements differ:

pingHistoryGroup,
pingNotificationsGroup
pingCtlDataFill
pingCtlFrequency
pingCtlMaxRows
pingCtlTrapGeneration
pingCtlProbeFailureFilter
pingCtlTestFailureFilter
pingCtlDescr
pingCtlByPassRouteTable
pingProbeHistoryTime

traceRouteHistoryGroup
traceRouteCtlByPassRouteTable
traceRouteCtlDontFragment
traceRouteCtlInitialTtl
traceRouteCtlFrequency
traceRouteCtlDescr
traceRouteCtlMaxRows
traceRouteCtlTrapGeneration
traceRouteCtlCreateHopsEntries
traceRouteCtlRowStatus
traceRouteHopsLastGoodProbe

lookupCtlRowStatus

Beyond the compliance statement I just made two changes to the document:

1. Added new section 3.4 introducing the compliance statement

2. Extended DESCRIPTION clause of object lookupPurgeTime by one sentence:

         "A value of 0 indicates that automatic deletion
          of entries is disabled."