Subject: ForCES Requirements Last Call issue resolution

From: "Putzolu, David" <[email-masked]>
Date: Wed, 29 May 2002 16:16:58 -0700

All,

Based on the list feedback and the responses of the
design team please find below the proposed issue
resolution for the ForCES Requirements last call
that just completed.

The design team has been asked to issue a new rev of
the requirements that incorporates the changes
proposed below.  Once that is available, a short
(1 week) last call will be held to review the changes
before this document is forwarded to the ADs.

If any issues were missed or the resolutions are not
properly documented please post a note to the list
ASAP.

Thanks,
David

--- cut here ---

Issue: Need for both a capabilities model and a state model
Resolution: Include in new rev of requirements. Lily Yang
has proposed some text that may be useful.

Issue: All failure notifications should be supported not
just "increase/decrease in available resources."
Resolution: Include in new rev. of requirements.

Issue: Should the requirements specify a minimal set of
functions?
Resolution: New rev. will include forwarding function
as the minimum.

Issue: Are there CE model requirements that need to be
included?
Resolution: Each requirement on the FE probably has a
corresponding control function on the CE - issue addressed.

Issue: FE should also be required to support error reporting
and monitoring.
Resolution: Include in new rev of requirements.