ISO/IEC 10021-6:1990/Amd 1:1994

Information Technology — Text communication — Message-Oriented Text Interchange Systems (MOTIS) — Part 6: Protocol Specifications — Amendment 1

Technologies de l'information — Communication de texte — Systèmes d'échange de texte en mode message — Partie 6: Spécification de protocole — Amendement 1

General Information

• Status: Withdrawn
• Publication Date: 30-Nov-1994
• Withdrawal Date: 30-Nov-1994
• ICS: 35.240.20 - IT applications in office work
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Drafting Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 30-Dec-1996

Relations

• Revised: ISO/IEC 10021-6:1996 - Information technology — Message Handling Systems (MHS): Protocol specifications — Part 6:
• Effective Date: 15-Apr-2008
• Amends: ISO/IEC 10021-6:1990 - Information Technology — Text communication — Message-Oriented Text Interchange Systems (MOTIS) — Part 6: Protocol Specifications
• Effective Date: 06-Jun-2022
• Child: ISO/IEC 10021-6:1990 - Information Technology — Text communication — Message-Oriented Text Interchange Systems (MOTIS) — Part 6: Protocol Specifications
• Effective Date: 15-Apr-2008

Standards Content (Sample)

INTERNATIONAL iSO/iEC
i
STANDARD 10021-6
First edition
1990-1 2-0 1
AMENDMENT 1
1994-1 2-0 1
Information technology - Text Communication -
Message-Oriented Text Interchange Systems
(MOTIS) -
Part 6:
Protocol Specifications
AMENDMENT 1: Message Store Extensions
Technologies de l'information - Communication de texte - Systèmes d'échange
de texte en mode message (MOTIS) -
Partie 6: Spécifications du protocole
AMENDEMENT I: Extensions de dépôt de message
Reference number
ISO/IEC 1002 1-6: 1990/Amd.l: 1994(E)

---------------------- Page: 1 ----------------------
ISO/iEC 10021-6:1990/Amd.l:1994(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 committees collaborate in fields of mutual interest. Other
international organizations, 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 voting. Publication
as an International Standard requires approval by at least 75 % of the national
bodies casting a vote.
Amendment 1 to International Standard ISO/IEC 10021-6: 1990 was prepared by
Joint Technical Committee ISOAEC JTC 1, Information technology,
Subcommittee 18, Document processing and related communication.
O ISO/IEC 1994
All rights reserved. Unless otherwise specified, no pari of this publication may be
or utilized in any form or by any means, electronic or mechanical, including
reproduced
photocopying and microfilm, without permission in writing from the publisher.
ISO/IEC Copyright Office Case postale 56 CH-1211 Genève 20 Switzerland
Printed in Switzerland
..
11

---------------------- Page: 2 ----------------------
Q ISO/I[EC
ISO/IEC 10021-61990 / Amd.l:1994 (E)
Information technology -Text Communication -
Message-Oriented Text Interchange Systems (MOTIS) -
Part 6:
Protocol Specifications
Amendment 1 : Message Store Extensions
O Introduction
This clause provides an introduction to this Amendment. The text in this clause Is not intended for inclusion in ISOIIEC
10021 -6.
This Amendment accommodates the requirements for additional Application Contexts arising from ISO/IEC 10021-5:1994
concerning Message Store extensions, and from Amendment 2 to ISO/IEC 1ûû21-4:1990 Concerning P3 extensions.
2.1 Open Systems Interconnection
Replace existing clause 2.1 with the following:
This part of ISO/iEC 10021 cites the following OS1 specifications:
Information technology - Open Systems Interconnection - Service Definition for the Association
.) ISOIIEC 8649: 1988,
Control Service Element.
ISOiIEC 8822 1994,
Information technoiogy - Open Systems Interconnection - Basic Presentation Service Definition.
ISOIiEC 8824-1: l), Infirmation technology - Open Systems Interconnection - Abstract Syntax Notation One (ASNJ):
Spec@cation of Basic Notation.
ISO/IEC 8824-2 l), - Open Systems Interconnection - Abstract Syntax Notation One (ASN.1):
Information technology
Information Object Specijlcation.
Information technology - Open Systems Interconnection - Abstract Syntax Notation One (ASN.1):
ISO/lEC 8824-3: l),
Constraint Specification.
To be published.
1

---------------------- Page: 3 ----------------------
IsO/IEC 10021-61990 / Amd.l:19!M CE) Q ISO/IEC
Information technology - Open Systems Interconnection - Abstract Syntax Notation One (ASN.1):
ISOJIX! 8824-4: l),
Parameterization of ASN.1 Specifications.
ISO/IEC 9066-1~1989, Information processing systems - Text communication - Reliable Tranrfer - Part I: Model and
service definition.
ISO/reC 9066-21989, Information processing systems - Text communication - Reliable Transfir - Part 2: Protocol
Specification.
ISO/ii%C 13712-1: *I, Information technology - Remote Operations: Concepts, Model and Notation.
Information technology - Remote Operations: OSI Realisations: Remote Operations Service
ïSO/reC 137 12-2: Il,
Element (ROSE) Service Defurition.
ISO/IEC 137 12-3: l), Information technology - Remote Operations: OSI Realisations: Remote Operations Service
Element (ROSE) Protocol Spec@cation.
2.2 Message Handling Systems
a
Repiàce existing clame 2.2 with the following:
This part of ISO/reC 1021 cites the following Message Handling specifications:
ISO/IEC 10021 - 1: 1990, Information technology -Text Communication - Message Oriented Text Interchange Systems
(MOTIS) - Part I: System and service overview.
ISO/reC 10021-1/Amd. 1: 1994, Information technology -Text Communication - Message Oriented Text Interchange Systems
(MOTIS) - Part I: System and service overview - Amendment I: Message Store Extensions.
ISO/cec 10021-2 1990, Injbmation technology -Text Communication - Message Oriented Text Interchge Systems
(MOTIS) - Part 2: Overall Architecture.
ISO/iEC 10021-2/Amd.l: 1994, Information technology -Text Communication - Message Oriented Text Interchange Systems
(MOTIS) - Part 2: Overall Architecture - Amendment 1 : Representation of OIR addresses for
human exchange.
ISO/reC 10021 -2lAmd.2 1994, Informatwn technology -Text Communication - Message Oriented Text Interchange System
(MOTIS) - Part 2: Overall Architecture - Amendment 2: Minor Enhancements - Multinational
e
organizations and terminal-form addresses.
ISO/IEC 10021-2/Amd.3: l), Information technology -Text Communication - Message Oriented Text Interchange System
(MOTIS) - Part 2 Overall Architecture - Amendment 3.
ISOJIEC 100214.1990, Inforrptation technology -Text Communication - Message Oriented Text Interchange System
(MOTIS) - Part 4: Message Transfer System: Abstract Service Definition and Procedures.
ISO/reC 10021-4/Amd. 1: 1994, In.mtwn technology -Text Communication - Message Oriented Text Interchange Systems
(MOTIS) - Part 4: Message Tranqfet System: Abstract Service Definition and Procedures -
Amendment I: Minor Enhancements: Notification type and Directory substitution.
To be published
2

---------------------- Page: 4 ----------------------
Q ISO/IE3C
ISOhEC 10021-6:1990 / Amd.l:1994 (E)
ISOIiEC 10021 -4lAmd.2: l), Information technology -Text Communication - Message Oriented Text Interchange Systems
(MOTIS) - Part 4: Message Tran$èr System: Abstract Service Definition and Procedures -
Amendment 2: ASN.l and P3 extensions.
ISOiIEC 1W1-5: 1994, Information technology -Text Communication - Message Oriented Text Interchange Systems
(MOTIS) - Part 5: Message Store -Abstract service definition.
ISO/iEC 1002 1-6 1990. Information technology -Text Communication - Message Oriented Text Interchange Systems
(MOTIS) - Part 6: Protocol Specifications.
ISO/iEC 10021-7: 1990, Information technology -Text Communication - Message Oriented Text Interchange Systems
(MOTIS) - Part 7: Interpersonal messaging system.
ISOPFC 10021-7lAmd. 1: 1994, Information technology -Text Communication - Message Oriented Text Interchange Systems
(MOTIS) - Part 7: Interpersonal messaging system - Amendment I: Minor Enhancements: File
transfir body part and auto-submission indication.
ISO/IEC 10021 -1IAmd.2: Il, Information technology -Text Communication - Message Oriented Text Interchange Systems
(MOTIS) - Part 7: Interpersonal messaging system - Amendment 2: Voice body part and new
e ASN.1.
ISO/JEC 1002L7/Amd.3: 1994, Information technology -Text Communication - Message Oriented Text Interchange Systems
(MOTIS) - Part 7: Interpersonal messaging system - Amendment 3: Message Store Extensions.
6.1 MHS Access Protocol Model
Replace paragraph 5 of 6.1 (IIAccess to the MTS .") with the following:
Access to the MTS Abstract Service is realized by the pairing of three ports between the MTS and the MTS-user. Each port
is supported by an application-service-element; for some port types more than one version of the application-service-element
is defined. The Message Submission Service Element (MSSE) supports the services of the submission-port. The Message
Delivery Service Element 1988 (MDSE-88) and Message Delivery Service Element 1994 (MDSE-94) support the services of
the delivery-port. The Message Administration Service Element 1988 (MASE-88) and Message Administration Service
Element 1994 (MASE-94) support the services of the administration-port.
Replace paragraph 6 of 6.1 (~~SimiZarly, access to the MS .'y with the following:
Similarly, access to the MS Abstract Service is realized by the pairing of three ports between the MS and the MS-user. Each
e
port is supported by an application-service-element; for each port type more than one version of the application-service-
element is defined. The Message Submission Service Element (MSSE) and the MS Message Submission Service Element
(MS-MSSE) support the services of the MS-submission-port. The Message Retneval Service Element 1988 (MRSE-88) and
the Message Reîrievai Service Element 1994 (MRSE-94) support the services of the reîrieval-port. The Message
Administration Service Element 1988 (MASE-88) and Message Administration Service Element 1994 (MASE94) support
the services of the administration-port. The MS-user ASEs act as the consumer, and the MTS ASEs act as the supplier of the
MS Abstract Service.
Repüzce the second sentence of paragraph 8 of 6.1 ("The MSSE, MDSE .'y with the following:
The MSSE, MS-MSSE, MDSE-88, MDSE-P4, MRSE-88, MRSE94, MASE-88, and MASE-94 pvide the mapping
function of the abstract-syntax notation of an abstract service onto the services provided by the ROSE.
To be published
3

---------------------- Page: 5 ----------------------
(B ISOfiEC
IsO/ïEC 10021-6:1990 / Amd.l:1994 (E)
Replace the first sentence of paragraph 11 of 6.1 ("The cornbinaiion of one or more .") with the foliowing:
The combination of one or more of the MSSE, MS-MSSE, MDSE-88, MDSE-94, MRSE-88, MRSE-94, MASE-88, and
MASE-94, together with their supporting ASES, defines the application-context of an application-asswbtion.
Replace Tabïe 1 with the following:
Table 1 MHS Access Protocol Application Contexts
Message Handling ASKS
I Application Context I I
mts-access38
mts-forced-access-88
mts-reliable-access-88
mts-forced-access-94
mts-reliable-access-94
Legend
sent with initiator the consumc~
e
Replace the fourth last paragraph 4f6.1 (".lfthe MTS Access Protocol .IV with the following:
If the 1994 version of the MTS Access Protocol (P3) is supported, then support for the mts-access-94 and mts-forced-
access-94 application-contexts is mandatory for an MTA. If the 1988 version of the MTS Access Protocol (p3) is supported,
mts-access-88 and mts-forced-access-88 application-contexts is mandatory for an MTA. If an MTA
then support for the
supports the mts-relhble-access-94 application-context, it shall also support the mts-forced-reliable-access-94 application-
context, and vice versa. If an MTA supports the mts-reliable-access-88 application-context, it shall also support the mts-
forced-reliable-access-88 application-context, and vice versa. Support for each of the MTS Access Protocol (P3)
application-contexts is optional for an MTS-user. The 1994 versions of these application-contexts were introduced to provide
revised versions of the Delivery-control and Register operations.
Replace the third last paragraph of 6.1 the MS Access Protocol .'y with the following:
If the MS Access Protocol (p7) is supported, then support for the ms-access-88 application-context is mandatory for an MS,
and support for the ms-reliable-access-88, ms-access-94, and ms-relhble-access-94 application-contexts is optionai. If an
MS supports the ms-reliirb Ae-access-94 application-context, it shall also support the ms-reliable-access-88 and ms-access-
94 application-contexts. Support for each of the MS Access Protocol (w) application-contexts is optional for an MS-user.
The ms-access-94 and ms-reliable-access-94 application-contexts were introduced in the 1994 version of this part of
ISO/IEC 10021 in order to offer a broader range of Message Store services (see 7.4 of ISOhEC 10021-1:1994). These 1994
4

---------------------- Page: 6 ----------------------
O ISO/ni;C ISOAEC 10021-61990 / Amd.l:1994 (E)
application-contexts may be used to offer both the originai (1988) range of services and the enhanced range of services,
Nevertheless, these two application-contexts are intended to stay optional in the next version of this part of ISO/IEc 1021.
NOTE - An MS which supports one of the 1994 MS Access Protocols may be required to interwork with the MTS using one of the 1988
MTS Access Rotocols. If the MS-user invokes Register ( a 1994 operation), the MS should attempt to downgrade the Register argument
to a Register-88 argument, and invoice the Register-88 operation over its association with the MTS. If this is not possible the MS returns
a register-rejected error to the MS-user.
Append the foltowing to the second last paragraph of 6.1:
This illustrates oniy one of the possible application-contexts supporting the MTS Access Protocol; in the 1988 version of the
MTS Access Protocol, the MDSE-88 replaces the MDSE-94, and the MASE-88 replaces the MASE-94.
Append the following to the last paragraph of 6.1:
This illustrates only one of the possible application-contexts supporting the MS Access Protocol; in the 1988 version of the
MS Access Protocol, the MSSE replaces the MS-MSSE, the MRSE-88 replaces the MRSE-94, and the MASE-88 replaces
the MASE-94.
In Figures I anà 2, replace "MDSE" with "MDSE-94" (twice), ttMRSEtt with WRSE-94" (twice), and WASE" with
t'MASE-94*t (four times). In Figure 2, rephce "MSSE" with "MS-MSSEtt (twice).
6.2 Services provided by the MTS access protocol
In existing clause 6.2, reptace the last seven lines (from "Message Delivery Service Element" onwards) wifh:
Message Delivery Service Element 1988 (MDSE-88)
g) Message-delivery
h) Report-delivery
i) Delivery-control-88
Message Administration Service Element 1988 {MASE-88)
j) Register48
k) Change-credentials
In the 1994 version of the MTS Access Protocol, the Message Delivery Service Element 1988 and Message Administration
Service Element 1988 are replaced by the following:
Message Delivety Service Element 1994 (MDSE-94)
1) Message-delivery
m) Reportdelivery
n) Delivery-control
Message Administration Service Element 1994 {MASE-94)
O) Register
p) Change-credentials
5

---------------------- Page: 7 ----------------------
ISO/IEC 10021-61990 / Amd.l:1994 (E)
(6 ISOAEC
6.3 Services provided by the MS access protocol
In existing clause 6.3, replace the last ten lines (from "Message Retdeval Service Element" onwards) with:
Message Retrieval Service Element 1988 (MRSE-88)
g) Summarize
h) List
i) Fetch
j) Delete
k) Register-MS
1) Alert
Message Administration Service Element I988 (MASE-88)
m) Register-88
n) Change-credentials
In the 1994 version of the MS Access Protocol, the Message Submission Service Element, the Message Retrieval Service
Element 1988 and the Message Adminisîration Service Element 1988 are replaced by the following:
MS Message Submission Service Element (MS-MSSE)
O) MS-message-submission
p) MS-probe-submission
q) MS-cancel-deferred-delivery
r) MS-submission-conml
MesSage Retrieval Sewice Element 1994 (MRSE-94)
s) Modify (in addition to the operations defined for the MRSE-88)
Message Administration Service Element 1994 (WE-94)
t) Register
U) Change-credentials
7 MTS Access Protocol Abstract Syntax Definition
Replace thejht sentence of clause 7 wiZh the following:
The abstract-syntax of the 1994 and 1988 versions of the MTS Access Protocol (P3) is defined in Figure 3.
In existing clause 7, ~pZace the knst three paregnaphs @om "Message Submksion Service Element" onwards) and
Figure 3 with the following:
Abstract Syntaxes: definitions of the abstract-syntaxes for the supporting application-service-elements and for the
three principal application-serviceeiements (each of which include ROSE):
a) Message Submission Service Element (Figure 3 Part 4)
b) Message Delivery Service Element 1994 and 1988 (Figure 3 Part 4)
c) Message Adminisiration Service Element 1994 and 1988 (Figure 3 Part 5)
6

---------------------- Page: 8 ----------------------
O rsomc ISO/IEC 10021-631990 / Amd.l:1994 (E)
MTSAccessProtocol { joint-iso-ccitt mhs-motis (6) protocols (O) modules (O) mts-access-protocol (1)
version-1994 (O) 1
DEFINITIONS IMPLICIT TAGS ::=
BEGIN
-- Prologue
IMPORTS
-- MTS Abstract Service
administration, delivery, mts-access-contract, mts-connect, mts-forced-access-contract,
submission
----
FROM MTSAbstractService (joint-iso-ccitt mhs-motis(6) mts(3) modules(0)
mts-abstract-service (1) version-1994 (O) )
-- MTS Abstract Service (1988)
administration-88, delivery-88, mts-access-contract-88, mts-forced-access-contract-88
---_
FROM MTSAbstractService88 { joint-iso-ccitt mhs-motis (6) mts (3) modules (O)
mts-abstract-service (1) version-1988 (1988) )
-- Remote Operations
APPLICATION-CONTEXT
----
FROM Remote-Operations-Information-Objects-extensions (joint-iso-ccitt
remote-operations (4) information0bject.s-extensions (8) versionl (O) }
Code
----
FROM Remote-Operations-Information-Objects (joint-iso-ccitt remote-operations(4
informationObjects (5) versionl (O) )
Bind( }, InvokeId, Unbind(
----
FROM Remote-Operations-Generic-ROS-PDUs (joint-iso-ccitt remote-operations(4)
generic-ROS-PDUs (6) versionl (O) }
ROS-SingleAS()
----
FROM Remote-Operations-Useful-Definitions {joint-iso-ccitt remote-operations(4)
useful-definitions (7) versionl (O) }
acse, association-by-RTSE, pData, transfer-by-RTSE
----
FROM Remote-Operations-Realisations {joint-iso-ccitt remote-operations(4)
realisations (9) versionl (O) )
acse-abstract-syntax
----
FROM Remote-Operations-Abstract-Syntaxes {joint-iso-ccitt remote-operations(4)
remote-operations-abstract-syntaxes (12) versionl (O) 1
-- Reliable Transfer
RTSE-apdus
----
FROM Reliable-Transfer-APDUÇ {joint-iso-ccitt reliable-transfer(3) apdus(0)
Figure 3 - Abstract-Syntax Definition of the MTS Access Protocol (P3) (Part 1 of 5)
7

---------------------- Page: 9 ----------------------
IsO/IEC 10021-61990 / Amd.l:1994 (E) (a ISO/IEC
-- Object Identifiers
id-ac-mts-access-88, id-ac-mts-access-94, id-ac-mts-forced-access-88,
id-ac-mts-forced-access-94, id-ac-mts-forced-reliable-access-88,
id-ac-mts-forced-reliable-access-94, id-ac-mts-reliable-access-88,
id-ac-mts-reliable-access-94, id-as-mase-88, id-as-mase-94, id-as-mdse-88, id-as-mdse-94,
id-as-msse, id-as-mts, id-as-mts-rtse
__--
FROM MHSProtocolObjectIdentifiers { joint-iso-ccitt mhs-motis (6) protocole (O) modules (O)
object-identifiers (O) version-1994 (O) 1;
- - APPLICATION CONTEXTS
-- 1994 Application Contexts omitting RTSE
-- MTS-user initiated
mts-access-94 APPLICATION-CONTEXT ::= {
CONTRACT mt s-access-cont ract
ESTABLISHED BY acse
INFORMATION TRANSFER BY pData
ABSTRACT SYNTAXES {acse-abstract-syntax I
message-submission-abstract-syntax I
message-delivery-abstract-syntax I
message-administration-abstract-syntax-94 I
mts-bind-unbind-abstract-syntax }
APPLICATION CONTEXT NAME id-ac-mts-access-94 1
-- MTS initiated
mts-forced-access-94 APPLICATION-CONTEXT ::= (
CONTRACT mts-forced-access-contract
ESTABLISHED BY acse
INFORMATION TRANSFER BY pData
ABSTRACT SYNTAXES {acse-abstract-syntax I
message-submission-abstract-syntax I
message-delivery-abstract-syntax I
message-administration-abstract-syntax-94 I
mta-bind-unbind-abstract-syntax 1
APPLICATION CONTEXT NAME id-ac-mts-forced-access-94 )
-- 1994 Application Contexts including RTSE in normal mode
-- MTS-user initiated
mts-reliable-access-94 APPLICATION-CONTEXT ::= {
mts-access-contract
CONTRACT
ESTABLISHED BY association-by-RTSE
INFORMATION TRANSFER BY transfer-by-RTSE
ABSTRACT SYNTAXES (acse-abstract-syntax I
message-submission-abstract-syntax I
message-delivery-abstract-syntax I
message-administration-abstract-syntax-94 I
mts-bind-unbind-rtse-abstract-syntax 1
APPLICATION CONTEXT NAME id-ac-mts-reliable-access-94 )
-- MTS initiated
mts-forced-reliable-access-94 APPLICATION-CONTEXT ::= {
mts-forced-access-contract
CONTRACT
ESTABLISHED BY association-by-RTSE
INFORMATION TRANSFER BY transfer-by-RTSE
ABSTRACT SYNTAXES (acse-abstract-syntax I
message-submission-abstract-syntax I
message-delivery-abstract-syntax I
message-administration-abstract-syntax-94 I
mts-bind-unbind-rtse-abstract-syntax 1
APPLICATION CONTEXT NAME id-ac-mts-forced-reliable-access-94 1
Figure 3 - Abstract-Syntax Definition of the MTS Access Protocol (P3) (Part 2 of 5)
8

---------------------- Page: 10 ----------------------
O rsomc
ISO/ïEC 10021-61990 / Amd.l:1994 (E)
-- 1988 Application Contexts omitting RTSE
-- MTS-user initiated
mts-access-88 APPLICATION-CONTEXT ::- {
CONTRACT
mts-access-contract-88
ESTABLISHED BY acse
INFORMATION TRANSFER BY pData
ABSTRACT SYNTAXES iacse-abstract-syntax I
message-submission-abstract-syntax I
message-delivery-abstract-syntax-88 I
message-administration-abstract-syntax-88 I
mts-bind-unbind-abstract-syntax}
APPLICATION CONTEXT NAME id-ac-mts-access-88 )
-- MTS initiated
mts-forced-access-88 APPLICATION-CONTEXT ::= {
CONTRACT mts-forced-access-contract-88
ESTABLISHED BY acse
INFORMATION TRANSFER BY pData
ABSTRACT SYNTAXES {acse-abstract-syntax I
message-submission-abstract-syntax I
message-delivery-abstract-syntax-88 I
message-administration-abstract-syntax-88 1
mts-bind-unbind-abstract-syntax}
APPLICATION CONTEXT NAME id-ac-mts-forced-access-88 1
-- 1988 Application Contexts including RTSE in normal mode
-- MTS-user initiated
mts-reliable-access-88 APPLICATION-CONTEXT ::== (
CONTRACT mts-access-contract-88
ESTABLISHED BY association-by-RTSE
INFORMATION TRANSFER BY transfer-by-RTSE
ABSTRACT SYNTAXES {acse-abstract-syntax 1
message-submission-abstract-syntax I
message-delivery-abstract-syntax-88 I
message-administration-abstract-syntax-88 I
mts-bind-unbind-rtse-abstract-syntax}
APPLICATION CONTEXT NAME id-ac-mts-reliable-access-88 )
-- MTS initiated
mts-forced-reliable-access-88 APPLICATION-CONTEXT ::= {
CONTRACT mts-forced-access-contract-88
ESTABLISHED BY association-by-RTSE
INFORMATION TRANSFER BY transfer-by-RTSE
ABSTRACT SYNTAXES (acse-abstract-syntax I
message-submission-abstract-syntax I
message-delivery-abstract-syntax-88 I
message-administration-abstract-syntax-88
mts-bind-unbind-rtse-abstract-syntax)
APPLICATION CONTEXT NAME id-ac-mts-forced-reliable-access-88 1
Figure 3 - Abstract-Syntax Definition of the MTS Access Protocol (P3) (Part 3 of 5)
9

---------------------- Page: 11 ----------------------
ISO/IEC 10021-61990 / Amd.l:1994 (E) (8 ISOfiEC
-- ABSTRACT-SYNTAXES
-- Abstract Syntax for MTS-bind and MTS-unbind
mts-bind-unbind-abstract-syntax ABSTRACT-SYNTAX ::= {MTSBindUnbindPDUs IDENTIFIED BY id-as-mts
MTSBindUnbindPDUs ::a CHOICE {
bind Bind (mts-connect.&bindl,
unbind Unbind {mts-connect.&unbind) 1
-- Abstract Syntax for MTS-bind and MTS-unbind with RTSE
mts-bind-unbind-rtse-abstract-syntax ABSTRACT-SYNTAX ::a {
RTSE-apdus -- with MTS-bind and MTS-unbind -- IDENTIFIED BY id-as-mts-rtse 1
-- Abstract Syntax for Message Submission Service Element
message-submission-abstract-syntax ABSTRACT-SYNTAX ::= (
MessageSubmissionPDUs IDENTIFIED BY id-as-mssel
MessageSubmissionPDUs ::= ROS-SingleAS ((MTSInvokeIds), submission)
MTSInvokeIds ::- InvokeId (ALL EXCEPT absent:NULL)
-- Remote operations
Code ::a local:3
op-message-submission
op-probe-submission Code :- local:4
op-cancel-deferred-delivery Code := 1ocal:’l
Code := local:2
op-submission-control
-- Remote errors
err-submission-control-violated Code
:= 1ocal:l
err-element-of-service-not-subscribed Code :- local:4
::- 1ocal:E
err-deferred-delivery-cancellation-rejected Code
err-originator-invalid Code ::= local:2
err-recipient-improperly-specified Code ::- local:3
::- local:7
err-message-submission-identifier-invalid Code
err-inconsistent-request Code ::- 1ocal:ll
err-security-error Code
::5 local:12
err-unsupported-critical-function Code
::= 1ocal:lî
err-remote-bind-error Code
::= 1ocal:lS
-- Abstract Syntax for Message Delivery Service Element 2994
message-delivery-abstract-syntax ABSTRACT-SYNTAX ::= {
MessageDeliveryPDUs IDENTIFIED BY id-as-mdse-94 )
MessageDeliveryPDUs ::* ROS-SingleAS {(MTSInvokeIds), delivery)
-- Abstract Syntax for Message Delivery Service Element 1988
message-delivery-abstract-syntax-88 ABSTRACT-SYNTAX ::= {
MessageDeliveryPDUs88 IDENTIFIED BY id-as-mdse-88 1
MessageDeliveryPDUs88 ::= ROS-SingleAS ({MTSInvokeIds), delivery-88)
Fqure 3 - Abstract-Syntax Definition of the MTS Access Protocol (P3) (Part 4 of s)
10

---------------------- Page: 12 ----------------------
Q ISO/reC
ISO/IEC 10021-61990 / Amd.1: 1994 (E)
--
Remote Opera t i ons
op-message-delivery
Code ::= iocal:5
op- report -delivery
Code ::E iocal:6
op-delivery-control
Code ::- local:2
--
Remote Errors
. .=
err-delivery-control-violated
Code . 1ocal:l
err-control-violates-registration Code ::= local:14
err-operation-refused Code ::= local:16
-- err-security-error
Code ::= local:l2 defined above --
-- err-unsupported-critical -function
Code ::= local:13 defined above --
-- Abstract Syntax for Message Administration Service Element 1994
message-administration-abstract-syntax-94 ABSTRACT-SYNTAX ::= {
MessageAdministrationPDUs IDENTIFIED BY id-as-mase-94 )
MessageAdministrationPDUs ::E ROS-SingleAS {{MTSInvokeIds), administration)
-- Abstract Syntax €or Message Administration Service Element 1988
message-administration-abstract-syntax-88 ABSTRACT-SYNTAX ::- {
MessageAdministrationPDUs88 IDENTIFIED BY id-as-mase-88 }
MessageAdministrationPDUs88 ::= ROS-SingleAS {{MTSInvokeIds), administration-88)
-- Remote Operations
op-register Code ::= 1ocal:l
op-change-credentials Code ::= local:8
-- Remote Errors
10
err-register-rejected Code ::= local
local 6
err-new-credentials-unacceptable Code ::=
err-old-credentials-incorrectly-specified Code ::= local 5
END -- of MTSAccessProtocol
F'igure 3 - Abstract-Syntax Definition of the MTS Access Protocol (P3) (Part 5 of 5)

---------------------- Page: 13 ----------------------
(8 ISO/IEC
IsO/IEC 10021-61990 / Amd.l:1994 (E)
8 MS Access Protocol Abstract Syntax Definition
Replace the ffrss sentence of clause 8 with the following:
The abstract-syntax of the 1994 and 1988 versions of the MS Access Protocol (P7) is defined in Figure 4.
Rephce the last two paragraphs (beginning rrAppUcationContexts”) and Figure 4 in clause 8 with the foilowing:
Application Contexts: definitions of application-contexts that may be used between an MS-uses and an MS (Figure
4 Part 2).
Abstract Syntaxes: definitions of the abstract-syntaxes for MS-bind and MS-unbind, for the MS Message
Submission Service Element (MS-MSSE) and the Message Retrieval Service Element 1994 and 1988 (MRSE-94
and MRSE-88) (Figure 4 Part 3). The Message Administration Service Element 1994 and 1988 (MASE94 and
MASE-88) is defined in Figure 3.
11.1
MSAccessProtocol ( joint-iso-ccitt mhs-motis (6) protocols (O) modules (O) ms-access-protocoi(2)
version-1994 (O) 1
DEFINITIONS : :-
BEGIN
-- Pro1 ogue
IMPORTS
-- MS Abstract Service
ms-access-contract-88, ms-access-contract-94, ms-submission, retrieval, retrieval-88
----
FROM MSAbstractService (joint-iso-ccitt mhs-motis(6) ms(41 modules(0)
abstract-service(1) version-1994 (0)
-- Remote Operations
APPLICATION-CONTEXT
---e
FROM Remote-Operations-Information-Objects-extensions {joint-iso-ccitt
remote-operations (4) informationObjects-extensions (6) version1 (0)
Code
----
FROM Remote-Operations-Information-Objects (joint-iso-ccitt remOte-OperbtiOnS(4)
informationObjects (5) versionl (O) 1
Bind(}, InvokeId, Onbind0
----
FROM Remote-Operations-Generic-ROÇ-PDUs {joint-iso-ccitt remote-operations(4)
generic-ROS-PDUs (6) versionl (O) )
ROS-SingleAS0
----
FROM Remote-Operations-Useful-Definitions (joint-iso-ccitt remote-operations(4)
useful-definitions(7) versionl (O)
Figure 4 - Abstract Syntax Deriniton of the MS Access Protocol (P7) (Part 1 of 4)
12

---------------------- Page: 14 ----------------------
@ ISOAEC
ISOhEC 10021-6:1990 / Amd.l:1994 (E)
acse, association-by-RTSE, pData, transfer-by-RTSE
----
FROM Remote-Operations-Realisations (joint-iso-ccitt remote-operations(4)
realisations (9) versionl (O) )
acse-abstract-syntax
----
FROM Remote-Operations-Abstract-Syntaxes {joint-iso-ccitt remote-operations(4)
remote-operations-abstract-syntaxes (12) versionl (O) )
-- Reliable Transfer
RTSE-apdus
----
FROM Reliable-Transfer-APDUS {joint-iso-ccitt reliable-transfer(3) apdus(0))
-- MTS Access Protocol
message-administration-abstract-syntax-88, meSSage-adminiStratiOn-~bStS8Ct-Synt~X-94,
message-submission-abstract-syntax
----
FROM MTSAccessProtocol { joint-iso-ccitt mhs-motis (6) protocols (O) modules (O)
mts-access-protocol(1) version-1994 (O) )
-- Object Identifiers
id-ac-ms-access-08, id-ac-ms-access-94, id-ac-ms-reliable-access-00,
id-ac-ms-reliable-access-94, id-as-ms-msse, id-as-mase-00, id-es-mase-94, id-as-mdse-00,
id-as-mdse-94, id-as-mrse-00, id-as-mrse-94, id-as-ms-00, id-as-ms-94, id-as-ms-rtse,
id-as-msse
----
FROM MHSProtocolObjectIdenti€iers (joint-iso-ccitt mhs-motis(6) protocols(0i
modules (O) object-identifiers (O) version-1994 (O) 1 I
-- APPL ICATION-C
...