ISO/IEC ISP 11189:1997

Information technology — International Standardized Profile FDI2 — Directory Data Definitions — MHS Use of the Directory

Technologies de l'information — Profil normalisé international FDI2 — Définitions des données d'annuaire — Emploi MHS de l'annuaire

General Information

• Status: Withdrawn
• Publication Date: 24-Dec-1997
• Withdrawal Date: 24-Dec-1997
• ICS: 35.100.05 - Multilayer applications
• 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: 07-Sep-2004

Relations

• Revised: ISO/IEC FDISP 11189 - Information technology — International Standardized Profile FDI2 — Directory Data Definitions — MHS Use of the Directory
• Effective Date: 15-Apr-2008

Standards Content (Sample)

INTERNATIONAL ISOAEC
STANDARDIZED ISP
PROFILE 11189
First edition
19974245
Information technology - International
Standardized Profile FD12 - Directory Data
Definitions - MHS Use of the Directory
Technologies de l’informa tion - Profil normalis international FDl2 -
Dkfinitions des don&es d ’annuaire - Emploi MHS de I’annuaire
Reference number
ISO/IEC ISP 11189:1997(E)

---------------------- Page: 1 ----------------------
ISOhEC ISP 11189: 1997 (E)
Contents
1
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.
1. SCOPE
2
o~.ooo~.o~mooomoo~~ooo~~.o~.~.oo.~~oooo*o.~*~~D.*~.~~.~.~.~.~.~~.Do.o~~oo~oo~*oo*.o.~oDDD~~*.~
2. NORMATIVE REFERENCES
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. DEFINITIONS
5
5. CONFORMANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . ‘. 8
7. CONFORMANCE TO OBJECT CLASSES
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
8. CONFORMANCE TO ATTRIBUTE TYPES
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
9. CONFORMANCE TO MATCHING RULES
10
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.
ANNEX A - PROFILE REQUIREMENTS LIST
ANNEX B - RECOMMENDATIONS FOR DSA SUPPORT OF DIB FRAGMENTS IN AN
16
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OPERATIONAL ENVIRONMENT FOR MHS USE OF THE DIRECTORY
0 ISO/IEC 1997
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or
utilized in any form or by any means, electronic or mechanical, including photocopying and micro-
film, 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

---------------------- Page: 2 ----------------------
0 ISOIIEC ISO/IEC ISP 11189 : 1997 (E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the
international 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 JTCl . In addition to developing International
Standards, lSO/IEC JTCl has created a Special Group on Functional
Standardization for the elaboration of International Standardized Profiles.
An International Standardized Profile is an internationally agreed, harmonized
document which identifies a standard or group of standards, together with
options and parameters, necessary to accomplish a function or set of
functions.
Draft International Standardized Profiles are circulated to national bodies for
voting. Publication as an International Standardized Profile requires approval
by at least 75% of the national bodies casting a vote.
International Standardized Profile lSO/lEC ISP 11189 was prepared with the
collaboration of
l OSI Asia-Oceania Workshop (AOW);
0
European Workshop for Open Systems (EWOS);
l OSE Implementors’ Workshop (OIW).
Annex A forms an integral part of this International Standardized Profile.
Annex B is for information only.
. . .
111

---------------------- Page: 3 ----------------------
@ lSO/IEC
ISOAEC ISP 11189: 1997 (E)
Introduction
The concept and structure of International Standardised Profiles for
Information Systems are laid down in ISO/lEC TR 10000. The purpose of an
International Standardised Profile is to recommend when and how certain
information technology standards shall be used. This International
Standardised Profile ISO/IEC ISP 11189 specifies application profile FD12
as defined in ISO/IEC TR 10000-2.
ISO/IEC 10616 profiles information to be stored within the directory which is
common to a variety of application. ISOIIEC ISP 11189 augments this
information by specific information for use with Message Handling Systems.
To support the implementation of the Directory as defined by ITU-T Rec.
x.500 - series of Recommendations 1 ISOIIEC 9594, this ISP gives
requirements that are applicable to implementations of DSAs. Additionally,
these requirements may guide Directory users and administrative authorities
in defining their needs for the use of the Directory.
The primary objective of this International Standardized Profile is to define
the minimum capabilities that DSAs must have to support an MHS
application ’s view of Directory information. It does this by specifying a
minimum set of structure and naming elements for the DIT which a DSA
must be capable of holding and accessing, and other minimum schema
requirements.
This International Standardized Profile does not limit DSAs to these
minimum capabilities - DSAs that comply with this ISP and which have no
additional information handling (storage, retrieval and modification)
capabilities may not be adequate for many purposes, and Implementors are
strongly encouraged to provide such additional capabilities.
Likewise, this International Standardized Profile does not limit Naming
Authorities in any way, e.g. restrict their selection of object classes or
naming attributes to those which are required to be supported by this
Profile. Rather, it guarantees that selections made within the scope of this
International Standardized Profile will be within the capabilities of DSAs
compliant with this International Standardized Profile.
iv

---------------------- Page: 4 ----------------------
INTERNATIONAL STANDARDIZED PROFILE 0 ISO/IEC ISO/IEC ISP 11189: 1997 (E)
Information technology - International Standardized
Profile FD12 - Directory Data Definitions - MHS Use of the
Directory
1 Scope
1 .I General
ISOllEC ISP 10616 profiles information to be stored within the directory which is common to a variety of
applications. This International Standardized Profile augments this information by MHS specific information.
Statements and conformance requirements stated in ISO/IEC ISP 10616 for the information profiled by ISOllEC
ISP 10616 are also valid for the MHS specific information profiled by this International Standardized Profile.
This International Standardized Profile specifies the use of the Directory by MHS, using existing object classes
and attribute type definitions from the Directory specifications and the MHS specifications. The scope of
application of this International Standardized Profile covers the broad area of MHS Use of the Directory as
defined in annex A of ISO/IEC 10021-2 as indicated below:
l Determining an MHS User ’s OR-Address from the directory name
l MHS User capability assessment
l Determining information about the application entities supporting MTAs, MSs and UAs
l Storing and retrieving information on distribution lists for distribution list expansion.
1.2 Position within the taxonomy
This International Standardized Profile is identified by ISO/IEC TR 10000-2 as “Information technology -
International Standardized Profile - Directory Data Definitions - MHS Use of the Directory ”.
I .3 Scenario
An MHS application using its associated DUA ,directly or indirectly obtains Directory information by accessing
one or more DSAs in the Directory (See figure I).
\
The D irectory
/
\
I”s ”I
MHS
A p,plication
L 1
-DUA
or User
I DSA
0 lDsA
.
Figure 1 - MHS use of the Directory Scenario

---------------------- Page: 5 ----------------------
0 ISOAEC
ISOAEC ISP 11189: 1997 (E)
2 Normative References
The following documents contain provisions which, through reference in this text, constitute provisions of this
International Standardized Profile. At the time of publication, the editions indicated were valid. All documents are
subject to revision, and parties to agreements based on this International Standardized Profile are warned
against automatically applying any more recent editions of the documents listed below, since the nature of
references made by ISPs to such documents is that they may be specific to a particular edition. Members of IEC
and IS0 maintain registers of currently valid International Standards and ISPs, and ITU-T maintains published
editions of its current Recommendations.
2.1 ISP Framework Documents
ISOAEC TR 10000-1: 1995, information technology - Framework and taxonomy of international Standardized Profiles -
Part 1: Genera/ principles and documentation framework.
ISO/IEC TR 10000-2: 1995, lnfotmation technology - Framework and taxonomy of International Standardized Profiles -
Part 2: Principles and Taxonomy for OS/ profiles.
ISOAEC ISP 10616: 1995, Information technology - International Standardized Profile FDII I - Directory data definitions -
common Directory Use (Norma/).
2.2 Directory Standards - 1990 edition
Open Systems Interconnection - The Directory - Part I: Overview of
ISO/IEC 9594-l : 1990, information technology -
concepts, mode/s and service. [See also Recommendation X. 500 (7 988)].
The Directory - Part 2: Mode/s. [See also
ISOllEC 9594-2: 1990, lnformation technology - Open Systems Interconnection -
Recommendation X. 50 I (I 988)J
Open Systems interconnection - The Directory - Part 5: Protocol
ISOAEC 9594-5: 1990, information technology -
specifications [See also Recommendation X. 519 (I 988)J
The Directory - Part 6: Selected attribute
ISOAEC 9594-6: 1990, information technology - Open Systems Interconnection -
types. [See also Recommendation X. 520 (I 988)J
The Directory - Part 7: Selected object
iSO/IEC 9594-7: 1990. information technology - Open Systems interconnection -
classes. [See also Recommendation X. 52 I (I 988)J
2.3 Directory Standards - 1995 edition informative references
The following informative references to the 1995 edition of the directory standards are included because the
object classes, attributes and matching rules specified in this International Standardized Profile can be used on
Directory systems conforming to the 1995 Directory standards.
The Directory: Overview of concepts,
ISOAEC 9594-l: 1995, Information technology - Open Systems Interconnection -
models and service. [See a/so Recommendation X.500 (1995)J
ISOAEC 9594-2: 1995, Information technology - Open Systems Interconnection - The Directory: Mode/s. [See a/so
Recommendation X. 50 1 (I 995)J
ISO/IEC 9594-5: 1995, information technology - Open Systems Interconnection - The Directory: Protocol specifications [See
also Recommendation X. 5 I9 (I 995)J
The Directory: Selected attribute types.
ISO/IEC 9594-6: 1995, Information technology - Open Systems interconnection -
[See also Recommendation X. 520 (7 995)J
ISO/IEC 9594-7: 1995, Information technology - Open Systems interconnection - The Directory: Selected object c/asses.
[See also Recommendation X. 52 7 (I 995)].
2.4 Message Handling Systems Standards
ISOAEC +lOO21-2: 1996, information technology - Message Handling Systems (MHS) - Part 2: Overall architecture [See also
I TUT Recommendation X. 402 (I 996)J
ISOA EC 10021-5: 1996, Information technology - Message Handling Systems (MHS) - Part 5: Message store abstract
sewice definition. [See a/so /TUT Recommendation X.413 (1995)J
NOTE 1 - This International Standardized Profile is based on the 1996 versions of ISOllEC 10021 and x.400
Recommendations since the earlier versions are considered to be faulty.
2

---------------------- Page: 6 ----------------------
0 ISOAEC
ISO/IEC ISP 11189: 1997 (E)
NOTE 2 - In the 1990 edition of ISOllEC 9594, the syntax of attributes is defined separately using the ATTRIBUTE-SYNTAX
ASN.1 Macro. In the 1995 edition of ISO/IEC 9594, the syntax of attributes is specified within the attribute definition itself.
3 Definitions
For the purposes of this International Standardized Profile, definitions apply as defined in the referenced
standards. In addition, the following terms are defined.
3.1 General
The following definitions are made in ISOllEC ISP 10616:
Table 1 - Definitions used from ISOIIEC ISP 10616
Term Reference in
ISO/IEC ISP
10616
Auxiliary object class 3.1 .l
1
I I
Structural object class 3.1.2
Structure Element 3.1.3
The following terms. are% defined for the purposes of this International Standardized Profile:
3A.l Functional Group
A specificatibn of one or more Directory schema components (object classes, attribute types and associated
attribute syntaxes, matching rules and structure elements) or other identifiable features specified in base
standards which together support a significant optional area of DSA functionality.
3.2. Support classification
To specify the support level of schema elements for this International Standardized Profile, the following
terminology is defined.
3.2.1 Mandatory support (m):
3.2.1 .I General
Mandatory requirement for support. A feature (object class, attribute type and associated attribute
syntax, structure element, or matching rule) is supported by a DSA implementation if the DSA is able
to process the feature in accordance with the base standard, ISOllEC ISP 10616 or as specified in
this International Standardized Profile.
3.2.1.2 Mandatory support for Object Classes
Support of object classes by a DSA conformant with FD12 requires the DSA to be able to store,
modify and retrieve, via Directory operations, an entry of its fragment of the DIT, if the entry is
associated with supported object classes and the following conditions are fulfilled:
a) The entry lies within the DIT structure described in clause 6 and in A.6.5.1;
b) The entry contains all MUST CONTAIN attributes of its object classes;
c) The entry contains no other than MUST CONTAIN and MAY CONTAIN attributes of its object
classes.
3

---------------------- Page: 7 ----------------------
0 ISOAEC
ISO/IEC ISP 11189: 1997 (E)
3.2.1.3 Mandatory support for Attributes
A DSA conformant with FD12 shall support an attribute type as follows:
a) The DSA shall perform, on the original inclusion or on a subsequent modification attempt of an
attribute, the checking algorithm which is associated with the syntax of the attribute, when
required;
b) The DSA shall check that the number of attribute values complies with the multivalued
element of the attribute definition;
c) The DSA shall check that the attribute value(s) conform with the bounds defined in ITU-T Rec.
X.520 annex C (which is not an integral part of ISOllEC 9594-6);
d) The DSA shall support the equality matching algorithm that is associated with the attribute,
and shall execute this matching algorithm in a manner that conforms with ITU-T Rec. X.500
series 1 ISOllEC 9594 requirements as clarified in 9.3 of ISO/IEC ISP 10616.
NOTE - the word ‘equality’ has been added to the original FDII 1 text in ISO/IEC ISP 10616 to avoid the
necessity of mandating all of the OR-Address and OR-Name attribute matching rules which have been
defined in ISOllEC 10021.
e) The DSA shall support the attribute for each supported object class which references that
attribute.
9 The DSA shall be able to check values of the attribute syntax associated with the attribute for
syntactical correctness in compliance with limitations as defined by ITU-T Rec. X.520, annex C
and additional rules stated in clause 9 of ISO/IEC ISP 10616.
NOTE - Attribute Syntaxes are separately defined in the 1988/90 editions of the Directory documents and
referenced by the 1988/92 editions of the Message Handling Systems documents. In the 1993195
Directory documents and the 199W Message Handling System documents, Attribute Syntaxes are
implicitly defined in the definition of Attributes.
3.2.1.4 Mandatory support for Matching Rules
Mandatory support of a matching rule implies the DSA ’s ability to perform matches according to
rules defined in ITU-T Rec. X.520 1 ISO/IEC 9594-6 as well as the rules defined in annex D
subclause 12.4 and the additional rules stated in ISOllEC ISP 10616, 9.4. Support for a Matching
Rule implies that it is supported for all attributes which reference the matching rule;
3.2.1.5 Mandatory support for Structure Elements
(refer to clause 6 of ISOIIEC ISP 10616). The DSA complies with .a structure element for an entry of
a particular structural object class if:
a) its superior entry complies with at least one of the superior structure elements;
b) it is associated with the structural object class;
c) its RDN is formed using the naming attribute(s).
3.2.2 Optional support (0)
An implementation is not required to support the element (object class, attribute types and associated attribute
syntaxes, structure element or matching rule), If support is claimed, the element shall be treated as if it were
specified as mandatory for support.

---------------------- Page: 8 ----------------------
ISO/IEC ISP 11189: 1997 (E)
0 ISO/IEC
3.2.3 Conditional support (c)
The element (object class, attribute type and associated attribute syntax, structure element or matching rule)
shall be supported under the conditions specified in this International Standardized Profile. If these conditions
are met, the element shall be treated as if it were specified as mandatory support. If these conditions are not
met, the element shall be treated as if it were specified as optional support.
3.2.4 Not applicable (-) ’
The element is not applicable in the particular context in which this classification is used.
4 Abbreviations
The following abbreviations are defined in ISOllEC 9594
BIB Directory Information Base
DIT Directory Information Tree
DN Distinguished Name
DSA Directory Service Agent
DUA Directory User Agent
RDN Relative Distinguished Name
The following abbreviations are defined in other standards:
DL Distribution List - is defined in ISO/IEC 10021 - 2
ISP International Standardized Profile - is defined in ISO/IEC TR 10000-l
The following abbreviation is defined in this Profile
Functional Group
FG
5 Conformance
This International Standardized Profile states requirements placed upon DSA implementations to achieve
interworking. A claim of conformance to it is a claim that:
0
all requirements in the relevant directory base standards are satisfied. The object classes,
attributes, matching rules and structure elements profiled in this ISP are equally valid for
implementations of both the 1990 and 1995 editions of the directory protocols;
0
all requirements in ISO/lEC ISP 10616 are satisfied;
l .
all requirements in the following clauses and in annex A of this International Standardized Profile
are satisfied. Annex A states the relationship between these requirements and those of the base
standards.
5.1 Conformance Statement
For each implementation claiming conformance to profile FD12 as specified in this International Standardized
Profile, a PIGS shall be made available stating support or non-support of each option identified in this
International Standardized Profile. The scope of conformance to FD12 is restricted to DSAs.
Implementations for which conformance to FD12 is claimed shall implement all the mandatory (m) support object
classes, attribute types and associated attribute syntaxes, matching rules and structure elements specified in
annex A and the conformance statement shall state which optional (0) Object Classes, Attribute Types and
associated Attribute Syntaxes and Matching Rules are implemented.
5.2 Basic Requirements and Functional Groups
attributes and associated attribute
Annex A specifies the basic requirements for support of object classes,
syntaxes and matching rules for conformance to FD12. Basic requirements specify the level of support required
by all conformant DSAs. The basic requirements are further defined in 5.4 and classified in the ‘Basic’ column of
5

---------------------- Page: 9 ----------------------
ISO/IEC ISP 11189: 1997 (E) 0 ISOAEC
the tables in annex A. All implementations for which conformance to FDl2 is claimed shall support the basic
requirements.
Annex A also specifies any additional requirements for support of object classes, attributes and associated
attribute syntaxes and matching rules if support for an optional functional group (FG) is claimed. The following
clauses summarise the functionality supported by each of the optional FGs.
52.1 The Distribution List Functional Group - DL
This specifies the object classes, attributes and associated attribute syntaxes, matching rules and structure
elements for holding specifications of MHS Distribution Lists in the Directory. The requirements of the DL
functional group are further specified in 5.5 and classified in the ‘DL’ column of the tables in annex A.
5.2.2 The Additional Matching Rules Functional Group - AMR
This specifies a set of non-exact match rules which are comparatively easy to implement.
52.3 The Substring Matching Rules Functional Group - SMR
This specifies a group of matching rules which involve matching on substrings.
5.3 Conformance to ISO/IEC ISP 10616
Conformance to FD12 implies conformance to ISOllEC ISP 10616 as a precondition.
The requirements formulated in ISO/IEC ISP 10616 with respect to supported object classes, supported attribute
types and associated attribute syntaxes according to ISO/ISP 10616 are also valid for the additional supported
object classes, supported attribute types and associated attribute syntaxes according to this International
Standardized Profile.
Storage and modification of entry information imply checking and matching of attribute values for which eaualitv
matching is defined for that attribute type.
5.4 Conformance to Basic Requirements
All DSAs for which conformance to this profile is claimed shall support all of the object classes, attributes,
matching rules and structure elements of the basic requirements as classified in the ‘Basic’ column of the tables
in annex A.
A DSA for which conformance to this profile is claimed shall, after suitable set up, be capable of storing,
modifying and retrieving entries which fulfil all of the following conditions:
l
The entry lies within the part of the scope of the minimum set of structure and naming elements
specified in clause 6;
0
The entry ’s object classes are part of the set of those mandatory object classes specified in
A.6.4.1 of this profile and A.6.4.1 of ISO/IEC ISP 10616, and the subset of optional object
classes specified in A.6.4.2 of this profile and A.6.4.2 of ISO/IEC ISP 10616 for which support is
claimed for the DSA as classified in the ‘basic’ columns of the tables;
0
The entry ’s attributes are part of the set of mandatory attribute types specified in A.6.4.2 of this
profile and A.6.4.2 of ISOllEC ISP 10616, and the subset of optional attribute types specified in
A.6.4.2 of this profile and A.6.4.2 of ISO/IEC ISP 10616 as classified in the ‘basic’ columns of
the tables.
In addition to the matching rules mandated by ISOllEC ISP 10616, the DSA shall support the set of mandatory
matching rules specified in the ‘basic’ column of A.6.5.4, and may support those optional matching rules specified
in the ‘basic’ column of A.6.5.4.
5.5 Distribution List Functional Group Conformance
A DSA for which conformance to the Distribution List Functional Group of this profile is claimed shall, after
suitable set up, be capable of storing, modifying and retrieving entries which fulfil all of the following conditions:

---------------------- Page: 10 ----------------------
0 IS01 ‘IEC
ISO/IEC ISP 11189: 1997 (E)
l The entry lies within the part of the scope of the minimum set of structure and naming elements
specified in clause 6;
l The entry ’s object classes are part of the set of those mandatory object classes specified in
A.6.4.1 of this profile and A.6.4.1 of ISOllEC ISP 10616, and the subset of optional object
classes specified in A.6.4.2 of this profile and A.6.4.2 of lSO/IEC ISP 10616 for which support is
claimed for the DSA as classified in the ‘DL’ columns of the tables;
l The entry ’s attributes are part of the set of mandatory attribute types specified in A.6.4.2 of this
profile and A.6.4.2 of ISOllEC ISP 10616, and the subset of optional attribute types specified in
A.6.4.2 of this profile and A.6.4.2 of ISOllEC ISP 10616 as classified in the ‘DL’ columns of the
tables.
An implementation shall support the set of mandatory matching rules specified in the ‘DL’ column of A.6.5.4, and
may support those optional matching rules specified in the ‘DL’ column of A.6.5.4.
5.6 Additional Matching Rules Functional Group conformance
DSAs for which conformance to the Additional Matching Rules Functional Group is claimed shall support those
Matching Rules classified by ‘m’ in column AMR of Table A.6.5.4.
5.7 Substring Matching Rules Functional Group conformance
DSAs for which conformance to the Substring Matching Rules Functional Group is claimed shall support those
Matching Rules classified by ‘m’ in column SMR of Table A.6.5.4.
5.8 DUA conformance
DUAs typically need schema information as outlined in FD12 to support an MHS application ’s use of the Directory.
However, FD12 makes no statements about DUA conformance.
6 Conformance to DIT Structure
The purpose of this clause is to relate information specified in this International Standardized Profile to the
minimum set of structure and naming elements defined in ISO/IEC ISP 10616 and thus to provide locations for
entries of selected object classes.
The DIT structure which shall be supported as a minimum by DSA implementations for which conformance to
FD12 is claimed is the superset of those defined in ISO/IEC ISP 10616, and structure elements listed in A-6.5.1
of this profile.
Subclause A.6.5.2 defines how additional object classes defined in clause 7 are related to these structure
elements.
This DIT structure is supported in the sense that a conformant DSA shall be capable of storing, modifying and
retrieving entries which are part of a tree with this structure (for a more formal definition see ISO/IEC ISP 10616).

---------------------- Page: 11 ----------------------
ISOllEC ISP 11189: 1997 (E)
0 ISOAEC
7 Conformarice to Object Classes
The following object classes, all of which are defined in ISOIIEC 10021 - 2, shall be supported as specified in
annex A of this profile, in addition to those specified and mandated in ISO/IEC ISP 10616:
a
mhs-distribution-list
l
mhs-message-transfer-agent
0
mhs-message-store
mhs-user
0
mhs-user-agent
8 Conformance to Attribute Types
The following attribute types and their associated syntaxes, all of which are defined in ISOllEC 10021 - 2, shall be
supported as specified in annex A of this profile for conformance to this International Standardized Profile in
addition to those defined in ISOllEC ISP 10616:
l
mhs-acceptable-eits
0
mhs-deliverable-content-types
mhs-deliverable-classes
0
mhs-deliverable-eits
0
mhs-dl-archive-service
l
mhs-dl-members
l
mhs-dl-policy
l
mhs-dl-submit-permissions
0
mhs-dl-subscription-service
l
mhs-exclusively-acceptable-eits
NOTE - In previous versions this was called ‘mhs-deliverable-eits’
mhs-maximum-content-length
mhs-message-store-dn
a
mhs-or-addresses
a
mhs-or-address-with-capabilities
l
mhs-related-lists
0
mhs-supported-attributes
0
mhs-supported-automatic-actions
0
mhs-supported-content-types
0
mhs-supported-matching-rules
0
mhs-unacceptable-eits
NOTE - Since the 1995 Directory documents and 1995 Message Handling Systems documents do not
explicitly specify attribute syntaxes, the requirements for conformance to attribute syntaxes are considered to
be dealt with as an implicit part of conformance to attribute types.

---------------------- Page: 12 ----------------------
0 ISODEC ISO/lEC ISP II 189: 1997 (E)
9 Conformance to Matching Rules
9.1 Additional Matching Rules Functional Group
The following matching rules shall be supported as specified in annex A Table 6.5.4 column AMR of this profile
for conformance to the FD12 Additional Matching Rule Functional Group in addition to the equality matching rules
and those defined in ISOllEC ISP 10616 and in addition to the equality matching rules:
0
oRAddressElementsMatch
0
oRNameElementsMatch
0
oRNameMatch
0
oRNameSingleElementMatch
9.2 Substring Matching Rules Functional Group
The following matching rules shall be supported as specified in annex A Table 6.5.4 column SMR of this profile
for conformance to the FD12 Substring Matching Rule Functional Group in addition to the equality matching rules
and those defined in ISO/IEC ISP 10616 and in addition to the equality matching rules:
0
oRAddressSubstringElementsMatch
0
oRNameSubstringElementsMatch
9

---------------------- Page: 13 ----------------------
lSO/IEC ISP 11189: 1997 (E)
0 ISOAEC
AnnexAl
...