This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:

• While it is not required that each question be answered at this time, all questions must have answers before the response is submitted to The Open Group for review and publication.
• Press the "Save" button at any time to save work in progress. Once the work has been saved, there is the option to continue editing if required.
• Many questions have instructions to assist in development of answers. They are marked with the indicator. Please look at the instructions carefully.
• Although HTML markup can be included in answers, this is not recommended apart from basic tags such as <p> and <br>, since incorrect markup could effect the format of other items in the document.
• Questions on this system should be addressed to the Conformance Statement manager at The Open Group.

Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.

1. Directory Access

Product Information

Environment Specification

Answer the questions for each binary-compatible family. Alternately, provide the answers in the Appendix at the end of this document.

	Testing Environment	Binary-compatible Family	Portability Environment	Indicator of Compliance	Compliance Details
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended	None.	None.
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended	None.	None.
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended	None.	None.
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended	None.	None.
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended	None.	None.

Temporary Waivers

1.1 XDS Attribute Options

1.1.1 Asynchronous in a Context Object

Question 1: Is the Asynchronous attribute of a Context Object allowed to have the value true?

Response

Yes   No

Rationale

If this attribute can be set to true then up to max-outstanding-operations asynchronous operations can be outstanding for the session.

Reference

CAE Specification, API to Directory Services (XDS), Section 1.5, Mandatory and Optional Features and Section 3.7, Synchronous and Asynchronous Operations.

Question 2: Do asynchronous function calls wait until the operation has been submitted to the underlying directory service?

Response

The "Not Applicable" option should only be used when asynchronous operations are not supported.

Yes No Not Applicable

Rationale

An implementation may either return from an asynchronous call as soon as possible or may wait until the operation has been submitted to the underlying directory service.

Reference

CAE Specification, API to Directory Services (XDS), Section 1.5, Mandatory and Optional Features and Section 3.7, Synchronous and Asynchronous Operations.

Question 3: What is the value associated with the constant max-outstanding-operations?

Response

Rationale

The constant max-outstanding-operations limits the number of concurrently outstanding asynchronous operations permitted by the implementation. This value should be set to zero if the implementation does not support asynchronous operation.

Reference

CAE Specification, API to Directory Services (XDS), Section 3.7, Synchronous and Asynchronous Operations.

1.1.2 Automatic Connection Management

Question 4: Does the implementation provide automatic connection management?

Response

Yes   No

Rationale

An implementation may provide automatic management of the association, or connection, between the user and the directory. In particular, an implementation may not undertake a DirectoryBind operation when the Bind() interface function is called.

Reference

CAE Specification, API to Directory Services (XDS), Section 1.5, Mandatory and Optional Features and Section 3.9, Other Features of the Interface.

1.1.3 File-Descriptor in a Session Object

Question 5: Can the File-Descriptor attribute of an open Session object be used as a file descriptor for poll() and/or select()?

Response

Yes   No

Rationale

This facility is optional. If the answer is "No" then the attribute must have value No-Valid-File-Descriptor.

Reference

CAE Specification, API to Directory Services (XDS), Section 1.5, Mandatory and Optional Features and Section 5.32, Session.

1.2 XDS Interface Function Options

1.2.1 Abandon()

Question 6: Does a call to Abandon() cause an Abandon operation to be requested of the directory and cause the asynchronous operation to be abandoned?

Response

Yes   No

Rationale

A call to Abandon() ensures that the result of an outstanding asynchronous function call cannot be returned by a call to Receive-Result(). However, the call to Abandon() may not cause an Abandon operation on the directory or cause the directory to abandon the asynchronous operation.

Reference

CAE Specification, API to Directory Services (XDS), Section 1.5, Mandatory and Optional Features and Abandon() in Chapter 4, Interface Functions.

1.3 XDS Package Options

1.3.1 Optional Packages

Question 7: Which of the following optional packages are supported?

Response

Package	Supported
Basic Directory Contents	Yes   No
Strong Authentication	Yes   No
MHS Directory User	Yes   No

Rationale

These packages are all optional. Their use may be negotiated with the Version() function.

Reference

CAE Specification, API to Directory Services (XDS), Section 1.5, Mandatory and Optional Features.

1.3.2 Encode Option

Question 8: For which classes are the Encode() and Decode() functions provided?

Response

	Classes
Encode()
Decode()

Rationale

The product shall state which classes it provides the Encode() function for.

Reference

CAE Specification, API to Directory Services (XDS), Section 1.5, Mandatory and Optional Features, Section 5.2, Class Hierarchy and Section 6.2, OM Class Hierarchy.

1.4 Optional Subclasses

Question 9: Does the implementation define additional subclasses to provide alternative representations of Name OM class, Relative-name OM class and Address OM class?

Response

Class	Additional Subclasses Defined
Name OM class	Yes   No
Relative-Name OM class	Yes   No
Address OM class	Yes   No

Rationale

XDS allows, or expects, additional subclasses to be defined by the implementors for the following abstract classes:

• Name OM class (reference Section 5.24, NAME)
• Relative-Name OM class (reference Section 5.29, RELATIVE-NAME)
• Address OM class (reference Section 5.4, ADDRESS)

Reference

CAE Specification, API to Directory Services (XDS), Chapter 5, Interface Class Definitions.

2. OSI-Abstract-Data Manipulation (XOM)

2.1 Character Sets

Question 10: Is the service performing conversion to a local character set?

Response

Yes   No

Question 11: Does the conversion of information to and from the local character set result in the loss of information?

Response

Yes   No

Rationale

The translation of string data between the local character set and the non-local character set may incur the loss of data during translation in the case that these two sets are not equivalent.

Reference

CAE Specification, OSI-Abstract-Data Manipulation API (XOM), Section 1.5, Options, Section 1.6, Conformance and Section 4.2.2, Descriptor.

Question 12: What is the local character set representation, and what are the precise mappings between it and the various string syntaxes?

Response

Question 13: What are the precise definitions in C of the intermediate data types?

Response

Question 14: What is the length of the longest string that the Get() function will return?

Response

(Note that this number is not less than 1024.)

Question 15: Does the service report an exception if an object supplied to it as an argument is not minimally consistent?

Response

Rationale

The local character set representation and the precise mappings between it and the various string syntaxes are implementation-defined.

Reference

CAE Specification, OSI-Abstract-Data Manipulation API (XOM), Section 1.5, Options.

2.2 Intermediate Data Types

Question 16: What are the precise C definitions for the following intermediate data types?

Response

Intermediate Data Type	C Language Definition
Sint	Yes   No
Sint16	Yes   No
Sint32	Yes   No
Uint	Yes   No
Uint16	Yes   No
Uint32	Yes   No

Rationale

The precise C language definitions that correspond to the intermediate data types are system-specific.

Reference

CAE Specification, OSI-Abstract-Data Manipulation API (XOM), Section 1.5, Options and Section 4.2, Data Types.

2.3 XOM Options

2.3.1 Maximum String Attribute Length

Question 17: What is the maximum string length for an attribute value before the elements of the string are omitted by the Get() function?

Response

Rationale

The implementation may impose a limit on the size of the string that the Get() function will return. This number must be at least 1024.

Reference

CAE Specification, OSI-Abstract-Data Manipulation API (XOM), Section 1.5, Options and Section 4.3, Functions.

2.3.2 Error if Object not Minimally Consistent

Question 18: In operational versions of the XDS library, if an object supplied to the service is not minimally consistent is an error reported?

Response

Yes   No

Rationale

This is an aspect of service behaviour that is implementation-defined with no default specified.

Reference

CAE Specification, OSI-Abstract-Data Manipulation API (XOM), Section 1.5, Options to Section 2.5, Class Definitions.

Question 19: In debug versions of the XDS library, if an object supplied to the service is not minimally consistent is an error reported?

Response

Yes   No

Rationale

This is an aspect of service behaviour that is implementation-defined with no default specified.

Reference

CAE Specification, OSI-Abstract-Data Manipulation API (XOM), Section 1.5, Options to Section 2.5, Class Definitions.

3. Appendix

Copyright © 
All rights reserved.

4. Change History