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

        RFC 3216

        Title:      SMIng Objectives
        Author(s):  C. Elliott, D. Harrington, J. Jason,
                    J. Schoenwaelder, F. Strauss, W. Weiss
        Status:     Informational
        Date:       December 2001
        Mailbox:    chelliot@cisco.com, dbh@enterasys.com,
                    jamie.jason@intel.com, schoenw@ibr.cs.tu-bs.de,
                    strauss@ibr.cs.tu-bs.de, wweiss@ellacoya.com
        Pages:      33
        Characters: 58551
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-sming-reqs-06.txt

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

This document describes the objectives for a new data definition
language, suitable for the modeling of network management constructs,
that can be directly mapped into SNMP and COPS-PR protocol

The purpose of this document is to serve as a set of objectives that
a subsequent language specification should try to address.  It
captures the results of the working group discussions towards
consensus on the SMIng objectives.

This document is a product of the Next Generation Structure of
Management Information Working Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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

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.