| |
Home About Us A-Z Index Search • |
Organization | Compaq Computer Corporation |
---|---|
Author | Bonnie Talerico |
Product Identification | Version/Release Number | Product Supplier | |
---|---|---|---|
1. | Tru64 UNIX | 5.0 and later | Compaq Computer Corporation |
Testing Environment | Binary-compatible Family | Portability Environment | Indicator of Compliance | Compliance Details | |
---|---|---|---|---|---|
1. |
|
| Internationalised System Calls and Libraries Extended | Test Report from Test Suite | Test Suite:
VST5.2.4 Test Report: COMPAQ-VST5-051399-Alpha |
Question 1: Are the UX extensions in <xti.h> supported?
Response
Yes
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.
Question 2: Which service types and transport providers are supported by the product and what transport provider identifiers are used to access them?
Response
Service Type | Supported | Transport Provider Identifier(s) |
---|---|---|
T_COTS | No | n/a |
T_COTS_ORD | Yes | TCP/IP |
T_CLTS | Yes | UDP/IP |
Description of transport providers:
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().
Question 3: For which transport providers does the product support the sending of zero-length normal or expedited data transport service data units?
Response
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.
Question 4: Does the product support negotiation of the following Quality of Service options?
Response
QoS Parameter | XTI Name | Negotiation Supported |
---|---|---|
Throughput | TCO_THROUGHPUT | |
Transit Delay | TCO_TRANSDEL | |
Residual Error Rate | TCO_RESERRORRATE | |
Transfer Failure Probability | TCO_TRANSFAILPROB | |
Connection Establishment Failure Probability | TCO_ESTFAILPROB | |
Connection Release Failure Probability | TCO_RELFAILPROB | |
Connection Establishment Delay | TCO_ESTDELAY | |
Connection Release Delay | TCO_RELDELAY | |
Connection Resilience Protection | TCO_PROTECTION | |
Priority | TCO_PRIORITY | |
Expedited Data | TCO_EXPD |
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.
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 | |
Acknowledge Time | TCO_ACKTIME | |
Reassignment Time | TCO_REASTIME | |
Preferred Class | TCO_PREFCLASS | |
1st Alternate Class | TCO_ALTCLASS1 | |
2nd Alternate Class | TCO_ALTCLASS2 | |
3rd Alternate Class | TCO_ALTCLASS3 | |
4th Alternate Class | TCO_ALTCLASS4 | |
Extended Formats | TCO_EXTFORM | |
Flow Control | TCO_FLOWCTRL | |
Checksum Use | TCO_CHECKSUM | |
Network Expedited Data | TCO_NETEXP | |
Network Receipt Confirmation | TCO_NETRECPTCF |
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.
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 | |
Residual Error Rate | TCL_RESERRORRATE | |
Protection | TCL_PROTECTION | |
Priority | TCL_PRIORITY |
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.
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
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.
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 |
Get Maximum Segment Size | TCP_MAXSEG | Yes |
Don't Delay To Coalesce | TCP_NODELAY | Yes |
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.
Question 9: Does the product support user control of the computation of UDP checksums by means of the UDP_CHECKSUM option?
Response
Yes
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.
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 |
Bypass Routing | IP_DONTROUTE | Yes |
IP Per-Packet Options | IP_OPTIONS | Yes |
Local Address Reuse | IP_REUSEADDR | Yes |
IP Type Of Service | IP_TOS | Yes |
Time To Live | IP_TTL | Yes |
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.
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. | No |
ISO ISP 10608-5 (TA 1111) | TP4 and CLNS over PSTN SVC. | No |
ISO ISP 10609-6 (TC 1111) | TP0,2 and CONS over PSTN SVC. | No |
ISO ISP 10609-7 (TD 1111) | TP0 and CONS over PSTN SVC. | No |
TCP/IP | Yes | |
UDP/IP | Yes |
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.
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.
Question 13: Does your implementation use all the recommended values identified in the XTI specification as "recommended only, not mandatory for conformance"?
Response
Yes
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."
Copyright © 1999 Compaq Computer Corporation
All rights reserved.
Date | Name | Comment |
---|
The Open Group and Boundaryless Information Flow are trademarks and UNIX is a registered trademark of The Open Group in the United States and other countries. All other trademarks are the property of their respective owners.