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

Dear all,

When editing the last version, I made a few mistakes and failed
to apply three changes, that you will find listed at the end of
this message.

Since we are entering a short WG last call on this document
soon, please include three suggested changes below in your
review.

Thanks,

    Juergen


--On 20.07.2004 12:28 Uhr +0200 Juergen Quittek wrote:

> Dear all,
>
> Below please find the list of changes from version -02 to version -03.
>
> Thanks,
>
>     Juergen
 [...]
>

================================
suggested changes to version -03
================================



========================================================================
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 suggested
========================================================================


========================================================================
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 suggested
========================================================================


========================================================================
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 Secton 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 suggested
========================================================================