Title: CM - Incomplete requirement PDR Reference: 98050002 Originator Reference: ATNSI_CM01 SARPs Document Reference: CM SARPs, Section 2.1.5.4.5.2 Status: RESOLVED Impact : C (Clarification) PDR Revision Date: 17/08/98 (FORWARDED -> RESOLVED) 25/06/98 (PROPOSED -> FORWARDED) 20/05/98 (SUBMITTED -> ACCEPTED -> PROPOSED) PDR Submission Date: 12/05/98 Submitting State/Organization: AIRSYS ATM (ACI/ATNSI) Submitting Author Name: Ilkiewicz, M / Stokes, S. Submitting Author E-mail Address: michel.ilkiewicz@cdv.vly.sextant.thomson.fr Shawn.Stokes@ATNSI.COM Submitting Author Supplemental Contact Information: SARPs Date: IV2.2 SARPs Language: English Summary of Defect: If the CM-ASE receives a D-START confirmation with the D-START Result parameter having the abstract value of "rejected (transient)" or if the D-START Reject Source parameter has the abstract value of "DS Provider" and if the CM-user is not an active user, the SARPs do not specify what to do. As a consequence, in such a situation, the exception handling procedure applies. This is erroneous, because in such a situation the CM-ASE should simply do nothing. Assigned SME: Sub-Volume II SME Proposed SARPs amendment: The requirement should be changed to: If the CM-ASE receives a D-START confirmation with the D-START Result parameter having the abstract value of "rejected (transient)" or if the D-START Reject Source parameter has the abstract value of "DS Provider", the CM-ASE shall: a) if the CM-user is an active user, invoke CM-provider-abort service indication with the abstract value "communication-service-error" APDU as the CM-provider-abort Reason parameter value. SME Recommendation to CCB: The concept of an active user was introduced in order to clarify when responses should or should not be sent. By definition, an inactive user does not have the capability to perform functions. Therefore, it is assumed that if a user is not active, no actions will be taken; exception handling will not apply since it does not apply for inactive users. Since the protocol will still function properly and there are no interoperability issues, this issue is rejected. Actually, the way the requirement is currently specified may be confusing. The proposed wording removes the ambiguity. For clarification in the next version of the SARPs, this PDR is FORWARDED as an editorial PDR. CCB Decision: atnp_ccb_chair: SUBMITTED (12/05/98) atnp_ccb_chair: ACCEPTED (20/05/98) CCB-6 (Utrecht) : FORWARDED atnp_ccb_chair : RESOLVED (17/08/98)(1) (1) CCB agreed that this PDR should be upgraded to RESOLVED status and should appear as part of the first annual amendment to Doc 9705. FORWARDED status is not appropriate since it indicates a PDR which has been referred to an ATNP WG for addition to its work program, i.e. a enhancement or major change to the baseline.