ISO/IEC 10026-3:1992

I N TE R NAT I O NA L
ISOJIEC
STANDARD
10026-3
First edition
1992-1 2-1 5
Information technology - Open Systems
Interconnection - Distributed Transaction
Processing -
Part 3:
Protocol specification
Technologies de l’information - Interconnexion de systèmes ouverts
(OS11 - Traitement transactionnel réparti -
f
Partie 3: Spécification du protocole
Reference number
ISO/IEC 10026-3 1992 (E)
Contents
I
wiuction .
Intx x
1 Scope . 1
2 Nonnative references . 1
Definitions . 2
Abbreviations . 2
I 4
Conventions . 3
Model of the PM . 3
6.1 Overview . 3
I
principles of association usage . 3
6.1.1
6.1.2 Dialogue establishment . 4
6.1.3 Channel management . 4
6.1.4 Channel utilization . 5
6.1.5 Token control . 5
6.1.6 Concatenationheparation . 5
6.1.7 Embedding . 6
OS1 TP Protocol structure . 6
6.2
Components of the PM . 6
6.2.1
6.2.1.1 TheTPPM . 7
6.2.1.2 TheCPM . 8
Execution Rules . 8
7.1 Operation of the PM . 8
.
Relationship of SAO(s) to MACF(s) . 8
7.1.1
Input events to the PM . 9
7.1.2
7.1.3 Action sequences . 9
7.1.4 SACF queuing . 9
7.1.5 Input event blocking at the PSAP . 9
PM error conditions . 10
7.1.6
7.2 Procedure niles . 10
7.3 Definitions . 12
Log records used by the PM . 15
I 7.4
7.4.1 Log-ready record . 15
7.4.2 Log-commitreco rd . 15
7.4.3 Log-heunsticrecord . 15
7.4.4 Log-damage record . 15
7.5 Recovery-context-handle . 15
Use of ACSE. CCR and the Presentation Layer . 15
8.1 In@ocluction . 15
Use of ACSE Service primitives . 15
8.2
Use of the A-ASSOCIATE meters . 16
8.2.1
Use of the A-RELEASE parameters . 16
8.2.2
Use of the A-ABORT and A-P-ABORT parameters . 16
8.2.3
Use of CCR Service primitives . 17
8.3
Use of the Presentation Layer . 17
8.4
Use of Presentation Service primitives .
8.4.1
Mapping of C-ROLLBACK-RI to Presentation . 18
8.4.2
8.5 Association Management . 18
...........................................................................................
8.5.1 Induction 18
8.5.2 Association/dialogue compatibility . 18
8.5.3 Association/channel compatibility . 18
Initiating an association establishment . 18
8.5.4
Receiving an association establishment indication . 19
8.5.5
Responding to association establishment . 19
8.5.6
0 ISO/IEC 1992
All rights reserved . No part of this publication may be reproduced or utilized in any form or
by any means. electronic or mechanical. including photocopying and microfilm. without per-
mission in writing from the publisher .
ISO/IEC Copyright Office Case Postale 56 CH-I21 1 Genève 20 Switzerland
Printed in Switzerland
..
I
ISODEC 10026-3 : 1992 (E)
8.5.7 Receiving codition of assoCiation establishment . 20
8.5.8 Initiating an association release . 20
8.5.9 Aborting an association . 20
9 TP-ASE description . 21
9.1 Introduction . 21
..
9.2 AF Service Definition . 21
9.2.1 AF-BEGIN.DIAuxUE . 21
9.2.2 AF-BID . 21
9.2.3 AF-END-DIALOGUE . 22
9.2.4 AF-U-ERROR . 22
9.2.5 AF-ABORT . 22
9.2.6 AF-GRANT-CONTROL . 22
9.2.7 AF-REQ~ ST-CONTROL . 22
9.2.8 AF-HANDSHAKE . 22
9.2.9 AF-HANDSHAKE-AND-GRANT-CONTROL . 22
9.2.10 AF-DEFER . 22
9.2.11 AF.PREPARE . 22
9.2.12 AF.HEuRISTIC.REpoRT . 22
9.2.13 AF.ABORT.AND-HEURISTC.REPORT . 22
9.2.14 AF.RECOVER . 23
9.2.15 AF.TOKEN.GIVE . 23
9.2.16 AF-TOKEN-PLEASE . 23
AF-Services and TP APDUs: parameters and fields Mappings . 23
9.3
9.3.1 AF-BEGIN-DIALOGUE requestspondconflm. TP-BEGIN-DIALOGUE-
RI/-RC APDU . 23
request/indication/respnd confm. TP-BID-RI/-RC APDU . 25
AF-BID
9.3.2
9.3.3 AF-F3D-DIALOGUE request/ indicatiodrespon fm. Tp-END-DIALoGuE-R.I/-
RC APDU .
.................................. 25
9.3.4 AF-U-ERROR request/indication/ response/conflm. TP-U-ERROR-RV-RC APDU26
AF.ABORTreques.ication.Tp.ABORT .RI APDU . 26
9.3.5
9.3.6 AF-GRANT-CONTROL request/ indication. TP-GRANT-CONTROL-RI APDU 26
9.3.7 AF-REQUEST-CONTROL request/ indication. TP-REQUEST-CONTROL-RI APDU
........................................................................................................... 26
9.3.8 AF-HANDSHAKE request/indication/ respnse/mdm. TP-HANDSHAKE-RI/-RC
APDU . 26
9.3.9 AF-HANDSHAKE-AND-GRCONTROL requesthndicatioxdresponse confirm. TP-
HANDSHAKE-AND-GRANT-CONTROL-RY-RC APDU . 27
AF-DEFER request/indication. TP-DEFER-RI APDU . 27
9.3.10
1 AF-PREPARE requesthdication, TP-PREPARE-RI APDU . 27
9.3.1
AF-HEURISTIC-REPORT request/ indication. TP-HEURISTIC-REPORT-RI APDU
9.3.12
........................................................................................................... 27
9.3.13 AF-ABORT-AND-HEURISTIC-REPORT request/indication . 28
AF-RECOVER requesthdication. TP-RECOVER-RI APDU . 28
9.3.14
AF-TOKEN-GIVE request/indication. TP-TOKEN-GIVE-RI APDU . 28
9.3.15
AF-TOKEN-PLEASE request/ indication. TP-TOKEN-PLEASE-RI APDU . 29
9.3.16
9.4 Procedures . 29
................................................................ 29
9.4.1 AF-BEGIN-DLAux;uE
TP-BEGIN-DIALOGUE-RI TP APDU . 29
9.4.2
9.4.3 AF-BEGIN-DIALOGUE response . 29
TP-BEGIN-DIALMKJE-RC TP APDU . 29
9.4.4
9.4.5 AF-BID .
TP-BID-RI TP APDU . 29
9.4.6
9.4.7 AF-BID- . 29
TP-BID-RC TP APDU . 29
9.4.8
9.4.9 AF-END-DIALOGUE request . 29
TP-END-DIALOGUE-RI TP APDU . 29
9.4.10
9.4.1 1 AF-END-DIALOGUE . 29
TP-END-DIALOGUE-RC TP APDU . 29
9.4.12
9.4.13 AF-U-ERROR WWt . 29
TP-U-ERROR-RI TP AmlU . 29
9.4.14
9.4.15 AF-U-ERROR response . 29
TP-U-ERROR-RC TP APDU . 29
9.4.16
iii
ISODEC 10026-3 : 1992 (E)
AF-ABORT request . 30
9.4.17
TP-ABORT-RI TP APDU . 30
9.4.18
AF-GRA"TRoL request . 30
9.4.19
TP-GRANT-CONTROL-RI TP APDU . 30
9.4.20
AF-REQUEST-CONTROL request . 30
9.4.21
TP-WUEST-CONTROL-RI TP APDU . 30
9.4.22
AF-HANDSHAKE request . 30
9.4.23
TP-HANDSHAKE-RI TP APDU . 30
9.4.24
AF-HANDSHAKE response . 30
9.4/25
TP-HANDSHA=-RC TP APDU . 30
9.4,26
AF-HANDSHAKE-AND-GRANT-CONTROL request . 30
9.4127
TP-HANDSHAKE-AND-GRANT-CONTROL-RI TP APDU . 30
9.4128
AF-HANDSHAKE-AND-GRANT-CONTROL response . 30
9.4.29
TP-HANDSHAKE-AND-GRANT-CONTROL-RC TP APDU . 30
9.4.'30
AF-D- request . 30
9.43 1
TP-DEFER-RI TP APDU . 30
9.4.32
AF-PREPARE request . 30
9.4.33
C-PREPARE indication . 30
9.4.34
AF-HEURISTIC-REPORT request . 30
9.4.35
AF-ABORT- AND-HEURISTIC-REPORT request . 30
9.4.36
AF-RECOVER request . 30
9.4.37
C-RECOVER indication . 30
9.4.38
A-ABORT indication . 31
9.4.39
9.4.40 C-ROLLBACK indication . 31
C-ROLLBACK confirm . 31
9.4.41
C-COMMIT indication . 31
9.4.42
C-COMMIT confirm . 31
9.4.43
C-RECOVER confirm . 31
9.4.44
P-TOKEN-GIVE (sync-minor) indication . 31
9.4.45
AF-TOKEN-GIVE request . 32
9.4.46
P-TOKEN-PLEASE (sync-minor) indication . 32
9.4.47
AF-TOKEN-PLEASE request . 32
9.4.48
,.
9.5 Mapping . JL
10 SACF description . 33
10.1 Introduction . 33
10.2 SACF states . 33
Service definitions for SAF-DmACH-ASSOCIATION and SAF-ASSOCIATION-LOST . 34
10.3
10.3.1 SAF-DETACH-ASSOCIATION request . 34
10.3.2 SAF-ASSOCIATION-LOST indication . 34
procedure for SAF-D~ACH-ASSOCIA~ONATION~~~~~~~ . 34
10.4
Procedures for TP-ASE. CCR. ACSE. and Presentation Service Primitives . 35
10.5
10.5.1 AF-BEGIN-DIALOGUE request . 35
10.5.2 AF-BEGIN-DIALOGUE indication . 35
10.5.3 AF-BEGIN-DIALWUE resp~nse . 36
10.5.4 AF-BEGIN-DIALffiUEconfi . 36
10.5.5 AF-BID indication . 36
10.5.6 AF-BID =firm . 37
10.5.7 AF-END-DIALOGUE request . 37
10.5.8 AF-END-DIALOGUE indication . 37
10.5.9 AF-END-DWUE confvm . 38
10.5.10 AF-U-ERROR request . 38
10.5.1 1 AF-U-ERROR indication . 38
10.5.12 AF-U-ERROR Coiifirm . 38
10.5.13 AF-ABORTreqUeSt . 38
(provider. abortRI) indication . 38
10.5.14 AF-ABORT
10.5.15 AF-ABORT (user. dataRI) indication . 38
A-ABORTrequestor A-RELEASE (Resuit=affiitive)respon se . 38
10.5.16
10.5.17 A-[p-]ABORT indication or A-RELEASE (Resultdhnative) confirm . 38
10.5.18 AF-GRANT-CONTROL request . 39
10.5.19 AF-GRANT-CONTROL indication . 39
10.5.20 AF-REQUEST-CONTROL request . 39
10.5.21 AF-REQUEST-CONTROL indication . 39
iv
ISO/IEC 10026-3 : 1992 (E)
10.5.22 AF-HANDSHAKE muat . 39
10.5.23 AF-HANDSHAKE indication . 39
10.5.24 AF-HANDSHAKE confirm . 39
10.5.25 AF.HANDSHAKE.AND-GRANT.CONTROLrequest . 39
AF-HANDSHAKE-AND-GRANT-CONTROL indication . 39
10.5.26
AF-HANDSHAKEUND-GRANT-CONTROL COnflllll . 39
1 O . 5.27
10.5.28 AF-DEFER quest . 39
AF-DEFER indication . 40
10.5.29
AF-PREPARE request . 40
10.5.30
10.5.31 AF-PREPARE indication . 40
10.5.32 AF-HEURISTIC-REPORT (commitRC) indication. or AF-HEURISTIC-REPORT
(recoverDoneRC) indication . 40
C-BEGIN . 40
’ 10.5.33
C-BEGlN indication . 40
10.5.34
10.5.35 C-BEGIN confirm . 40
C-READY indication . 40
10.5.36
C-COMMIT indication or C-COMMIT+C-BEGINindication . 40
10.5.37
10.5.38 AF-ABORT (user. commitRI) indication or AF-ABORT (user. commitRC) indication .
........................................................................................................... 41
10.5.39 C-COMMIT confirm . 41
AF-ABORT-AND-HEURISTIC-REPORT (commitRC) indication . 41
10.5.40
10.5.41 C-ROLLBACK re9uest . 41
10.5.42 C-ROLLBACK indication . 41
10.5.43 AF-ABORT (rollbackRI) indication. AF-ABORT-AND-HEURISTIC-REPORT
(rollbackRI) indication. or AF-HEURISTIC-REPORT (rollbackRI) indication . 41
C-ROLLB ACK confirm. AF-HEURISTIC-REPORT (rolibackRC) indication. AF-
10.5.44
ABORT (user/provider, roilbackRC) indication or AF-ABORT-AND-HEURISTIC-
REPORT (rollbackRC) indication . 42
10.5.45 AF-RECOVER indication . 42
C-RECOVER request or AF-RECOVER request . 42
10.5.46
10.5.47 C-RECOVERindication . 42
C-RECOVER con firm . 42
10.5.48
10.5.49 U-ASErequest . 42
10.5.50 U-ASE indication . 42
10.5.5 1 AF-TOKEN-GIVE (reguiar) indication . 43
10.5.52 AF-TOKEN-GIVE (keep) indication . 43
10.5.53 AF-TOKEN-GIVE (two-way-recovery) request . 43
10.5.54 AF-TOKEN-GIVE (two-way-recovery) indication . 43
10.5.55 P-TOKEN-GïVE (sync-minor) indication . 44
10.5.56 AF-TOKEN-PLEASErequest . 44
10.5.57 AF-TOKEN-PLEASEindication . 44
10.5.58 P-TOKEN-PLEASE indication . 44
10.5.59 Protocol error . 44
1 O . 5.60 Other service primitives . 44
10.6 SACF internal events . 44
10.6.1 Unsolicited BID reject . 44
.
10.7 Concatenation . 45
10.7.1 Mapping precedence . 45
10.7.2 Concatenation rules . 45
10.8 Routeing . 46
11 MACF description . 46
11.1 Introduction . 46
CAF service definition . 46
1 1.2
11.2.1 CAF-PLEASErequest . 46
11.2.2 CAF-GIVE indication . 47
CAF-FAIL indication . 47
1 1.2.3
11.2.4 CAF-DETACH request . 47
-RECOVER indication . 47
11.3 . 48
................................................................. 48
t
on (TPPM and CPM) . 48
............................................................. 49
V
ISO/IEC 10026-3 : 1992 (E)
11.3.4
11.3.5
..., ..... . ....... . .. .. .... 50
11.3.6
.. ........................ 51
11.3.7
....................... , ..................... . ...... 51
11.3.8
indication ,. . . . . . . . . . .52
11.3.9
dication (CPM) . 52
11.3.10
11.3.1 1
11.3.12
11.3.13
nse . . . . . . . . . . . . . . . . . . . .54
11.3.14
11.3.15
11.3.16
11.3.17
11.3.18
11.3.19
11.3.20
11.3.21
A-RELEASE (Result=affimtive) response, or A-
) confilm on a dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . .56
11.3.22
11.3.23
....... ,. .. .. . .. .. .. .. .. ..... .... .... .. .. . .. .. .. .. .. .. . . . .58
11.3.24
11.3.25
11.3.26
11.3.27
11.3.28
11.3.29
............................................................. ,. ... * .. 59
11.3.30
. . . . . ,. . . . . .I. ., . . . . . . . . . .59
11.3.31
-CONTROL request . 59
11.3.32
11.3.33
11.3.34
conîirm . . . . . . . . . . , . . . . , . . . . . . . . . .60
11.3.35
11.3.36
. . . . . . . . . , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . , . . . . . . . . . . . . . . . . .60
11.3.37
....... .......... .. . .. .. .. .. .......... ... .. .... .. .. .... .. .. ..’... .. .. .. .. .... ... .. .61
11.3.38
..... .. ........ .. ....... .. .. .......... . .. .... .... .. .. ,. .. ... .. .. .. .... .. .... .. ... .61
11.3.39
.......................................... . ............. ... ......................... 61
11.3.40
11.3.41
11.3.42
...... .. .. .. ......... .... .. .. .. .. .. .. . .. .. .. .. .. .. .. ... .. .... .. .. .. .. .. .. . .. .61
11.3.43
.. .. .. .. .. .. ......... .. .. .. .. .. .. ..... .. .. .. .... .. ..... .. .... .. .. .... .... . .. .61
11.3.44
11.3.45
11.3.46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
11.3.47 . . . . . . . . . . . . . . . . . . . . , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
11.3.48
11.3.49
11.3.50
11.3.5 1
11.3.52
11.3.53
11.3.54
11.3.55
11.3.56
11.3.57
vi
ISODEC 10026-3 : 199
REPORT (rollbackRC) indication . 66
1 1.3.58 CAF-RECOVER (ready) indication . 67
11.3.59 C-RECOVER (ready) indication or AF-RECOVER (ready) indication (CPM) . 68
1 1.3.60 CAF-REÇOVER (commit) indication . 68
11.3.61 C-RECOVER (commit) indication . 69
11.3.62 C-RECOVER (commit) indication or AF-RECOVER (commit) indication (CPM) 69
11.3.63 C-RECOVER (done) confirm or AF-HEURISTIC-REPORT (recoverDoneRC)
indication . 70
11.3.64 C-RECOVER (unknown) confitm . 70
C-RECOVER (unknown) confirm (CPM) . 70
11.3.65
11.3.66 C-RECOVER (re~-later)confum . 70
1 1.3.67 C-RECOVER (retry-later) confirm (CPM) . 70
1 1.3.68 AF-TOKEN-GIVE (two-way-recovery) indication on a channel VPPM) . 70
11.3.69 AF-TOKEN-GIVE indication (CPM) . 70
11.3.70 AF-TOKEN-PLEASE indication on a channel (TPPM) . 71
11.3.71 AF-TOKEN-PLEASE indication (CPM) . 71
11.3.72 CAF-PLEASE request (CPM) . 71
11.3.73 CAF-GIVE indication . 71
1 1.3.74 CAF-FAIL indication . 72
11.3.75 CAF-DETACH request (CPM) . 72
11.4 Internai event procedures . 72
11.4.1 Deiay recovery . 72
11.4.2 Heuristic damage compensation for subûee . 72
11.4.3 Restart after node crash (CPM) . 72
11.4.4 Retry recovery . 72
11.4.5 Taking a heuristic decision . 73
11.4.6 Terminating a channel (CPM) . 73
11.4.7 TPPM creation after node crash . 73
11.4.8 TPPM-initiated rollback . 73
11.5 Common procebures . 73
1 1.5.1 Completing commitment . 73
11.5.2 Enterhg READY state . 75
1 1 S.3 First requestlresponse . 75
11.5.4 Initiating a transaction branch . 75
...................................................................... 76
11.5.5 Initiating rollback at TPPM
11.5.6 Initiating transaction after rollback . 77
11.5.7 Making commitment decision . 77
1 1.5.8 Receiving commit order . 78
1 1 S.9 Recording the heuristic condition . 78
11.5.10 orting rollback to superior . 79
1 1.5.1 1 Rollback next transaction . 80
Sending commit order . 80
11.5.12
Structure and encoding of TP APDUs . 82
Abstract syntax of the TP-ASE APDUs . 82
12.1
Rules of extensibility . 88
12.2
Conformance . 88
Static conformance requirements . 88
13.1
13.1.1 Conformance classes . 88
13.1.1.1 GendrequiremRnts . 88
13.1.1.2 Application transaction branches class . 88
13.1.1.3 Chained provider-supported transaction branches class . 88
.................. 88
13.1.1.4 Unchaineù provider-supported aansaction branches class
13.1.2 Capabilities . 88
13.1.2.1 General capabiiities . 88
13.1.2.2 Constraints . 89
13.1.3 Functional units . 89
13.1.3.1 Defmition . 89
13.1.3.2 Description of recovery functional unit . 89
13.1.3.3 Requirements on TP APDUs . 89
Dependencies on other standards . 91
13.1.4
Dynamic conformanm requVemenrs . 91
13.2
13.2.1 GeneraireqWenîs . 91
vii
ISOflEC 10026-3 : 1992 (E)
13.2.2 Specific requirements . 92
Protocol Implementation Conformance Statement . 92
13.3
Receiving TP APDUs . 92
13.4
14 Camp liante . 92
15 precedence statement . 92
Index of Actions and Events . 93
Annexes
A OS1 TP protocol - State tables . 97
Requirements for writing U-ASES and application contexts . 207
B
C Scenarios . 209
Summary of assigned object idenflier values . 315
D
E Recovery from destruction of atomic action data . 317
F TPPM transaction states . . 319
Estelle description of the TP protocol . 323
G
H LOTOS description ofthe TP protocol . 509
viii
ISO/IEC 10026-3 : 1992 (E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the Inter-
national Electrotechnical Commission) form the specialized system for
worldwide standardization. National bodies that are members of IS0 or
IEC participate in the development of International Standards through
technical committees established by the respective organization to deal
with particular fields of technical activity. IS0 and IEC technical com-
mittees collaborate in fields of mutual interest. Other international organ-
izations, governmental and non-governmental, in liaison with IS0 and IEC,
also take part in the work.
In the field of information technology, IS0 and IEC have established a joint
technical committee, ISO/IEC JTC 1. Draft International Standards adopted
by the joint technical committee are circulated to national bodies for vot-
at least
ing. Publication as an International Standard requires approval by
75 % of the national bodies casting a vote.
International Standard ISO/IEC 10026-3 was prepared by Joint Technical
Committee ISO/IEC JTC 1, Information technology.
ISO/IEC 10026 consists of the following parts, under the general title In-
formation technology - Open Systems Interconnection - Distributed
Transaction Processing:
- Part 1: OS1 TP Model
- Part 2: OS1 TP Service
- Part 3: Protocol specification
- Part 4: Protocol implementation conformance statement (PICS)
proforma
- Part 5: Application context proforma
- Part 6: Unstructured data transfer
Annexes A and B form an integral part of this part of ISO/iEC 10026. An-
nexes C, D, E, F, G and H are for information only.

ISOnEC 10026-3 : 1992 (E)
Introduction
ISOBIEC 10026, Distributed Transaction Processing (OS1 TP), is one of a set of
standards produced to facilitate the interconnection of computer systems. It is
related to other International Standards in the set as defined by the Reference
Model for Open Systems Interconnection (IS0 7498). The Reference Model
subdivides the area of standardization for interconnection into a series of layers of
specification, each of manageable size.
The aim of Open Systems Interconnection (OSI) is to allow, with a
minimum of technical agreement outside the interconnection standards, the
interconnection of computer systems:
a) from different manufacûmm;
b) under different management;
c) of different levels of complexity; and
d) of different technologies.
ISO/IEC 10026 defines an OS1 TP Model, an OS1 TP Service and specifies an
OS1 TP Protocol available within the Application Layer of the OS1 Reference
Model.
The OS1 TP Service is an Application Layer service. It is concerned with
identifiable information which can be related as transactions, which may involve
two or more Open Systems.
ISO/IEC 10026 provides sufficient facilities to support transaction processing,
and establishes a framework for coordination across multiple TP resources in
separate open systems.
ISO/IEC 10026 does not specify the interface to local resources, nor does it

ISO/IEC 10026-3 : 1992 (E)
INTERNATIONAL STANDARD
Information technolo Systems Interconnection -
g - Part 3:
Distributed Transacti
Protocol specifiçati
2 Normative references
I 1 Scope
The following standards contain provisions which, through
This past of ISOm 10026 provides
reference in this text, constitute provisions of this part of
ISO/IEC 10026. At the time of publication, the editions
a) a statement (clauses 6 to 11) of the nature of the
indicated were valid. All standards are subject to revision,
automaton giving the necessary behaviour of each of the
and parties to agreements based on this part of ISWC
participating entities which are providing the OS1 TP
ncouraged to investigate the pa&iiIity of
Service, covering
st recent editiw of the standards indicated
~6 E an& SO maintain registers of
1) the actions to be taken cm mduing reqws% am3
Stanrn.
response primitives. issued by a! TP Semias
imwwtion;
ï@rmation proceming systems - Open
nection - Basic Refemnnae Model.
indication
esentation
IS0 7498-2 : 1989, Informution procprs9ing ~~~ - Open
Systems Interconnection - Basic Referme&
Securiîy architecture.
3) the actions to be takm as 8 result of certain
events within the local system;
IS0 7498-3 : 1989, Informution process
Systems Interconnection - Basic Reference
4) the actions to be taken as a result of interactions
Naming and aaidressing.
with other ASES;
ISD 8326 : 1987, Information processing systems - OpeW
b) the definition (clause 12) of the abstract synWf
&"ems Interconnection = Bait connection oriented
required to convey the TP protocol control information;
Mbn service definition.
c) the CO ents to be met by
implementatiomaf @ks * -l), Information technology -
on - Basic connection oriented
- Amendment 4: Addilional
The scope of this pWdISmC'lm is limited to the
interconnection of system&; it dbes not specify or restrict
the implementation of PUssible interfaces within a
computer system.
IS0 8327 : 1987/Amd 3: -l), Information procB@ing
systems - Open Systems Interconnection - Basic connection
oriented session protocol specification. - Amendment 3:
I
ISO/IEC 10026-3 : 1992 (E)
Additional synchronization functionality.
ISOAEC 9594-6 : 1990, Informution technology - Open
System Interconnection - The Directory - Part 6: Selected
ISOirR 8509 : 1987, Informution processing systems -
Attribute Types.
Open System Interconnection - Service conventions.
ISOAEC 9646-1 : 1991, Information technology - Open
IS0 8649 : 1988, Informution processing system - Open
Systems Interconnection - Conformance testing
Systems Interconnection - Se definition for the
metwiogy &framework - Part I: General concepts.
Association Control Service Eleme
ISO/IEC 9804 : 1990, &formation technology - Open
IS0 8650 : 1988, Information processing systems - Open
Systems Interconnection - Service definition for the
Systems Interconnection - Protocol spec fication for the
Commitment, Concurrency and Recovery service element.
Association Control Service Element.
IS0 8822 : 1988, Information processing system - Open ISO/IEC 9804/Amd 2 -l), Information technology -
- Connection oriented presentation Open System Interconnection - Service definition for the
Systems Interconnection
service definition. Commitment, Concurrency and Recovery service element -
Amendment 2: Session mapping changes.
IS0 8822 : 1988/Amd 5: -l), Information technology -
ISO/IEC 9805 : 1990, Information technology - Open
Open Systems Interconnection - Connection oriented
Systems Interconnection - Protocol spec@ation for the
presentation service definition - Amendment 5: Additional
Commitment, Concurrency and Recovery service element.
synchronization jùnctionality.
IS0 8823 : 1988/Amd 5: -l), Information technology - ISO/IEC 9805/Amd 2 -l), Information technology -
Open Systems Interconneccion - Protocol spec&catwn for
Open Systems Interconnection - Connection oriented
presentation protocol specifcation - Amendment 5: the Commitment, Concurrency and Recovery service
element - Amendment 2: Session mapping changes.
Additional synchronization functionality.
ISO/IEC 8824 : 1990, Information technology - Open
3 Definitions
Systems Interconnection - Specification of Abstract Syntax
Notation One (ASN. 1).
For the purposes of this part of ISO/IEC 10026, the
ISO/IEC 8825 : 1990, Information technology - Open definitions given in ISO/DEC 10026-1 (TP Model) and
Systems Interconn
...