Final Requirements Process for SMIng:

["Durham, David" <david.durham@intel.com>]

Greetings smingers,

This mail is to announce that the period for specifying additional
requirements for the sming data definition language that are to be included
in the Requirements document is drawing to an end. According to the Charter,
the Requirements document is to go to last call in May 2001. Due to this,
any additional requirements must be submitted directly to the sming mailing
list NO LATER than April 15th 2001 using the form specified below to be
considered for inclusion in the Requirements document. Also by this date,
motivation needs to be supplied for the existing requirements that don't
have a clear motivation (i.e. use) or they will be removed from the
requirements document (requirements without any motivation will not be
considered). Please note: we want to see REALISTIC REQUIREMENTS that can be
supported by the SNMP and COPS-PR protocols as they exist today.

After the April 15th date, all the requirements specifying a motivation will
be integrated into a requirements list that will be available online by
April 22nd. No later than April 30th, any issue with any requirement
specified in this list must be submitted to the sming mailing list for
consideration with regards to the Requirements document. The Requirements
document authors will review the proposals submitted to the sming mailing
list and create a final requirements document to be submitted for WG last
call in May. 

Note: The Charter already assumes two key requirements which should keep the
size of the requirements list to a minimum:
1. SMIng MUST support all existing SMIv2 features except those specifically
identified as not needed. (i.e. if anyone wants remove anything that's
already in the SMI, then they must list that as a separate requirement, e.g.
Remove IMPLIED keyword).
2. SMIng MUST support all existing SPPI features except those specifically
identified as not needed. (i.e. if anyone wants remove anything from the
SPPI, then they must list that as a separate requirement).

Form for submitting additional requirements or motivating existing
requirements for sming...

Add/Update Requirement:
	Name of the Requirement (considered update if name already exists):
	Specify where requirement is from (SMI, SPPI, or NEW):
	Description of the Requirement:
	Motivation (what problem is it going to solve? what does it
simplify? is it already in the SMI/SPPI? etc.):
	Example showing a possible syntax that demonstrates the requirement:

Form for specifying problems with an existing requirement...

Problematic Requirement:
	Requirement name:
	Description of the problem with the requirement: