Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
RFC 4560, “Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations”, is a Proposed Standard document published in June 2006 by J. Quittek, K. White. It obsoletes RFC 2925. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 4560 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4559 SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows
- RFC 4561 Definition of a Record Route Object Node-Id Sub-Object
- RFC 4558 Node-ID Based Resource Reservation Protocol Hello: A Clarification Statement
- RFC 4562 MAC-Forced Forwarding: A Method for Subscriber Separation on an Ethernet Access Network
- RFC 4557 Online Certificate Status Protocol Support for Public Key Cryptography for Initial Authentication in Kerberos
- RFC 4563 The Key ID Information Type for the General Extension Payload in Multimedia Internet KEYing
- RFC 4556 Public Key Cryptography for Initial Authentication in Kerberos
- RFC 4564 Objectives for Control and Provisioning of Wireless Access Points