<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-disman-remops-mib-v2" target="https://datatracker.ietf.org/doc/html/draft-ietf-disman-remops-mib-v2-09">
   <front>
      <title>Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations</title>
      <author initials="K. D." surname="White" fullname="Kenneth D. White">
         <organization>IBM Corp.</organization>
      </author>
      <author initials="J." surname="Quittek" fullname="Juergen Quittek">
         <organization>NEC</organization>
      </author>
      <date month="February" day="22" year="2006" />
      <abstract>
	 <t>This memo defines Management Information Bases (MIBs) for performing ping, traceroute, and lookup operations at a host. When managing a network, it is useful to be able to initiate and retrieve the results of ping or traceroute operations when they are performed at a remote host. A lookup capability is defined in order to enable resolution of either an IP address to an DNS name or a 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. [STANDARDS-TRACK]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-disman-remops-mib-v2-09" />
   
</reference>
