Environment Specification

A product may be registered in all members of a binary-compatible family
of products on the basis of a single test report.

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

Test Suite:
Test Report:

Test Suite:
Test Report:

Test Suite:
Test Report:

Test Suite:
Test Report:

Test Suite:
Test Report:

Temporary Waivers

Enter the waiver number and expiry date for each temporary waiver granted by The Open Group.

Waiver Number

Expiry Date

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.

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().

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.

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.