Title:                              ADS - Missing exception case

PDR Reference                       97080006
Originator reference:               PDR-3
SARPs Document Reference:           ADS SARPs, Section 2.2.1.5.4
Status:                             ADOPTED
PDR Revision Date:                  22/09/97 (SUBMITTED -> ACCEPTED)
				    	      22/08/97 (ACCEPTED -> PROPOSED)
						20/10/97 (PROPOSED -> RESOLVED)
PDR Submission Date:                18/08/97
Submitting State/Organisation:      ATNP/WG3/SG2
Submitting Author Name:             T I Maude
Submitting Author E-mail Address:   maude@level-7.co.uk
Submitting Author Supplemental
Contact Information:                Fax +44 1344 868 442
SARPs Date:                         IV1.1, March 97
SARPs Language:                     English

Summary of defect:

2.2.1.5.4 covers various exception cases which result in an abort. One exception is not covered - that is the case where a dialogue primitive (ind or cnf) is invoked by the dialogue service provider, and there is no user data.

If no amendment is made, then a compliant implementation will fail under these circumstances since the LI module will not react to this situation.


Assigned SME:                       Sub volume II SME

Proposed SARPs amendment:

Add the following to 2.2.1.5.4:

"2.2.1.5.4.7.2  Upon receipt of a D-START indication, a D-START confirmation or a D-DATA indication with no user data, the air or ground  AB module shall be requested to abort with reason decoding-error."

("decoding-error" should be in italics or otherwise highlighted.)


SME Recommendation to CCB:          -

CCB Decision:                       atnp_ccb_chair: SUBMITTED (18/08/97)
				  	      atnp_ccb_chair: ACCEPTED (22/09/97)
					      atnp_ccb_chair: RESOLVED (20/10/97)