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

Dear all,

Please find the list of changes between version -03 and version -04
listed at the end of this message.  We already discussed the changes
on this list and - so far - there are no further open issues left.

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 09.08.2004 15:25 h -0400 [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-04.txt
> 	Pages		: 89
> 	Date		: 2004-8-9


	
=======================================
changes from version -03 to version -04
=======================================



========================================================================
29. Bad numbering of objects in DISMAN-TRACEROUTE-MIB
========================================================================
Problem Description:
------------------------------------------------------------------------
OID { traceRouteGroups 6 } is assigned twice,
to traceRouteCtlRowStatusGroup and to traceRouteHistoryGroup
========================================================================
Suggested solution:
------------------------------------------------------------------------
replcace for traceRouteHistoryGroup OLD
   ::= { traceRouteGroups 6 }
with NEW
   ::= { traceRouteGroups 7 }
========================================================================
Status: solution committed
========================================================================


========================================================================
30. traceRouteMinimumCompliancy does not cover
    traceRouteCtlRowStatusGroup
========================================================================
Problem Description:
------------------------------------------------------------------------
The traceRouteMinimumCompliancy statement does not cover the new
traceRouteCtlRowStatusGroup.
========================================================================
Suggested solution:
------------------------------------------------------------------------
add to traceRouteMinimumCompliancy:
            GROUP traceRouteCtlRowStatusGroup
            DESCRIPTION
                "A compliant implementation does not have to implement
                the traceRouteCtlRowStatusGroup."
========================================================================
Status: solution committed
========================================================================


========================================================================
31. Coverage of excessive lookup in security considerations
========================================================================
Problem Description:
------------------------------------------------------------------------
The Security considerations do not describe the threat of excessively
using the lookup service.

raised by Dan Romascanu
========================================================================
Suggested solution:
------------------------------------------------------------------------
In Section 5. Security Considerations replace OLD
   In general, both the ping and traceroute functions when used
   excessively are considered a form of system attack.  In the case of
   ping sending a system requests too often can negatively effect its
   performance or attempting to connect to what is supposed to be an
   unused port can be very unpredictable.  Excessive use of the
   traceroute capability can like ping negatively affect system
   performance.  In insecure environments it is RECOMMENDED that the
   MIBs defined within this memo not be supported.
with NEW
   In general, all three, the ping, traceroute and lookup functions,
   when used excessively are considered a form of system attack.  In the
   case of ping sending a system requests too often can negatively
   effect its performance or attempting to connect to what is supposed
   to be an unused port can be very unpredictable.  Excessive use of the
   traceroute capability can like ping negatively affect system
   performance.  The same applies to excessive use of the lookup
   service, particularly, if the lookup cannot be resolved locally.  In
   insecure environments it is RECOMMENDED that the MIBs defined within
   this memo not be supported.
========================================================================
Status: solution committed
========================================================================