RFC 2788: Network Services Monitoring MIB
In plain English — editorial summary, not part of the RFC
This document defines a MIB which contains the elements common to the monitoring of any network service application. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2788
- Published
- March 2000
- Authors
- N. Freed; S. Kille
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 22
- Also known as
- —
- Obsoletes:
- RFC 2248
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1565 (1994)
- RFC 2248 (1998)
- RFC 2788 (2000)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2789Mail Monitoring MIBCurrent
March 2000
- RFC 2605Directory Server Monitoring MIBCurrent
June 1999
- RFC 2594Definitions of Managed Objects for WWW ServicesCurrent
May 1999
- RFC 2562Definitions of Protocol and Managed Objects for TN3270E Response Time Collection Using SMIv2 (TN3270E-RT-MIB)Current
April 1999
- RFC 2287Definitions of System-Level Managed Objects for ApplicationsCurrent
February 1998
- RFC 6065Using Authentication, Authorization, and Accounting Services to Dynamically Provision View-Based Access Control Model User-to-Group MappingsCurrent
December 2010
- RFC 2787Definitions of Managed Objects for the Virtual Router Redundancy ProtocolObsoleted
March 2000
- RFC 2742Definitions of Managed Objects for Extensible SNMP AgentsCurrent
January 2000
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?