CurrentPROPOSED STANDARDIETF stream

RFC 4560: Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC4560
Published
June 2006
Authors
J. Quittek; K. White
Status
PROPOSED STANDARD
Stream
IETF
Area
ops
Pages
100
Also known as
Obsoletes:
RFC 2925

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/4560-definitions-of-managed-objects-for-remote-ping-traceroute-and-lookup-operations