Title: FIS - Invalid list of allowed APDU in the D-START confirmation 

PDR Reference:					98040007
Originator Reference: 				dstart
SARPs Document Reference: 			FIS SARPs, Sections 2.4.5.3.12.7
Status: 						FORWARDED
PDR Revision Date: 				25/06/98 (PROPOSED -> FORWARDED)
							20/05/98 (ACCEPTED -> PROPOSED)
							27/04/98 (SUBMITTED -> ACCEPTED)
PDR Submission Date:  				09/04/98
Submitting State/Organization: 		CENA, CHARME
Submitting Author Name: 			Jean, M
Submitting Author E-mail Address: 		jean@cenatls.cena.dgac.fr
Submitting Author Supplemental 
Contact Information:			
SARPs Date:  					IV2.2
SARPs Language:	 				English

Summary of Defect:
 
In order to allow the sequence of events described in Figure 2.4.5-11 "ground cancellation during contract establishment phase", the air LI-module shall be designed to receive in a D-START confirmation User Data parameter a [FISCancelUpdateContract] APDU.

Section 2.4.5.3.12.7 specifies only the [FISAccept] and the [FISReject] APDUs as valid D-START confirmation User Data parameter.

Editor's note: Further study of this situation showed that Figure 2.4.5-11 is operationally incorrect. Indeed, when the ground user receive a FIS-udate-contract indication it can either accept or reject the contract by invoking the FIS-update-contract response. It is meaningless to allow him to cancel the update contract before accepting it. 

Impact On Interoperability:

With the current specification, if the ground user replies to an FIS-update-contract indication with a FIS-cancel-update-contract, the FIS-air-ASE aborts the dialogue. This is not clean, since all the contracts not impacted by the cancellation have to be re-installed. However, this situation does not jeopardize the interoperability.

Assigned SME: 				Sub-Volume II SME

Proposed SARPs amendment: 

1/ Allow the ground user to invoke the FIS-cancel-update request after receipt of an FIS-update-contract indication. Change the SARPs to fix the problem. 

Change  section 2.4.5.3.12.7 from:
Upon receipt of a D-START confirmation with a Result parameter containing the abstract value "accepted" and with a UserData parameter containing a FISUplinkAPDU [FISAccept] or [FISReject] APDU, then

to:
Upon receipt of a D-START confirmation with a Result parameter containing the abstract value "accepted" and with a UserData parameter containing a FISUplinkAPDU [FISAccept], [FISReject] or [FISCancelUpdateContract] APDU, then

2/ Forbid the ground user to invoke the FIS-cancel-update request after receipt of an FIS-update-contract indication. 


SME Recommendation to CCB: 		

SG2 proposes to keep the SARPs unchanged for Package-1 but to identify the problem in the Guidance. Advices should be given in the GM to ground ASE implementors to not allow the cancellation of an update contract during the contract establishment phase (and to reject the contract instead). The FIS protocol in Package-2 should be modified in such a way the cancellation is not authorized during the contract establishment phase.

CCB Decision:				atnp_ccb_chair: SUBMITTED (09/04/98)
					atnp_ccb_chair: ACCEPTED (27/04/98)
					CCB-6 (Utrecht): FORWARDED (25/06/98)