RFC 3231 on Schedule MIB

RFC Editor <rfc-ed@ISI.EDU> Fri, 11 January 2002 23:51 UTC

Message-Id: <200201112339.g0BNd1H24099@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3231 on Schedule MIB
Cc: rfc-ed@ISI.EDU, disman@dorothy.bmc.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 11 Jan 2002 15:39:01 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 3231

        Title:	    Definitions of Managed Objects for Scheduling
                    Management Operations
        Author(s):  D. Levi, J. Schoenwaelder
        Status:     Standards Track
	Date:       January 2002
        Mailbox:    dlevi@nortelnetworks.com, schoenw@ibr.cs.tu-bs.de 
        Pages:      29
        Characters: 61308
        Obsoletes:  2591

        I-D Tag:    draft-ietf-disman-schedule-mib-v2-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3231.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 a set of managed objects that are used to
schedule management operations periodically or at specified dates and
times.

This document obsoletes RFC 2591.

This document is a product of the Distrubuted 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 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/rfc3231.txt"><ftp://ftp.isi.edu/in-notes/rfc3231.txt>

RFC 3231 on Schedule MIB RFC Editor