Re: I-D ACTION:draft-ietf-disman-remops-mib-v2-06.txt

Dear all,

This version contains just a few minor fixes based on comments from Randy.

There is only one modification that I would like to mention explicitly.
Please find it described at the end of this message.

Thanks,

    Juergen
-- 
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


--On 14.12.2004 15:56 h -0500 [email protected] wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Distributed Management Working Group of the IETF.
>
> 	Title		: Definitions of Managed Objects for Remote Ping, Traceroute,
> 			  and Lookup Operations
> 	Author(s)	: J. Quittek, K. White
> 	Filename	: draft-ietf-disman-remops-mib-v2-06.txt
> 	Pages		: 97
> 	Date		: 2004-12-14
> 	
> This memo defines Management Information Bases (MIBs) for performing
> remote ping, traceroute and lookup operations at a remote host.  When
> managing a network it is useful to be able to initiate and retrieve
> the results of ping or traceroute operations when performed at a
> remote host.  A Lookup capability is defined in order to enable
> resolving of either an IP address to an DNS name or an DNS name to an
> IP address at a remote host.
> Currently, there are several enterprise-specific MIBs for performing
> remote ping or traceroute operations.  The purpose of this memo is to
> define a standards-based solution to enable interoperability.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-06.txt



=======================================
changes from version -05 to version -06
=======================================


========================================================================
33. Slighly ambiguous description of pingCtlMaxRows, traceRouteCtlMaxRows
========================================================================
Problem Description:
------------------------------------------------------------------------
The description of the semantics of objects pingCtlMaxRows and
traceRouteCtlMaxRows is slightly ambiguous.  The respective semantics
are described in Sections 3.1.4 and 3.2.4, in the DESCRIPTION clauses
of the objects and in the DESCRIPTION classes of the respective
history tables.
Some phrases are not clear about whether the MaxRows value applies
to all rows in the respective table or only to the number of rows
corresponding to the entry containing the MaxRows value.
========================================================================
Suggested solution:
------------------------------------------------------------------------
Clarify the descriptions.
========================================================================
Status: solution committed
========================================================================