ISO/IEC 14392:1996

Information technology — Directory services — Application Program Interface (API) (Language independent)

The purpose is to define an application program interface (API) to directory services, including, but not limited to, the services described in ISO/IEC 9594 and the CCITT X.500 Series recommendations in terms that are independent of any particular programming language. Identical to IEEE 1224.2-1993.

Technologies de l'information — Services de l'annuaire — Interface de programme d'application (API) (indépendante du langage)

General Information

• Status: Withdrawn
• Publication Date: 29-May-1996
• Withdrawal Date: 29-May-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 14392
First edition
1996-06-o 1
Information technology - Directory
services - Application Program Interface
(API) [Language independent]
Technologies de /‘information - Services de I’annuaire - Interface de
programme d ‘application (A PI) [independan te du langage]
Reference number
SO/I EC 14392: 1996(E)

---------------------- Page: 1 ----------------------
ISWIEC 14392:1996(E)
Contents
PAGE
0 . . . . 0 0 . 1
............
Section 1: General
. 0 . . 0 0 0 0 1
1.1 Scope
0 0 . . . 0 0 . 3
................
1.2 Normative References
0 0 . . 0 * . . 4
...........
1.3 Conformance
0 . . . 0 . 0 . 7
...........
1.4 Test Methods
0 0 . . 0 . . . 9
Section 2: Terminology and General Requirements .
0 0 . 0 0 0 . . 9
...........
2.1 Conventions
. 0 0 0 . . 11
............ 0 0
2.2 Definitions
. . . . 0 23
.......... 0 . .
Section 3: Description
23
. 8 0 . . . . .
3.1 General .
. . 24
...... . . . . 0 0
3.2 Initialization and Shutdown
0 . 0 25
. 0 . 0 .
3.3 Session .
26
. . 0 0 . . 8 .
3.4 Context .
26
8 0 . 0 0 0 0 .
3.5 Operation Parameters .
29
. . 0 . . . . 0
3.6 Operation Results .
30
0 . . . 0
3.7 Synchronous and Asynchronous Directory Operations
. 0 . . 0 0 0 32
3.8 Automatic Connection Management l o . .
. . 0 . . . . 32
3.9 Automatic Continuation and Referral Handling
0 . 0 . 35
0 . 0
Section 4: Interface Operations l l l l . . l o
0 . 35
. 0 . 0 .
4.1 Datatype Definitions l l . . l . l . .
. 36
0 0 0 . . 0
4.2 Abandon . l l o l . l l . l l . .
37
0 0 0 0 0 . .
4.3 AddEntry o o l . l . l o o l l . .
39
. 0 . . 8 0 0
4.4 Bind. o . . . . o . . . . . l o o
. . 0 . . . . 40
4.5 Compare l . l . . . l . . . l . o
. 0 . . . . . 42
4.6 Initialize . . . l l . l . l . . l .
43
. 0 . 0 . . 0
4.7 List o l . o o o o . . . o l . . l
. . 0 . . . 0 44
4.8 Modify Entry l l l o o . l l l l l l
. 0 0 0 0 . . 46
4.9 Modify RDN o . l o l . . . l . l .
0 0 0 0 0 . 48
.
4.10 Read l e l l . l . . o l l l . . l
0 0 50
0 . . . 0
4.11 Receive Result . . l l l l l l l l .
52
0 0 0 . . 0 .
4.12 RemoveEntry l l l l l l . l l . .
0 ISOLIEC 1996
All rights reserved. Unless otherwise specified, no part of this publication may be repro-
electronic or mechanical, including
duced or utilized in any form or by any means,
photocopying and microfilm, without permission in writing from the publisher.
0 Case postale 56 l CH-1211 Geneve 20 l Switzerland
ISO/IEC Copyright Office
Printed in Switzerland
ii

---------------------- Page: 2 ----------------------
ISO/IEC 14392:1996(E)
OISO/IEC
l l 53
l l l l l l l l l
4.13 Search . l . . . . . e
l 55
l l l l l
4.14 Shutdown . . . . . . I .
l l 56
l l l l
4.15 Unbind . l . . . . . .
l l 57
e l l l
4.16 Version . . . . . l . .
l l l l l l l l 59
Section 5: Interface Class Definitions
l l l l l l l l l 59
51 . Overview . l l . o
l l l l l l l 59
52 . Class Hierarchy . . .
l l 0 l l l l 60
53 . Access Point ‘. . . .
l l l l l l l l 61
54 . Address . . l . l l
l l l l l l l l l l l l l l 61
55 . Attribute l l l l
l l l l l l l l l l l l l l 62
56 . Attribute List l l l l
l l l l l l 0 l l l l l l l 63
57 . AVA l l l e l l l
l l l l l e l l l l l l l 63
. Common Results l l l l l
58
l l l l l l l l l 64
Compare Result l l l l l l
59
l l l l l l 65
Context l l l l l l l l l l l l
5'10
l l l l l l l 69
Continuation Reference l l l l l
5'11
l l l l l l l l 71
l l l l l l
5'12 DSDN l l l l l l
l l l l l l l l 71
l l l l l l l l
5'13 DS RDN
l l l 72
l l
5'14 Entry Information’ l l
l l l 73
l
5'15 Entry Information Selection
l l l 74
Entry Modification l l l l
5'16
l 75
l l l l
5'17 Entry Modification List
l l l 76
l
5'18 Extension l l l l l l
l l l 77
l l l l l l l
5'19 Filter
l l 78
l l l
5'20 Filter Item l l l l l l
l l l 80
l l l l l l
5'21 List Info l
l 81
l l
5'22 List Info Item l l l l l
l l 82
l l l l l l l
5'23 List Result l l l l l l
l l l 82
l l l l l l l l
5'24 Name
l l l 83
l l l l l l
5'25 Operation Progress l
l l l 84
l l l l l l
5'26 Partial Outcome Qualifier l
86
l l l l l l l l l l l
5'27 Presentation Address l l
l l l l l l l l l l l l l l l 86
5'28 Read Result
l l l l l l l l l l 87
5'29 Relative Name l l . l l
l l l l l l l 88
5'30 Search Info l l l l l
l l l l l l 88
5'31 Search Result l l l l l l
l l l l l l 89
Session l l l l l l l l
5'32 .
l l l 93
l l l l l l l l
Section 6: Error Class Definitions
l l l 93
l l l l 0 l l l l l
6.1 Introduction l l l l l
l l l l 94
l l l l l l l l l
6.2 OM Class Hierarchy l l
l l l l 94
l l l l l l l l l l
6.3 Error l l l
l l 96
l l l l l l
6.4 Abandon Failed l l e l
l l 97
l l l l l
6.5 Attribute Error l l l
l l l l 98
l l l
6.6 Attribute Problem’
l l l l 99
l l l 0 l
6.7 Communications Error l l
l l l l l 99
l l l l
6.8 Library Error l l l l l
l l l l 101
l e l l l
l
6.9 NameError l l l l l
l l l 102
l l l l l l l l l l
6.10 Referral l l l l e l l
l l l l l l l l l e l l l 102
l
6.11 Security Error l l l l
. . .
111

---------------------- Page: 3 ----------------------
OISO/IEC
ISO/IEC 14392:1996(E)
0 0 0 0 103
0 0 0 l . 0
0 0 0
6.12 ServiceError l l l l l l
0 0 l 0 105
0 . 0 0 0 0
0 0 0
6.13 SystemError l l o l l l
l l 0 0 105
0 0 0 0 0 l
l l 0
6.14 Update Error l l l . l l
0 . l 0 l 107
0 0 0 l e l l 0
Section 7: The X.500 Directory Service
0 l l l 0 l 107
l 0 l l l l l
7.1 Introduction l l l l . l
0 l 0 l 0 108
l l 0 l 0 l 0 l
7.2 Package Object Identifiers l
l l l 108
l l l 0 0 l 0 l l 0
7.3 Selected Attribute Types l l
l l 0 0 113
l 0 l 0 0 0 l l l
7.4 Selected Object Classes l l
0 115
l 0 l l l l l l l l 0 0
7.5 OM Class Hierarchy l l l
0 118
0 0 . 0 0 0 0 l 0 l 0 l
7.6 Algorithm Identifier l l l
0 l 0 l 0 119
0 l 0 e 0 0 0 0
7.7 Certificate l l l l l l l
l 0 l 0 120
0 0 0 . 0 l 0 . 0
7.8 Certificate List l l l l l
. 0 0 l 0 121
0 0 0 0 0 0 l l
7.9 Certificate Pair l l l l l
0 0 0 0 121
0 0 l l 0 l l 0 .
7.10 Certificate Sublist l l l l
0 0 122
0 0 0 0 0 0 l l 0 . 0 0
e l l
7.11 Certificates
123
0 0 0 0 0 l l 0 0 0 0 0 0
l l l
7.12 Cross-Certificates ’
0 0 123
0 0 0 0 . l 0 0 0 l 0
7.13 DL Submit Permission l
124
0 0 l 0 0 0 0 0 . 0
0 l l
7.14 Facsimile Telephone Number l
125
0 0 0 l 0 l 0 0 0 0
l l l
7.15 Forward-Certification-Path l
126
l l l 0 0 0 0 0 0 0
l l l
7.16 Postal Address l l l l l
126
l 0 0 l l . e 0 0
0 0 0 0
7.17 SearchCriterion l l l l l
127
0 0 l 0 l 0 0 0 0 0 0 0 0
7.18 SearchGuide l l l o l l
0 0 0 128
0 0 l 0 l 0 0 0 0 0
7.19 Signature l l l l . l l
0 129
0 0 l 0 0 0 0 l 0 0
l l 0
7.20 Teletex Terminal Identifier
0 130
0 l l 0 0 0 0 0 .
0 0 l
7.21 TelexNumber l l l l l
0 0 0 0 0 0 . 0 0 131
. 0 0 0
Section 8: Definitions of Constants
0 . 0 0 0 0 0 0 0 131
0 8 0
8.1 Introduction l l l l l l
131
l . 0 0 0 0 0 0 0
0 0 0
8.2 Directory Service Package l
131
0 0 0 . 0 0 0 0 l
0
Basic Directory Contents Package l
8.3
0 0 0 0 0 0 l 131
l l
8.4 Strong Authentication Package l l
0 0 0 0 0 0 0 132
0 0
8.5 MHS Directory User Package l l
l 0 0 0 0 0 l 137
l l
Annex A (informative) Concepts and Models l
l l l 0 0 0 137
l 0
A.1 Overview l e l l l l l l l l
0 l 0 0 137
0 l 0
A.2 Directory Model l l l l l l l l
0 0 139
0 l l
A.3 OM Concepts l l l o l l l . .
143
0 0 0 0 l
A.4 Security l . l l l l . . . . .
145
l 0 0 0
Annex B (informative) Bibliography l o l
. l l 0 149
Alphabetic Topical Index l l l l l l l l l
FIGURES
138
Example Directory Distinguished Name l l l l l l
Figure A-l -
139
Overview of Directory Components l l l l l o l l
Figure A-2 -
iv

---------------------- Page: 4 ----------------------
ISO/IEC 14392:1996(E)
OISO/IEC
TABLES
Table 3-1 - Interface Operations Summary l l l . l l l l l l
24
Table 5-l 0 OM Attributes ofAccess-Point l l l l l l l l . l
61
Table 5-2 - OM Attributes of Attribute l l l l l
l l l l l 62
l l l l l l l l l
Table 5-3 - OMAttibutes of Attribute-list 63
Table 5-4 0 OMAttributes of Common-Results l l l . l l l . l 64
Table 5-5 - OMAttributes of Compare-Result l . . l l l l l l 64
Table 5-6 - OMAttributes of Context l l l l l l l l l l l l 66
- OM Attributes of Continuation-Reference . l l l l l 69
Table 5-7
Table 5-8 - OMAttributes of DS-DN l l l l l l l ; l l l l 71
- OMAttributes ofDS-RDN l l l l l l l l l l l l
Table 5-9 72
Table 5-10 - OM Attributes of Entry-Information l l l l l l l l 72
Table 5-l 1 - OM Attributes of Entry-Information-Selection l l l l l 73
Table 5-12 - OM Attributes of Entry-Modification l l l l l l l l 74
Table 5-13 - OM Attributes of Entry-Modification-List l l l l l l 75
OMAttributes of Extension l l l l l l l l l l l 76
Table 5-14 -
OM Attributes of Filter l l l l l l l l l l l l l 77
Table 5-15 -
78
Table 5-16 - OM Attributes of Filter-Item l l l l l l l l l l l
Table 5-17 - OM Attributes of List-Info l l l l l l l l l l l l 80
Table 5-18 - OM Attributes of List-Info-Item l l l l l l l l l l 81
Table 5-19 - OM Attributes of List-Result l l l l l l l l l l l 82
Table 5-20 - OM Attributes of Operation-Progress l e l l l l l l 84
- OM Attributes of Partial-Outcome-Qualifier l l l l l l 85
Table 5-2 1
- OM Attributes of Presentation-Address l l l l l l l 86
Table 5-22
87
Table 5-23 - OMAttributes of Read-Result l l l l l l l l l l
Table 5-24 - OMAttributes of Search-Info l l l l l l l l l l l 88
- OM Attributes of Search-Result l l l l l l l l l l 89
Table 5-25
OMAttributes of Session l l l l l l l l l l l l 90
Table 5-26 -
95
Table 6-1 - OMAttributes ofError l l l l l l l l l l l l l
Table 6-2 - OM Attributes ofAttribute-Error l l l l l l l l l 97
Table 6-3 - OMAttributes ofAttribute-Problem l l l l l l l l 98
Table 6-4 - OM Attributes of Name-Error l l l l l 101
Table 7-l - Object Identifiers for Selected Attribute ’Types l l 114
115
Table 7-l - Object Identifiers for Selected Attribute Types (con&kcE; l
l l 116
Table 7-2 - Representation of Values for Selected Attribute Types
Table 7-2 - Representation of Values for Selected Attribute Types
117
(concluded) l l l l l l l l l l l l l l l l l l l l l
- Object Identifiers for Selected Object Classes l l l l l 117
Table 7-3
- OMAttributes ofAlgorithm-Identifier . l l l l l l l 118
Table 7-4
- OM Attributes of Certificate l l l l l l a l l l l 119
Table 7-5
120
Table 7-6 - OM Attributes of Certificate-List l l l l l l l l l
121
Table 7-7 - OMAttributes of Certificate-Pair l l l l l l l l l
Table 7-8 - OM Attributes of Certificate-Sublist l l l l l l l l 122
Table 7-9 - OM Attributes of Certificates l l l l l l l l l l l 122
Table 7-10 - OM Attributes of Cross-Certificates l l l l l l l l l 123
124
Table 7-l 1 - OM Attributes of DL-Submit-Permission l l l e l l l
V

---------------------- Page: 5 ----------------------
ISO/lEC 14392:1996(E) OISO/IEC
o . l l
Table 7-12 OM Attributes of Facsimile-Telephone-Number 125
Table 7-13 ON Attributes of Forward-Certificate-Path l l l l l l 125
Table 7-14 OM Attributes of Postal-Address l l l l o l l l l 126
OMAttributes of Search-Criterion l . l l . o o l . 127
Table 7-15
OM Attributes of Search-Guide l o l o l l l l l l
Table 7-16 128
OM Attributes of Signature e o l e l l o l l l l
Table 7-17 128
Table 7-18 OM Attributes of Teletex-Terminal-Identifier e l l l l 129
Table 7-19 OMAttributes of Telex-Number e l l l o l l l . l 130
Table 8-1 DSP OM Class Object Identifier Suffixes e l l l o l . 132
DSP OMAttribute Type Identifiers l l l l o o o l l 133
Table 8-2
Table 8-3 BDCP OM Class Object Identifier Suffixes l l o l l l 133
3134
Table 8-4 BDCP OMAttribute Type Identifiers l l o e l . l l
Table 8-5 SAP OM Class Object Identifier S&Ekes l l l l l l l 134
Table 8-6 SAP OMAttribute Type Identifiers e l l l l l . l l 134
Table 8-7 MDUPOM Class Object Identifier Suffixes l l l o l l 134
Table 8-8 MDUP OMAttribute Type Identifiers l l o l l l l l 135

---------------------- Page: 6 ----------------------
OISO/IEC ISO/IEC 14392: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 14392 was prepared by IEEE (as
IEEE Std 1224.2-1993) and was adopted, under a special “fast-track
procedure ”, by Joint Technical Committee ISO/IEC JTC 1, Information
technoZogy, in parallel with its approval by national bodies of IS0 and
IEC.
Annexes A and B of this International Standard are for information
only.
vii

---------------------- Page: 7 ----------------------
ISO/IEC 14392:1996(E)
OISO/IEC
1
Introduction
(This introduction is not a normative part of ISO/IEC 14392, Information technology-Directory
2
services-Application Program Interface (API) [Language independent], but is included for informa-
3
4 tion only.)
5 The purpose of this International Standard is to define an application program
interface (API) to directory services, including, but not limited to, the services
6
described in ISO/IEC 9594: 1990 and the CCITT X.500 Series recommendations
7
(References (5-11)) in terms that are independent of any particular programming
8
9 language.
10 Related Standards
.
11 This International Standard is intended to provide the basis for the definition of
12 programming language bindings to which implementations and applications can
13 conform. Such a language binding to this International Standard, for the C pro-
gramming language, is contained in ISO/IEC 14394 (B9).
14
15 The API that this International Standard defines uses the mechanism for OS1
16 abstract data manipulation (OM) defined in ISO/IEC 14360 [12}.
This International Standard, and the language bindings derived from it, may be
17
18 used in conjunction with related APIs, such as the API to X.400-based messaging
19 services defined in ISO/IEC 14361(13}.
ISO/IEC 14393 (14) contains a set of requirements to be satisfied by test methods
20
21 for measuring conformance to this International Standard. They are stated in
22 terms that are independent of any particular programming language, and they
apply to test methods for measuring conformance to all standards defining pro-
23
gramming language bindings of this International Standard.
24
25 Overview
26 This International Standard defines a mandatory generic interface to directory ser-
27 vices and an optional extension of that interface for use in conjunction with the ser-
28 vice described in ISO/IEC 9594: 1990 and the CCITT X.500 Series recommenda-
29 tions (References (5-11)).
. . .
vlll
Introduction

---------------------- Page: 8 ----------------------
OISO/IEC
ISOLIEC 14392:1996(E)
Related Standards Activities
30
The following areas are under active consideration at this time, or are expected to
31
become active in the near future, concerning standards for APIs that are related to
32
the API defined in this International Standard. Similar efforts can be anticipated
33
in the future?
34
35 (1) X.400.based message handling
36 (2) FTAMAPI
37 (3) Other OS1 application layer APIs
38 (4) Network interface facilities
(5) System administration.
39
40 This International Standard is based on IEEE Std 1224.2-1993 {BlO), which was
prepared by the Namespace and Directory Services Working Group (P1224.2, form-
41
42 erly P1003.17), sponsored by the Portable Applications Standards Committee of
43 the IEEE Computer Society.
44 1) A Standards Status Report that lists all current IEEE Computer Society standards projects is
45 available fkom the IEEE Computer Society, 1730 Massachusetts Avenue NW, Washington, DC
46 20036-1903, USA; Telephone: (+l) 202 371-0101; Fax: [phone].
Introduction ix

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

---------------------- Page: 10 ----------------------
INTERNATIONAL STANDARD OISO/IEC
ISOIIEC 14392:1996(E)
1 Information technology-Directory
2 services-Application Program Interface
3 (API) [Language independent]
4 Section 1: General
5 1.1 Scope
6 A directory is a distributed collection of information, which programs can access in
7 order to make queries or updates. This International Standard defines an applica-
8 tion program interface (API) to directory services. This API is known as the direc-
tory services API (DS API). It is referred to as the interface throughout this
9
10 International Standard.
11 This International Standard defines a standard directory service interface to sup-
12 port application portability at the source-code level. It is intended to be used by
13 both application developers and directory service implementors.
14 The interface defined in this International Standard is intended to be used to pro-
15 vide access to a range of directory services that are instances of a common abstract
16 model. That model is defined in the 1988 CCITT X.500 Series recommendations
17 and ISO/IEC 9594. The CCITT Recommendations and ISO/IEC 9594 (5-1l}l) were
18 developed in close collaboration and are technically aligned. Hereinafter, they are
19 referred to as the X.500 directory standards. A summary description of the model
20 is contained in A.2.
21 This International Standard prescribes how the interface that it defines is to be
22
used to access the particular directory service defined in the X.500 directory stan-
23 dards and indicates how it may be used to access other particular directory ser-
24 vices that conform to the same abstract model.
25 The numbers in curly brackets correspond to those of the references in 1.2. When preceded by a
1)
26 “B,” the numbers correspond to those of the bibliography in Annex B.
1.1 Scope

---------------------- Page: 11 ----------------------
ISO/lEC14392:1996(E) @ISO/IEC
This International Standard defines an API that application programs can use to
27 access the functionality of the underlying directory service. It does not define or
28 imply any profile of that service.
29 Nothing in this International Standard requires that the implementation of the
30 interface or the directory itself actually make use of the Directory Access Protocol
31 (DAP), the Directory System Protocol (DSP), or other parts of the model, just so
32 long as it provides the defined service. Also, the scope of the directory to which an
33 application has access is not determined. It is entirely a local matter whether
34 objects in other directory system agents (DSAs) are accessible.
The interface is designed for operational interactions with a directory, rather than
35
for management interactions, such as knowledge management or schema manage-
36
ment. Also, security features are not generally visible in the interface in order to
37
permit flexibility in security policies.
38
39 It is intended that an application program should be able to use the interface
40 defined in this International Standard to access a single directory service or to
41 access several directory services at the same time.
This International Standard uses concepts of OS1 abstract data manipulation (OM)
42
43 that are defined in ISOAEC 14360 (12). They are summarized in A.3.
44 The directory service interface is defined in this International Standard in a pro-
45 gramming language independent manner. ,It contains:
- Definitions of the interface operations
46
47 - Definitions of the information structures used in the interface that are asso-
48 ciated with the abstract model of directory services
49 - Definitions of the information structures used in the interface that are asso-
50 ciated with the particular instance of the model that is defined in ISO/IEC
51 9594 (5).(11).
This International Standard describes the external characteristics and facilities
52
that are of importance to applications developers, rather than the internal con-
53
struction techniques employed to achieve these capabilities. Special emphasis is
54
55 placed on those functions and facilities that are needed in a wide variety of com-
mercial applications.
56
57 This International Standard is defined exclusively at the source-code level. The
58 objective is that a conforming application source program can be translated to exe-
59 cute in conjunction with one or more conforming implementations.
2
1 General

---------------------- Page: 12 ----------------------
@ ISO/IEC
ISO/lEC14392:1996(E)
1.2 Normative References
60 The following standards contain provisions which, through reference in this text,
61 constitute provisions of this International Standard. At the time of publication,
the editions indicated were valid. All standards are subject to revision, and parties
62
to agreements based on this International Standard are encouraged to investigate
63
the possibility of applying the most recent editions of the standards indicated
64
below. Members of IEC and IS0 maintain registers of currently valid Interna-
65
tional Standards.
66
ISO/IEC 8824: 1990 (CCITT Recommendation X.208: 1988),2) Information
67 (1)
technology-Open Systems Interconnection
68 -Specification of Abstract Syntax
Notation One (ASN. 1).
69
70 ISO/IEC 8825: 1990 (CCITT Recommendation X.209: NSS), Information
(2)
71 technology-Open Systems Interconnection -Specification of Basic Encoding
72 Rules for Abstract Syntax Notation One (ASN.1).
ISO/IEC 9072-l: 1989 (CCITT Recommendation X.219: 1988), Information
73
(3)
processing systems- Text communication-Remote Operations-Part 1:
74
Model, notation and service definition.
75
76 ISO/IEC 9072-2: 1989 (CCITT Recommendation X.229: 1988), Information
(4)
77 processing systems- Text communication-Remote Operations-Part 2: Pro-
78 tocol specification.
79 ISO/IEC 9594-1: 1990 (CCITT Recommendation X.500: 1988), Information
(5)
80 technology-Open Systems Interconnection-The Directory-Part 1: Over-
81 view of concepts, models and services.
82 ISO/IEC 9594-2: 1990 (CCITT Recommendation X.501: 1988), Information
(6)
technology-Open Systems Interconnection-The Directory-Part 2: Models.
83
84 ISO/IEC 9594-3: 1990 (CCITT Recommendation X.511: 1988), Information
technology-Open Systems Interconnection-The Directory-Part 3: Abstract
85
service definition.
86
87 ISO/IEC 9594-4: 1990 (CCITT Recommendation X.518: 1988), Information
88 technology-Open Systems Interconnection-The Directory-Part 4: Pro-
89 cedures for distributed operation.
90 ISO/IEC 9594-6: 1990 (CCITT Recommendation X.520: 1988), Information
technology-Open Systems Interconnection-The Directory-Part 6: Selected
91
attribute types.
92
93 ISO/IEC 9594-7: 1990 (CCITT Recommendation X.521: 1988), Information
94 technology-Open Systems Interconnection-The Directory-Part 7: Selected
object classes.
95
96 2) ISO/IEC documents can be obtained from the IS0 CentraI Secretariat, 1 Rue de Varembe, Case
97 Postale 56, CH-1211, Geneve 20, Switzerland/Suisse. CCITT documents can be obtained from
98 the Telecommunication Standardization Bureau of the International Telecommunication Union,
99 Sales Section, Place des Nations, CH-1211, Geneve 20, Switzerland/Suisse.
1.2 Normative References

---------------------- Page: 13 ----------------------
OISO/IEC
ISOREC 14392:1996(E)
(11) ISO/IEC 9594-8: 1990 (CCITT Recommendation X.509: 1988), Information
technology-Open Systems Interconnection-The Directory-Part 8: Authen-
100
101 tication framework.
102 (12) ISO/IEC 14360: 1996, Information technology-Open Systems Interconnec-
103 tion (OSI) abstract data manipulation- Application Program Interface (API)
104 [Language independent].
technology-MHS-based electronic
105 ISO/IEC 14361: 1996, Information
106 messaging-Application Program Interface (API) [Language independent].
PO7 ) ISOIIEC 14393: 1996, Information technology-Test methods for measuring
108 conformance to directory services- Application Program Interface (API)
109 [Language independent].
110 (15) CCITT Recommendation F.200: 1984, Teletex Service. CCITT Red Book,
111 Fascicle 11.5.
I.12 (16) CCITT Series T Recommendations: Terminal Equipment and Protocols for
Telematic Services, Fascicle VII.3, 1984.
113
114 1.3 Conformance
115 1.3.1 Implementation Conformance
116 1.3.1.1 Codwmance Requirements
117 A conforming implementation for a programming language binding specification
118 for this International Standard shall meet all of the following criteria:
119 (1) The implementation shall support all required behavior defined in this
120 International Standard.
(2) The implementation shall support all required interfaces defined in the
121
122 programming language binding specification. Those interfaces shall sup-
123 port the behavior described in this International Standard and in the pro-
gramming language specification.
124
125 (3) The implementation may provide additional functions or facilities not
126 required by this International Standard or by the programming language
127 binding specification. Each such nonstandard extension shall be identified
128 as such in the system documentation Nonstandard extensions, when
129 used, may change the behavior of functions or facilities defined by this
130 International Standard or by the programming language binding
131 specification. The conformance document shall define an environment in
132 which an application can be run with the behavior specified by this Inter-
133 national Standard and the programming language binding specification.
134 In no case shall such an environment require modification of a Strictly
135 Conforming Application.
4 1 General

---------------------- Page: 14 ----------------------
@ISO/IEC ISO/lEC 14392:1996(E)
1.3.1.2 Conformance Documentation
136 A conformance document with the following information shall be available for an
137 implementation claiming conformance to a programming language binding
specification for this International Standard. The conformance document shall be
138
in two parts. The first part shall have the same structure as this International
139
140 Standard, with the information presented in the appropriately numbered sections,
141 clauses, and subclauses. The second part shall have the same structure as the pro-
142 gramming language binding specification, with the information presented in the
143 appropriately numbered sections, clauses, and subclauses. The conformance docu-
144 ment shall not contain information about extended features or capabilities outside
145 the scope of this International Standard and the programming language binding
146 specification.
147 The conformance document shall identify the programming language binding
148 specification to which the implementation conforms.
The conformance document shall contain a statement that indicates the full
149
names, numbers, and dates of the language-independent and programming
150
language binding specification standards that apply.
151
152 The conformance document shall state which of the optional features defined in
153 this International Standard and in the programming language binding
154 specification are supported by the implementation.
155 The conformance document shall describe the behavior of the implementation for
156 all implementation-defined features defined in this International Standard and in
157 the programming language binding specification. This requirement shall be met
158 by listing these features and by providing either a specific reference to the system
159 documentation or full syntax and semantics of these features. The conformance
160 document may specify the behavior of the implementation for those features where
161 this International Standard or the programming language binding specification
162 states that implementations may vary or where features are identified as
163 undefined or unspecified.
No specifications other than those specified by this International Standard and the
164
programming language binding specification shall be present in the conformance
165
166 document. ’
167 The phrases “shall document” or “shall be documented” in this International Stan-
168 dard or in a programming language binding specification for this International
169 Standard mean that documentation of the feature shall appear in the conformance
170 document, as described previously, unless the system documentation is explicitly
mentioned.
171
172 The system documentation should also contain the information found in the confor-
173 mance document.
1.3 Conformance 5

---------------------- Page: 15 ----------------------
ISOLIEC 14392:1996(E)
OISO/IEC
1.3.1.3 Conforming Implementation Options
All the interface operations are mandatory; none are optional.
174
175 Some OM attributes are optional; these are marked as such in the OM class
176 definitions. They are:
177 - Asynchronous in a
...