Title: AARQ parameter support PDR Reference: 98100009 Originator Reference: (email 15/10/98) SARPs Document Reference: ULCS SARPs Table 4.6-9 Status: RESOLVED Impact: D (Minor) PDR Revision Date: 18/01/99 (PROPOSED -> RESOLVED) 17/11/98 (SUBMITTED -> PROPOSED) PDR Submission Date: 28/10/98 Submitting State/Organization: ATNP/WG3/SG2 Submitting Author Name: Greg Saccone Submitting Author E-mail Address: gsaccone@home.com Submitting Author Supplemental Tel: (604) 681-5829 Contact Information: SARPs Date: Doc 9705 ed 1 SARPs Language: English Summary of Defect: Table 4.3-8 (D-START request primitive) specifies the Calling AP- and Calling AE-Invocation Identifiers as not used, but table 4.6-9 (Supported AARQ Parameters) shows them as optional for the sender Table 4.6-9 does seem inconsistent, especially since the Called parameters are all X for sending. The Calling invocation ids should be X for sending. Also, the calling AP title and calling AE qualifier should be M for sending, not O as currently specified, since support for Calling Peer ID is mandatory, even though it may not always be used in every instance of communication. Assigned SME: Sub-Volume IV SME (Tony Kerr) Proposed SARPs amendment: In Table 4.6-9, in the column (Sender, ATN Support): a) Change the entry for row 5 (Calling AP title) from O to M b) Change the entry for row 6 (Calling AE qualifier) from O to M c) Change the entry for row 7 (Calling AP invocation-identifier) from O to X d) Change the entry for row 8 (Calling AE invocation-identifier) from O to X Impact on interoperability: There should be no impact on interoperability. A strict interpretation of Table 4.6-9 would have allowed a valid implementation to omit support for Calling AP title and calling AE qualifier fields in AARQ APDUs. However, this would then have been inconsistent with 4.3.3.3.2.2.1.e). SME Recommendation to CCB: Progress the PDR to RESOLVED, with the solution as proposed above. CCB Decision: RESOLVED (CCB-8 meeting, Honolulu)