home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.iso
- Path: sparky!uunet!walter!att-out!pacbell.com!decwrl!deccrl!news.crl.dec.com!dbased.nuo.dec.com!e2big.mko.dec.com!col01.enet.dec.com!goebbels
- From: goebbels@col01.enet.dec.com (My name is fp goebbels)
- Subject: cmis problem on RO-REJECT
- Message-ID: <1992Dec14.152041.18024@e2big.mko.dec.com>
- Sender: usenet@e2big.mko.dec.com (Mr. USENET)
- Organization: Digital Equipment Corporation
- Date: Mon, 14 Dec 1992 21:24:27 GMT
- Lines: 39
-
-
-
-
- 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.
-