RFC 2591 on Scheduling MIB

RFC Editor <rfc-ed@ISI.EDU> Mon, 24 May 1999 17:25 UTC

Received: by ietf.org (8.9.1a/8.9.1a) id NAA11029 for ietf-123-outbound.10@ietf.org; Mon, 24 May 1999 13:25:02 -0400 (EDT)
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10903 for <all-ietf@ietf.org>; Mon, 24 May 1999 13:19:17 -0400 (EDT)
Received: from akamai.isi.edu (akamai.isi.edu [128.9.160.24]) by zephyr.isi.edu (8.8.7/8.8.6) with SMTP id KAA12192; Mon, 24 May 1999 10:19:17 -0700 (PDT)
Message-Id: <199905241719.KAA12192@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC 2591 on Scheduling MIB
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 24 May 1999 10:22:17 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


	RFC 2591: 

        Title: 	    Definitions of Managed Objects for
                    Scheduling Management Operations
   	Author(s):  D. Levi, J. Schoenwaelder
        Status:     Proposed Standard
	Date:       May 1999
        Mailbox:    dlevi@nortelnetworks.com, schoenw@ibr.cs.tu-bs.de
        Pages:      25
        Characters: 53146
        Updates/Obsoletes/See Also: None 
        I-D Tag:    draft-ietf-disman-schedule-mib-06.txt

	pathname on ftp.isi.edu: in-notes/rfc2591.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 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 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 Alegre Ramos
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/rfc2591.txt"><ftp://ftp.isi.edu/in-notes/rfc2591.txt>