[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
WG Last call announcement on draft-ietf-sming-reqs-02.txt
This mail is to announce Working Group last call for the SMIng Requirements
ID. This ID reflects the culmination of input from the last IETF meeting,
the SMIng requirements finalization process executed in April, and the SMIng
interim meeting in May. WG last call is the WG's opportunity to point out
any remaining issues with the ID before the document is sent to the IESG.
WG last call for this document will last two weeks, starting today (June
15th) and ending EOD June 29th.
I would like to thank the WG and the authors for all their contributions &
hard work to date.
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Thursday, June 14, 2001 4:09 AM
Subject: I-D ACTION:draft-ietf-sming-reqs-02.txt
A New Internet-Draft is available from the on-line Internet-Drafts
This draft is a work item of the Next Generation Structure of Management
Information Working Group of the IETF.
Title : SMIng Requirements
Author(s) : C. Elliott, D. Harrington, J. Jason,
J. Schoenwaelder, F. Strauss, W. Weiss
Filename : draft-ietf-sming-reqs-02.txt
Pages : 42
Date : 13-Jun-01
This document describes the requirements of a data modeling language,
suitable for the modeling of network management constructs, that can
be directly mapped into SNMP  and COPS-PR  protocol PDUs.
A URL for this Internet-Draft is:
Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
A list of Internet-Drafts directories can be found in
Internet-Drafts can also be obtained by e-mail.
Send a message to:
In the body type:
NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the