ISO/IEC FDISP 11189
(Main)Information technology — International Standardized Profile FDI2 — Directory Data Definitions — MHS Use of the Directory
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
Relations
Standards Content (Sample)
FINAL
INTERNATIONAL ISO/IEC
DRAFT
STANDARDIZED FDISP
PROFILE 11189
ISO/IEC JTC 1
Information technology — International
Secretariat: ANSI
Standardized Profile FDI2 — Directory Data
Voting begins on:
Definitions — MHS Use of the Directory
1999-11-04
Voting terminates on:
Technologies de l'information — Profil normalisé international FDI2 —
2000-01-04
Définitions des données d'annuaire — Emploi MHS de l'annuaire
Please see the administrative notes on page i-2
RECIPIENTS OF THIS DOCUMENT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS, NOTIFI-
CATION OF ANY RELEVANT PATENT RIGHTS OF
WHICH THEY ARE AWARE AND TO PROVIDE
SUPPORTING DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
Reference number
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO-
ISO/IEC FDISP 11189:1999(E)
LOGICAL, COMMERCIAL AND USER PURPOSES,
DRAFT INTERNATIONAL STANDARDS MAY ON
OCCASION HAVE TO BE CONSIDERED IN THE
LIGHT OF THEIR POTENTIAL TO BECOME STAN-
DARDS TO WHICH REFERENCE MAY BE MADE IN
©
ISO/IEC 1999
NATIONAL REGULATIONS.
---------------------- Page: 1 ----------------------
ISO/IEC FDISP 11189:1999(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not
be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this
file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this
area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters
were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event
that a problem relating to it is found, please inform the Central Secretariat at the address given below.
Copyright notice
This ISO document is a Draft International Standard and is copyright-protected by ISO. Except as permitted
under the applicable laws of the user’s country, neither this ISO draft nor any extract from it may be reproduced,
stored in a retrieval system or transmitted in any form or by any means, electronic, photocopying, recording or
otherwise, without prior written permission being secured.
Requests for permission to reproduce should be addressed to either ISO at the address below or ISO’s member
body in the country of the requester.
ISO copyright office
Case postale 56 � CH-1211 Geneva 20
Tel. +412274901 11
Fax + 41 22 734 10 79
E-mail copyright@iso.ch
Web www.iso.ch
Reproduction may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
i-1 © ISO/IEC 1999 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC FDISP 11189:1999(E)
In accordance with the provisions of Council Resolution 21/1986, this document is circulated in the English
language only.
© ISO/IEC 1999 – All rights reserved i-2
---------------------- Page: 3 ----------------------
ISO/IEC FDISP 11189: 1999 (E) ãã
................................ ................................ ................................ ..........................
1. SCOPE . . . . .1
................................ ................................ ................................ ....2
................................ ................................ ................................ .............................3
4. ABBREVIATIONS . . . .5
................................ ................................ ................................ ......................65
................................ ................................ ...............87
7. CONFORMANCE TO OBJECT CLASSES . . .98
8. CONFORMANCE TO ATTRIBUTE TYPES . . .98
................................ ................................ .........109
................................ ................................ ......1110
B.1 OBJECT CLASSES . . . .1816
B.2 ATTRIBUTES . . . .1917
B.3 ATTRIBUTE SYNTAXES . . . .2220
B.4 MATCHING RULES . . . .2220
B.5 STRUCTURE ELEMENTS . . .2321
ii
ANNEX A - PROFILE REQUIREMENTS LIST
9. CONFORMANCE TO MATCHING RULES
6. CONFORMANCE TO DIT STRUCTURE
5. CONFORMANCE
3. DEFINITIONS
2. NORMATIVE REFERENCES
IV INTRODUCTION
Contents
ISO/IEC
---------------------- Page: 4 ----------------------
ISO/IEC FDISP 11189:1999(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission)
form the specialized system for worldwide standardization. National bodies that are members of ISO 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. ISO and IEC technical committees
collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in
liaison with ISO and IEC, also take part in the work.
In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. In
addition to developing International Standards, ISO/IEC JTC 1 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 a 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 ISO/IEC ISP 11189 was prepared with the collaboration of
� Asia-Oceania Workshop (AOW);
� European Workshop for Open Systems (EWOS);
� Open Systems Environment Implementors' Workshop (OIW).
This second edition cancels and replaces the first edition (ISO/IEC ISP 11189:1997), which has been technically
revised.
Attention is drawn to the possibility that some of the elements of this International Standardized Profile may be the
subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
Annex A forms a normative part of this International Standardized Profile. Annex B is for information only.
© ISO/IEC 1999 – All rights reserved iii
---------------------- Page: 5 ----------------------
ISO/IEC FDISP 11189: 1999 (E) ãã
The concept and structure of International Standardised Profiles for
Information Systems are laid down in ISO/IEC 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 FDI2
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. ISO/IEC 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 | ISO/IEC 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
Introduction
ISO/IEC
---------------------- Page: 6 ----------------------
ãã 11189: 19979 (E)
Information technology - International Standardized Profile
FDI2 - Directory Data Definitions - MHS Use of the
Directory
1 Scope
1.1 General
ISO/IEC 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 ISO/IEC
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:
·
·
·
· Storing and retrieving information on distribution lists for distribution list expansion.
1.2
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".
1.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 1).
Th e Directory
M HS DSA
App licati on
DUA
DSA
or User
DSA
Figure 1 - MHS use of the Directory Scenario
1
Position within the taxonomy
Determining information about the application entities supporting MTAs, MSs and UAs
MHS User capability assessment
Determining an MHS User's OR-Address from the directory name
FDISP ISO/IEC ISP ISO/IEC INTERNATIONAL STANDARDIZED PROFILE
---------------------- Page: 7 ----------------------
ISO/IEC FDISP 11189: 1999 (E) ãã
2
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 ISO maintain registers of currently valid International Standards and ISPs, and ITU-T maintains
2.1
ISO/IEC TR 10000-1: 19958, Information technology - Framework and taxonomy of International Standardized Profiles -
Part
ISO/IEC TR 10000-2: 19958, Information technology - Framework and taxonomy of International Standardized Profiles -
Part
ISO/IEC ISP 10616: 1995, Information technology - International Standardized Profile FDI11 - Directory data definitions -
2.2
ISO/IEC 9594-1: 1998, Information technology - Open Systems Interconnection - The Directory: Overview of concepts,
ISO/IEC 9594-2 : 1998, Information technology - Open Systems Interconnection - The Directory: Models. [See also
ISO/IEC 9594-5: 1998,
ISO/IEC 9594-6: 1998, Information technology - Open Systems Interconnection - The Directory: Selected attribute types.
ISO/IEC 9594-7: 1998, Information technology - Open Systems Interconn - The Directory: Selected object classes.
2.3
The following informative references to the 1990 edition of the directory standards are inc luded because the
object classes, attributes and matching rules specified in this International Standardized Profile can be used on
ISO/IEC 9594-1: 1990, Information technology - Open Systems Interconnection - The Directory - Part 1: Overview of
ISO/IEC 9594-2: 1990, Information technology - Open Systems Interconnection - The Directory - Part 2: Models. [ See also
ISO/IEC 9594-5: 1990, Information technology - Open Systems Interconnection - The Directory - Part 5: Protocol
ISO/IEC 9594-6: 1990, Information technology - Open Systems Interconnection - The Directory - Part 6: Selected attribute
ISO/IEC 9594-7: 1990. Information technology - Open Systems Interconnection - The Directory - Part 7: Selected object
NOTE - In the 1990 edition of ISO/IEC 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 d efinition itself.
2
classes. [See also Recommendation X.521 (1988)].
types. [See also Recommendation X.520 (1988)].
specifications [See also Recommendation X.519 (1988)].
Recommendation X.501 (1988)].
concepts, models and service. [See also Recommendation X.500 (1988)].
The contexts cannot. Directory systems conforming to the 1990 Directory standards.
informative references Directory Standards - 1990 edition
[See also Recommendation X.521 (1997)].
ection
[See also Recommendation X.520 (1997)].
commendation X.519 (1997)]. also Re
Information technology - Open Systems Interconnection - The Directory: Protocol specifications [See
Recommendation X.501 (1997)].
models and service. [See also Recommendation X.500 (1997)].
Directory Standards - 1998 edition
Common Directory Use (Normal).
2: Principles and Taxonomy for OSI profiles.
1: General principles and documentation framework.
ISP Framework Documents
published editions of its current Recommendations.
Normative References
ISO/IEC
---------------------- Page: 8 ----------------------
ãã ISP ISO/IEC 11189: 1997 1999
2.4
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
ISO/IEC 9594-1: 1995, Information technology - Open Systems Interconnection - The Directory: Overview of concept s,
ISO/IEC 9594-2: 1995, Information technology - Open Systems Interconnection - The Directory: Models. [See also
ISO/IEC 9594-5: 1995,
ISO/IEC 9594-6: 1995, Information technology - Open Systems Interconnection - The Directory: Selected attribute types.
ISO/IEC 9594-7: 1995, Information technology - Open Systems Interconnection - The Directory: Selected object classes.
2.5
ISO/IEC 10021-2: 19969, Information technology - Message Handling Systems (MHS) - Part 2: Overall architecture [See
69)].
ISO/IEC 10021-5: 19996, Information technology - Message Handling Systems (MHS) - Part 5: Message store abstract
95)].
NOTE 1 - This International Standardized Profile is based on the 1996 versions of ISO/IEC 10021 and X.400
NOTE 2 - In the 1990 edition of ISO/IEC 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
For the purposes of this International Standardized Profile, definitions apply as defined in the referenced
3.1 General
The following definitions are made in ISO/IEC ISP 10616:
Table 1 - Definitions used from ISO/IEC ISP 10616
Term
ISO/IEC ISP
Auxiliary object class
Structure Element
The following terms are defined for the purposes of this International Standardized Profile:
3
3.1.3
3.1.2 Structural object class
3.1.1
10616
Reference in
standards. In addition, the following terms are defined.
Definitions
Recommendations since the earlier versions are considered to be faulty.
service definition. [See also ITU-T Recommendation X.413 (199
also ITU-T Recommendation X.402 (199
Message Handling Systems Standards
[See also Recommendation X.521 (1995)].
[See also Recommendation X.520 (1995)].
also Recommendation X.519 (1995)].
Information technology - Open Systems Interconnection - The Directory: Protocol specifications [See
Recommendation X.501 (1995)].
models and service. [See also Recommendation X.500 (1995)].
The contexts cannot. Directory systems conforming to the 1995 Directory standards.
Directory Standards - 1995 edition informative references
(E) ISO/IEC
---------------------- Page: 9 ----------------------
ISO/IEC FDISP 11189: 1999 (E) ãã
3.1.1
A specification 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
3.2.
To specify the support level of schema elements for this International Standardized Profile, the following
terminology is defined.
3.2.1
3.2.1.1 General
Mandatory requirement for support. A feature (object class, attribute type and associated attribute
syntax, structure element, or matching rule , or context ) is supported by a DSA implementation if
as specified in this International Standardized Profile.
3.2.1.2
Support of object classes by a DSA conformant with FDI2 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
c) The entry contains no other than MUST CONTAIN and MAY CONTAIN attributes of its object
3.2.1.3
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
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
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 | ISO/IEC 9594 requirements as clarified in 9.3 of ISO/IEC ISP 10616.
NOTE - the word 'equality' has been added to the original FDI11 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 ISO/IEC 10021.
e) The DSA shall support the attribute for each supported object class which references that
attribute.
f) 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
4
and additional rules stated in clause 9 of ISO/IEC ISP 10616.
Rec. X.520 annex C (which is not an integral part of ISO/IEC 9594-6);
required;
A DSA conformant with FDI2 shall support an attribute type as follows:
Mandatory support for Attributes
classes.
b) The entry contains all MUST CONTAIN attributes of its object classes;
a) The entry lies within the DIT structure described in clause 6 and in A.6.5.1;
associated with supported object classes and the following conditions are fulfilled:
Mandatory support for Object Classes
the DSA is able to process the feature in accordance with the base standard, ISO/IEC ISP 10616 or
Mandatory support (m):
Support classification
standards which together support a significant optional area of DSA functionality.
Functional Group
ISO/IEC
---------------------- Page: 10 ----------------------
ãã ISP ISO/IEC 11189: 1997 1999
- 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 1993/95
Directory documents and the 1995/7 Message Handling System documents, Attribute Syntaxes are
implicitly defined in the definition of Attributes.
3.2.1.4
Mandatory support of a matching rule implies the DSA’s ability to perform matches according to
rules defined in ITU-T Rec. X.520 | ISO/IEC 9594-6 as well as the rules defined in annex D
subclause 12.4 and the additional rules stated in ISO/IEC 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
(refer to clause 6 of ISO/IEC ISP 10616). The DSA complies with a structure element for an entry
of a particular structural object class if:
c) its RDN is formed using the naming attribute(s).
3.2.1.6
A DSA shall be able to store a list of contexts associated with each value of an attribute. It shall be able
to supply all the associated context properties with each att ribute when the values of an attribute are
read. Furthermore, the DSA shall be capable of selecting values of an attribute based on properties of
3.2.2
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
3.2.3
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
The following abbreviations are defined in ISO/IEC 9594
Directory Information Base
DIT Directory Information Tree
Directory Service Agent
Directory
Relative Distinguished Name
5
RDN
User Agent DUA
DSA
Distinguished Name DN
DIB
Abbreviations
Conditional support (c)
specified as mandatory for support.
Optional support (o)
the associated contexts.
Mandatory support for Contexts
b) it is associated with the structural object class;
a) its superior entry complies with at least one of the superior structure elements;
Mandatory support for Structure Elements
Mandatory support for Matching Rules
NOTE
(E) ISO/IEC
---------------------- Page: 11 ----------------------
ISO/IEC FDISP 11189: 1999 (E) ãã
- is defined in ISO/IEC 10021 - 2
ISP International Standardized Profile - is defined in ISO/IEC TR 10000-1
The following abbreviation is defined in this Profile
FG
5
This International Standardized Profile states requirements placed upon DSA implementations to achieve
interworking. A claim of conformance to it is a claim that:
· 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
· all requirements in ISO/IEC ISP 10616 are satisfied;
· 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
5.1
For each implementation claiming conformance to profile FDI2 as specified in this International Standardized
Profile, a PICS shall be made available stating support or non-support of each option identified in this
International Standardized Profile. The scope of conformance to FDI2 is restricted to DSAs.
Implementations for which conformance to FDI2 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 (o) Object Classes, Attribute
5.2
Annex A specifies the basic requirements for support of object classes, attributes and associated attribute
syntaxes and matching rules for conformance to FDI2. 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
the tables in annex A. All implementations for which conformance to FDI2 is claimed shall support the basic
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
5.2.1
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
This specifies a set of non-exact match rules which are comparatively easy to implement.
5.2.3
This specifies a group of matching rules which involve matching on substrings.
5.3 Conformance to ISO/IEC ISP 10616
Conformance to FDI2 implies conformance to ISO/IEC ISP 10616 as a precondition.
6
The Substring Matching Rules Functional Group - SMR
The Additional Matching Rules Functional Group - AMR
The Distribution List Functional Group - DL
clauses summarise the functionality supported by each of the optional FGs.
requirements.
Basic Requirements and Functional Groups
Types and associated Attribute Syntaxes and Matching Rules are implemented.
Conformance Statement
the base standards.
implementations of both the 1990 and 1995 editions of the directory protocols;
Conformance
Functional Group
Distribution List DL
The following abbreviations are defined in other standards:
ISO/IEC
---------------------- Page: 12 ----------------------
ãã ISP ISO/IEC 11189: 1997 1999
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
equality matching is defined for that attribute type.
5.4
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:
·· The entry lies within the part of the scope of the minimum set of structure and naming
;
· 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;
· 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 ISO/IEC 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
In addition to the matching rules mandated by ISO/IEC 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
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:
·· The entry lies within the part of the scope of the minimum set of structure and naming
;
· 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 'DL' columns of the tables;
· The entry's attributes are part of the set of mandatory attribute
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.