Previous section.

DCE 1.1: Directory Services
Copyright © 1997 The Open Group

Conformance Statement for GDS

This chapter specifies the requirements for conforming GDS implementations. The specification is based on the Protocol Implementation Conformance Statement (PICS) Proformas for X.500 and the related protocol stack.

The following definitions apply to the contents of this chapter:

Notations and Abbreviations

In order to enhance the readability of the tables in this chapter, the following notations and abbreviations are used:

Status column

This column indicates the requirements of the Open Systems Testing Consortium PICS Proforma for DAP/DUA and DAP/DSA.

M (mandatory)
The operation or protocol element is a mandatory requirement for static conformance to the referenced capability.

O (optional)
The operation is an optional requirement for static conformance to the referenced capability.

- (not applicable)
There is no static requirement associated with the related item.

Support column

This column indicates whether or not the item is supported by GDS, or if the conformance statement is not applicable. It contains one of the following abbreviations:

Y (supported)
The item is supported by GDS.

N (not supported)
The item is not supported by GDS.

- (not applicable)
The conformance statement is either not applicable or not required.

Value column

The value or range of values in this column shall be implemented where relevant.

Note:
The Protocol Element column in the Directory Access Protocol (DAP) tables (or, similarly, the first column in other tables) sometimes employs indentation to indicate subordination, as follows:

* (bullet)
indicates second level

- (dash)
indicates third level

simple indentation
indicates fourth and further levels.

Where subordination is indicated, the description of the superior element takes precedence over the subordinate element.

Directory Protocol Implementation Conformance

The Protocol Implementation Conformance Statement Proformas (PICS) for the Global Directory Service (GDS) consists of descriptions of the capabilities and options that are supported by the Directory User Agent (DUA) and Directory Service Agent (DSA) of the GDS. The PICS is designed for conformance test purposes. The PICS used for the X.500 protocols (ISO 9594-5) is based on the ones available from the Open Systems Testing Consortium (OSTC). Their scope is the DUA accessing the DSA in a stand-alone environment.

The PICS does not include statements about:

There are no PICS available for the Directory System Protocol (DSP). The PICS used for upper OSI layers in X.500 (ACSE, ROSE, Presentation, Session) are based on ISO and CCITT work (see X.500 Services and Protocols ).

Support of Attribute Syntaxes, Attribute Types and Object Classes

Attribute syntaxes are defined in X.520 Attribute Syntaxes for X.520, X.402 Attribute Syntaxes for X.402, and Private Attribute Syntaxes for those that are private to GDS.

For explanations of the abbreviations used in the following tables, see Notations and Abbreviations .

Attribute Syntax Status Support
Undefined Syntax - Y
Distinguished Name O Y
Object Identifier Syntax O Y
Case Exact String O Y
Case Ignore String O Y
Printable String O Y
Numeric String O Y
Case Ignore List O Y
Boolean Syntax - Y
Integer Syntax - Y
Octet String O Y
UTC Time - Y
Telephone Number Syntax O Y
Search Guide Syntax - Y
Postal Address Syntax O Y
Telex Number Syntax O Y
Teletex Terminal Identifier Syntax O Y
FAX Number Syntax O Y
Preferred Delivery Method Syntax O Y
Presentation Address Syntax O Y
Country Name Syntax - Y
Password Syntax - Y
Certificate Syntax - Y
Certificate Pair Syntax - Y
Certificate List Syntax - Y

Table: X.520 Attribute Syntaxes

Attribute Syntax Support
MHS DL Submit Permission Syntax Y
MHS O/R Address Syntax Y
MHS O/R Name Syntax Y
MHS Preferred Delivery Method Syntax Y

Table: X.402 Attribute Syntaxes

Attribute Syntax Support Definition
Access Control List Syntax Y In addition to authentication, access protection is implemented for each object at attribute level.
ASN1 Y This dummy-syntax may be used for all attributes whose syntax is not supported by the DSA. Attribute values are not decoded from ASN.1 representation to local format. No syntax checking is performed and no matching is allowed. This definition is the same as for ANY in ISO 8824.
Case Ignore IA5-String Y The valid character set is IA5-String for this syntax. Matching is as defined for Case Ignore String.

Table: Private Attribute Syntaxes

Attribute types are defined in X.520 Attribute Types for X.520, X.402 Attribute Types for X.402, and Private Attribute Types for those that are private to GDS.

The following abbreviations are used in X.520 Attribute Types to Private Attribute Types inclusive:

Max Nbr.
The maximum number of attribute values the implementation accepts. A U in this field means unlimited.

The values in this column are the values in the default GDS schema. This schema can be modified using GDS administration tools.

Max Size
The maximum size (in octets) the implementation accepts. The maximum size can be expressed either as a maximum number of octets (here 180), or as a maximum number of lines (6 for this standard) of a given maximum of octets per line (here 30 for either T61 String or Printable String).

Table: X.520 Attribute Types

  Standard Implemented
  _ _
Attribute Type Max Max Max Max Support
  Nbr. Size Nbr. Size  
System Object-Class     U 28 Y
Attribute Types Aliased-Object-Name 1   1 1024 Y
  Knowledge-Information     U 1024 Y
Labeling Common-Name   64 2 64 Y
Attribute Types Surname   64 2 64 Y
  Serial-Number   64 2 64 Y
Geographical Country-Name 1 1 2 Y
Attribute Types Locality-Name   128 2 128 Y
  State-or-Province-Name   128 2 128 Y
  Street-Address   128 2 128 Y
Organizational Organization-Name   64 2 64 Y
Attribute Types Org.-Unit-Name   64 2 64 Y
  Title   64 2 64 Y

  Standard Implemented
  _ _
Attribute Type Max Max Max Max Support
  Nbr. Size Nbr. Size  
Explanatory Description   1024 U 1024 Y
Attribute Types Search-Guide     U 256 Y
  Business-Category     2 128 Y
Postal Addressing Postal-Address   6 2 180 Y
Attribute Types T61-String   30 30 30 Y
  Printable-String   30 30 30 Y
  Postal-Code   40 2 40 Y
  Post-Office-Box   40 2 40 Y
  Phys.-Deliv.-Office-Name   128 2 128 Y
Telecommunications Telephone-Number   32 U 32 Y
Addressing Telex-Number     U 26 Y
Attribute Types Telex-Number   14 14 14 Y
  Country-Code   4 4 4 Y
  Answerback   8 8 8 Y
  TTX-Terminal-Identifier     U   Y
  Teletex-Terminal   1024   1024 Y
  Parameters         Y
  Fax-Telephone-Number     U 37 Y
  Telephone-Number   32     Y
  Parameters         Y
  X121-Address   15 U 15 Y
  Internat.-ISDN-Number   16 U 16 Y
  Registered-Address   6 2 180 Y
  T61-String   30 30 30 Y
  Printable-String   30 30 30 Y
  Destination-Indicator   128 2 128 Y
Preferences Preferred-Delivery-Method 1   1 40 Y
Attribute Types            
OSI Application Presentation-Address     1 268 Y
Attribute Types Suppl.-Applic.-Context     2 28 Y
Relational Member     U 1024 Y
Attribute Types Owner     U 1024 Y
  Role-Occupant     U 1024 Y
  See-Also     U 1024 Y
Security User-Password   128 2 128 Y
Attribute Types User-Certificate   3024 0 3024 Y
  CA-Certificate   3024 0 3024 Y
  Authority-Revocation-List   32503 0 32503 Y
  Certificate.-Revoc.-List   32503 0 32503 Y
  Cross-Certificate-Pair   6056 0 6056 Y

§
The size of a Country-Name value must be precisely 2.


  Standard Implemented
  _ _
Attribute Type Max Max Max Max Support
  Nbr. Size Nbr. Size  
MHS Attributes MHS-Deliv.-Cont.Length 1 4 1 4 Y
  MHS-Deliv.-Cont.-Types     4 28 Y
  MHS-Deliverable-EITs     8 28 Y
  MHS-DL-Members     U 3596 Y
  MHS-DL-Submit-Permission     U 3604 Y
  MHS-Message-Store 1   1 1024 Y
  MHS-OR-Address     U 2564 Y
  MHS-Pref.-Deliv.-Meth. 1   1 40 Y
  MHS-Supp.-Autom.-Action     4 28 Y
  MHS-Supp.-Content-Types     4 28 Y
  MHS-Supp.-Optional-Attr.     U 28 Y

Table: X.402 Attribute Types

    Max Max  
Attribute Type Syntax Nbr. Size Support
Master-Knowledge Distinguished Name 1 1024 Y
Access-Control-List Access Control List Syntax 1 20500 Y
Time-Stamp UTC Time 1 18 Y
Structure-Rule-Table Printable String U 29 Y
Object-Class-Table Printable String U 397 Y
Attribute-Table Printable String U 101 Y
CDS-Cell Octet String 1 284 Y
CDS-Replica Octet String 1 905 Y
Principal-Name Printable String 1 1024 Y
Authentication-Mechanism Integer Syntax 4 4 Y
Alternate-Address Octet String 1 800 Y

Table: Private Attribute Types

Object classes are listed in X.521 Object Classes for X.521, X.402 Object Classes for X.402, and Other Implemented Object Classes for object classes that are private to GDS.

Object Class Status Support
Top - Y
Alias (or subclass of alias) O Y
Country O Y
Locality O Y
Organization O Y
Organizational-Unit O Y
Person - Y
Organizational-Person O Y
Organizational-Role - Y
Group-of-Names O Y
Residential-Person - Y
Application-Process - Y
Application-Entity - Y
Directory-Service-Agent - Y
Device - Y
Strong-Auth.-User - Y
Certification-Authority - Y

Table: X.521 Object Classes

Object Class Support
MHS-Distribution-List Y
MHS-Message-Store Y
MHS-Mess-Transfer-Agent Y
MHS-User Y
MHS-User-Agent Y

Table: X.402 Object Classes

Name Subclass of Must Contain May Contain
GDS-Top Top   Master-Knowledge
      Access-Control-List
Schema GDS-Top Common-Name Time-Stamp
      Structure-Rule-Table
      Object-Class-Table
      Attribute-Table

Table: Other Implemented Object Classes

DAP Protocol Implementation Conformance

Global Statement of Conformance for DAP shows the global conformance statement for the Directory Access Protocol (DAP). Bind, unbind and directory operations are included.

The following tables are also included in the DAP conformance statement:

For explanations of the abbreviations used in the following tables, see Notations and Abbreviations .

Operation Status Support
DirectoryBind M Y
DirectoryUnbind M Y
Read M Y
Compare M Y
Abandon M Y
List M Y
Search M Y
AddEntry M Y
RemoveEntry M Y
ModifyEntry M Y
ModifyRDN M Y

Table: Global Statement of Conformance for DAP

Various Extra Requirements contains the conformance requirements for elements of the Directory Access Service beyond or outside the requirements for the DAP.

  Status Support
Can the DSA contain Alias entries, and handle them appropriately? O Y
Can the DSA contain Replicated entries, and handle them appropriately? O Y
(ROSE) Does the DSA support operation Class 2 (asynchronous operations)? M Y
Does the DSA have the capability to act as a first level DSA? - Y

Table: Various Extra Requirements

  Status Support
Does the DSA support Signing of:    
arguments - N
results - N

Table: Requirements for Signing

  DUA DSA
  _ _
Protocol Element Transmit Receive Transmit Receive
  _ _ _ _
  Status Support Status Support Status Support Status Support
DirectoryBind Argument M Y - - - - M Y
* credentials O Y - - - - O Y
- simple O Y - - - - O Y
name M Y - - - - M Y
validity - N - - - - - N
time1 - N - - - - - N
time2 - N - - - - - N
random1 - N - - - - - N
random2 - N - - - - - N
password O Y - - - - O Y
- strong - N - - - - - N
- external procedure - N - - - - - N
* versions M Y - - - - M Y
DirectoryBind Results - - M Y M Y - -
* credentials - - O Y O Y - -
- simple - - O Y O Y - -
name - - M Y M Y - -
validity - - - N - N - -
time1 - - - N - N - -
time2 - - - N - N - -
random1 - - - N - N - -
random2 - - - N - N - -
password - - O Y O N - -
- strong - - - N - N - -
- external procedure - - - N - N - -
* versions - - M Y M Y - -
DirectoryBind Error - - M Y M Y - -
* versions - - O Y O Y - -
* Service-Error - - M Y M Y - -
- unavailable - - M Y M Y - -
* Security-Error - - M Y M Y - -
- inappropriate-authentication - - M Y M Y - -
- invalid-credentials - - M Y M Y - -

Table: Requirements on DirectoryBind

  DUA DSA
  _ _
Protocol Element Transmit Receive Transmit Receive
  _ _ _ _
  Status Support Status Support Status Support Status Support
DirectoryUnbind Argument - - - - - - - -
DirectoryUnbind Result - - - - - - - -

Table: Requirements on DirectoryUnbind

No conformance requirements are specified for DirectoryUnbind.

Directory Operations

  DUA DSA
  _ _
Protocol Element Transmit Receive Transmit Receive
  _ _ _ _
  Status Support Status Support Status Support Status Support
Read Argument M Y - - - - M Y
* Object M Y - - - - M Y
* Entry-Information-Selection M Y - - - - M Y
* Common Arguments M Y - - - - M Y
Read Result - - M Y M Y - -
* Entry-Information - - M Y M Y - -
- Object-Name - - M Y M Y - -
- From-Entry - - O Y O Y - -
- SET OF CHOICE - - M Y M Y - -
Attribute-Type - - M Y M Y - -
Attribute - - M Y M Y - -
* Common-Results - - M Y M Y - -

Table: Requirements on the Read Operation

  DUA DSA
  _ _
Protocol Element Transmit Receive Transmit Receive
  _ _ _ _
  Status Support Status Support Status Support Status Support
Compare Argument M Y - - - - M Y
* Object M Y - - - - M Y
* Purported M Y - - - - M Y
* Common Arguments M Y - - - - M Y
Compare Result - - M Y M Y - -
* Object-Name - - M Y M Y - -
* Matched - - M Y M Y - -
* From-Entry - - M Y M Y - -
* Common-Results - - M Y M Y - -

Table: Requirements on the Compare Operation

  DUA DSA  
  _ _  
Protocol Element Transmit Receive Transmit Receive Comment
  _ _ _ _  
  Status Support Status Suppor. Status Support Status Support  
Abandon Argument M N - - - - M Y -
* Invoke-ID M N - - - - M Y -
Abandon Result - - M N M Y - - The DSA returns an Abandon-Failed error with Problem cannot-abandon.

Table: Requirements on the Abandon Operation

  DUA DSA
  _ _
Protocol Element Transmit Receive Transmit Receive
  _ _ _ _
  Status Support Status Support Status Support Status Support
List Argument M Y - - - - M Y
* Object M Y - - - - M Y
* Common Arguments M Y - - - - M Y
List Result - - O Y O Y - -
* List-Info - - M Y M Y - -
- Object-Name - - M Y M Y - -
- Subordinates - - M Y M Y - -
RDN - - M Y M Y - -
Alias-Entry - - O Y O Y - -
From-Entry - - O Y O Y - -
- Partial-Outcome-Qualifier - - M Y M Y - -
Limit-Problem - - M Y M Y - -
time-limit-exceeded - - O Y O Y - -
size-limit-exceeded - - O Y O Y - -
administrative-limit-exceeded - - O Y O Y - -
Unexplored - - - Y - Y - -
Unavailable-Crit-Ext - - - N - N - -
- Common-Results - - M Y M Y - -
* Uncorrelated-List-Info - - O N O N - -

Table: Requirements on the List Operation

  DUA DSA
  _ _
Protocol Element Transmit Receive Transmit Receive
  _ _ _ _
  Status Support Status Support Status Support Status Support
Search Argument M Y - - - - M Y
* Object M Y - - - - M Y
* Subset M Y - - - - M Y
* Filter M Y - - - - M Y
- Filter-Item M Y - - - - M Y
equality M Y - - - - M Y
substrings M Y - - - - M Y
greater-or-equal M Y - - - - M Y
less-or-equal M Y - - - - M Y
present M Y - - - - M Y
approximate-match M Y - - - - M Y
- and M Y - - - - M Y
- or M Y - - - - M Y
- not M Y - - - - M Y
* Search-Aliases M Y - - - - M Y
* Selection M Y - - - - M Y
* Common Arguments M Y - - - - M Y
Search Result - - M Y M Y - -
* Search-Info - - M Y M Y - -
- Object-Name - - M Y M Y - -
- Entries - - M Y M Y - -
SET OF Entry-Information - - M Y M Y - -
Object-Name - - O Y O Y - -
From-Entry - - O Y O Y - -
SET OF CHOICE - - M Y M Y - -
Attribute-Type - - M Y M Y - -
Attribute - - M Y M Y - -
- Partial-Outcome-Qualifier - - M Y M Y - -
Limit-Problem - - M Y M Y - -
Unexplored - - - Y - Y - -
Unavailable-Crit-Ext - - - N - N - -
- Common-Results - - M Y M Y - -
* Uncorrelated-Search-Info - - - N - N - -

Table: Requirements on the Search Operation

  DUA DSA
  _ _
Protocol Element Transmit Receive Transmit Receive
  _ _ _ _
  Status Support Status Support Status Support Status Support
AddEntry Argument M Y - - - - M Y
* Object M Y - - - - M Y
* Entry M Y - - - - M Y
* Common Arguments M Y - - - - M Y
AddEntry Result M Y - - - - M Y

Table: Requirements on the AddEntry Operation

  DUA DSA
  _ _
Protocol Element Transmit Receive Transmit Receive
  _ _ _ _
  Status Support Status Support Status Support Status Support
RemoveEntry Argument M Y - - - - M Y
* Object M Y - - - - M Y
* Common Arguments M Y - - - - M Y
RemoveEntry Result M Y - - - - M Y

Table: Requirements on the RemoveEntry Operation

  DUA DSA
  _ _
Protocol Element Transmit Receive Transmit Receive
  _ _ _ _
  Status Support Status Support Status Support Status Support
ModifyEntry Argument M Y - - - - M Y
* Object M Y - - - - M Y
* Changes M Y - - - - M Y
- ADD_ATTRIBUTE M Y - - - - M Y
- REMOVE_ATTRIBUTE M Y - - - - M Y
- ADD_VALUES M Y - - - - M Y
- REMOVE_VALUES M Y - - - - M Y
* Common Arguments M Y - - - - M Y
ModifyEntry Result M Y - - - - M Y

Table: Requirements on the ModifyEntry Operation

  DUA DSA
  _ _
Protocol Element Transmit Receive Transmit Receive
  _ _ _ _
  Status Support Status Support Status Support Status Support
ModifyRDN Argument M Y - - - - M Y
* Object M Y - - - - M Y
* New-RDN M Y - - - - M Y
* Delete-Old-RDN M Y - - - - M Y
* Common Arguments M Y - - - - M Y
ModifyRDN Result M Y - - - - M Y

Table: Requirements on the ModifyRDN Operation

Common Elements

  DUA DSA  
  _ _  
Protocol Element Transmit Receive Transmit Receive Comment
  _ _ _ _  
  Status Support Status Support Status Support Status Support  
Service Controls O Y - - - - O Y -
* options O Y - - - - O Y -
- Prefer-Chaining - Y - - - - - Y -
- Chaining-Prohib - Y - - - - - Y -
- Local-Scope - Y - - - - - Y -
- Dont-Use-Copy - Y - - - - - Y -
- Dont-Dereference-Aliases M Y - - - - M Y -
* Priority - Y - - - - - Y Accepted and ignored
* Time-Limit O Y - - - - O Y -
* Size-Limit O Y - - - - O Y -
* Scope-Of-Referral - Y - - - - - Y -
Security Parameters - N - - - - - N -
* Cert-Path - - - - - - - - -
* Name - - - - - - - - -
* Time - - - - - - - - -
* Random - - - - - - - - -
* Target - - - - - - - - -
Requestor O N - - - - O Y Accepted and ignored
Operation-Progress - Y - - - - - Y -
Aliased-RDNs - Y - - - - - Y -
Extensions - N - - - - - N -

Table: Requirements on Elements in Common Arguments

  DUA DSA
  _ _
Protocol Element Transmit Receive Transmit Receive
  _ _ _ _
  Status Support Status Support Status Support Status Support
Security Parameters - - - N - N - -
* Cert-Path - - - - - - - -
* Name - - - - - - - -
* Time - - - - - - - -
* Random - - - - - - - -
* Target - - - - - - - -
Performer - - O N O N - -
Alias-Dereferenced - - O Y O Y - -

Table: Requirements on Elements in Common-Results

  DUA DSA
  _ _
Protocol Element Transmit Receive Transmit Receive
  _ _ _ _
  Status Support Status Support Status Support Status Support
Attribute-Error - - M Y M Y - -
* Object-Name - - M Y M Y - -
* Problems - - M Y M Y - -
- Problem - - M Y M Y - -
- Attribute-Type - - M Y M Y - -
- Attribute-Value - - M Y M Y - -
Name-Error - - M Y M Y - -
* Problem - - M Y M Y - -
* Matched - - M Y M Y - -
Referral - - M Y M Y - -
* Candidate - - M Y M Y - -
Abandoned - - M N M Y - -
Security-Error - - M Y M Y - -
* Problem - - M Y M Y - -
Service-Error - - M Y M Y - -
* Problem - - M Y M Y - -
- busy - - M Y M Y - -
- unavailable - - M Y M Y - -
- unwilling-to-perform - - M Y M Y - -
- chaining-required - - - N - N - -
- unable-to-proceed - - - Y - Y - -
- invalid-reference - - - Y - Y - -
- time-limit-exceeded - - O Y O Y - -
- administrative-limit-exceeded - - - Y - Y - -
- loop-detected - - - Y - Y - -
- unavailable-critical-extension - - - Y - Y - -
- out-of-scope - - - Y - Y - -
- dit-error - - - N - N - -
Abandon-Failed - - M N M Y - -
* Problem - - M - M Y - -
- no-such-operation - - M - M N - -
- too-late - - M - M N - -
- cannot-abandon - - M - M Y - -
* Operation - - M - M Y - -
Update-Error - - M Y M Y - -
* Problem - - M Y M Y - -
- naming-violation - - O Y O Y - -
- object-class-violation - - O Y O Y - -
- not-allowed-on-non-leaf - - O Y O Y - -
- entry-already-exists - - O Y O Y - -
- affects-multiple-DSAs - - - Y - Y - -
- object-class-modification-prohibited - - O Y O Y - -

Table: Requirements on Errors and Parameters

DSP Protocol Implementation Conformance

No PICS are available for the Directory System Protocol (DSP). GDS supports the DSP protocol as defined in ISO 9594-5.

ACSE Protocol Implementation Conformance

Requirements for Supported Functions to Requirements for Normal Mode Parameters inclusive contain the PICS for the Association Control Service Element (ACSE).

For explanations of the abbreviations used in these tables, see Notations and Abbreviations .

Protocol Mechanism Status Support
Normal-Mode O Y
X.410-1984-Mode O N
Rules-For-Extensibility M Y
Supports-Operation-Of-Session-V2 O Y

Table: Requirements for Supported Functions

  Transmit Receive
  _ _
APDU Status Support Status Support
A-associate-request APDU (AARQ) M Y M Y
A-associate-response APDU (AARE) M Y M Y
A-release-request APDU (RLRQ) M Y M Y
A-release-response APDU (RLRE) M Y M Y
A-abort APDU (ABRT) M Y M Y

Table: Requirements for Normal Mode APDUs

  Transmit Receive  
  _ _  
APDU Parameter Status Support Status Support Value & Comment
AARQ          
* Protocol-Version M Y M Y -
* Application-Context-Name M Y M Y -
* Calling-AP-Title O Y O Y -
* Calling-AE-Qualifier O N O N accepted
* Calling-AP-Invokation-Identifier O N O N accepted
* Calling-AE-Invokation-Identifier O N O N accepted
* Called-AP-Title O Y O Y -
* Called-AE-Qualifier O N O N accepted
* Called-AP-Invokation-Identifier O N O N accepted
* Called-AE-Invokation-Identifier O N O N accepted
* Implementation-Information O N M N accepted
* User-Information M Y M Y -
AARE          
* Protocol-Version M Y M Y -
* Application-Context-Name M Y M Y -
* Responding-AP-Title O Y O Y -
* Responding-AE-Qualifier O N O N accepted
* Responding-AP-Invokation-Identifier O N O N accepted
* Responding-AE-Invokation-Identifier O N O N accepted
* Result M Y M Y -
* Result-Source-Diagnostic M Y M Y -
* Implementation-Information O N M N accepted
* User-Information M Y M Y -
RLRQ          
* Reason M Y M Y
Transmit specify Reason = normal (0)
* User-Information M Y M Y -
RLRE          
* Reason M Y M Y
Transmit specify Reason = normal (0)
* User-Information M Y M Y -
ABRT          
* Abort-Source M Y M Y -
* User-Information O Y O Y -

Table: Requirements for Normal Mode Parameters

ROSE Protocol Implementation Conformance

Requirements for Association and Operation Class to Requirements for Supported Parameters inclusive contain the PICS for the Remote Operation Service Elements (ROSE).

For explanations of the abbreviations used in the following tables, see Notations and Abbreviations .

Class Code Support
Association Class for DAP 1 Y
Association Class for DSP 3 Y
Operation Class for DAP 1 or 2 Y
Operation Class for DSP 2 Y

Table: Requirements for Association and Operation Class

  Transmit Receive
  _ _
APDU Status Support Status Support
RO-Invoke APDU (ROIV) M Y M Y
RO-Result APDU (RORS) M Y M Y
RO-Error APDU (ROER) M Y M Y
RO-Reject APDU (RORJ) M Y M Y

Table: Requirements for Supported APDUs

  Transmit Receive  
  _ _  
APDU Parameter Status Support Status Support Value & Comment
ROIV          
* Invoke-ID M Y M Y -
* Linked-ID M Y M Y
The Directory does not use the Linked-ID parameter.
* Operation-Value M Y M Y -
* Argument O Y O Y
Transmit Argument is Directory Operation Argument.
RORS          
* Invoke-ID M Y M Y -
* Operation-Value O Y O Y -
* Result O Y O Y
Transmit Result is Directory Operation Result.
ROER          
* Invoke-ID M Y M Y -
* Error-Value M Y M Y -
* Error-Parameter O Y O Y -
RORJ          
* Invoke-ID M Y M Y -
- Invoke-ID-Type O Y M Y -
- NULL M Y M Y -
* Problem (choice of) M Y M Y -
- General-Problem M Y M Y All values (0-2) supported.
- Invoke-Problem M Y M Y All values (0-7) supported.
- Return-Result-Problem O Y M Y All values (0-2) supported.
- Return-Error-Problem O Y M Y All values (0-4) supported.

Table: Requirements for Supported Parameters

Presentation Service Elements Protocol Implementation Conformance

Requirements for Supported Protocol Mechanisms to Requirements for PPDU-Parameters (Kernel Function Unit) inclusive contain the PICS for the Presentation Service Elements.

For explanations of the abbreviations used in the following tables, see Notations and Abbreviations .

Mode Status Support
Normal O Y
X.410-1984 O N

Table: Requirements for Supported Protocol Mechanisms

Functional Unit Status Support Comment
Kernel M Y -
Presentation-Context-Management O N Not used by X.500.
Presentation-Context-Restoration - N Not used by X.500.

Table: Requirements for Supported Functional Units

  Transmit Receive  
  _ _  
PPDU Status Support Status Support Comment
CP M Y M Y -
CPA M Y M Y -
CPR M Y M Y -
ARU M Y M Y -
ARP M Y M Y -
TD M Y M Y -
TE   -   - Not used by X.500.
TTD   -   - Not used by X.500.
TC   -   - Not used by X.500.
TCC   -   - Not used by X.500.

Table: Requirements for PPDUs (Kernel Function Unit)

  Transmit Receive  
  _ _  
PPDU Parameter Status Support Status Support Value & Comment
CP          
* Calling-Presentation-Selector O Y M Y -
* Called-Presentation-Selector O Y M Y -
* Mode-Selector M Y M Y normal mode
* Presentation-Context-Definition-List O Y M Y
abstract-syntax-names, transfer-syntax-names (up to five names)
* Default-Context-Name O N M Y -
* Protocol-Version O Y M Y -
* Presentation-Requirements O N M Y kernel, In Transmit all bits = 0
* User-Session-Requirements O N M Y kernel, duplex
* User-Data O Y M Y -
CPA          
* Responding-Presentation-Selector O Y M Y -
* Mode-Selector M Y M Y normal mode
* Presentation-Context-Definition-Result-List O Y M Y -
* Protocol-Version O Y M Y -
* Presentation-Requirements O Y M Y kernel, In Transmit all bits = 0
* User-Session-Requirements O N M Y kernel, duplex
* User-Data O Y M Y -
CPR          
* Response-Presentation-Selector O Y M Y -
* Presentation-Context-Definition-Result-List O Y M Y -
* Default-Context-Result O Y M Y provider rejection
* Protocol-Version O Y M Y -
* Provider-Reason O Y M Y -
* User-Data O Y M Y -
ARU          
* Presentation-Context-Identifier-List O Y M Y -
* User-Data O Y M Y -
ARP          
* Provider-Reason O Y M Y -
* Event-Identifier O Y M Y -
TD          
* User-Data O Y M Y -

Table: Requirements for PPDU-Parameters (Kernel Function Unit)

Session Service Elements Protocol Implementation Conformance

Requirements for Supported Functional Units to Requirements for SPDU Parameters (Kernel Function Unit) inclusive contain the PICS for the Session Service Elements.

For explanations of the abbreviations used in the following tables, see Notations and Abbreviations .

Functional Unit Status Support Comment
Kernel M Y -
Negotiated-Release O N Not used by X.500
Half-Duplex O N Not used by X.500
Duplex O Y -
Expedited-Data O N Not used by X.500
Typed-Data O N Not used by X.500
Capability-Data-Exchange O N Not used by X.500
Minor-Synchronize O N Not used by X.500
Symmetric-Synchronize O N Not used by X.500
Major-Synchronize O N Not used by X.500
Resynchronize O N Not used by X.500
Exceptions O N Not used by X.500
Activity-Management O N Not used by X.500

Table: Requirements for Supported Functional Units

Protocol Mechanism Status Support
Use of transport expedited data
(Extended Control Quality of Service)
O N
Refuse of transport connection (sending) O N
Refuse of transport connection (receiving) O Y
Basic concatenation M Y
Extended concatenation (sending) O N
Extended concatenation (receiving) O N
Segmenting (sending) O N
Segmenting (receiving) O N
Segmenting for unlimited user data (sending) O N
Segmenting for unlimited user data (receiving) O N

Table: Requirements for Supported Protocol Mechanisms

  Transmit Receive  
  _ _  
SPDU Status Support Status Support Comment
Connect SPDU (CN) M Y M Y -
Accept SPDU (AC) M Y M Y -
Refuse SPDU (RF) M Y M Y -
Finish SPDU (FN) O Y M Y -
Disconnect SPDU (DN) O Y O Y -
Abort SPDU (AB) M Y M Y -
Data Transfer SPDU (DT) O Y M Y -
Connect Data Overflow SPDU (CDO) O - O - Not used by X.500.
Overflow Accept SPDU (CDO) O - O - Not used by X.500.
Abort Accept SPDU (CDO) O - O - Not used by X.500.
Prepare SPDU (CDO) - - - - Not used by X.500.

Table: Requirements for SPDUs (Kernel Function Unit)

Table: Requirements for SPDU Parameters (Kernel Function Unit)

  Transmit Receive  
  _ _  
SPDU Parameter Status Support Status Support Value & Comment
Connect          
* Connection-Identifier O Y M Y -
- PGI-Default (absent) O Y M Y -
- PGI-Default (empty) O Y M Y -
- Calling-SS-User-Reference O Y M Y -
- Common-Reference O Y M Y -
- Additional-Reference-Information O Y M Y -
* Connect-Accept-Item O Y M Y -
- PGI-Default (absent) O Y M Y -
- PGI-Default (empty) O Y M Y -
- PGI-Default (not empty) O Y M Y -
- Protocol-Options M Y M Y -
- TSDU-Maximum-Size O N M Y -
- Version-Number M Y M Y -
- Initial-Serial-Number O Y M Y -
- Token-Setting-Item O Y M Y -
- Second-Initial-Serial-Number - N - N -
* Session-User-Requirements O Y M Y -
* Calling-SSAP-Identifier O Y M Y -
* Called-SSAP-Identifier O Y M Y -
* User-Data O Y M Y
max size is 512 octets
* Data-Overflow O N M Y -
* Extended-User-Data O N M Y
max size is 10240 octets

  Transmit Receive  
  _ _  
SPDU Parameter Status Support Status Support Value & Comment
Accept          
* Connection-Identifier O Y M Y -
- PGI-Default (absent) O Y M Y -
- PGI-Default (empty) O Y M Y -
- Called-SS-User-Reference O Y M Y -
- Common-Reference O Y M Y -
- Additional-Reference-Information O Y M Y -
* Connect-Accept-Item O Y M Y -
- PGI-Default (absent) O Y M Y -
- PGI-Default (empty) O Y M Y -
- PGI-Default (not empty) O Y M Y -
- Protocol-Options M Y M Y -
- TSDU-Maximum-Size O N M Y -
- Version-Number M Y M Y -
- Initial-Serial-Number O Y M Y -
- Token-Setting-Item O Y M Y -
- Second-Initial-Serial-Number - N - N -
* Token-Item O Y M Y -
* Session-User-Requirements O Y M Y -
* Calling-SSAP-Identifier O Y O Y -
* Called-SSAP-Identifier O Y M Y -
* User-Data O Y M Y
max size is 10240 octets
* Enclosure-Item - N - N -
Refuse          
* Connection-Identifier O Y M Y -
- PGI-Default (absent) O Y M Y -
- PGI-Default (empty) O Y M Y -
- Called-SS-User-Reference O Y M Y -
- Common-Reference O Y M Y -
- Additional-Reference-Information O Y M Y -
* Transport-Disconnect O N M Y -
* Session-User-Requirements O Y M Y -
* Version-Number O Y M Y -
* Reason-Code M Y M Y -
* Enclosure-Item - N - N -
Finish          
* Transport-Disconnect O N M Y -
* User-Data O Y M Y
max size is 10240 octets
* Enclosure-Item - N - N -
Disconnect          
* User-Data O Y M Y
max size is 10240 octets
* Enclosure-Item - N - N -

  Transmit Receive  
  _ _  
SPDU Parameter Status Support Status Support Value & Comment
Abort          
* Transport-Disconnect M Y M Y -
* Reflect-Parameter-Values O Y M Y -
* User-Data O Y M Y
max size is 10240 octets
* Enclosure-Item - N - N -
Data Transfer          
* Enclosure-Item - N - N -
* User-Information-Field O Y M Y -


Please note that the html version of this specification may contain formatting aberrations. The definitive version is available as an electronic publication on CD-ROM from The Open Group.

Contents Next section Index