RFC 3434 on Remote Monitoring MIB Extensions for High Capacity Alarms

rfc-editor@rfc-editor.org Tue, 24 December 2002 21:17 UTC

Message-Id: <200212242109.gBOL9oD04194@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3434 on Remote Monitoring MIB Extensions for High Capacity Alarms
Cc: rfc-editor@rfc-editor.org, rmonmib@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 24 Dec 2002 13:09:50 -0800
Sender: owner-ietf-announce@ietf.org
Precedence: bulk

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:    abierman@cisco.com, kzm@cisco.com
        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 IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc3434.txt"><ftp://ftp.isi.edu/in-notes/rfc3434.txt>

RFC 3434 on Remote Monitoring MIB Extensions for … rfc-editor