idnits 2.17.1 draft-ietf-sming-reqs-06.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3216 5 Title: SMIng Objectives 6 Author(s): C. Elliott, D. Harrington, J. Jason, 7 J. Schoenwaelder, F. Strauss, W. Weiss 8 Status: Informational 9 Date: December 2001 10 Mailbox: chelliot@cisco.com, dbh@enterasys.com, 11 jamie.jason@intel.com, schoenw@ibr.cs.tu-bs.de, 12 strauss@ibr.cs.tu-bs.de, wweiss@ellacoya.com 13 Pages: 33 14 Characters: 58551 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-ietf-sming-reqs-06.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3216.txt 21 This document describes the objectives for a new data definition 22 language, suitable for the modeling of network management constructs, 23 that can be directly mapped into SNMP and COPS-PR protocol 24 operations. 26 The purpose of this document is to serve as a set of objectives that 27 a subsequent language specification should try to address. It 28 captures the results of the working group discussions towards 29 consensus on the SMIng objectives. 31 This document is a product of the Next Generation Structure of 32 Management Information Working Group of the IETF. 34 This memo provides information for the Internet community. It does 35 not specify an Internet standard of any kind. Distribution of this 36 memo is unlimited. 38 This announcement is sent to the IETF list and the RFC-DIST list. 39 Requests to be added to or deleted from the IETF distribution list 40 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 41 added to or deleted from the RFC-DIST distribution list should 42 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 44 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 45 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 46 help: ways_to_get_rfcs. For example: 48 To: rfc-info@RFC-EDITOR.ORG 49 Subject: getting rfcs 51 help: ways_to_get_rfcs 53 Requests for special distribution should be addressed to either the 54 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 55 specifically noted otherwise on the RFC itself, all RFCs are for 56 unlimited distribution.echo 57 Submissions for Requests for Comments should be sent to 58 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 59 Authors, for further information.