SIST ETS 300 374-6:1999

SLOVENSKI STANDARD
01-julij-1999
Inteligentno omrežje (IN) - Prvi nabor zmožnosti (CS1) inteligentnega omrežja -
Jedrni aplikacijski protokol inteligentnega omrežja (INAP) - 6. del: Izjava o
skladnosti izvedbe protokola (PICS) - Proforma specifikacije za vmesnik med
funkcijo krmiljenja storitve (SCF) in funkcijo storitvenih podatkov (SDF)
Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core Intelligent
Network Application Protocol (INAP); Part 6: Protocol Implementation Conformance
Statement (PICS) proforma specification for the Service Control Function (SCF) - Service
Data Function (SDF) interface
Ta slovenski standard je istoveten z: ETS 300 374-6 Edition 1
ICS:
33.040.35 Telefonska omrežja Telephone networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 374-6
TELECOMMUNICATION September 1998
STANDARD
Source: SPS Reference: DE/SPS-03032-2
ICS: 33.020
Key words: IN, INAP, CS1, PICS
Intelligent Network (IN);
Intelligent Network Capability Set 1 (CS1);
Core Intelligent Network Application Protocol (INAP);
Part 6: Protocol Implementation Conformance Statement (PICS)
proforma specification for the Service Control Function (SCF) -
Service Data Function (SDF) interface
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: secretariat@etsi.fr - http://www.etsi.fr - http://www.etsi.org
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1998. All rights reserved.

Page 2
ETS 300 374-6: September 1998
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Standards Making Support Dept." at the address shown on the title page.

Page 3
ETS 300 374-6: September 1998
Contents
Foreword .5
Introduction.5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .7
3.1 Definitions .7
3.2 Abbreviations .8
4 Conformance to this PICS proforma specification .8
Annex A (normative): PICS proforma for ETS 300 374-5 .9
A.1 Guidance for completing the PICS proforma .9
A.1.1 Purposes and structure.9
A.1.2 Abbreviations and conventions.9
A.1.3 Instructions for completing the PICS proforma.11
A.2 Identification of the implementation.11
A.2.1 Date of the statement .11
A.2.2 Implementation Under Test (IUT) identification .11
A.2.3 System Under Test (SUT) identification .11
A.2.4 Product supplier.12
A.2.5 Client.12
A.2.6 PICS contact person.13
A.3 Identification of the protocol .13
A.4 PICS proforma tables.13
A.4.1 Global statement of conformance.13
A.4.2 System definition.14
A.4.2.1 System implementation.14
A.4.2.2 SDF implementation and/or system .14
A.4.2.3 SCF implementation and/or system .15
A.4.3 IN Directory information objects supported.15
A.4.4 Operations and extensibility supported (SDF) .15
A.4.4.1 Operations.15
A.4.4.2 Extensibility.16
A.4.5 Parameters (SDF).16
A.4.5.1 DirectoryBind Parameters .16
A.4.5.1.1 DirectoryBindArgument.16
A.4.5.1.2 DirectoryBindResult .17
A.4.5.1.3 DirectoryBindError .17
A.4.5.2 Search .17
A.4.5.2.1 SearchArgument.17
A.4.5.2.2 SearchResult .18
A.4.5.3 AddEntry.18
A.4.5.3.1 AddEntryArgument .18
A.4.5.3.2 AddEntryResult.18
A.4.5.4 RemoveEntry.19
A.4.5.4.1 RemoveEntryArgument .19
A.4.5.4.2 RemoveEntryResult.19
A.4.5.5 ModifyEntry.19

Page 4
ETS 300 374-6: September 1998
A.4.5.5.1 ModifyEntryArgument. 19
A.4.5.5.2 ModifyEntryResult . 20
A.4.5.6 Errors. 20
A.4.5.7 Common arguments. 21
A.4.5.8 Common results . 21
A.4.5.9 ServiceControls . 21
A.4.5.10 EntryInformationSelection. 22
A.4.5.11 EntryInformation . 22
A.4.5.12 FilterElements. 22
A.4.5.13 FilterItemElements. 23
A.4.6 Operations and extensibility supported (SCF). 23
A.4.6.1 Operations . 23
A.4.6.2 Extensibility. 24
A.4.7 Parameters (SCF). 24
A.4.7.1 DirectoryBind Parameters. 24
A.4.7.1.1 DirectoryBindArgument. 24
A.4.7.1.2 DirectoryBindResult . 25
A.4.7.1.3 DirectoryBindError. 25
A.4.7.2 Search . 26
A.4.7.2.1 SearchArgument . 26
A.4.7.2.2 SearchResult. 26
A.4.7.3 AddEntry . 27
A.4.7.3.1 AddEntryArgument. 27
A.4.7.3.2 AddEntryResult . 27
A.4.7.4 RemoveEntry . 27
A.4.7.4.1 RemoveEntryArgument. 27
A.4.7.4.2 RemoveEntryResult . 27
A.4.7.5 ModifyEntry . 28
A.4.7.5.1 ModifyEntryArgument. 28
A.4.7.5.2 ModifyEntryResult . 28
A.4.7.6 Errors. 29
A.4.7.7 Common Arguments. 29
A.4.7.8 Common Results . 30
A.4.7.9 Service Controls . 30
A.4.7.10 EntryInformationSelection. 30
A.4.7.11 EntryInformation . 31
A.4.7.12 FilterElements. 31
A.4.7.13 FilterItemElements. 31
A.4.8 Directory schema . 32
A.4.8.1 Supported object classes. 32
A.4.8.1.1 Standard object classes. 32
A.4.8.2 Supported attribute types. 32
A.4.8.2.1 Standard attribute types . 32
A.4.8.3 Standard matching rules. 33
A.4.8.4 Standard contexts. 33
A.4.8.5 Information framework. 33
A.4.8.5.1 Information framework object classes . 34
A.4.8.5.2 Information framework attributes . 34
A.4.8.5.3 Information framework matching rules. 34
A.4.8.6 Subschema administration . 34
A.4.8.6.1 Subschema administration object classes. 34
A.4.8.6.2 Subschema administration attributes. 35
A.4.8.6.3 Subschema administration matching rules . 35
A.4.8.7 Access control . 35
A.4.8.7.1 Access control object classes. 35
A.4.8.7.2 Access control attributes. 35
A.4.8.7.3 Access control matching rules . 35
History. 36

Page 5
ETS 300 374-6: September 1998
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols and
Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).
The present document is part 6 of a multi-part standard covering the Capability Set 1 (CS1) core
Intelligent Network Application Protocol (INAP) as described below:
Part 1: "Protocol specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma specification for Service
Switching Function (SSF), Specialized Resource Function (SRF) and Service Control
Function (SCF)";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification for Service Switching
Function (SSF) and Specialized Resource Function (SRF)";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
(PIXIT) proforma specification for Service Switching Function (SSF) and Specialized
Resource Function (SRF)";
Part 5: "Protocol specification for the Service Control Function (SCF) - Service Data Function (SDF)
interface";
Part 6: "Protocol Implementation Conformance Statement (PICS) proforma specification for
the Service Control Function (SCF) - Service Data Function (SDF) interface";
Part 9: "Test Suite Structure and Test Purposes (TSS&TP) specification for the Service Control
Function (SCF) to Service Switching Function (SSF) and the SCF to Specialized Resource
Function (SRF) interfaces".
NOTE: Parts 7 and 8 are currently not planned.
Transposition dates
Date of adoption of this ETS: 21 August 1998
Date of latest announcement of this ETS (doa): 31 December 1998
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 June 1999
Date of withdrawal of any conflicting National Standard (dow): 30 June 1999
Introduction
To evaluate conformance of a particular implementation, it is necessary to have a statement of which
capabilities and options have been implemented for a telecommunication specification. Such a statement
is called a Protocol Implementation Conformance Statement (PICS).
This ETS has been produced to facilitate the interconnection of telecommunication systems to provide
directory services as part of the core Intelligent Network Application Protocol (INAP). The set of all such
systems, together with the directory information which they hold, can be viewed as an integrated whole,
called the Directory. The information held by the Directory, collectively known as the Directory Information
Base (DIB), is typically used to facilitate communication between, with or about objects such as
application entities of the Intelligent Network (IN) Capability Set 1 (CS1) Service Control Function (SCF) -
Service Data Function (SDF) interface.

Page 6
ETS 300 374-6: September 1998
The Directory plays a significant role in Open Systems Interconnection (OSI), whose aim is to allow, with a
minimum of technical agreement outside of the interconnection standards themselves, the interconnection
of telecommunication systems:
- from different manufacturers;
- under different managements;
- of different levels of complexity; and
- of different ages.
Page 7
ETS 300 374-6: September 1998
1 Scope
This sixth part of ETS 300 374 provides the Protocol Implementation Conformance Statement (PICS)
proforma for the Intelligent Network (IN) Capability Set 1 (CS1) core Intelligent Network Application
Protocol (INAP) for the Service Control Function (SCF) - Service Data Function (SDF) interface as defined
in ETS 300 374-5 [1] in compliance with the relevant requirements and in accordance with the relevant
guidance given in ISO/IEC 9646-7 [9] and in ETS 300 406 [2].
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 374-5 (1996): "Intelligent Network (IN); Intelligent Network Capability
Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 5:
Protocol specification for the Service Control Function (SCF) - Service Data
Function (SDF) interface".
[2] ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol
and profile conformance testing specifications; Standardization methodology".
[3] ITU-T Recommendation X.501 (1997) | ISO/IEC 9594-2 (1997): "Information
technology - Open systems interconnection - The Directory: The Models".
[4] ITU-T Recommendation X.509 (1997) | ISO/IEC 9594-8 (1997): "Information
technology - Open systems interconnection - The Directory: Authentication
Framework".
[5] ITU-T Recommendation X.511 (1997) | ISO/IEC 9594-3 (1997): "Information
technology - Open systems interconnection - The Directory: Abstract Service
Definition".
[6] ITU-T Recommendation X.519 (1997) | ISO/IEC 9594-5 (1997): "Information
technology - Open systems interconnection - The Directory: Protocol
Specifications".
[7] ITU-T Recommendation X.520 (1997) | ISO/IEC 9594-6 (1997): "Information
technology - Open systems interconnection - The Directory: Selected Attribute
Types".
[8] ISO/IEC 9646-1: "Information technology - Open systems interconnection -
Conformance testing methodology and framework - Part 1: General concepts".
[9] ISO/IEC 9646-7: "Information technology - Open systems interconnection -
Conformance testing methodology and framework - Part 7: Implementation
Conformance Statements".
[10] ITU-T Recommendation Q.1218 (1995): "Interface Recommendation for
intelligent network CS-1".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
- terms defined in ETS 300 374-5 [1];
- terms defined in ISO/IEC 9646-1 [8] and in ISO/IEC 9646-7 [9].

Page 8
ETS 300 374-6: September 1998
In particular, the following terms defined in ISO/IEC 9646-1 [8] apply:
Protocol Implementation Conformance Statement (PICS): A statement made by the supplier of an
implementation or system claimed to conform to a given specification, stating which capabilities have
been implemented.
PICS proforma: A document, in the form of a questionnaire, which when completed for an
implementation or system becomes an PICS.
The following definitions also apply:
centralized DSA: A DSA that is not capable of holding knowledge information about other DSAs. Such a
DSA is not capable of returning referrals.
co-operating DSA: A DSA that is capable of holding knowledge references. Such a DSA is capable of
returning referrals, and may also be a chaining DSA.
chaining DSA: A co-operating DSA that is capable of invoking chained operations, functioning as a DSP
invoker. A chaining DSA is also a co-operating DSA.
For the INAP SCF-SDF interface, the DUA is the SCF, and the DSA is the SDF (this is a centralized DSA).
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
DSA Directory System Agent
DSP Directory System Protocol
DUA Directory User Agent
IUT Implementation Under Test
PICS Protocol Implementation Conformance Statement
SCF Service Control Function
SCS System Conformance Statement
SDF Service Data Function
SUT System Under Test
TBS To Be Supplied ("?" in the status has similar meaning)
4 Conformance to this PICS proforma specification
If it claims to conform to this PICS proforma specification, the actual PICS proforma to be filled in by a
supplier shall be technically equivalent to the text of the PICS proforma given in annex A, and shall
preserve the numbering/naming and ordering of the proforma items.
A PICS which conforms to this PICS proforma specification shall be a conforming PICS proforma
completed in accordance with the guidance for completion given in annex A, clause A.1.

Page 9
ETS 300 374-6: September 1998
Annex A (normative): PICS proforma for ETS 300 374-5
Notwithstanding the provisions of the copyright clause related to the text of this ETS, ETSI grants that
users of this ETS may freely reproduce the PICS proforma in this annex so that it can be used for its
intended purposes and may further publish the completed PICS.
A.1 Guidance for completing the PICS proforma
A.1.1 Purposes and structure
The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of
the requirements defined in ETS 300 374-5 [1] may provide information about the implementation in a
standardized manner.
The PICS proforma is subdivided into subclauses for the following categories of information:
- instructions for completing the PICS proforma;
- identification of the implementation;
- identification of the reference specification;
- PICS proforma tables;
- global statement of conformance;
- IN Directory information objects supported;
- operations and extensibility supported;
- parameters;
- Directory schema.
A.1.2 Abbreviations and conventions
The PICS proforma contained in this annex is comprised of information in tabular form in accordance with
the guidelines presented in ISO/IEC 9646-7 [9] and ETS 300 406 [2].
Item column
The item column contains a number which identifies the item in the table.
Item description column
The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It
implicitly means "is supported by the implementation?".
Status column
The following notations, defined in ISO/IEC 9646-7 [9], are used for the status column:
m mandatory - the capability is required to be supported.
o optional - the capability may be supported or not.
n/a not applicable - in the given context, it is impossible to use the capability.
i irrelevant or out-of-scope - this capability is outside the scope of this
specification , and hence irrelevant and not subject to conformance testing for
this specification.
x prohibited (excluded) - there is a requirement not to use this capability in the
given context.
o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is
an integer which identifies an unique group of related optional items and the
logic of their selection which is defined immediately following the table.

Page 10
ETS 300 374-6: September 1998
ci conditional - the requirement on the capability ("m", "o", "x" or "n/a") depends on
the support of other optional or conditional items. "i" is an integer identifying an
unique conditional status expression which is defined immediately following the
table.
c:o conditional optional - the capability may be supported or not if the hierarchically
preceding capability is supported.
c:m conditional mandatory - the capability is required to be supported if the
hierarchically preceding capability is supported.
Reference column
The reference column gives reference to the requirements defined in ETS 300 374-5 [1], except where
explicitly stated otherwise.
Support column
The support column shall be filled in by the supplier of the implementation. The following common
notations, defined in ISO/IEC 9646-7 [9], are used for the support column:
Y or y supported by the implementation.
N or n not supported by the implementation.
N/A, n/a or - no answer required (allowed only if the status is n/a or i, directly or after
evaluation of a conditional status).
If this PICS proforma is completed in order to describe a multiple-profile support in a system, it is
necessary to be able to answer that a capability is supported for one profile and not supported for another.
In that case, the supplier shall enter the unique reference to a conditional expression, preceded by "?"
(e.g. ?3). This expression shall be given in the cell provided at the bottom of the table. It uses predicates
defined in the SCS, each of which refers to a single profile and which takes the value TRUE if and only if
that profile is to be used.
EXAMPLE: ?3: IF prof1 THEN Y ELSE N
It is also possible to provide a comment to an answer in the space provided at the bottom of the table.
NOTE: As stated in ISO/IEC 9646-7 [9], support for a PDU requires the ability to parse all valid
parameters of that PDU. Supporting a PDU while having no ability to parse a valid
parameter is non-conformant. Support for a parameter on a PDU means that the
semantics of that parameter are supported.
Values allowed column
The values allowed column contains the values or the ranges of values allowed.
Values supported column
The values supported column shall be filled in by the supplier of the implementation. In this column, the
values or the ranges of values supported by the implementation shall be indicated.
References to items
For each possible item answer (answer in the support column) within the PICS proforma exists a unique
reference, used, for example, in the conditional expressions. It is defined as the table identifier, followed
by a solidus character "/", followed by the item number in the table. If there is more than one support
column in a table, the columns shall be discriminated by letters (a, b, etc.), respectively.
EXAMPLE 1: A.5/4 is the reference to the answer of item 4 in table 5 of annex A.

Page 11
ETS 300 374-6: September 1998
EXAMPLE 2: A.6/3b is the reference to the second answer (i.e. in the second support column)
of item 3 in table 6 of annex A.
Prerequisite line
A prerequisite line takes the form: Prerequisite: .
A prerequisite line after a clause or table title indicates that the whole clause or the whole table is not
required to be completed if the predicate is FALSE.
A.1.3 Instructions for completing the PICS proforma
The supplier of the implementation shall complete the PICS proforma in each of the spaces provided.
More detailed instructions are given at the beginning of the different subclauses of the PICS proforma.
A.2 Identification of the implementation
Identification of the Implementation Under Test (IUT) and the system in which it resides (the System
Under Test (SUT)) should be filled in so as to provide as much detail as possible regarding version
numbers and configuration options.
The product supplier information and client information should both be filled in if they are different.
A person who can answer queries regarding information supplied in the PICS should be named as the
contact person.
A.2.1 Date of the statement
.........................................................................................................................................................................
A.2.2 Implementation Under Test (IUT) identification
IUT name:
.........................................................................................................................................................................
.........................................................................................................................................................................
IUT version:
.........................................................................................................................................................................
A.2.3 System Under Test (SUT) identification
SUT name:
.........................................................................................................................................................................
.........................................................................................................................................................................
Hardware configuration:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................

Page 12
ETS 300 374-6: September 1998
Operating system:
........................................................................................................................................................................
A.2.4 Product supplier
Name:
........................................................................................................................................................................
Address:
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................
Telephone number:
........................................................................................................................................................................
Facsimile number:
........................................................................................................................................................................
E-mail address:
........................................................................................................................................................................
Additional information:
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................
A.2.5 Client
Name:
........................................................................................................................................................................
Address:
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................
Telephone number:
........................................................................................................................................................................
Facsimile number:
........................................................................................................................................................................

Page 13
ETS 300 374-6: September 1998
E-mail address:
.........................................................................................................................................................................
Additional information:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................
A.2.6 PICS contact person
Name:
.........................................................................................................................................................................
Telephone number:
.........................................................................................................................................................................
Facsimile number:
.........................................................................................................................................................................
E-mail address:
.........................................................................................................................................................................
Additional information:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................
A.3 Identification of the protocol
This PICS proforma applies to the following standard:
ETS 300 374-5 (1996): "Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core
Intelligent Network Application Protocol (INAP); Part 5: Protocol Specification for the Service Control
Function (SCF) - Service Data Function (SDF) interface".
A.4 PICS proforma tables
An explicit answer shall be entered, in each of the support or supported column boxes provided, using the
notation described in subclause A.1.2.
A.4.1 Global statement of conformance
Are all mandatory capabilities implemented? (Yes/No) .
NOTE: Answering "No" to this question indicates non-conformance to ETS 300 374-5 [1]
specification. Non-supported mandatory capabilities are to be identified in the PICS,
with an explanation of why the implementation is non-conforming, on pages attached
to the PICS proforma.
Page 14
ETS 300 374-6: September 1998
A.4.2 System definition
A.4.2.1 System implementation
Table A.1: Identification of the system
Item Question Status Support
1 The supplied implementation is an SDF o.1
2 The supplied implementation is an SCF o.1
o.1 At least on of the implementations should be supplied.
A.4.2.2 SDF implementation and/or system
Table A.2: SDF implementation and/or system
Prerequisite: A.1/1
Item Question Reference Status Support
1 Are all mandatory First-level SDF/DSA [3] ; 18.5 m
requirements implemented?
(ITU-T Recommendation X.501, 18.5, page 73)
2 Supported Security none [3] ; 15 m
3 Level(s) simple [3] ; 15 o
4 Does the SDF follow the rules of extensibility as [6] ; 7.5 m
defined in section 7.5 of
ITU-T Recommendation X.519?
5 Is the alias mechanism implemented? [3] ; 9.3 m
(ITU-T Recommendation X.501)
6 Does the SDF support the inDirectoryAccessAC [10] ; o
application-context? 2.2.2.2.2.2.1
(ITU-T Recommendation Q.1218)
7 Supported Access Simplified Access [3] ; 16 o
Controls Control
8 (ITU-T Recommendation Basic Access Control [3] ; 16 o
X.501, 16)
9 Is the SDF capable of supporting collective [3] ; 12.4 o
attributes? (ITU-T Recommendation X.501, 12.4)
10 Is the SDF capable of supporting operational [3] ; 12.4 m
attributes? (ITU-T Recommendation X.501, 12.4)
11 Is the SDF capable of supporting hierarchical [3] ; 12.4 o
attributes? (ITU-T Recommendation X.501, 12.4)
12 Is the SDF capable of supporting auxiliary object [3] ; 12.3 o
classes? (ITU-T Recommendation X.501, 12.3)
13 Is the SDF capable of supporting the subschema [3] ; 14 o
for its portion of the DIT?
(ITU-T Recommendation X.501, 14)

Page 15
ETS 300 374-6: September 1998
A.4.2.3 SCF implementation and/or system
Table A.3: SCF implementation and/or system
Prerequisite: A.1/2
Item Question Reference Status Support
1 Is the inDirectoryAccessAC application-context [10] ;2.2.2.2.2.2.1 m
supported?
2 Supported Security none [3] ; 15 m
3 Level(s) simple [3] ; 15 o
4 Does the SCF/DUA follow the rules of [6] ; 7.5 m
extensibility as define in section 7.5 of
ITU-T Recommendation X.519?
A.4.3 IN Directory information objects supported
Table A.4: Application contexts supported
Item Name Reference Status Support Values
Allowed Supported
1 directoryAccessAC [6] ; 7.2.1 m in-ds*) 3 1
*) in-ds = ITU-T Recommendation Q.1218 sdf-object
Table A.5: Abstract syntaxes supported
Item Name Reference Status Support Values
Allowed Supported
1 directoryOperationsAS [10] ; 2.2.2.2.2.1.1 m in-ds*) 5 1
2 directoryBindingAS [10] ; 2.2.2.2.2.1.1 m in-ds*) 5 2
*) in-ds = ITU-T Recommendation Q.1218 sdf-object
A.4.4 Operations and extensibility supported (SDF)
A.4.4.1 Operations
Table A.6: Operations supported (SDF)
Prerequisite A.1/1 -- if SDF implemented
Item Operation Receiving (SDF)
Reference Status Support
1 DirectoryBind [5] ; 8.1 m
2 DirectoryUnbind [5] ; 8.2 m
3 Search [5] ; 10.2 m
4 AddEntry [5] ; 11.1 m
5 RemoveEntry [5] ; 11.2 m
6 ModifyEntry [5] ; 11.3 m
Page 16
ETS 300 374-6: September 1998
A.4.4.2 Extensibility
This table defines a number of extensions which are available in the 1993 edition of the Directory. The
supplier of the implementation shall indicate in the following table, which conformance is claimed.
Table A.7: Extensibility
Prerequisite A.1/1 -- if SDF implemented
Item Parameters Receiving (SDF)
Reference Status Support
1 subentries [5] ; 7.3.1 o
2 copyShallDo [5] ; 7.3.1 i
3 attributeSizeLimit [5] ; 7.3.1 o
4 extraAttributes [5] ; 7.3.1 o
5 modifyRightsRequest [5] ; 7.3.1 i
6 pagedResultsRequest [5] ; 7.3.1 i
7 matchedValuesOnly [5] ; 7.3.1 m
8 extendedFilter [5] ; 7.3.1 o
9 targetSystem [5] ; 7.3.1 i
10 useAliasOnUpdate [5] ; 7.3.1 m
11 newSuperior [5] ; 7.3.1 i
12 useContexts [10] ; 2.2.2.4.6 m
13 reverseMatch [10] ; 2.2.2.4.6 m
14 selectionOnModify [10] ; 2.2.2.4.6 m
15 extendedEntryMods [10] ; 2.2.2.4.6 m
A.4.5 Parameters (SDF)
This clause needs only to be completed if SDF is implemented.
A.4.5.1 DirectoryBind Parameters
A.4.5.1.1 DirectoryBindArgument
Table A.8: DirectoryBindArgument Parameters (SDF)
implemented
Prerequisite A.1/1 -- if SDF
Item Parameter
Reference Status Support Values
Allowed Supported
1 DirectoryBindArg [5] ; 8.1.1 m
1.1 credentials [5] ; 8.1.1 c:m
1.1.1 simple [5] ; 8.1.1 c802
1.1.1.1 name [5] ; 8.1.1 c:m
1.1.1.2 validity [5] ; 8.1.1 c:m
1.1.1.3 password [5] ; 8.1.1 c:m
1.1.1.3.1 unprotected [5] ; 8.1.1 c:m
1.1.1.3.2 protected [5] ; 8.1.1 c:m
1.2 versions [5] ; 8.1.1 c:m v1
c802: IF A.2/3 then m else N/A --simple security

Page 17
ETS 300 374-6: September 1998
A.4.5.1.2 DirectoryBindResult
Table A.9: DirectoryBindResult Parameters (SDF)
Prerequisite A.1/1 -- if SDF implemented
Item Parameter
Reference Status Support Values
Allowed Supported
1 DirectoryBindResult [5] ; 8.1.1 m
1.1 credentials [5] ; 8.1.1 c:m
1.1.1 simple [5] ; 8.1.1 c902
1.1.1.1 name [5] ; 8.1.1 c:m
1.1.1.2 validity [5] ; 8.1.1 c:m
1.1.1.3 password [5] ; 8.1.1 c:m
1.1.1.3.1 unprotected [5] ; 8.1.1 c:m
1.1.1.3.2 protected [5] ; 8.1.1 c:m
1.2 versions [5] ; 8.1.1 c:m v1
c902: IF A.2/3 then m else N/A --simple security
A.4.5.1.3 DirectoryBindError
Table A.10: DirectoryBindError Parameters (SDF)
Prerequisite A.1/1 -- if SDF implemented
Item Parameter
Reference Status Support Values
Allowed Supported
1 DirectoryBindError [5] ; 8.1.1 m
1.1 versions [5] ; 8.1.1 c:m d({v1})
1.2 ServiceError [5] ; 8.1.1 c:m 2
1.3 SecurityError [5] ; 8.1.1 c:m 1,2,7
A.4.5.2 Search
A.4.5.2.1 SearchArgument
Table A.11: SearchArgument Parameters (SDF)
Prerequisite A.1/1 AND A.27/3 then m else N/A -- if SDF and Search implemented
Item Parameter
Reference Status Support Values
Allowed Supported
1 SearchArgument [5] ; 10.2.1 m
1.1 SIGNED SearchArgument [5] ; 10.2.1 c:o
1.2 baseObject [5] ; 10.2.1 c:m d(baseobject)
1.3 subset [5] ; 10.2.1 c:m
1.4 filter [5] ; 10.2.1 c:m
1.5 searchAliases [5] ; 10.2.1 c:m
1.6 selection [5] ; 10.2.1 c:m d({})
1.7 matchedValuesOnly [5] ; 10.2.1 c1101 d(FALSE)
1.8 CommonArguments [5] ; 7.3 c:m
c1101: IF A.28/7 then m else N/A --

Page 18
ETS 300 374-6: September 1998
A.4.5.2.2 SearchResult
Table A.12: SearchResult Parameters (SDF)
Prerequisite A.1/1 AND A.27/3 then m else N/A -- if SDF and Search implemented
Item Parameter
Reference Status Support Values
Allowed Supported
1 SearchResult [5] ; 10.2.1 m
1.1 SIGNED SearchResult [5] ; 10.2.1 c:o
1.2 searchInfo [5] ; 10.2.1 c:m
1.2.1 name [5] ; 10.2.1 c:o
1.2.2 entries [5] ; 10.2.1 c:m
1.2.3 PartialOutcome-Qualifier [5] ; 10.2.1 c:o
1.2.3.1 limitProblem [5] ; 10.1.3 c:o
1.2.3.2 unavailableCriticalExt [5] ; 10.1.3 c:m
1.2.4 CommonResults [5] ; 7.4 c:m
A.4.5.3 AddEntry
A.4.5.3.1 AddEntryArgument
Table A.13: AddEntryArgument Parameters (SDF)
Prerequisite A.1/1 AND A.27/4 then m else N/A -- if SDF and AddEntry implemented
Item Parameter
Reference Status Support Values
Allowed Supported
1 AddEntryArgument [5]
...