ISO/IEC 14363:1996

Information technology — Test methods for measuring conformance to MHS-based electronic messaging — Application Program Interface (API) (Language independent)

Defines test methods for the language-independent MHS-based electronic messaging API contained in ISO/IEC 14361 (IEEE 1326.1-1993).

Technologies de l'information — Méthodes d'essai pour mesurer la conformité à la messagerie électronique basée sur MHS — Interface de programme d'application (API) (indépendante du langage)

General Information

• Status: Withdrawn
• Publication Date: 26-Jun-1996
• Withdrawal Date: 26-Jun-1996
• ICS: 35.100.70 - Application layer
• Technical Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Drafting Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 18-Dec-2003

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 14363
First edition
1996-06-o 1
Information technology - Test methods
for measuring conformance to MHS-based
electronic messaging - Application
Program Interface (API) [Language
independent]
Technologies de /‘information - R/l6 thodes d ‘essai pour mesurer la
conform26 2 la messagerie 6lectronique bas6e sur MHS - Interface de
programme d ‘applica tion (A PI) [indkpendan te du langage]
Reference number
ISO/I EC 14363: 1996(E)

---------------------- Page: 1 ----------------------
ISO/IEC 14363:1996(E)
Contents
PAGE
.‘ . 1
Section 1: General .
1
11 . Scope .
1
Normative References
12 .
2
13 . Conformance .
........ 3
Section 2: Terminology and General Requirements
3
21 . Conventions .
4
22 . Definitions .
.......... 7
Section 3: Test Assertions for Section General
7
31 . Scope .
7
Normative References
32 .
7
Conformance
33 . .
7
3.3.1 Implementation Conformance .
3.3.2 Application Conformance . 10
10
Test Assertions
34 . .
. .
11
Section 4: Test Assertions for Terminology and General Requirements
............ 13
Section 5: Test Assertions for Overview
13
51 . Purpose. .
13
52 . Overview
.................................
13
53 . Object Management
. Features 13
54 .
......
6: Test Assertions for Message Handling Interfaces 15
Section
15
61 . Datatypes .
15
6.1.1 Boolean List .
15
6.1.2 Feature List .
15
6.1.3 Interval .
6.1.4 Object Count 16
..............................
16
6.1.5 Sequence Numbe ’r
16
62 . Access Operations .
.............. 19
6.2.1 Cancel Submission
22
6.2.2 Close .
24
6.2.3 Finish Delivery .
28
6.2.4 Finish Retrieval .
c
SO
6.2.5 Open .
6.2.6 Size 35
....................
0 ISO/IEC 1996
All rights reserved. Unless otherwise specified, no part of this publication may be repro-
duced or utilized in any form or by any means, electronic or mechanical, including
photocopying and microfilm, without permission in writing from the publisher.
ISO/IEC Copyright Office l Case postale 56 l CH-1211 Geneve 20 l Switzerland
Printed in Switzerland
ii

---------------------- Page: 2 ----------------------
0 ISO/IEC
ISO/IEC 14363:1996(E)
6.2.7 Start Delivery . 38
6.2.8 Start Retrieval . 113
6.2.9 Submit . 189
6.2.10 Wait 227
.................................
6.3 Transfer Operations
231
6.3.1 Close 232
6.3.2 Finish Transfer In .
234
6.3.3 Open . 236
6.3.4 Size . 241
6.3.5 Start Transfer In 243
6.3.6 Transfer Out . 319
6.3.7 Wait . 350
6.4 Return Codes . 352
Section 7: Test Assertions for Interpersonal Messaging Packages . 359
7.1 Class Hierarchy .
359
7.2 Class Definitions . 359
7.3 Class Definitions . 360
...........
7.3.1 Bilaterally Defined Body Part 360
7.3.2 Body Part 361
7.3.3 Externally Denned Body Part . 361
7.3.4 G3 Fax Body Part . 362
7.3.5 G4 Class 1 Body Part . 364
7.3.6 General Text Body Part . 364
7.3.7 IA5TextBodyPart . 366
7.3.8 Interpersonal Message . 367
7.39 Interpersonal Notification . 381
7.3.10 IPM Identifier . 384
7.3.11 IPMS Extension . 386
7.3.12 Message Body Part . 386
73.13 Mixed-mode Body Part .
388
...........
7.3.14 Nationally Defined Body Part 389
.............
7.3.15 Non-receipt Notification 389
.......
7.3.16 Office Document Architecture Body Part 392
7.3.17 OR Descriptor . 394
7.3.18 Receipt Notification . 396
7.3.19 Recipient Specifier . 398
7.3.20 Teletex Body Part . 401
7.3.21 Unidentified Body Part . 403
7.3.22 Videotex Body Part . 405
7.4 Syntax Definitions . 407
7.4.1 Acknowledgement . 407
7.4.2 Auto-submitted . 407
7.4.3 Discard Reason .
408
................
7.4.4 IA5 Repertoire 410
7.4.5 Importance . 411
..............
7.4.6 Non-receipt Reason 411
7.4.7 Notification Request . 412
7.4.8 Sensitivity . 413
7.4.9 Videotex Syntax . 414
. . .
111

---------------------- Page: 3 ----------------------
@ ISO/IEC
ISO/IEC 14363:1996(E)
. . . 417
Section 8: Test Assertions for Section Message Handling Packages
417
8.1 Class Hierarchy . . . . . . . . . . . . . . . . . .
418
8.2 Class Definitions . . . . . . . . . . . . . . . . . .
418
8.2.1 Algorithm . . . . . . . . . . . . . . . . .
419
.............
8.2.2 Algorithm and Result
.............. 419
8.2.3 Asymmetric Token
............. 421
8.2.4 Bilateral Information
................ 423
8.2.5 Communique
432
8.2.6 Content .
........................ 432
Delivered Message
8.2.7
432
Delivered Per-recipient Dk
8.2.8
434
Delivered Per-recipient NDR .
8.2.9
.......... 436
Delivered Per-recipient Report
8.2.10
439
Delivered Report .
8.2.11
440
.............
8.2.12 Delivery Confirmation
441
...............
8.2.13 Delivery Envelope
452
...............
8.2.14 Delivery Report
............... 459
8.2.15 EITs
............... 460
8.2.16 Expansion ‘Record
............... 461
8.2.17 Extensible Object
............. 463
Extension
8.2.18
465
External Trace Entry .
8.2.19
469
8.2.20 G3 Fax NBPs .
471
General Content .
8.2.21
.............. 471
Internal Trace Entry
8.2.22
........... 477
Local Delivery Confirmation
8.2.23
........... 477
Local Delivery Confirmations
8.2.24
478
Local NDR .
8.2.25
478
Local Per-recipient NDR .
8.2.26
480
Message .
8.2.27
484
.................
8.2.28 Message RD
............... 487
8.2.29 MT Public Data
................ 489
8.2.30 MTS Identifier
................. 491
8.2.31 OR Address
.................. 494
8.2.32 OR Name
............... 496
8.2.33 Per-recipient DR
.............. 498
8.2.34 Per-recipient NDR
.............. 500
Per-recipient Report
8.2.35
502
Probe .
8.2.36
504
Probe RD .
8.2.37
0 . 0 . 0 . . 0 . . 507
. 0 .
8.2.38 RD
................ 507
8.2.39 Redirection Record
................... 509
8.2.40 Report
................ 512
8.2.41 Security Label
514
8.2.42 Session .
.............. 516
8.2.43 Submission Results
............ 518
8.2.44 Submitted Communique
521
..............
8.2.45 Submitted Message
526
.............
8.2.46 Submitted Message RD
529
...............
8.2.47 Submitted Probe
iv

---------------------- Page: 4 ----------------------
0 ISO/IEC ISO/IEC 14363:1996(E)
..............
8.2.48 Submitted Probe RD 531
8.2.49 Teletex NBPs . 534
8.2.50 Token . 536
8.2.51 Token Public Data . 536
8.3 Syntax Definitions . 536
8.3.1 Action . 536
8.3.2 Builtin EIT . 537
8.3.3 Delivery Mode . 538
8.3.4 Delivery Point . 539
8.3.5 Diagnostic . 541
8.3.6 .Explicit Conversion . 549
8.3.7 Postal Mode . 550
8.3.8 Postal Report . 551
.................. 552
8.3.9 Priority
8.3.10 Reason 552
.............................
8.3.11 Redirection Reason 554
................. 555
8.3.12 Registration
8.3.13 Report Request . 556
8.3.14 Security Classification . 557
8.3.15 Terminal Type . 557
Section 9: Test Assertions for Section Secure Messaging Package . 559
9.1 Class Hierarchy . 560
.................. 560
9.2 Class Definitions
............. 561
9.2.1 Integrity Check Basis
.............. 561
9.2.2 Origin Check Basis
............ 563
9.2.3 Per-recipient Check Basis
......... 563
9.2.4 Per-recipient Delivery Check Basis
....... 565
9.2.5 Per-recipient Non-delivery Check Basis
............. 565
9.2.6 Proof of Delivery Basis
............ 566
9.2.7 Proof of Submission Basis
............... 567
9.2.8 MT Secret Data
.............. 568
9.2.9 Token Secret Data
................. 569
9.3 Syntax Definitions
571
.....
Section 10: Test Assertions for Section Definition of Constants
....... 571
10.1 Object Identifier for This International Standard
............ 571
10.2 OIDs for Features and Packages
.......... 573
10.3 Interpersonal Messaging Package OIDs
........ 575
10.4 Message Handling Package Value Definitions
........ 578
10.5 Secure Messaging Package Value Definitions
Annex A (informative) Test Assertions for Annex Functional Architecture of
579
API. .
............... 579
A.1 Message Access Interface
.............. 581
A.2 Message Transfer Interface
583
Annex B (informative) Bibliography . . . . . . . . . . . . .
585
Alphabetic Topical Index . . . . . . . . . . . . . . . . . .
V

---------------------- Page: 5 ----------------------
0 ISO/IEC
ISO/IEC 14363:1996(E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the
International Electrotechnical Commission) form the specialized sys-
tem for worldwide standardization. National bodies that are members
of IS0 or IEC participate in the development of International Stan-
dards through technical committees established by the respective or-
ganization 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 Stan-
dards 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.
International Standard ISO/IEC 14363 was prepared by IEEE (as
IEEE Std 1326.1-1993) and was adopted, under a special “fast-track
procedure ”, by Joint Technical Committee ISO/IEC JTC 1, Information
technology, in parallel with its approval by national bodies of IS0 and
IEC.
Annexes A and B of this International Standard are for information
only.

---------------------- Page: 6 ----------------------
0 ISO/IEC
ISO/IEC 14363:1996(E)
1 Introduction
(This introduction is not a normative part of ISO/IEC 14363, Information technology-Test methods
2
for measuring conformance to MHS-based electronic messaging-Application Program Interface
3
(API) [Language independent], but is included for information only.)
4
5 The purpose of this International Standard is to define test methods for the
6 language-independent MHS-based electronic messaging API contained in ISO/IEC
14361 (3).
8 Related Standards
ISO/IEC 14361 (3) is intended to provide the basis for the definition of program-
9
10 ming language bindings to which implementations and applications can conform. A
11 specification for such a language binding, for the C programming language, is con-
12 tained in ISO/IEC 14365 (B2). This International Standard applies to test
methods for measuring conformance to any such programming language binding
13
14 specification.
15 The API defined in ISO/IEC 14361 (3) uses the mechanism for OS1 abstract data
16 manipulation (OM) defined in ISO/IEC 14360 (2). ISO/IEC 14362 (4) defines the
17 requirements that shall apply to test methods for measuring conformance to
18 ISO/IEC 14360 {2}. A set of test methods used to measure conformance to ISO/IEC
19 14361 (3) shall satisfy the requirements of ISO/IEC 14362 {4}, as well as conform-
20 ing to this International Standard.
IEEE Std 1003.3-1991 (5) defines the general requirements that shall apply to test
21
22 methods for measuring conformance to POSIX. A set of test methods used to meas-
23 ure conformance to ISO/IEC 14361 (3) shall satify the requirements of IEEE Std
1003.3-1991 {5}, as well as conforming to this International Standard.
25 Overview
26 For each section of ISO/IEC 14361 {3}, this International Standard contains a
27 corresponding section containing test assertions, in accordance with IEEE Std
28 1003.3-1991 (5). A set of test methods conforms to this International Standard if it
29 tests all of the test assertions.
vii

---------------------- Page: 7 ----------------------
ISO/IEC 14363:1996(E) 0 ISO/IEC
Related Standards Activities
The following areas are under active consideration at this time, or are expected to
31
32 become active in the near future, concerning extensions to this International Stan-
33 dard and similar efforts can be anticipated in the future?
(1) Directory services
35 (2) FTAMAPI
(3) Verification testing methods
36
37 (4) Network interface facilities
38 (5) System administration.
39 This International Standard is based on IEEE Std 1326.1-1993 {B4}, which was
40 prepared by the P1224 Working Group, sponsored by the Portable Applications
41 Standards Committee of the IEEE Computer Society.
1) A Standards Status Report that lists all current IEEE Computer Society standards projects is
42
available from the IEEE Computer Society, 1730 Massachusetts Avenue NW, Washington, DC
43
20036-1903; Telephone: [phone]; FAX: [phone].
44
. . .
Vlll Introduction

---------------------- Page: 8 ----------------------
INTERNATIONAL STANDARD OISO/IEC
ISOIIEC 14363:1996(E)
Information technology-Test methods for
1
2 measuring conformance to MHS-based
3 electronic messaging-Application Program
4 Interface (API) [Language independent]
5 Section 1: General
6 1.1 Scope
This International Standard defines requirements for test methods for measuring
7
8 conformance to ISO/IEC 1436113).
9 ISO/IEC 14361 (3) is stated in terms that are independent of any particular pro-
10 gramming language, but each implementation that conforms to it implements a
11 particular programming language binding, and conforms to its programming
12 language binding specification. Each set of test methods for measuring confor-
13 mance to ISO/IEC 14361 (3) assumes a particular programming language binding
14 specification. Each programming language binding specification may impose
15 further programming language specific requirements on the test methods which, in
conjunction with the requirements imposed by this International Standard, consti-
16
17 tute the requirements that shall be satisfied by test methods used for measuring
18 conformance to that programming language binding specification. This Interna-
19 tional Standard applies to all sets of test methods for measuring conformance to
20 any programming language binding specification for ISO/IEC 14361 (3).
21 1.2 Normative References
The following standards contain provisions which, through reference in this text,
22
constitute provisions of this International Standard. At the time of publication,
23
the editions indicated were valid. All standards are subject to revision, and parties
24
25 to agreements based on this International Standard are encouraged to investigate
the possibility of applying the most recent editions of the standards indicated
26
1.2 Normative References 1

---------------------- Page: 9 ----------------------
ISO/IEC 14363:1996(E)
OISO/IEC
below. Members of IEC and IS0 maintain registers of currently valid Interna-
27 tional Standards.
IS0 3166: 1993,l’ Codes for the Representation of Names of Countries.
28
(1)
29 ISOIIEC 14360: 1996, Information technology-Open Systems Interconnec-
12)
30 tion (OSI) abstract data manipulation -Application Program Interface (API)
31 [Language independent].
32 ISO/IEC 14361: 1996, Information technology-MHS-based electronic
33 messaging-Application Program Interface (API) [Language independent].
ISOIIEC 14362: 1996, Information technology-Test methods for measuring
34
35 conformance to Open Systems Interconnection (OSI) abstract data
36 manipulation -Application Program Interface (API) [Language indepen-
37 dent].
IEEE Std 1003.3-1991,2) IEEE Standard for Information Technology-Test
38
Methods for Measuring Conformance to POSIX.
39
40 CCITT Recommendation X. 121: 1984,3) International Numbering Plan for
41 Public Data Networks. CCITT Red Book, Fascicle VIII.4.
42 1.3 Conformance
43 A set of test methods that conforms to this International Standard shall conform to
44 IEEE Std 1003.3-1991 {5}, with references to the “P0SIX.n test method
45 specification” being interpreted as references to this International Standard, and
46 references to “the POSIX standard for which conformance is being measured” being
47 interpreted as references to ISO/IEC 14361 (3).
In addition to meeting the conformance criteria defined in IEEE Std 1003.3-1991
48
49 {5}, a set of test methods that conforms to this International Standard shall test all
50 documentation assertions defined in this International Standard.
51 NOTE: Conformance to IEEE Std 1003.3 (5) implies that the test methods will test all other asser-
52 tions defined in this International Standard.
53 1) ISO/IEC documents can be obtained from the IS0 Central Secretariat, 1 Rue de Varembe, Case
54 Postale 56, CH-12 11, Geneve 20, SwitzerlantiSuisse.
55 2) IEEE documents can be obtained from the IEEE Service Center, 445 Hoes Lane, P.O. Box 1331,
56 Piscataway, NJ, 08855-1331, USA. Telephone: 1(800)67%IEEE or [phone] (outside
57 US).
58 3) CCITT documents can be obtained from the Telecommunication Standardization Bureau of the
59
International Telecommunication Union, Sales Section, Place des Nations, CH- 12 11, Geneve 20,
60 SwitzerlandKuisse.
2
1 General

---------------------- Page: 10 ----------------------
0 ISO/IEC
ISO/IlX 14363:1996(E)
1 Section 2: Terminology and General Requirements
2 2.1 Conventions
3 2.1.1 General and Typographical Conventions
Language-independent concrete OM class names, OM attribute names, and OM-
attribute value names are spelled with hyphens between words (e.g.,
conversion-loss-prohibited). The first letters of language-independent OM class
and OM attribute names are capitalized (e.g., Redirection-Record).
8 Language-independent datatype, operation, argument and error names are
9 lowercase and are spelled with underscores between words (e.g., ma-start-delivery).
10 The use of fonts in this International Standard is as follows:
11 - The Helvetica font is used for:
12 - Language-independent operation names, such as ma-start_delivery
13 - Language-independent datatype names, such as m h-interval-type
- Language-independent error names, such as feature unavailable
14
-
15 - The itaZic font is used for:
16 - Language-independent operation arguments, such as user address
-
17 The introduction of important terms
18 - Cross-references in 2.2
19 - The bold font is used for:
- Language-independent concrete OM class names, such as Delivered-
20
21 Report
22 - Language-independent OM attribute names, such as Algorithm-Datum
23 - Language-independent OM attribute values, such as conversion-loss-
24 prohibited
25 - The bold itaZic font is used for:
- Language-independent abstract OM class names, such as DeZiuery-
27 Report
2.1 Conventions

---------------------- Page: 11 ----------------------
ISO/IEC 14363:1996(E)
OISOLIEC
- The constant width (Courier) font is used for:
28 - References to terms defined in international standards upon which this
29 International Standard is based.
30 2.2 Definitions
31 2.2.1 Terminology
32 For the purposes of this International Standard, the following definitions apply:
2.2.1.1 conformance document: A document provided by an implementor that
33
34 contains implementation details. [ISOIEC 9945-l {Bl}]
35 2.2.1.2 may: An indication of an optional feature. [ISO/IEC 9945-l {Bl}]
With respect to implementations, the word may is to be interpreted as an optional
36
37 feature that is not required in this International Standard, but that can be pro-
38 vided. With respect to Strictly Conforming Applications, the word may means that
39 the optional feature shall not be used.
40 2.2.1.3 shall: An indication of a requirement on the implementation or on Strictly
41 Conforming Applications, where appropriate. [ISO/IEC 9945-l (Bl)]
42 2.2.1.4 should:
an indication of an implementation
43 (1) With respect to implementations,
44 recommendation, but not a requirement.
(2) With respect to applications, an indication of a recommended program-
45
46 ming practice for applications and a requirement for Strictly Conforming
47 Applications. [ISO/IEC 9945-l {Bl}]
48 2.2.1.5 supported: A condition regarding optional functionality.
49 Certain functionality in this International Standard is optional, but the interfaces
50 to that functionality are always required. If the functionality is supported, the
interfaces work as specified by this International Standard (except that they do not
51
return the error condition indicated for the unsupported case). If the functionality
52
is not supported, the interface shall always return the indication specified for this
53
54 situation. [ISO/IEC 9945-l {Bl}]
provided with an implemen-
55 2.2.1.6 system documentation: All documentation
56 tation, except the conformance document.
Electronically distributed documents for an implementation are considered part of
57
the system documentation. [ISO/IEC 9945-l {Bl}]
58
2 Terminology and General Requirements

---------------------- Page: 12 ----------------------
OISO/IEC
ISO/IEC 14363:1996(E)
2.2.2 General Terms
For the purposes of this International Standard, the following definitions apply:
59
60 2.2.2.1 assertion: A statement that is derived from the standard to which confor-
61 mance is being measured, that is true for a conforming implementation, and that
62 pertains either to functionality or behavior of a functional interface or namespace
63 allocation or to the documentation associated with the implementation being tested
64 [ISO/IEC 14360 (2}].
65 2.2.2.2 generic interface: A version of an interface that is independent, of any
particular programming language.
66
67 2.2.2.3 programming language binding specification: For a language-
68 independent specification, a document that specifies, in terms of a particular pro-
69 gramming language, the behavior that the language-independent specification
70 specifies in language-independent terms.
It may also specify additional behavior that is relevant to the usage of the particu-
71
72 lar programming language [ISO/IEC 14360 {2}].
73 2.2.2.4 test methods: The software, procedures, or other means specified to
74 measure conformance to a specification [ISO/IEC 14360 (211.
2.2.3 Abbreviations
75
For the purposes of this International Standard, the following abbreviations apply:
76
2.2.3.1 OM: Object Management.
77
2.2 Definitions

---------------------- Page: 13 ----------------------
This page intentionally left blank

---------------------- Page: 14 ----------------------
ISOLIEC 14363:1996(E)
0 ISO/IEC
1 Section 3: Test Assertions for Section General
2 3.1 Scope
3 There are no test assertions for this clause.
4 3.2 Normative References
There are no test assertions for this clause.
5
3.3 Conformance
6
7 3.3.1 Implementation Conformance
8 3.3.1.1 Conformance Requirements
The manufacturer shall identify the interface (MA, MT, or both) that
9 DO1
the product implements, and state what roles (client, service, or both)
10
it plays for each.
11
12 001(A) The product shall implement the OM interface as defined in ISO/IEC
14360 {2}, satisfying its conformance requirements, and play the same
13
roles for that interface as it plays for the MA and MT interfaces.
14
If the product plays the role of service for the MA or MT interface:
15 DO2
The manufacturer shall state which features the product imple-
16
17 ments.
If the product plays the role of service for the MA interface:
18 002(C)
The product shall implement the Basic Access FU.
19
20 003(C) If the product plays the role of service for the MA interface:
21 The product shall implement the Submission FU, the Delivery
22 FU, the Retrieval FU, or any combination of the three.
If the product plays the role of service for the MT interface:
23 004(C)
24 The product shall implement the Basic Transfer FU.
3.3 Conformance

---------------------- Page: 15 ----------------------
ISOLIEC 14363:1996(E)
OISO/IEC
005(C) If the product plays the role of service for the MT interface:
25 The product shall implement the Transfer In FU, the Transfer
26 Out FU, or both.
27 006(C) If the product plays the role of service for the MA or MT interface:
28 The product shall implement the MH 88 Package, the MH 84
29 Package, or both.
30 GAO1 For FU of Basic Access FU, Submission FU, Delivery FU, Retrieval
31 FU, Basic Transfer FU, Transfer In FU, Transfer Out FU:
32 If the product plays the role of service for FU:
33 The product shall implement every aspect of every func-
34 tion in FU.
For package of IM 88 Package, MH 88 Package:
35 DO3
36 If the product implements package:
37 The product documentation shall state which (if any) of
38 the 1988 classes ofpackage the product implements.
For package of IM 88 Package, IM 84 Package:
39 DO4
If the product implements package:
40
41 The product documentation shall state which (if any)
42 immediate subclasses of the Body-Part class the pro-
43 duct implements.
For package of IM 84 Package, SM 88 Package:
44 GAO2
If the product implements package:
45
The product shall implement every class the package
46
47 contains.
48 007(C) If the product implements the MH 84 package:
49 The product shall implement all of those classes that are used
50 by the functional units that it supports.
51 008(A) The product shall implement the closures of all classes it implements.
The product documentation shall state what classes it provides the
52 DO5
om encode function for.
53
-
54 DO6 If the product plays the role of service for the MA interface:
55 The manufacturer shall state whether or not the product real-
izes the interface by means of X.400 ’s Message Submission and
56
Delivery Protocol (P3) or Message Retrieval Protocol (P7).
57
58 DO7 If the product plays the role of service for the MT interface:
59 The manufacturer shall state whether or not it realizes the
interface by means of X.400 ’s Message Transfer Protocol (PI).
60
61 DO8 If the product plays the role of service for the MA interface or the MT
62 interface and implements the IM 88 Package or the IM 84 Package:
63 The manufacturer shall state whether or not the product real-
64 izes the interface by means of X.400 ’s InterpersonaL Messaging
65 Protocol (P2).
For protocoZ of Pl (1988), P3 (1988), P7 (1988):
66 GAO3
67 If the product implements protocol:
The manufacturer and product shall satisfy the
8 3 Test Assertions for Section General

---------------------- Page: 16 ----------------------
OISO/IEC
ISO/IEX 14363:1996(E)
conformance requirements of X.400 (1988) with respect
68 to protocol.
69 009(D) If the product implements Pl(l988):
70 The manufacturer and product shall satisfy the conformance
requirements of X.400 (1988) with respect to Pl (1988). (See
71
GAO3 in 3.3.1.1.)
72
73 010(D) If the product implements P3 (1988):
74 The manufacturer and product shall satisfy the conformance
75 requirements of X.400 (1988) with respect to P3 (1988). (See
76 GAO3 in 3.3.1.1.)
product implements P7 (1988):
77 011(D) If the
The manufacturer and product shall satisfy the conformance
78
79 requirements of X.400 (1988) with respect to P7 (1988). (See
80 GAO3 in 3.3.1.1.)
product plays the role of service for the MA or MT interface:
81 DO9 If the
The manufacturer shall state the behavior of implementation-
82
83 defined options.
84 3.3.1.2 Conformance Documentation
85 There are no test assertions for this subclause.
86 3.3.1.3 Conforming Implementation Options
87 DlO The circumstances that define abnormal termination of a session shall
88 be documented.
Dll For funct of ma-open, mt-open :
89
The features of a session that funct supplies as defaults shall be
90
documented.
91
92 D12 Documentation shall state whether the service shall accept any cir-
93 cumstances as causes of temporary delivery failure.
94 D13 The maximum number of users that may be assigned to a single
95 delivery queue shall be documented.
D14 The maximum number of sessions that may exist simultaneously
96
97 shall be documented.
D15 The documentation shall state which qualifying object in the delivery
98
queue (if there are several such objects) ma start delivery selects for
99
- -
delivery.
100
101 D16 The documentation shall state which qualifying object in the input
102 queue (if there are several such objects) ma start transfer in selects
- - -
for transfer in.
103
3.3 Conformance 9

---------------------- Page: 17 ----------------------
ISO/IEC 14363:1996(E) OISO/IEC
For funct of ma wait, mt wait:
104 D17
- -
The documenta
...