RFC 3434: Remote Monitoring MIB Extensions for High Capacity Alarms
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 managed objects for extending the alarm thresholding capabilities found in the Remote Monitoring (RMON) MIB (RFC 2819), to provide similar threshold monitoring of objects based on the Counter64 data type. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3434
- Published
- December 2002
- Authors
- A. Bierman; K. McCloghrie
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3433Entity Sensor Management Information BaseCurrent
December 2002
- RFC 3440Definitions of Extension Managed Objects for Asymmetric Digital Subscriber LinesCurrent
January 2003
- RFC 3287Remote Monitoring MIB Extensions for Differentiated ServicesCurrent
July 2002
- RFC 3591Definitions of Managed Objects for the Optical Interface TypeCurrent
September 2003
- RFC 3592Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface TypeCurrent
September 2003
- RFC 2742Definitions of Managed Objects for Extensible SNMP AgentsCurrent
January 2000
- RFC 4547Event Notification Management Information Base for Data over Cable Service Interface Specifications (DOCSIS)-Compliant Cable Modems and Cable Modem Termination SystemsUpdated
June 2006
- RFC 4712Transport Mappings for Real-time Application Quality-of-Service Monitoring (RAQMON) Protocol Data Unit (PDU)Updated
October 2006
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?