RE: Final Requirements Process for SMIng: - #44 Attribute Constraints

["Andrea Westerinen" <andreaw@cisco.com>]

Also for #44 (attribute value constraints), the current Requirements draft
says ...

"Constraints on attribute values [occur] where one or more attributes may
affect the value or range of values for another attribute. One such
relationship exists in IPSEC, where the type of security algorithm
determines the range of possible values for other attributes such as the
corresponding key size."

This should be listed as the Motivation.

Andrea

-----Original Message-----
From: owner-sming@ops.ietf.org [mailto:owner-sming@ops.ietf.org]On
Behalf Of Durham, David
Sent: Wednesday, April 18, 2001 7:44 AM
To: 'sming@ops.ietf.org'
Subject: RE: Final Requirements Process for SMIng:


This message is to announce that we are now in the second phase of the SMIng
requirements finalization process. Please review the original message below.
The WG now will focus on identifying problematic requirements, and
specifying the reasons why a particular requirement may be problematic.
Don't be bashful... If you have any issue with any proposed requirement, you
have until April 30th to voice your concerns before the requirements
document goes to last call.

The current proposed requirements list can be found at:
http://www.ibr.cs.tu-bs.de/projects/sming/issues.html
http://www.ibr.cs.tu-bs.de/projects/sming/issues.txt
And the SMIng requirements document in which they were originally defined
can be found at:
http://www.ietf.org/internet-drafts/draft-ietf-sming-reqs-00.txt

Note that unmotivated new requirements (new = not already in SMI/SPPI) will
now be removed from the requirements list.

Thanks,
-Dave

> -----Original Message-----
> From: Durham, David [mailto:david.durham@intel.com]
> Sent: Friday, March 30, 2001 10:05 AM
> To: 'sming@ops.ietf.org'
> Subject: Final Requirements Process for SMIng:
>
>
> 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:
>
>
>