RFC 2925: Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4560.
Current version: 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 remote ping, traceroute and lookup operations at a remote host. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2925
- Published
- September 2000
- Authors
- K. White
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 77
- Also known as
- —
- Obsoleted by:
- RFC 4560
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2940Definitions of Managed Objects for Common Open Policy Service (COPS) Protocol ClientsCurrent
October 2000
- RFC 2981Event MIBCurrent
October 2000
- RFC 2982Distributed Management Expression MIBCurrent
October 2000
- RFC 3014Notification Log MIBCurrent
November 2000
- RFC 2742Definitions of Managed Objects for Extensible SNMP AgentsCurrent
January 2000
- RFC 3144Remote Monitoring MIB Extensions for Interface Parameters MonitoringCurrent
August 2001
- RFC 3165Definitions of Managed Objects for the Delegation of Management ScriptsCurrent
August 2001
- RFC 2669DOCSIS Cable Device MIB Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination SystemsObsoleted
August 1999
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?