Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
RFC 4560
Revision differences
Document history
Date | By | Action |
---|---|---|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This memo defines Management Information Bases (MIBs) for performing ping, traceroute, and lookup operations at a … Received changes through RFC Editor sync (changed abstract to '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]') |
2017-05-16
|
(System) | Changed document authors from "Juergen Quittek" to "Juergen Quittek, Kenneth White" |
2015-10-14
|
(System) | Notify list changed from randy_presuhn@mindspring.com, quittek@netlab.nec.de, Juergen Schoenwaelder to (None) |
2006-07-13
|
Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
2006-07-13
|
Amy Vezza | [Note]: 'RFC 4560' added by Amy Vezza |
2006-06-30
|
(System) | RFC published |