RFC 3179 on SMX Protocol 1.1
RFC Editor <rfc-ed@ISI.EDU> Sat, 20 October 2001 05:28 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23710; Sat, 20 Oct 2001 01:28:16 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id BAA13261 for ietf-123-outbound.10@ietf.org; Sat, 20 Oct 2001 01:15:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA07915 for <all-ietf@loki.ietf.org>; Fri, 19 Oct 2001 18:58:59 -0400 (EDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04363 for <all-ietf@ietf.org>; Fri, 19 Oct 2001 18:58:56 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id f9JMwvH07701; Fri, 19 Oct 2001 15:58:58 -0700 (PDT)
Message-Id: <200110192258.f9JMwvH07701@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3179 on SMX Protocol 1.1
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 19 Oct 2001 15:58:57 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
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: schoenw@ibr.cs.tu-bs.de, quittek@ccrle.nec.de
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.
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.
- RFC 3179 on SMX Protocol 1.1 RFC Editor