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. X.400 Gateway

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 Internationalised System Calls and Libraries Extended V2	None.	None.
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended Internationalised System Calls and Libraries Extended V2	None.	None.
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended Internationalised System Calls and Libraries Extended V2	None.	None.
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended Internationalised System Calls and Libraries Extended V2	None.	None.
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended Internationalised System Calls and Libraries Extended V2	None.	None.

Temporary Waivers

1.1 X.400 Message Transfer Interface Options

1.1.1 X.400 Message Transfer Interface Roles

Question 1: Which of the following roles are supported?

Response

Role	Supported
Service	Yes   No
Client	Yes   No

At least one of the alternatives above must be marked as "Yes".

Rationale

An X.400 Message Transfer Interface must provide at least one of the client or service roles.

Reference

CAE Specification, API to Electronic Mail (X.400), Section 1.8, Conformance.

1.1.2 Message Transfer Interface Optional Functional Units

Question 2: If the MT interface is supported in the service role which of the following optional Functional Units (FU) are supported?

Response

Functional Unit	Supported
Transfer In	Yes   No
Transfer Out	Yes   No

At least one functional unit should be supported.

Rationale

Although the FUs mentioned above are all optional, at least one of them must be supported if the implementation is to perform any useful work.

Reference

CAE Specification, API to Electronic Mail (X.400), Section 1.8, Conformance.

Question 3: What is the maximum number of simultaneous MT sessions per client?

Response

Enter the value or enter "Variable" if the limit is undefined and varies with time.

Rationale

The implementation may limit the number of sessions that simultaneously exist. This may either be a hard limit or may vary with time.

Reference

CAE Specification, API to Electronic Mail (X.400), Section 1.7, Options.

Question 4: How many sessions does the Wait() function notify of any object's arrival when several sessions provide access to the queue?

Response

Question 5: What is the criteria for the session(s) to be selected to receive the signal from the Wait() function?

Response

Question 6: What is the criteria for an object to be selected for transfer-in when there is more than one object available in the queue?

Response

1.1.3 Default Features Supplied by Open()

Question 7: Which of the features associated with the MT interface are supplied as default by a call to mt_open()?

Response

Rationale

The features of a session that are supplied as defaults on a call to Open() are implementation-defined.

Reference

CAE Specification, API to Electronic Mail (X.400), Section 1.7, Options.

1.1.4 MT Protocol Realisations

Question 8: If the MT interface is supported in the service role which of the following alternate realisations is used?

Response

Protocol	Realised
P1	Yes   No
Other than P1	Yes   No

Rationale

At least one of the above must be marked "Yes".

Reference

CAE Specification, API to Electronic Mail (X.400), Section 1.8, Conformance.

1.2 Message Handling Packages

1.2.1 MH Package Implementation

Question 9: If the MT interface is supported in the service role which of the following packages are implemented?

Response

Package	Implemented
MH84	Yes   No
MH88	Yes   No

Rationale

At least one of the above must be implemented.

Reference

CAE Specification, API to Electronic Mail (X.400), Section 1.8, Conformance.

1.2.2 MH88 Classes

Question 10: If the MH88 package is supported then which, if any, of the following classes are supported?

Response

Class	Supported
Algorithm	Yes   No
Algorithm and Result	Yes   No
Asymmetric Token	Yes   No
Delivery Confirmation	Yes   No
Local Delivery Confirmation	Yes   No
Expansion Record	Yes   No
Extensible Object	Yes   No
Submitted Message	Yes   No
Extension	Yes   No
Local Delivery Confirmations	Yes   No
OR Name	Yes   No
Redirection Record	Yes   No
Security Label	Yes   No
MT Public Data	Yes   No

Rationale

These are the 1988 classes within the MH88 package. None of them need be supported.

Reference

CAE Specification, API to Electronic Mail (X.400), Section 1.8, Conformance, Section 5.1, Class Hierarchy and Section 5.2, Class Definitions.

1.2.3 Encode Option

Question 11: If the MH84 package is supported then for which classes is Encode() provided (in addition to OR Address)?

Response

Rationale

The product shall state which classes it provides the Encode() function for. Only OR Address is specified as having this function provided.

Reference

CAE Specification, API to Electronic Mail (X.400), Section 1.8, Conformance and Section 5.1, Class Hierarchy.

Question 12: If the MH88 package is supported then for which classes is Encode() provided (in addition to OR Address and OR Name)?

Response

Rationale

The product shall state which classes it provides the Encode() function for. Only OR Address and OR Name are specified as having this function provided.

Reference

CAE Specification, API to Electronic Mail (X.400), Section 1.8, Conformance and Section 5.1, Class Hierarchy.

1.3 Interpersonal Messaging Packages

1.3.1 IM Package Implementation

Question 13: If the MT interface is supported in the service role which, if any, of the following packages implemented?

Response

IM Package	How Implemented
IM84	P2 Protocol Otherwise Not Implemented
IM88	P2 Protocol Otherwise Not Implemented

Rationale

Neither the IM84 or IM88 Package need be implemented and, if they are, they need not use the P2 Protocol.

Reference

CAE Specification, API to Electronic Mail (X.400), Section 1.8, Conformance.

1.3.2 IM Classes

Question 14: If the IM84 or IM88 Package is supported then which, if any, of the following immediate subclasses of Body Part class are implemented?

Response

Immediate Subclass of Body Part	Implemented
Bilaterally Defined Body Part	Yes   No
Externally Defined Body Part	Yes   No
G3 Fax Body Part	Yes   No
G4 Class 1 Body Part	Yes   No
General Text Body Part	Yes   No
IA5 Text Body Part	Yes   No
ISO 6937 Text Body Part	Yes   No
Message Body Part	Yes   No
Mixed Mode Body Part	Yes   No
Nationally Defined Body Part	Yes   No
ODA Body Part	Yes   No
Teletex Body Part	Yes   No
Unidentified Body Part	Yes   No
USA Nationally Defined Body Part	Yes   No
Videotex Body Part	Yes   No

Rationale

None of these classes need be implemented. Both Externally Defined Body Part and General Text Body Part are defined only in IM88.

Reference

CAE Specification, API to Electronic Mail (X.400), Section 1.8, Conformance, Section 4.1, Class Hierarchy and Section 4.2, Class Definitions.

1.3.3 Encode Option

Question 15: If the IM84 package is supported then for which classes is Encode() provided?

Response

Rationale

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

Reference

CAE Specification, API to Electronic Mail (X.400), Section 1.8, Conformance and Section 4.1, Class Hierarchy.

Question 16: If the IM88 package is supported then for which classes is Encode() provided?

Response

Rationale

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

Reference

CAE Specification, API to Electronic Mail (X.400), Section 1.8, Conformance and Section 4.1, Class Hierarchy.

1.4 Other Packages

1.4.1 Package Implementations

Question 17: Is the SM88 package implemented?

Response

Package	Implemented
SM88	Yes   No

Rationale

If the SM88 package is supported, then the Encode/Decode functions with canonical-BER should also be supported.

Reference

CAE Specification, API to Electronic Mail (X.400), Section 1.6, Features.

2. OSI-Abstract-Data Manipulation (XOM)

2.1 Character Sets

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

Response

Yes   No

Question 2: 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 3: What is the local character set representation, and what are the precise mappings between it and the various string syntaxes?

Response

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

Response

Question 5: 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 6: Does the service report an exception if an object supplied to it as an argument is not minimally consistent?

Response

Yes   No

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 7: 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 8: 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 9: 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 10: 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