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. Transport Service (XTI)

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 XPG3 Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			Select from this list XPG3 Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			Select from this list XPG3 Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			Select from this list XPG3 Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			Select from this list XPG3 Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended	Select from this list Test Report from Test Suite	Test Suite: Test Report:

Temporary Waivers

1.1 Optional Features

Question 1: Are the UX extensions in <xti.h> supported?

Response

Yes   No

Rationale

Networking Services, Issue 4 requires that prototypes for the XTI functions are defined in <xti.h> if _XOPEN_SOURCE_EXTENDED is defined. This is mandatory for the UNIX Product Standard but is optional otherwise.

Reference

X/Open CAE Specification, Networking Services, Issue 4, Appendix F, Headers and Definitions for XTI.

1.2 Scope of the Implementation

1.2.1 Transport Providers Supported

Question 2: Which service types and transport providers are supported by the product and what transport provider identifiers are used to access them?

Response

Where indicated in the following table select one of the options "Yes" or "No" if the product supports the service class identified. In addition, enter the name of the transport provider where shown.

Service Type	Supported	Transport Provider Identifier(s)
T_COTS	Yes   No
T_COTS_ORD	Yes   No
T_CLTS	Yes   No

Description of transport providers:

Add a brief description of each of the transport providers below; e.g., ISO connection mode, UDP.

Rationale

The X/Open Transport Interface (XTI) requirements allow three service types T_COTS, T_COTS_ORD and T_CLTS which are not all mandatory and these services may be supplied by a number of transport providers. An XTI user process must have knowledge of the service type and the transport provider identifiers supported by a product if it is to make use of an XTI implementation. Transport provider identifiers are supplied in the name parameter of t_open() and the service type is supplied in the info->servtype parameter of t_open().

Reference

X/Open CAE Specification, Networking Services, Issue 4, Chapter 7, XTI Library Functions and Parameters, t_open().

1.3 Technical Requirements

1.3.1 Zero-length Data

Question 3: For which transport providers does the product support the sending of zero-length normal or expedited data transport service data units?

Response

Enter the names of the transport providers for which the sending of zero-length normal data or expedited data tsdus is supported. If this behaviour is forbidden for all providers write "None".

Rationale

Some transport providers forbid the sending of zero-length transport service data units.

Reference

X/Open CAE Specification, Networking Services, Issue 4, Chapter 7, XTI Library Functions and Parameters.

1.4 ISO Connection Mode Transport Provider

1.4.1 Quality of Service Options

Question 4: Does the product support negotiation of the following Quality of Service options?

Response

QoS Parameter	XTI Name	Negotiation Supported
Throughput	TCO_THROUGHPUT	Yes   No
Transit Delay	TCO_TRANSDEL	Yes   No
Residual Error Rate	TCO_RESERRORRATE	Yes   No
Transfer Failure Probability	TCO_TRANSFAILPROB	Yes   No
Connection Establishment Failure Probability	TCO_ESTFAILPROB	Yes   No
Connection Release Failure Probability	TCO_RELFAILPROB	Yes   No
Connection Establishment Delay	TCO_ESTDELAY	Yes   No
Connection Release Delay	TCO_RELDELAY	Yes   No
Connection Resilience Protection	TCO_PROTECTION	Yes   No
Priority	TCO_PRIORITY	Yes   No
Expedited Data	TCO_EXPD	Yes   No

Rationale

An XTI-compliant transport provider may support none, all or a subset of the options available for use with the ISO Transport service.

Reference

ISO 8072:1986, Information Processing Systems \(em Open Systems Interconnection \(em Transport Service Definition.

X/Open CAE Specification, Networking Services, Issue 4, Section A.2.1.1, Options for Quality of Service and Expedited Data.

1.4.2 Management Options

Question 5: Which of the following XTI management options are supported by the product?

Response

Option	XTI Name	Supported
Maximum Length of TPDU	TCO_LTPDU	Yes   No
Acknowledge Time	TCO_ACKTIME	Yes   No
Reassignment Time	TCO_REASTIME	Yes   No
Preferred Class	TCO_PREFCLASS	Yes   No
1st Alternate Class	TCO_ALTCLASS1	Yes   No
2nd Alternate Class	TCO_ALTCLASS2	Yes   No
3rd Alternate Class	TCO_ALTCLASS3	Yes   No
4th Alternate Class	TCO_ALTCLASS4	Yes   No
Extended Formats	TCO_EXTFORM	Yes   No
Flow Control	TCO_FLOWCTRL	Yes   No
Checksum Use	TCO_CHECKSUM	Yes   No
Network Expedited Data	TCO_NETEXP	Yes   No
Network Receipt Confirmation	TCO_NETRECPTCF	Yes   No

Rationale

XTI offers additional management options to those defined as protocol parameters for Quality of Service use in ISO 8072:1986. Not all of these need be supported.

Reference

X/Open CAE Specification, Networking Services, Issue 4, Section A.2.1.2, Management Options.

1.5 ISO Connectionless Mode Transport Service

1.5.1 Quality of Service Options

Question 6: Which of the following Quality of Service parameters are supported by the XTI product when an ISO Connectionless Mode transport service is used as the service provider?

Response

QoS Parameter	XTI Name	Supported
Transit Delay	TCL_TRANSDEL	Yes   No
Residual Error Rate	TCL_RESERRORRATE	Yes   No
Protection	TCL_PROTECTION	Yes   No
Priority	TCL_PRIORITY	Yes   No

Rationale

Not all Quality of Service parameters need be supplied by all implementations.

Reference

X/Open CAE Specification, Networking Services, Issue 4, Section A.2.2.1, Options for Quality of Service.

1.5.2 Management Options

Question 7: Does the product support the use of the TCL_CHECKSUM management option to allow user control over whether a checksum is computed for PDUs issued by an ISO Connectionless Mode transport provider?

Response

Yes   No

Rationale

This management option is not defined in ISO 8072/Add.1:1986 although it does appear as a protocol parameter in ISO 8602. It is offered as an additional option by XTI but need not be supported by all implementations.

Reference

X/Open CAE Specification, Networking Services, Issue 4, Section A.2.2.2, Management Options.

1.6 TCP Transport Providers

1.6.1 TCP Options

Question 8: Which of the following options are supported for use with TCP transport providers?

Response

Option	XTI Name	Supported
Check Connections Alive	TCP_KEEPALIVE	Yes   No
Get Maximum Segment Size	TCP_MAXSEG	Yes   No
Don't Delay To Coalesce	TCP_NODELAY	Yes   No

Rationale

A transport provider which is compliant to the XTI specification may support none, all or any subset of the TCP-level options.

Reference

X/Open CAE Specification, Networking Services, Issue 4, Section B.2.1, TCP-level Options.

1.7 UDP Transport Provider

1.7.1 UDP Options

Question 9: Does the product support user control of the computation of UDP checksums by means of the UDP_CHECKSUM option?

Response

Yes   No

Rationale

A transport provider compliant to the XTI specification implements none, all or any of the subset of options defined for TCP, UDP and IP.

Reference

X/Open CAE Specification, Networking Services, Issue 4, Section B.2.2, UDP-level Options.

1.8 Internet Protocol Support

1.8.1 IP Options

Question 10: Which of the following options are supported at the IP-level by the transport provider(s) associated with the XTI product?

Response

Option	XTI Name	Supported
Permit Broadcast	IP_BROADCAST	Yes   No
Bypass Routing	IP_DONTROUTE	Yes   No
IP Per-Packet Options	IP_OPTIONS	Yes   No
Local Address Reuse	IP_REUSEADDR	Yes   No
IP Type Of Service	IP_TOS	Yes   No
Time To Live	IP_TTL	Yes   No

Rationale

Compliant XTI implementations may implement all, none or any subset of the defined options for control over the IP level of transport providers.

Reference

X/Open CAE Specification, Networking Services, Issue 4, Section B.2.3, IP-level Options.

1.9 Communications Interface

1.9.1 Required Protocol Stack Support

Question 11: Which protocol stacks does the product support?

Response

Protocol Stack	Description	Supported?
ISO ISP 10608-2 (TA-51)	TP4 and CLNS over LLC1 and 8802-3 LAN.	Yes   No
ISO ISP 10608-5 (TA 1111)	TP4 and CLNS over PSTN SVC.	Yes   No
ISO ISP 10609-6 (TC 1111)	TP0,2 and CONS over PSTN SVC.	Yes   No
ISO ISP 10609-7 (TD 1111)	TP0 and CONS over PSTN SVC.	Yes   No
TCP/IP		Yes   No
UDP/IP		Yes   No

Rationale

Products conforming to the Transport Service (XTI) Product Standard definition must be available in configurations that support at least one of the above transport profiles.

Reference

Transport Service (XTI) Product Standard Definition.

X/Open Guide, Guide to the Internet Protocol Suite.

1.9.2 Optional Support for Protocols or Protocol Profiles

Question 12: What other protocols or protocol profiles does your product support?

Response

Rationale

The Conformance Statement provides an opportunity to declare support for other protocols or protocol profiles.

Reference

Transport Service (XTI) Product Standard Definition.

1.10 Recommended XTI Header Values Implemented

Question 13: Does your implementation use all the recommended values identified in the XTI specification as "recommended only, not mandatory for conformance"?

Response

Yes   No

If "No", enter the non-recommended values in the table below.

If you select no for any entry in the table below, place the corresponding value in the third column.

Symbolic Constant	Recommended Value	Implementation Value
General definitions for option management:
T_ALLOPT	Yes   No
XTI-level:
XTI_GENERIC	Yes   No
XTI-level options:
XTI_DEBUG	Yes   No
XTI_LINGER	Yes   No
XTI_RCVBUF	Yes   No
XTI_RCVLOWAT	Yes   No
XTI_SNDBUF	Yes   No
XTI_SNDLOWAT	Yes   No
Protocol levels:
ISO_TP	Yes   No
Options for QoS and expedited data
(ISO 8072:1986):
TCO_THROUGHPUT	Yes   No
TCO_TRANSDEL	Yes   No
TCO_RESERRORRATE	Yes   No
TCO_TRANSFAILPROB	Yes   No
TCO_ESTFAILPROB	Yes   No
TCO_RELFAILPROB	Yes   No
TCO_ESTDELAY	Yes   No
TCO_RELDELAY	Yes   No
TCO_CONNRESIL	Yes   No
TCO_PROTECTION	Yes   No
TCO_PRIORITY	Yes   No
TCO_EXPD	Yes   No
TCL_TRANSDEL	Yes   No
TCL_RESERRORRATE	Yes   No
TCL_PROTECTION	Yes   No
TCL_PRIORITY	Yes   No
Management options:
TCO_LTPDU	Yes   No
TCO_ACKTIME	Yes   No
TCO_REASTIME	Yes   No
TCO_EXTFORM	Yes   No
TCO_FLOWCTRL	Yes   No
TCO_CHECKSUM	Yes   No
TCO_NETEXP	Yes   No
TCO_NETRECPTCF	Yes   No
TCO_PREFCLASS	Yes   No
TCO_ALTCLASS1	Yes   No
TCO_ALTCLASS2	Yes   No
TCO_ALTCLASS3	Yes   No
TCO_ALTCLASS4	Yes   No
TCL_CHECKSUM	Yes   No
TCP-level:
INET_TCP	Yes   No
TCP-level options:
TCP_NODELAY	Yes   No
TCP_MAXSEG	Yes   No
TCP_KEEPALIVE	Yes   No
UDP level:
INET_UDP	Yes   No
UDP-level options:
UDP_CHECKSUM	Yes   No
IP-level:
INET_IP	Yes   No
IP-level options:
IP_OPTIONS	Yes   No
IP_TOS	Yes   No
IP_TTL	Yes   No
IP_REUSEADDR	Yes   No
IP_DONTROUTE	Yes   No
IP_BROADCAST	Yes   No

Rationale

An XTI transport provider does not have to implement these recommended values in order to be compliant. However, it is valuable to know this so that users can easily check whether an XTI application which relies on these values will be portable to this XTI implementation: if the answer is "Yes" then such an XTI application will be portable to this implementation; if "No" then it will not.

Reference

X/Open Corrigendum U008 to CAE Specification, Networking Services, Issue 4. This Corrigendum revises Appendix F, XTI Headers and Definitions, to define certain values assigned to constants as "recommended, not mandatory."

2. Appendix

Copyright © 
All rights reserved.

3. Change History