Re: LC Review: draft-ietf-disman-remops-mib-v2-09.txt

That's a good enough reason to keep it.
I think that all the functionality is provided by the ping portion, 
but a little duplication to avoid an incompatibility mess is fine.

Yours,
Joel

At 06:44 PM 3/15/2006, Juergen Quittek wrote:
>Joel,
>
>So far, I did not answer the last question of your initial email.
>Please find an answer inline.
>
>--On 3/6/06 6:10 PM -0500 Joel M. Halpern wrote:
>
>>I was selected as General Area Review Team reviewer for this specification
>>(for background on Gen-ART, please see
>>http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>
>[...]
>
>>Minor: What is the purpose of traceRouteCtlByPassRouteTable?
>>I can understand with ping needing to be able to say "ping this
>>neighbor, even if routing is confused.  However, why is there a
>>similar entry in the traceroute control table?  Given that the
>>restriction is that one is talking to a neighbor, what is the
>>point of sending a traceroute?
>
>It is a common option of existing traceroute implementations.
>For the BSD traceroute it reflects the -r option:
>
>     -r      Bypass the normal routing tables and send directly to a host on
>             an attached network.  If the host is not on a directly-attached
>             network, an error is returned.  This option can be used to ping a
>             local host through an interface that has no route through it
>             (e.g., after the interface was dropped by routed(8)).
>
>Object traceRouteCtlByPassRouteTable gives access to this option.
>I agree that it is not really needed if also the PING MIB is available.
>It might be useful, however, if not.  Anyway, it is contained in the first
>version of the TRACEROUTE MIB in RFC 2925 and it would create an unnecessary
>incompatibility if we removed it.
>
>Thanks,
>
>    Juergen
>
>>
>>
>>At 04:50 PM 3/1/2006, Mary Barnes wrote:
>>>---------------------------
>>>Reviewer: Joel Halpern
>>>
>>>- 'Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup
>>>    Operations '
>>>    <draft-ietf-disman-remops-mib-v2-09.txt> as a Proposed Standard
>>>
>>>IETF LC ends on 2006-03-09.
>>>
>>>The file can be obtained via
>>><http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-09.txt>http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-09.txt
>