RFC 3780 on SMIng - Next Generation Structure of Management Information

rfc-editor@rfc-editor.org Sat, 15 May 2004 14:44 UTC

Message-Id: <200405142345.i4ENjNJ11254@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3780 on SMIng - Next Generation Structure of Management Information
Cc: rfc-editor@rfc-editor.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 14 May 2004 16:45:23 -0700
Sender: ietf-announce-admin@ietf.org
Errors-To: ietf-announce-admin@ietf.org
Precedence: bulk

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


        RFC 3780

        Title:      SMIng - Next Generation Structure of Management
                    Information
        Author(s):  F. Strauss, J. Schoenwaelder
        Status:     Experimental
        Date:       May 2004
        Mailbox:    strauss@ibr.cs.tu-bs.de,
                    j.schoenwaelder@iu-bremen.de
        Pages:      64
        Characters: 141049
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-irtf-nmrg-sming-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3780.txt


This memo defines the base SMIng (Structure of Management
Information, Next Generation) language.  SMIng is a data definition
language that provides a protocol-independent representation for
management information.  Separate RFCs define mappings of SMIng to
specific management protocols, including SNMP.

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.

ftp://ftp.isi.edu/in-notes/rfc3780.txt"><ftp://ftp.isi.edu/in-notes/rfc3780.txt>

RFC 3780 on SMIng - Next Generation Structure of … rfc-editor