RFC 2593 on SMX Protocol 1.0

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

Received: by ietf.org (8.9.1a/8.9.1a) id NAA11829 for ietf-123-outbound.10@ietf.org; Mon, 24 May 1999 13:45: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 NAA11124 for <all-ietf@ietf.org>; Mon, 24 May 1999 13:28:08 -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 KAA12845; Mon, 24 May 1999 10:28:10 -0700 (PDT)
Message-Id: <199905241728.KAA12845@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC 2593 on SMX Protocol 1.0
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 24 May 1999 10:31:09 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


	RFC 2593: 

        Title: 	    Script MIB Extensibility Protocol Version 1.0
   	Author(s):  J. Schoenwaelder, J. Quittek
        Status:     Experimental
	Date:       May 1999
        Mailbox:    schoenw@ibr.cs.tu-bs.de, quittek@ccrle.nec.de
        Pages:      22
        Characters: 49663
        Updates/Obsoletes/See Also: None 
        I-D Tag:    draft-schoenw-smx-00.txt

	pathname on ftp.isi.edu: in-notes/rfc2593.txt


The IETF Script MIB defines an interface for the delegation of
management functions based on the Internet management framework. A
management script is a set of instructions that are executed by a
language specific runtime system.  The Script MIB extensibility
protocol (SMX) defined in this memo separates language specific
runtime systems from language independent Script MIB implementations.

This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.  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/rfc2593.txt"><ftp://ftp.isi.edu/in-notes/rfc2593.txt>