draft-ietf-rmonmib-hc-alarm-mib

Last Version:	draft-ietf-rmonmib-hc-alarm-mib-02.txt		Tracker Entry
Date:	29-Mar-2004
Disposition:	RFC3434 (diff)
Previous Versions:	draft-ietf-rmonmib-hc-alarm-mib-02.txt (diff)    - 07-Jan-2003
	draft-ietf-rmonmib-hc-alarm-mib-01.txt (diff)    - 19-Sep-2002
	draft-ietf-rmonmib-hc-alarm-mib-00.txt (diff)    - 18-Apr-2002

A new Request for Comments is now available in online RFC libraries.


        RFC 3434

        Title:      Remote Monitoring MIB Extensions for
                    High Capacity Alarms
        Author(s):  A. Bierman, K. McCloghrie
        Status:     Standards Track
        Date:       December 2002
        Mailbox:    [email protected], [email protected]
        Pages:      24
        Characters: 51072
        Updates/Obsoletes/See Also:   None

        I-D Tag:    draft-ietf-rmonmib-hc-alarm-mib-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3434.txt


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.

This document is a product of the Remote Network Monitoring Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [email protected]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[email protected].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.