cmis problem on RO-REJECT

Thread View: comp.protocols.iso

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by My name is fp goebbels Mon, 14 Dec 1992 21:24

#1274

Author: My name is fp goebbels
Date: Mon, 14 Dec 1992 21:24

39 lines
1685 bytes



Due to ISO 9596-1 (see for example chapter 6.6: Action procedure, 
6.6.4: Receipt of response) the following scenario may occur:

     Invoker                         Performer 

     M-Action-req  -------------->   M-Action-ind

                  <--------------    M-Action-rsp
       (*1)
	 

     RO-Reject-U   ------------->     ?????????


(*1): As some special error occur (APDU not well formed) no confirmation
      is delivered to the invoker. An APDU ist sent to the Performer 
      using the RO-REJECT-U procedure.

      This scenario holds true for the following RO-Reject parameters:

          duplicate-invocation, mistyped-argument, resource-limitation,
	  unrecognized-operation.

Problems:
 	  
     I.) There is no description of the behaviour of the Performers CMIPM 
         on receipt of RO-REJECT-APDU. 

     II.) No confirmation is delivered to the invoking entity.

     III.) ISO 9596-1 defines a mapping of the above mentioned RO-Reject
         parameters to CMIS-Service Confirmation parameters (see 6.2.2 in
	 ISO 9596-1). But a description when the CMIPM shall deliver
	 this parameters is missing.
	 
Thanks in advance for any comments.

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads