RFC 2287: Definitions of System-Level Managed Objects for Applications
In plain English — editorial summary, not part of the RFC
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a basic set of managed objects for fault, configuration and performance management of applications from a systems perspective. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2287
- Published
- February 1998
- Authors
- C. Krupczak; J. Saperia
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 44
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2562Definitions of Protocol and Managed Objects for TN3270E Response Time Collection Using SMIv2 (TN3270E-RT-MIB)Current
April 1999
- RFC 2594Definitions of Managed Objects for WWW ServicesCurrent
May 1999
- RFC 2605Directory Server Monitoring MIBCurrent
June 1999
- RFC 2788Network Services Monitoring MIBCurrent
March 2000
- RFC 2789Mail Monitoring MIBCurrent
March 2000
- RFC 6065Using Authentication, Authorization, and Accounting Services to Dynamically Provision View-Based Access Control Model User-to-Group MappingsCurrent
December 2010
- RFC 2266Definitions of Managed Objects for IEEE 802.12 Repeater DevicesCurrent
January 1998
- RFC 2232Definitions of Managed Objects for DLUR using SMIv2Current
November 1997
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?