| |
| | |
Home • About Us •A-Z Index• Search • | |
| Organization | Sun Microsystems, Inc. |
|---|---|
| Author | Kristin Amundsen |
| Product Identification | Version/Release Number | Product Supplier | |
|---|---|---|---|
| 1. | Solaris x86 Platform Edition | 9 12/02 X86 and later | Sun Microsystems, Inc. |
| Testing Environment | Binary-compatible Family | Portability Environment | Indicator of Compliance | Compliance Details | |
|---|---|---|---|---|---|
| 1. |
|
| Internationalised System Calls and Libraries Extended v2 | Test Report from Test Suite | Test Suite:
VST 5.2.6 Test Report: vst5_sol9_x86-32 |
Question 1: 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 | |
| T_COTS_ORD | Yes | TCP /dev/tcp |
| T_CLTS | Yes | UDP /dev/udp |
Description of transport providers:
Rationale
The Transport Interface (XTI) V2 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
CAE Specification, Networking Services, Issue 5, Chapter 7, XTI Library Functions and Parameters, t_open().
Question 2: Does the product support negotiation of the following Quality of Service options?
Response
| QoS Parameter | XTI Name | Negotiation Supported |
|---|---|---|
| Throughput | T_TCO_THROUGHPUT | No |
| Transit Delay | T_TCO_TRANSDEL | No |
| Residual Error Rate | T_TCO_RESERRORRATE | No |
| Transfer Failure Probability | T_TCO_TRANSFAILPROB | No |
| Connection Establishment Failure Probability | T_TCO_ESTFAILPROB | No |
| Connection Release Failure Probability | T_TCO_RELFAILPROB | No |
| Connection Establishment Delay | T_TCO_ESTDELAY | No |
| Connection Release Delay | T_TCO_RELDELAY | No |
| Connection Resilience Protection | T_TCO_PROTECTION | No |
| Priority | T_TCO_PRIORITY | No |
| Expedited Data | T_TCO_EXPD | 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 - Open Systems Interconnection - Transport Service Definition.
CAE Specification, Networking Services, Issue 5, Section A.2.1.1, Options for Quality of Service and Expedited Data.
Question 3: Which of the following XTI management options are supported by the product?
Response
| Option | XTI Name | Supported |
|---|---|---|
| Maximum Length of TPDU | T_TCO_LTPDU | No |
| Acknowledge Time | T_TCO_ACKTIME | No |
| Reassignment Time | T_TCO_REASTIME | No |
| Preferred Class | T_TCO_PREFCLASS | No |
| 1st Alternate Class | T_TCO_ALTCLASS1 | No |
| 2nd Alternate Class | T_TCO_ALTCLASS2 | No |
| 3rd Alternate Class | T_TCO_ALTCLASS3 | No |
| 4th Alternate Class | T_TCO_ALTCLASS4 | No |
| Extended Formats | T_TCO_EXTFORM | No |
| Flow Control | T_TCO_FLOWCTRL | No |
| Checksum Use | T_TCO_CHECKSUM | No |
| Network Expedited Data | T_TCO_NETEXP | No |
| Network Receipt Confirmation | T_TCO_NETRECPTCF | 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
CAE Specification, Networking Services, Issue 5, Section A.2.1.2, Management Options.
Question 4: 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 | T_TCL_TRANSDEL | No |
| Residual Error Rate | T_TCL_RESERRORRATE | No |
| Protection | T_TCL_PROTECTION | No |
| Priority | T_TCL_PRIORITY | No |
Rationale
Not all Quality of Service parameters need be supplied by all implementations.
Reference
CAE Specification, Networking Services, Issue 5, Section A.2.2.1, Options for Quality of Service.
Question 5: Does the product support the use of the T_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
CAE Specification, Networking Services, Issue 5, Section A.2.2.2, Management Options.
Question 6: Which of the following options are supported for use with TCP transport providers?
Response
| Option | XTI Name | Supported |
|---|---|---|
| Check Connections Alive | T_TCP_KEEPALIVE | No |
| Get Maximum Segment Size | T_TCP_MAXSEG | Yes |
| Don't Delay To Coalesce | T_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
CAE Specification, Networking Services, Issue 5, Section B.2.1, TCP-level Options.
Question 7: Does the product support user control of the computation of UDP checksums by means of the T_UDP_CHECKSUM option?
Response
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
CAE Specification, Networking Services, Issue 5, Section B.2.2, UDP-level Options.
Question 8: 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 | T_IP_BROADCAST | No |
| Bypass Routing | T_IP_DONTROUTE | No |
| IP Per-Packet Options | T_IP_OPTIONS | No |
| Local Address Reuse | T_IP_REUSEADDR | No |
| IP Type Of Service | T_IP_TOS | No |
| Time To Live | T_IP_TTL | 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
CAE Specification, Networking Services, Issue 5, Section B.2.3, IP-level Options.
Question 9: 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) V2 Product Standard definition must be available in configurations that support at least one of the above transport profiles.
Reference
Transport Service (XTI) V2 Product Standard Definition.
X/Open Guide, Guide to the Internet Protocol Suite.
Question 10: 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) V2 Product Standard Definition.
Question 11: Does your implementation use all the recommended values identified in the XTI specification as "recommended only, not mandatory for conformance"?
Response
No
If "No", enter the non-recommended values in the table below.
| Symbolic Constant | Recommended Value | Implementation Value |
|---|---|---|
| General definitions for option management: | ||
| T_ALLOPT | No | 0x0 |
| XTI-level: | ||
| XTI_GENERIC | No | 0xFFFE |
| XTI-level options: | ||
| XTI_DEBUG | No | 0x0001 |
| XTI_LINGER | No | 0x0080 |
| XTI_RCVBUF | No | 0x1002 |
| XTI_RCVLOWAT | No | 0x1004 |
| XTI_SNDBUF | No | 0x1001 |
| XTI_SNDLOWAT | No | 0x1003 |
| Protocol levels: | ||
| T_ISO_TP | No | not applicable |
| Options for QoS and expedited data | ||
| (ISO 8072:1986): | ||
| T_TCO_THROUGHPUT | No | not applicable |
| T_TCO_TRANSDEL | No | not applicable |
| T_TCO_RESERRORRATE | No | not applicable |
| T_TCO_TRANSFAILPROB | No | not applicable |
| T_TCO_ESTFAILPROB | No | not applicable |
| T_TCO_RELFAILPROB | No | not applicable |
| T_TCO_ESTDELAY | No | not applicable |
| T_TCO_RELDELAY | No | not applicable |
| T_TCO_CONNRESIL | No | not applicable |
| T_TCO_PROTECTION | No | not applicable |
| T_TCO_PRIORITY | No | not applicable |
| T_TCO_EXPD | No | not applicable |
| T_TCL_TRANSDEL | No | not applicable |
| T_TCL_RESERRORRATE | No | not applicable |
| T_TCL_PROTECTION | No | not applicable |
| T_TCL_PRIORITY | No | not applicable |
| Management options: | ||
| T_TCO_LTPDU | No | not applicable |
| T_TCO_ACKTIME | No | not applicable |
| T_TCO_REASTIME | No | not applicable |
| T_TCO_EXTFORM | No | not applicable |
| T_TCO_FLOWCTRL | No | not applicable |
| T_TCO_CHECKSUM | No | not applicable |
| T_TCO_NETEXP | No | not applicable |
| T_TCO_NETRECPTCF | No | not applicable |
| T_TCO_PREFCLASS | No | not applicable |
| T_TCO_ALTCLASS1 | No | not applicable |
| T_TCO_ALTCLASS2 | No | not applicable |
| T_TCO_ALTCLASS3 | No | not applicable |
| T_TCO_ALTCLASS4 | No | not applicable |
| T_TCL_CHECKSUM | No | not applicable |
| TCP-level: | ||
| T_INET_TCP | No | 0x6 |
| TCP-level options: | ||
| T_TCP_NODELAY | No | 0x1 |
| T_TCP_MAXSEG | No | 0x2 |
| T_TCP_KEEPALIVE | No | 0x8 |
| UDP level: | ||
| T_INET_UDP | No | 0x11 |
| UDP-level options: | ||
| T_UDP_CHECKSUM | No | 0x0600 |
| IP-level: | ||
| T_INET_IP | No | 0x0 |
| IP-level options: | ||
| T_IP_OPTIONS | No | 0x107 |
| T_IP_TOS | No | 0x108 |
| T_IP_TTL | No | 0x4 |
| T_IP_REUSEADDR | No | 0x104 |
| T_IP_DONTROUTE | No | 0x105 |
| T_IP_BROADCAST | No | 0x106 |
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
CAE Specification, Networking Services, Issue 5, Appendix F, XTI Headers and Definitions.
Copyright © 2000 Sun Microsystems, Inc.
All rights reserved.
| Date | Name | Comment |
|---|---|---|
| 06-Dec-2002 | Kristin Amundsen | Changed for Solaris 9 12/02 x86 Platform Edition |
| 19-Mar-2002 | Kristin Amundsen | Solaris 9 updates. |
| 06-Jan-2000 | Lee Damico | Solaris 8 updates. |
| 28-Oct-1998 | Lee Damico | Release version update. |
| 22-Sep-1998 | Lee Damico | Document creation. |
Copyright © 1998-2011 The Open Group. All Rights Reserved.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.