Re: WG Last call announcement on draft-ietf-sming-reqs-02.txt

[Michael Kirkham <mikek@muonics.com>]

Does the last call include the possibility for additions or just
clarifications of the existing set?  If possible I would add, for the sake
of leaving it open for discussion/consideration at some point (per some
previous notes sent to the list):

_____  Attribute Transaction Constraints #2 (Refinements)

Number: ______

Type: new/should

From: Individual

Description:  The SMI should allow specifying range and size constraints
where applicable, and in a parseable manner, based on transaction type.
This would be extend the semantics of WRITE-SYNTAX used by SMIv2's
AGENT-CAPABILITIES and MODULE-COMPLIANCE statements into any definition of
a derived type or attribute definition.

Motivation:
    * Allows code generation tools to automatically instrument rejection
      rules when generating code for those attributes or derived types.
    * Allows applications to have stronger failsafes against bumping into
      other implementations' non-conformant behavior (ie., don't send what
      you know won't be accepted by a conformant implementation and might
      do bad things to a non-conformant implementation).
    * Allows conformance and QA testing tools to further automate the
      testing process.
    * Allows further generalization of user tools for configuration.

Notes:
    * In-line with the working group charter ("syntax optimized for
      parseability, human readability, and non-redundancy")
    * Partly in-line with 4.3.26 (Attribute Transaction Constraints)
    * In line with 4.1.34 (Range and Size Constraints).
    * In line with 4.1.23 (Extended Data Types).

Here are just a few SNMP objects/derived types with peculiar semantics
about what values can be read or written.  Currently, such constraints can
be and are only represented by text within the DESCRIPTION field. The list
is not exclusive (there likely are and will be others).

    *RowStatus
        active(1) - read-write
        notInService(2) - read-write
        notReady(3) - read-write
        createAndGo(4) - write-only
        createAndWait(5) - write-only
        destroy(6) - write-only
    tcpConnState
        deleteTCB(12) - write-only
        all others    - read-only
    *KeyChange
        SIZE(0)     - read-only
        SIZE(other) - write-only


On Fri, 15 Jun 2001, Durham, David wrote:

> Greetings,
>
> 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.
>
> -Dave
>
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Thursday, June 14, 2001 4:09 AM
> Cc: sming@ops.ietf.org
> Subject: I-D ACTION:draft-ietf-sming-reqs-02.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 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 [1] and COPS-PR [9] protocol PDUs.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sming-reqs-02.txt
>
> 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
> 	"get draft-ietf-sming-reqs-02.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-sming-reqs-02.txt".
>
> 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
> Internet-Draft.
>
>
>