Transport Layer Interface (TLI)

Description: OpenSS7 Documentation Conformance.

The Linux Fast-STREAMS X/Open Transport Interface (XTI) or Transport Layer Interface (TLI) library is tested to OpenGroup XNS 5.2, UNIX '98 and POSIX/SUSv3 specifications.

The strxnet package provides the timod(4) and tirdwr(4) STREAMS(9) modules. These modules are tested using the test-timod(8) and test-tirdwr(8) test programs contained in the package distribution.

The tirdwr test suite contains some x odd test cases listed in the table below. The strxnet package passes all of these test cases.

Test Group	Test Case	Test Reference	Test Description
Sanity checks	XNS-TIRDWR/0.1: Check test case guard timer.	(none)	Tests that the test case guard timer will fire and bring down the children.
Pushing and popping the tirdwr module	XNS-TIRDWR/1.1: Normal push and pop sequence	(none)	Tests the simple pushing and popping of the tirdwr module. It ensures that pushing the module on an empty stream has no effect, while popping the module from the stream results in a T_DISCON_REQ being sent to the transport peer.
Pushing and popping the tirdwr module	XNS-TIRDWR/1.2: Pop after orderly release	(none)	Tests the pushing and popping of the tirdwr module. It ensures that the pushing the module on an empty stream has no effect, while popping the module from the stream after receiving an orderly release indication results in a T_ORDREL_REQ being sent to the transport peer.
Pushing and popping the tirdwr module	XNS-TIRDWR/1.3: Push after receiving M_DATA	(none)	Tests that the module can be successfully pushed after a number of M_DATA have been received on the stream.
Pushing and popping the tirdwr module	XNS-TIRDWR/1.4: Push after receiving T_DATA_IND	(none)	Tests that the module cannot be pushed on a stream that has already received T_DATA_IND primitives.
Receiving data	XNS-TIRDWR/2.1: Receiving M_DATA	(none)	Tests that the application can receive data formatted as M_DATA messages after pushing the module.
Receiving data	XNS-TIRDWR/2.2: Receiving T_DATA_IND	(none)	Tests that the application can receive data formatted as T_DATA_IND messages after pushing the module.
Receiving data	XNS-TIRDWR/2.3: Receiving T_OPTDATA_IND	(none)	Tests that the application can receive data formatted as T_OPTDATA_IND messages after pushing the module.
Receiving data	XNS-TIRDWR/2.4: Receiving after orderly release	(none)	Tests that the application can receive data formatted as T_DATA_IND messages after pushing the module. It also ensures that the application will receive zero returns to reads after an orderly release indication has been received.
Receiving data	XNS-TIRDWR/2.5: Receiving after orderly release	(none)	Tests that the application can receive data formatted as T_DATA_IND messages after pushing the module. It also ensures that the application will receive zero returns to reads after disconnect indication has been received.
Sending data	XNS-TIRDWR/3.1: Sending data with write(2)	(none)	Tests that data can be sent with write(2) after pushing the module.
Sending data	XNS-TIRDWR/3.2: Sending data with writev(2)	(none)	Tests that data can be sent with writev(2) after pushing the module.
Sending data	XNS-TIRDWR/3.3: Sending data with putmsg(2)	(none)	Tests that data can be sent with putmsg(2) after pushing the module.
Sending data	XNS-TIRDWR/3.4: Sending data with putpmsg(2)	(none)	Tests that expedited data cannot be sent with putpmsg(2) after pushing the module.
Sending data	XNS-TIRDWR/3.5: Sending data with write(2) after orderly release	(none)	Tests that data can be sent with write(2) after orderly release.
Sending data	XNS-TIRDWR/3.6: Sending data with write(2) after abortive disconnect	(none)	Tests that data cannot be sent with write(2) after disconnect.
Sending data	XNS-TIRDWR/3.7: Sending data with putmsg(2) after orderly release	(none)	Tests that data can be sent with putmsg(2) after orderly release.
Sending data	XNS-TIRDWR/3.8: Sending data with putmsg(2) after abortive disconnect	(none)	Tests that data cannot be sent with putmsg(2) after disconnect.
Unexpected messages received from Transport Provider	XNS-TIRDWR/4.1.1: Receiving T_CONN_IND	(none)	Tests that receipt of a T_CONN_IND after the module has been pushed results in an error on the stream.
Unexpected messages received from Transport Provider	XNS-TIRDWR/4.1.2: Receiving T_CONN_CON	(none)	Tests that receipt of a T_CONN_CON after the module has been pushed results in an error on the stream.
Unexpected messages received from Transport Provider	XNS-TIRDWR/4.1.3: Receiving T_EXDATA_IND	(none)	Tests that receipt of a T_EXDATA_IND after the module has been pushed results in an error on the stream.
Unexpected messages received from Transport Provider	XNS-TIRDWR/4.1.4: Receiving T_INFO_ACK	(none)	Tests that receipt of a T_INFO_ACK after the module has been pushed results in an error on the stream.
Unexpected messages received from Transport Provider	XNS-TIRDWR/4.1.5: Receiving T_BIND_ACK	(none)	Tests that receipt of a T_BIND_ACK after the module has been pushed results in an error on the stream.
Unexpected messages received from Transport Provider	XNS-TIRDWR/4.1.6: Receiving T_ERROR_ACK	(none)	Tests that receipt of a T_ERROR_ACK after the module has been pushed results in an error on the stream.
Unexpected messages received from Transport Provider	XNS-TIRDWR/4.1.7: Receiving T_OK_ACK	(none)	Tests that receipt of a T_OK_ACK after the module has been pushed results in an error on the stream.
Unexpected messages received from Transport Provider	XNS-TIRDWR/4.1.8: Receiving T_UNITDATA_IND	(none)	Tests that receipt of a T_UNITDATA_IND after the module has been pushed results in an error on the stream.
Unexpected messages received from Transport Provider	XNS-TIRDWR/4.1.9: Receiving T_UDERROR_IND	(none)	Tests that receipt of a T_UDERROR_IND after the module has been pushed results in an error on the stream.
Unexpected messages received from Transport Provider	XNS-TIRDWR/4.1.10: Receiving T_OPTMGMT_ACK	(none)	Tests that receipt of a T_OPTMGMT_ACK after the module has been pushed results in an error on the stream.
Unexpected messages received from Transport Provider	XNS-TIRDWR/4.1.11: Receiving T_ADDR_ACK	(none)	Tests that receipt of a T_ADDR_ACK after the module has been pushed results in an error on the stream.
Unexpected messages received from Transport Provider	XNS-TIRDWR/4.1.12: Receiving T_CAPABILITY_ACK	(none)	Tests that receipt of a T_CAPABILITY_ACK after the module has been pushed results in an error on the stream.
Unexpected messages sent from the Transport User	XNS-TIRDWR/4.2.1: Sending T_CONN_REQ	(none)	Tests that sending a T_CONN_REQ after the module has been pushed results in an error on the stream.
Unexpected messages sent from the Transport User	XNS-TIRDWR/4.2.2: Sending T_CONN_RES	(none)	Tests that sending a T_CONN_RES after the module has been pushed results in an error on the stream.
Unexpected messages sent from the Transport User	XNS-TIRDWR/4.2.3: Sending T_DISCON_REQ	(none)	Tests that sending a T_DISCON_REQ after the module has been pushed results in an error on the stream.
Unexpected messages sent from the Transport User	XNS-TIRDWR/4.2.4: Sending T_DATA_REQ	(none)	Tests that sending a T_DATA_REQ after the module has been pushed results in an error on the stream.
Unexpected messages sent from the Transport User	XNS-TIRDWR/4.2.5: Sending T_EXDATA_REQ	(none)	Tests that sending a T_EXDATA_REQ after the module has been pushed results in an error on the stream.
Unexpected messages sent from the Transport User	XNS-TIRDWR/4.2.6: Sending T_INFO_REQ	(none)	Tests that sending a T_INFO_REQ after the module has been pushed results in an error on the stream.
Unexpected messages sent from the Transport User	XNS-TIRDWR/4.2.7: Sending T_BIND_REQ	(none)	Tests that sending a T_BIND_REQ after the module has been pushed results in an error on the stream.
Unexpected messages sent from the Transport User	XNS-TIRDWR/4.2.8: Sending T_UNBIND_REQ	(none)	Tests that sending a T_UNBIND_REQ after the module has been pushed results in an error on the stream.
Unexpected messages sent from the Transport User	XNS-TIRDWR/4.2.9: Sending T_UNITDATA_REQ	(none)	Tests that sending a T_UNITDATA_REQ after the module has been pushed results in an error on the stream.
Unexpected messages sent from the Transport User	XNS-TIRDWR/4.2.10: Sending T_OPTMGMT_REQ	(none)	Tests that sending a T_OPTMGMT_REQ after the module has been pushed results in an error on the stream.
Unexpected messages sent from the Transport User	XNS-TIRDWR/4.2.11: Sending T_ORDREL_REQ	(none)	Tests that sending a T_ORDREL_REQ after the module has been pushed results in an error on the stream.
Unexpected messages sent from the Transport User	XNS-TIRDWR/4.2.12: Sending T_OPTDATA_REQ	(none)	Tests that sending a T_OPTDATA_REQ after the module has been pushed results in an error on the stream.
Unexpected messages sent from the Transport User	XNS-TIRDWR/4.2.13: Sending T_ADDR_REQ	(none)	Tests that sending a T_ADDR_REQ after the module has been pushed results in an error on the stream.
Unexpected messages sent from the Transport User	XNS-TIRDWR/4.2.14: Sending T_CAPABILITY_REQ	(none)	Tests that sending a T_CAPABILITY_REQ after the module has been pushed results in an error on the stream.
Unexpected XTI IO controls from the Transport User	XNS-TIRDWR/4.3.1: Performing TI_GETINFO	(none)	Tests that performing a TI_GETINFO IO control after the module has been pushed results in an error on the stream.
Unexpected XTI IO controls from the Transport User	XNS-TIRDWR/4.3.2: Performing TI_OPTMGMT	(none)	Tests that performing a TI_OPTMGMT IO control after the module has been pushed results in an error on the stream.
Unexpected XTI IO controls from the Transport User	XNS-TIRDWR/4.3.3: Performing TI_BIND	(none)	Tests that performing a TI_BIND IO control after the module has been pushed results in an error on the stream.
Unexpected XTI IO controls from the Transport User	XNS-TIRDWR/4.3.4: Performing TI_UNBIND	(none)	Tests that performing a TI_UNBIND IO control after the module has been pushed results in an error on the stream.
Unexpected XTI IO controls from the Transport User	XNS-TIRDWR/4.3.5: Performing TI_GETMYNAME	(none)	Tests that performing a TI_GETMYNAME IO control after the module has been pushed results in an error on the stream.
Unexpected XTI IO controls from the Transport User	XNS-TIRDWR/4.3.6: Performing TI_GETPEERNAME	(none)	Tests that performing a TI_GETPEERNAME IO control after the module has been pushed results in an error on the stream.
Unexpected XTI IO controls from the Transport User	XNS-TIRDWR/4.3.7: Performing TI_SETMYNAME	(none)	Tests that performing a TI_SETMYNAME IO control after the module has been pushed results in an error on the stream.
Unexpected XTI IO controls from the Transport User	XNS-TIRDWR/4.3.8: Performing TI_SETPEERNAME	(none)	Tests that performing a TI_SETPEERNAME IO control after the module has been pushed results in an error on the stream.
Unexpected XTI IO controls from the Transport User	XNS-TIRDWR/4.3.9: Performing TI_SYNC	(none)	Tests that performing a TI_SYNC IO control after the module has been pushed results in an error on the stream.
Unexpected XTI IO controls from the Transport User	XNS-TIRDWR/4.3.10: Performing TI_GETADDRS	(none)	Tests that performing a TI_GETADDRS IO control after the module has been pushed results in an error on the stream.
Unexpected XTI IO controls from the Transport User	XNS-TIRDWR/4.3.11: Performing TI_CAPABILITY	(none)	Tests that performing a TI_CAPABILITY IO control after the module has been pushed results in an error on the stream.

The timod test suite contains some x odd test cases listed in the table below. The strxnet package passes all of these test cases.

Test Group	Test Case	Test Reference	Test Description
Sanity checks	XNS-TIMOD/0.1: Check test case guard timer.	(none)	Checks that the test case guard timer will fire and bring down the children.
Pushing and popping the timod module	XNS-TIMOD/1.1: Normal push and pop sequence	(none)	This test case tests the simple pushing and popping of the timod module. It ensures that pushing the module on an empty stream has no effect, while popping the module from the stream results in a T_DISCON_REQ being sent to the transport peer.
Performing IO controls on the timod module	XNS-TIMOD/2.1.1: TI_GETINFO IO control positive acknowledgement	(none)	This test case test the execution of the TI_GETINFO IO control with positive results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.1.2: TI_OPTMGMT IO control positive acknowledgement	(none)	This test case test the execution of the TI_OPTMGMT IO control with positive results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.1.3: TI_BIND IO control positive acknowledgement	(none)	This test case test the execution of the TI_BIND IO control with positive results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.1.4: TI_UNBIND IO control positive acknowledgement	(none)	This test case test the execution of the TI_UNBIND IO control with positive results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.1.5: TI_GETMYNAME IO control positive acknowledgement	(none)	This test case test the execution of the TI_GETMYNAME IO control with positive results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.1.6: TI_GETPEERNAME IO control positive acknowledgement	(none)	This test case test the execution of the TI_GETPEERNAME IO control with positive results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.1.7.1: TI_SETMYNAME IO control positive acknowledgement	(none)	This test case test the execution of the TI_SETMYNAME IO control with positive results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.1.7.2: TI_SETMYNAME (disconnect) IO control positive acknowledgement	(none)	This test case test the execution of the TI_SETMYNAME (disconnect) IO control with positive results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.1.8.1: TI_SETPEERNAME IO control positive acknowledgement	(none)	This test case test the execution of the TI_SETPEERNAME IO control with positive results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.1.8.2: TI_SETPEERNAME (disconnect) IO control positive acknowledgement	(none)	This test case test the execution of the TI_SETPEERNAME (disconnect) IO control with positive results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.1.10: TI_GETADDRS IO control positive acknowledgement	(none)	This test case test the execution of the TI_GETADDRS IO control with positive results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.1.11: TI_CAPABILITY IO control positive acknowledgement	(none)	This test case test the execution of the TI_CAPABILITY IO control with positive results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.2.1: TI_GETINFO IO control negative acknowledgement	(none)	This test case test the execution of the TI_GETINFO IO control with negative results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.2.2: TI_OPTMGMT IO control negative acknowledgement	(none)	This test case test the execution of the TI_OPTMGMT IO control with negative results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.2.3: TI_BIND IO control negative acknowledgement	(none)	This test case test the execution of the TI_BIND IO control with negative results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.2.4: TI_UNBIND IO control negative acknowledgement	(none)	This test case test the execution of the TI_UNBIND IO control with negative results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.2.5: TI_GETMYNAME IO control negative acknowledgement	(none)	This test case test the execution of the TI_GETMYNAME IO control with negative results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.2.6: TI_GETPEERNAME IO control negative acknowledgement	(none)	This test case test the execution of the TI_GETPEERNAME IO control with negative results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.2.7.1: TI_SETMYNAME IO control negative acknowledgement	(none)	This test case test the execution of the TI_SETMYNAME IO control with negative results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.2.7.2: TI_SETMYNAME (disconnect) IO control negative acknowledgement	(none)	This test case test the execution of the TI_SETMYNAME (disconnect) IO control with negative results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.2.8.1: TI_SETPEERNAME IO control negative acknowledgement	(none)	This test case test the execution of the TI_SETPEERNAME IO control with negative results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.2.8.2: TI_SETPEERNAME (disconnect) IO control negative acknowledgement	(none)	This test case test the execution of the TI_SETPEERNAME (disconnect) IO control with negative results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.2.10: TI_GETADDRS IO control negative acknowledgement	(none)	This test case test the execution of the TI_GETADDRS IO control with negative results on using the timod module.
Performing IO controls on the timod module	XNS-TIMOD/2.2.11: TI_CAPABILITY IO control negative acknowledgement	(none)	This test case test the execution of the TI_CAPABILITY IO control with negative results on using the timod module.
Multiple process IO controls	XNS-TIMOD/2.3: Two child processes attempting same IO control	(none)	This test case tests two child processes attempting the same IO control. One is given a positive acknowledgement and the other a negative acknowledgement.
IO controls with data	XNS-TIMOD/2.4.1: TI_SETMYNAME with data	(none)	Tests that IO controls with optional data parts can be sent with data. This test case tests the TI_SETMYNAME IO control.
IO controls with data	XNS-TIMOD/2.4.2: TI_SETPEERNAME with data	(none)	Tests that IO controls with optional data parts can be sent with data. This test case tests the TI_SETPEERNAME IO control.
IO controls with data	XNS-TIMOD/2.4.3: TI_SETMYNAME (disconnect) with data	(none)	Tests that IO controls with optional data parts can be sent with data. This test case tests the TI_SETMYNAME (disconnect) IO control.
IO controls with data	XNS-TIMOD/2.4.4: TI_SETPEERNAME (disconnect) with data	(none)	Tests that IO controls with optional data parts can be sent with data. This test case tests the TI_SETPEERNAME (disconnect) IO control.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.1.1: T_INFO_REQ with positive acknowledgement	(none)	This test case test the pass through of T_INFO_REQ with positive acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.1.2: T_CONN_REQ with positive acknowledgement	(none)	This test case test the pass through of T_CONN_REQ with positive acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.1.3: T_CONN_RES with positive acknowledgement	(none)	This test case test the pass through of T_CONN_RES with positive acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.1.4: T_DISCON_REQ with positive acknowledgement	(none)	This test case test the pass through of T_DISCON_REQ with positive acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.1.5: T_BIND_REQ with positive acknowledgement	(none)	This test case test the pass through of T_BIND_REQ with positive acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.1.6: T_UNBIND_REQ with positive acknowledgement	(none)	This test case test the pass through of T_UNBIND_REQ with positive acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.1.7: T_OPTMGMT_REQ with positive acknowledgement	(none)	This test case test the pass through of T_OPTMGMT_REQ with positive acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.1.8: T_ADDR_REQ with positive acknowledgement	(none)	This test case test the pass through of T_ADDR_REQ with positive acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.1.9: T_CAPABILITY_REQ with positive acknowledgement	(none)	This test case test the pass through of T_CAPABILITY_REQ with positive acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.2.1: T_INFO_REQ with negative acknowledgement	(none)	This test case test the pass through of T_INFO_REQ with negative acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.2.2: T_CONN_REQ with negative acknowledgement	(none)	This test case test the pass through of T_CONN_REQ with negative acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.2.3: T_CONN_RES with negative acknowledgement	(none)	This test case test the pass through of T_CONN_RES with negative acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.2.4: T_DISCON_REQ with negative acknowledgement	(none)	This test case test the pass through of T_DISCON_REQ with negative acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.2.5: T_BIND_REQ with negative acknowledgement	(none)	This test case test the pass through of T_BIND_REQ with negative acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.2.6: T_UNBIND_REQ with negative acknowledgement	(none)	This test case test the pass through of T_UNBIND_REQ with negative acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.2.7: T_OPTMGMT_REQ with negative acknowledgement	(none)	This test case test the pass through of T_OPTMGMT_REQ with negative acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.2.8: T_ADDR_REQ with negative acknowledgement	(none)	This test case test the pass through of T_ADDR_REQ with negative acknowledgement.
Non-IO control pass through of TPI messages	XNS-TIMOD/3.2.9: T_CAPABILITY_REQ with negative acknowledgement	(none)	This test case test the pass through of T_CAPABILITY_REQ with negative acknowledgement.