Title: ATSMHS / conversion of forwarded IPMs

PDR Reference: 97060015

Originator Reference: 

SARPs Document Reference: Sections 3.1.2.3.5.2.1.4, Table 
3.1.2-11/Part 3/8.2, 3.1.2.3.5.2.3.4

Status: 	ACCEPTED -> 	PROPOSED	21/08/97
			 ->	RESOLVED	17/10/97

PDR Revision Date: 17/10/97

PDR Submission Date: 27/06/97

Submitting State/Organization: SITA

Submitting Author Name: Edem E.

Submitting Author E-mail Address: efifiom.edem@par.sita.int

Submitting Author Supplemental Contact Information: 
-------------------------------------------------------------------- 
Efifiom (Fif) Edem              Tel      : +33 1 46.41.13.70
SITA                            Fax      : +33 1 46.41.15.94 Messaging 
& EDI Projects Dept.  IATA     : jpuspxs
18 rue Paul Lafargue            Internet : efifiom.edem@par.sita.int 
92904 Paris-La Defense          X.400    : C=ww; A=sitamail; O=sita; 
France                                     OU1=par; OU2=es
S=edem; G=efifiom
--------------------------------------------------------------------

SARPs Date: ICAO version 1.1 (Phuket output)

SARPs Language: english

Summary of Defect:
An AMHS/AFTN Gateway should reject an incoming IPM (nested) Forwarded 
message since the concept of AFTN (nested) Forwarded Messages does NOT 
exist.
To illustrate the comment above, the following scenario may be 
considered:
Direct User DU1 sends an IPM to Direct User DU2. DU2 forwards it to 
Direct User DU3 who in turn forwards it to Indirect User IU1 via an 
AFTN/AMHS Gateway. Since the AFTN/AMHS Gateway generates the AFTN 
Originator Indicator and Addressee Indicator from the originator-name 
and the recipient-name fields on the AMHS Message envelope 
respectively, the AFTN user corresponding to IU1 will consider the 
message to be directly from the AFTN user corresponding to DU3 since 
the AFTN Message will NOT contain any information concerning the 
DU1/DU2 and DU2/DU3 message exchanges.

Assigned SME: Sub-Volume 3 SME

Proposed SARPs amendment :

A) 3.1.2.3.5.2.1.4, item a): delete sub-items 5) and 6);

B) 3.1.2.3.5.2.1.4, item a): append the word "or" to items 3) and 4);

C) 3.1.2.3.5.2.1.4, item b): replace the words "types 1) to 6)" with 
the words "types 1) to 4)";

D) Table 3.1.2-11, Part 3, item 8:
replace item 8 which is currently:
8   message   O   M   M   T   see Part 3/8.1 and 8.2 
with:
8   message   O   M   M   X   see Note 2

E) Table 3.1.2-11, Part 3: delete items 8.1, 8.1.1, 8.1.2 and 8.2

F) Table 3.1.2-11, Part 4, item 7:
replace item 7 which is currently:
7   message-body-part   O   M   M   T   see Part 3/8 
with:
7   message-body-part   O   M   M   X   see Note 2

G) 3.1.2.3.5.2.3.4: delete clause (including subsequent Note) and 
renumber clause 3.1.2.3.5.2.3.5 accordingly;

H) Table 3.1.2-11, Part 4, item 11, column Mapping / Notes:
replace reference to 3.1.2.3.5.2.3.5 a reference to 3.1.2.3.5.2.3.4.


SME Recommendation to CCB: RESOLVED


CCB Decision:		RESOLVED