Title: CM - Reception of a D-START Calling Peer ID with a wrong type PDR Reference: 98120007 Originator Reference: acicm05 SARPs Document Reference: CM SARPs, Sections 2.1.4.2.1, 2.1.5.3.2.2.1 and 2.1.5.4 Impact : C (Clarification) Status: RESOLVED PDR Revision Date: 21/01/99 (PROPOSED -> RESOLVED) 19/01/99 (ACCEPTED -> PROPOSED) 18/01/99 (SUBMITTED -> ACCEPTED) 15/12/98 (SME comment added) PDR Submission Date: 03/12/98 Submitting State/Organization: AIRSYS ATM (ACI) Submitting Author Name: Ilkiewicz, M / Stokes, S Submitting Author E-mail Address: michel.ilkiewicz@cdv.vly.sextant. thomson-csf.com, shawn.stokes@atnsi.com Submitting Author Supplemental Contact Information: SARPs Date: IV2.2, IV2.3 (Doc 9705 Ed1) SARPs Language: English Summary of Defect: The CM ASE should abort with a reason indicating Invalid Calling Peer ID (not yet defined as a abstract syntax value for the CMAbortReason in section 2.1.4.2.1) when a D-START indication is received with a Calling Peer ID which is not valid for the expected peer originator end system type of the D-START message. Consider the following cases, which should result in an abort by the CM ASE: a) CM-air-ASE receives a D-START indication with a Calling Peer ID which is not a valid four to eight character facility designator. Note: Requirement 2.1.5.3.2.2.1 should also indicate as a precondition to this requirement that the Calling Peer ID is a valid facility designator. b) CM-ground-ASE receives a D-START indication containing a [CMLogonRequest] APDU with a Calling Peer ID which is not a valid 24 bit Aircraft Address. c) CM-ground-ASE receives a D-START indication containing a [CMForwardRequest] APDU with a Calling Peer ID which is not a valid four to eight character facility designator. Assigned SME: Sub-Volume II SME Proposed SARPs amendment: Solution A/ 1/ The abstract syntax for the CMAbortReason in section 2.1.4.2 should add one additional value as follows: invalid-calling-peer-id (10), 2/ The requirement text for section 2.1.5.3.2.2.1 should be changed from: Upon receipt of a D-START indication, if the CM-air-ASE is in the state and the D-START indication Quality-of-Service parameter has the abstract value "flight regularity communications" and the Quality-of-Service parameter has the abstract value of "low" then: To: Upon receipt of a D-START indication, if the CM-air-ASE is in the state and the D-START indication Quality-of-Service parameter has the abstract value "flight regularity communications", the Quality-of-Service parameter has the abstract value of "low", and the parameter is a valid four to eight character facility designation then: 3/ Add a new section 2.1.5.4.9 and subsections for the following textual requirements as follows: 2.1.5.4.9 D-START Indication Calling Peer ID Parameter Not as Expected 2.1.5.4.9.1 Upon receipt by the CM-air-ASE of a D-START indication with a Calling Peer ID which is not a valid four to eight character facility designator, the CM-air-ASE shall: a) stop all timers b) create a CMAircraftMessage APDU with a CMAbortReason [invalid-calling-peer-id] APDU message element c) invoke D-ABORT request with 1) the abstract value "provider" as the D-ABORT Originator parameter value, and 2) the APDU as the D-ABORT User Data parameter value, and d) enter the IDLE state 2.1.5.4.9.2 Upon receipt by the CM-ground-ASE of a D-START indication containing a [CMLogonRequest] with a Calling Peer ID which is not a valid 24 bit Aircraft Address, the CM-ground-ASE shall: a) stop all timers b) create a CMGroundMessage APDU with a CMAbortReason [invalid-calling-peer-id] APDU message element c) invoke D-ABORT request with 1) the abstract value "provider" as the D-ABORT Originator parameter value, and 2) the APDU as the D-ABORT User Data parameter value, and d) enter the IDLE state 2.1.5.4.9.3 Upon receipt by the CM-ground-ASE of a D-START indication containing a [CMForwardRequest] with a Calling Peer ID which is not a valid four to eight character facility, the CM-ground-ASE shall a) stop all timers b) create a CMGroundMessage APDU with a CMAbortReason [invalid-calling-peer-id] APDU message element c) invoke D-ABORT request with 1) the abstract value "provider" as the D-ABORT Originator parameter value, and 2) the APDU as the D-ABORT User Data parameter value, and d) enter the IDLE state Solution B/ In order to be able to map the value received in the D-START ind parameter to the CM-logon parameter or to the CM-update/CM-contact , a check ON THE TYPE of the must first be performed by the ASE. This is done in sections 2.1.5.3.3.2.1 and 2.1.5.3.3.2.2. This is not done in section 2.1.5.3.2.2.1. There is an exception handling procedure (section 2.1.5.4.4.3 introduced by PDR 98110002) defined for the case an unexpected primitive or parameter primitive is received. If the peer ASE has used the wrong type for the Calling Peer Id, the dialogue is aborted on the ground that the protocol has not been respected by the peer (reason "protocol error"). Therefore, only change 2 in solution A/ above is proposed to be accepted. The changes 1 and 3 above are proposed to be rejected. SME Recommendation to CCB: CCB Decision: atnp_ccb_chair: SUBMITTED (03/12/98) CCB-8 (Honolulu) : ACCEPTED (18/01/99) CCB-8a (Honolulu) : RESOLVED (21/01/99) With solution B/