Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 100
- 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]
- Publication Date
- 2006-06-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC4560- Link
- https://doi.org/10.17487/RFC4560
- Author(s)
- Juergen QuittekKenneth D. White
- Keyword(s)
- MIB, DISMAN-PING-MIB, DISMAN-TRACEROUTE-MIB, DISMAN-NSLOOKUP-MIB
Latest version of IETF RFC 4560
Document Versions — IETF RFC 4560
-
▶ IETF RFC 4560 (2006-06-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 2578 [Active*]
- IETF RFC 2579 [Active*]
- IETF RFC 2580 [Active*]
- IETF RFC 2863 [Active*]
- IETF RFC 3411 [Active*]
- IETF RFC 4001 [Active*]
Bibliographic Reference(s)
- IETF RFC 792 [Active*]
- IETF RFC 862 [Active*]
- IETF RFC 1812 [Active*]
- IETF RFC 2474 [Active*]
- IETF RFC 3260 [Active*]
- IETF RFC 3410 [Active*]
- IETF RFC 3415 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4560.json
Supersedes:
IETF RFC 2925 [Superseded*]
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4560, Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations. Available at https://doi.org/10.17487/RFC4560
Snippet:
IETF RFC 4560, Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations. Available at https://doi.org/10.17487/RFC4560
HTML (ISO 690 compliant)
Preview:
IETF RFC 4560, Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations. Available at https://doi.org/10.17487/RFC4560
Snippet:
<span class="citation"><cite>IETF RFC 4560</cite>, Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations. Available at <a href="https://doi.org/10.17487/RFC4560" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4560</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4560, Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
doi: 10.17487/RFC4560
url: https://doi.org/10.17487/RFC4560
doi: 10.17487/RFC4560
url: https://doi.org/10.17487/RFC4560
Snippet:
<li> <cite id="bib-rfc4560">IETF RFC 4560</cite>, Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations <span class="doi">10.17487/RFC4560</span> </li>
Referenced By
- IETF RFC 5388 [Active*]