Script MIB Extensibility Protocol Version 1.1
The information below is for an old version of the document that is already published as an RFC.
This is an older version of an Internet-Draft that was ultimately published as RFC 3179.
|Authors||Juergen Quittek , Jürgen Schönwälder|
|Last updated||2013-03-02 (Latest revision 2001-06-29)|
|RFC stream||Legacy stream|
|RFC Editor Note||(None)|
|IESG||IESG state||RFC 3179 (Experimental)|
|Send notices to||(None)|
A new Request for Comments is now available in online RFC libraries. RFC 3179 Title: Script MIB Extensibility Protocol Version 1.1 Author(s): J. Schoenwaelder, J. Quittek Status: Experimental Date: October 2001 Mailbox: email@example.com, firstname.lastname@example.org Pages: 25 Characters: 56311 Obsoletes: 2593 I-D Tag: draft-schoenw-rfc-2593-update-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3179.txt The Script MIB extensibility protocol (SMX) defined in this memo separates language specific runtime systems from language independent Script MIB implementations. 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. 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.