RFC 2819: Remote Network Monitoring Management Information Base
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 TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2819
- Published
- May 2000
- Authors
- S. Waldbusser
- Status
- INTERNET STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 98
- Also known as
- STD59
- Obsoletes:
- RFC 1757
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1271 (1991)
- RFC 1757 (1995)
- RFC 2819 (2000)
Read the full history of Remote Network Monitoring Management Information Base →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2895Remote Network Monitoring MIB Protocol Identifier ReferenceUpdated
August 2000
- RFC 3287Remote Monitoring MIB Extensions for Differentiated ServicesCurrent
July 2002
- RFC 3395Remote Network Monitoring MIB Protocol Identifier Reference ExtensionsCurrent
September 2002
- RFC 3434Remote Monitoring MIB Extensions for High Capacity AlarmsCurrent
December 2002
- RFC 2742Definitions of Managed Objects for Extensible SNMP AgentsCurrent
January 2000
- RFC 2925Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup OperationsObsoleted
September 2000
- RFC 2940Definitions of Managed Objects for Common Open Policy Service (COPS) Protocol ClientsCurrent
October 2000
- 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?