A new Request for Comments is now available in online RFC libraries.
RFC 2981
Title: Event MIB
Author(s): R. Kavasseri (Editor of this version)
B. Stewart (Author of previous version)
Status: Standards Track
Date: October 2000
Mailbox: [EMAIL PROTECTED]
Pages: 50
Characters: 98248
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-disman-event-mib-10.txt
URL: ftp://ftp.isi.edu/in-notes/rfc2981.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 that can be
used to manage and monitor MIB objects and take action through
events.
The Event MIB provides the ability to monitor MIB objects on the local
system or on a remote system and take simple action when a trigger
condition is met.
This document is a product of the Distributed Management 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.
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.
rfc2981.txt
