SCTP_TS: Valid8.com/ACATS SCTP Conformance Test Suite V.2.0, for use with SCTP Signaling Tester
TEST SUITE OVERVIEW
ReferencesETSI TS 102 369 V1.1.1 (2004-11) / ETSI TS 102 144 V1.1.1) / IETF RFC4960, 2960, 3309
Archive/Projectvoip/sctp_ts
Version19171703
Date20 Dec 2009
Number of Scenarios337
Number of Groups74
Average per Group4
GROUP/SCENARIOTEST PURPOSE
Initialize_SCTP_IUT_ServerInitialize SCTP towards IUT and verify an association can be made
Reference: DTS/MTS-00086 v0.0.4 (2004-07)
Initialize_SCTP_IUT_ClientReceive incoming SCTP connection from IUT and verify an association can be made
Reference: DTS/MTS-00086 v0.0.4 (2004-07)
SCTP_Client_Tests
SCTP_Client_Tests/
SCTP_AS
SCTP_Client_Tests/
SCTP_AS/
SCTP_AS_V
SCTP_AS_V_1_1_1Ensure the IUT makes a complete association procedure
Configure the IUT to send an INIT to the tester.
SUT: Client
Reference: RFC 4960/2960 [1], sections 5.1[1] and 5.1.6[1]
SCTP_AS_V_1_5_1Ensure that the IUT on re-establishing an association to a peer, uses a random Initiate-Tag value in the INIT message
association can be established and terminated between tester and SUT.
Status: Mandatory
SCTP_AS_V_1_6_2Ensure that the IUT on receipt of an INIT-ACK message with the listed parameters accepts this message
and responds to it.
tester such that the listed parameters (IPv4 Address Parameter, IPv6 Address Parameter, CookiePreservative
are sent in INIT-ACK message.
SUT: Client
SCTP_AS_V_1_7_3 Ensure that the IUT, if there is a mismatch in the Outbound Stream and Inbound Stream parameters in INIT and INIT-ACK message,
either aborts the association or settles with minimum of the two parameters.
at the tester such that INIT-ACK message is sent from tester with MaximumInboundStreams XSUT: Client
SCTP_AS_V_1_10_2 Ensure that the IUT on receipt of an INIT-ACK message with no optional IP
addresses sends an COOKIE_ECHO message to the source IP address from which
INIT-ACK was received.
the data at the tester such that no IP addresses are sent in INIT-ACK optional
IP address field.
SUT: Client
SCTP_AS_V_1_11_2Ensure that the IUT on receipt of an INIT-ACK message with one or more
IP addresses uses all of these IP addresses plus the IP address from where
INIT-ACK comes combined with the SCTP source port number as the destination
transport address and sends an COOKIE-ECHO message to one of the transport
addresses.
Arrange the data at the tester such that one or more IP addresses are sent
in INIT-ACK message.
SUT: Client
SCTP_Client_Tests/
SCTP_AS/
SCTP_AS_I
SCTP_AS_I_1_2_1Ensure that the IUT, if T1-Init timer expires, transmits the INIT message again
Arrange the data at the tester such that INIT-ACK is never sent in response to INIT message.
SUT: Client
SCTP_AS_I_1_2_2Ensure that the IUT, if T1-Cookie timer expires, transmits the COOKIE-ECHO message again
to send an INIT to the tester. Arrange the data at the tester such that COOKIE-ACK is not
sent in response to COOKIE-ECHO message
Status: Mandatory
SUT: Client
Reference: RFC 4960/2960 [1], sections 5.1[1] and 5.1.6[1]
SCTP_AS_I_1_3_1Ensure that the IUT, if INIT is retransmitted for MAX_INIT_RETRANS times, stops the initialisation
process.
to the tester. Arrange the data at the tester such that INIT-ACK is never sent in response to INIT message
SUT: Client
Reference: RFC 4960/2960 [1], section 4 (Note 2) [1]
SCTP_AS_I_1_3_2Ensure that the IUT, if COOKIE-ECHO message is retransmitted for MAX_INIT_RETRANS times, stops the initialisation process
Arrange the data at the tester such that COOKIE-ACK is never sent in response to COOKIE-ECHO message.
SUT: Client
Status: Mandatory
SCTP_AS_I_1_7_4 Ensure that the IUT, if OutboundStreams is found zero in the received INIT-ACK message, destroys its TCB and may send an ABORT message
for that INIT-ACK. Further message exchanges between tester and IUT need to take place to verify the TCB removal from outside the SUT.
the tester such that INIT-ACK message with OutboundStreams equal to 0 is sent from tester.
SUT: Client
SCTP_AS_I_1_12_2Ensure that the IUT on receipt of an INIT-ACK message with Host Name address
and no other IP address sends an ABORT message with error Unresolvable Address.
the data at the tester such that Host Name address is sent to SUT with no other
IP address in INIT-ACK message
SUT: Client
SCTP_AS_I_1_14_2Ensure that the IUT on receipt of an INIT-ACK message with Init-Tag equal to
zero destroys the TCB and may send an ABORT.
Arrange the data at the tester such that Initiate-tag field equal to zero is
sent to SUT in INIT-ACK message.
SUT: Client
SCTP_AS_I_1_15Ensure that the IUT uses all configured addresses for association
establishment.
addresses X and Y. Association is not established between tester and
SUT. Arrange the data at the tester such that no INIT-ACK message is sent
to SUT in Response to an INIT.
SUT: Client
SCTP_Client_Tests/
SCTP_AS/
SCTP_AS_O
SCTP_AS_O_1_9_1Ensure the IUT on receipt of an INIT message for starting an association with
transport addresses which are already in assocation, responds with an INIT-ACK
message.
data at the tester such that INIT message is sent for making an association with
SUT using the same IP addresses.
SUT: MGC
Reference: RFC 4960/2960 [1], sections 5.2.2 and darft ietf[6], section 2.6
SCTP_AS_O_1_9_2Ensure the IUT on receipt of an INIT message for starting association with
transport addresses which are not the same as the already established, responds
with an ABORT message with error "restart of an association with new
addresses.
data at the tester such that INIT message is sent for establishing an
association with SUT. The additional transport addresses should contain a
new, not yet used, IP address.
SUT: MGC
Reference: RFC 4960/2960 [1], sections 5.1[1] and 5.1.6[1]
SCTP_Client_Tests/
SCTP_AT
SCTP_Client_Tests/
SCTP_AT/
SCTP_AT_V
SCTP_Client_Tests/
SCTP_IMH
SCTP_Client_Tests/
SCTP_IMH/
SCTP_IMH_I
SCTP_IMH_I_3_2 Ensure that the IUT on receipt of an invalid INIT-ACK message with message
length < length of all mandatory parameters, discards the message or may send
an ABORT message.
Pre-condition: Association is not established between tester and SUT. Arrange
the data at the tester such that INIT-ACK message is sent to SUT with message
length less than the length of all mandatory parameters.
Reference:RFC 4960/2960[1], section 5.1
SUT: Client
SCTP_Client_Tests/
SCTP_DM
SCTP_Client_Tests/
SCTP_DM/
SCTP_DM_O
SCTP_DM_O_4_1 Ensure that the IUT on receipt of an INIT message after sending
an INIT message on its own, sends an INIT-ACK message.
Arrange the data at the tester such that INIT message is sent to
SUT upon reception of an INIT from the SUT.
SUT: Client
SCTP_DM_O_4_3Ensure that the IUT on receipt of a duplicate INIT-ACK message, after sending
a COOKIE-ECHO message, discards the INIT-ACK message.
Arrange the data at the tester such that the same INIT-ACK message is
sent to SUT after receiving COOKIE-ECHO message.
SUT: Client
SCTP_DM_O_4_6_1Ensure that the IUT on receipt of a SHUTDOWN message, after sending an
INIT message on its own, discards the SHUTDOWN message.
Arrange the data at the tester such that SHUTDOWN message is sent to SUT after
receiving INIT message from it.
SUT: Client
SCTP_DM_O_4_7_1Ensure that the IUT on receipt of a SHUTDOWN-ACK message, in Cookie Wait
state, sends a SHUTDOWN-COMPLETE message and current state is not disturbed.
Arrange the data at the tester such that SHUTDOWN-ack message is sent to SUT after
receiving INIT message from it.
SUT: Client
SCTP_DM_O_4_9Ensure the IUT on receipt of a SHUTDOWN COMPLETE message in Cookie wait
state, discards the message.
Arrange the data at the tester such that SHUTDOWN COMPLETE message is
sent to SUT after receiving INIT message from it.
Status: Mandatory
Reference: RFC 4960/2960 [1], sections 9.2
SCTP_Client_Tests/
SCTP_FH
SCTP_Client_Tests/
SCTP_FH/
SCTP_FH_V
SCTP_Client_Tests/
SCTP_FH/
SCTP_FH_O
SCTP_Client_Tests/
SCTP_E
SCTP_Client_Tests/
SCTP_E/
SCTP_E_O
SCTP_E_O_6_1Ensure that the IUT on receipt of ERROR message with cause Stale
Cookie Error in Cookie Echoed state, takes one of the following
actions depending on the implementation:
1) Sends a new INIT message to the tester to generate a new
cookie and reattempt the setup procedure.
2) Discards the TCB and changes the state to closed.
3) Sends a new INIT message to the tester adding a cookie
preservative parameter requesting the extension on lifetime
of cookie.
Arrange the data at the tester such that ERROR message with cause stale
cookie error is sent in response to COOKIE-ECHO message.
SUT: Client
SCTP_Client_Tests/
SCTP_E/
SCTP_E_I
SCTP_E_I_6_4Ensure that the IUT on receipt of INIT-ACK message without a Cookie
parameter, sends an ERROR message with cause Missing Mandatory
Parameter or may send an ABORT or no message at all.
Arrange the data at the tester such that a INIT-ACK is sent to SUT
without Cookie parameter.
SUT: Client
SCTP_E_I_6_5Ensure that the IUT on receipt of INIT-ACK message with an
unknown TLV parameter, sends an ERROR message with cause
Unrecognized Parameters.
Arrange the data at the tester such that a INIT-ACK is sent to SUT
with an unknown TLV parameter.
SUT: Client
SCTP_Client_Tests/
SCTP_BDC
SCTP_Client_Tests/
SCTP_BDC/
SCTP_BDC_V
SCTP_BDC_V_7_5Ensure that the IUT on receipt of COOKIE-ACK chunk
bundled with DATA chunks, accepts the COOKIE-ACK and
responds with a SACK.
Arrange the data at the tester such that DATA chunks are bundled with
COOKIE-ACK with COOKIE-ACK as the first chunk.
SUT: Client
SCTP_Client_Tests/
SCTP_BDC/
SCTP_BDC_I
SCTP_BDC_I_7_2Ensure that the IUT on receipt of DATA chunks bundled with
INIT-ACK chunk discards this packet or sends an ABORT or
accepts the INIT-ACK but ignores the DATA chunks.
Arrange the data at the tester such that a data chunks are bundled
with INIT-ACK message.
SUT: Client
SCTP_Client_Tests/
SCTP_D
SCTP_Client_Tests/
SCTP_D/
SCTP_D_V
SCTP_Client_Tests/
SCTP_D/
SCTP_D_I
SCTP_Client_Tests/
SCTP_A
SCTP_Client_Tests/
SCTP_A/
SCTP_A_V
SCTP_Client_Tests/
SCTP_A/
SCTP_A_O
SCTP_Client_Tests/
SCTP_M
SCTP_Client_Tests/
SCTP_M/
SCTP_M_I
SCTP_Client_Tests/
SCTP_RT
SCTP_Client_Tests/
SCTP_RT/
SCTP_RT_I
SCTP_Server_Tests
SCTP_Server_Tests/
SCTP_AS
SCTP_Server_Tests/
SCTP_AS/
SCTP_AS_V
SCTP_AS_V_1_1_2Ensure the IUT can establish a complete association after receiving an INIT from the tester
Arrange the data at the tester such that an INIT is sent to IUT.
SUT: Server
Status: Mandatory
Reference: RFC 4960/2960 [1], sections 5.1 [1] and 5.1.6[1]
SCTP_AS_V_1_5_2 Ensure that the IUT on re-establishing an association to a peer, uses a random Initiate-Tag value in the INIT-ACK message
Pre-condition: Association is not established between tester and SUT. Arrange the data at the tester such that normal association
can be established and terminated between tester and SUT.
SUT: Server
SCTP_AS_V_1_6_1Ensure that the IUT on receipt of an INIT message with the listed parameters accepts this message
and responds to it.
tester such that the listed parameters (IPv4 Address Parameter, IPv6 Address Parameter, CookiePreservative,
Supported Address Type Parameter) are sent in INIT message.
SUT: Server
SCTP_AS_V_1_7_1Ensure that the IUT, if there is a mismatch in the Outbound Stream and Inbound Stream parameters
in INIT and INIT-ACK message, either aborts the association or settles with minimum of the two parameters.
of the SUT is Z. Arrange data at the tester such that INIT message is sent from tester with MaximumInboundStreams YSUT: Server
SCTP_AS_V_1_7_5Ensure that the IUT supports at least 2 incoming streams and 2 outgoing streams
at the tester such that INIT message is sent from tester with OutboundStreams and
MaximumInboundStreams set to 2.
SUT: Server
SCTP_AS_V_1_10_1 Ensure that the IUT on receipt of an INIT message with no IP addresses
sends an INIT-ACK message to the source IP address from where INIT was
received.
Arrange the data at the tester such that no IP addresses are sent in INIT.
SUT: Server
SCTP_AS_V_1_11_1Ensure that the IUT on receipt of an INIT message with one or more IP
addresses sends an INIT-ACK message to the source IP addresses from where
INIT was received and uses all of these IP address plus the IP address
from where INIT comes combined with the SCTP source port number as the
destination transport address.
Arrange the data at the tester such that one or more IP addresses are sent in INIT message.
SUT: Server
SCTP_AS_V_1_12_1Ensure that the IUT on receipt of an INIT message with Host Name address and
no other IP address sends an ABORT message with error Unresolvable Address.
the data at the tester such that Host Name address is sent to SUT with no other
IP address in INIT message
SUT: Server
SCTP_AS_V_1_13_1Ensure that the IUT on receipt of an INIT message with Supported address field
sends an INIT-ACK message with the address of the type contained in the
Supported address field in the received INIT.
the data at the tester such that Supported Address field is sent in INIT. Also
the SUT is capable of using the address type mentioned in Supported Address field.
SUT: Server
SCTP_Server_Tests/
SCTP_AS/
SCTP_AS_I
SCTP_AS_I_1_4Ensure that the IUT remains in closed state if COOKIE-ECHO message is not received
INIT-ACK message. Also let maximum no of association which SUT can establish is n and n-1 of them are already established. Try to make the nth association.
SUT: Server
SCTP_AS_I_1_7_2Ensure that the IUT, if OutboundStreams are found zero in the received INIT message,
sends an ABORT message for that INIT. or silently discards the received message.
the tester such that INIT message with OutboundStreams equal to 0 is sent from tester.
SUT: Server
SCTP_AS_I_1_8_1Ensure that the IUT on receipt of unrecognised TLV parameters in received INIT message fills them
in the Unrecognised Parameters of the INIT-ACK and continues on processing of further parameters.
such that a datagram with undefined parameter type and MSB two bits in the parameter type equal
to 11 is sent to tester.
SUT: Server
Status: Mandatory
Reference: RFC4960/2960, section 3.3.3.1 / DTS/MTS-00086 v0.0.4 (2004-07)
SCTP_AS_I_1_8_2 Ensure that the IUT on receipt of an unrecognized parameter in the INIT-chunk does not process any further parameters and does not report it
a datagram with undefined parameter type and MSB two bits in the parameter type equal to 00 is sent to the IUT
Status: Mandatory
SUT: Server
SCTP_AS_I_1_8_3 Ensure that the IUT on receipt of an unrecognized parameter in the INIT-chunk does not process any further
parameters and report it using an Unrecognized Parameters parameter field."
datagram with undefined parameter type and MSB two bits in the parameter type equal to 01 is sent to the IUT.
SUT: Server
SCTP_AS_I_1_8_4Ensure that the IUT on receipt of an unrecognized
parameter in the INIT-chunk skips this parameter and does process any further parameters.
tester such that a datagram with undefined parameter type and MSB two bits in the parameter
type equal to 10 is sent to the IUT.
Status: Mandatory
SUT: Server
SCTP_AS_I_1_13_2Ensure that the IUT on receipt of an INIT message with Supported address type
which the receiver is incapable of using sends an ABORT message with cause
Unresolvable Address.
the data at the tester such that Supported address type field IPv6 is sent to
SUT in INIT message (END USER PLEASE NOTE: Supported Address Type IPv4 will not
be sent. Your SUT should not support IPv6.). Also
receiver (i.e. SUT) is not capable of using supported address type, i.e ONLY
IPv4.
SUT: Server
SCTP_AS_I_1_14_1Ensure that the IUT on receipt of an INIT message with Init-Tag equal to zero
destroys the TCB and may send an ABORT.
Pre-condition: Association is not established between tester and SUT. Arrange
the data at the tester such that Initiate-tag field equal to zero is sent to
SUT in INIT message.
SUT: Server
SCTP_Server_Tests/
SCTP_IMH
SCTP_Server_Tests/
SCTP_IMH/
SCTP_IMH_I
SCTP_IMH_I_3_1 Ensure that the IUT on receipt of an invalid INIT message with message
length < length of all mandatory parameters, discards the message or may
send an ABORT message.
the data at the tester such that INIT message is sent to SUT with message
length less than the length of all mandatory parameters.
SUT: Server
SCTP_IMH_I_3_3 Ensure that the IUT on receipt of a COOKIE-ECHO message with invalid
verification tag, discards the COOKIE-ECHO message.
Arrange the data at the tester such that COOKIE-ECHO message with a
different verification tag (Different from what received in INIT-ACK)
is sent in response to INIT-ACK.
SUT: Server
SCTP_IMH_I_3_4 Ensure that the IUT on receipt of an INIT message with wrong CRC-32c
checksum, discards the INIT message.
Tester_IP_CDC --> RFC3309_CRC32_Checksum in the System Configuration to FALSE
and restart the test environment.
Arrange data at the tester such that it sends INIT message to SUT with
wrong CRC-32c checksum.
SUT: Server
SCTP_IMH_I_3_5 Ensure that the IUT on receipt of a COOKIE-ECHO message with other cookie
than sent in INIT_ACK, discards the message.
the data at the tester such that COOKIE-ECHO message is sent with cookie
different from received cookie in INIT-ACK.
SUT: Server
SCTP_IMH_I_3_6Ensure that the IUT on receipt of a COOKIE-ECHO message after lifetime
received in INIT-ACK message has expired, should send an ERROR with cause
“"Stale Cookie Error”".
the data at the tester such that COOKIE-ECHO message is sent after life time
of the received cookie in INIT-ACK message has expired.
SUT: Server
SCTP_IMH_I_3_8 Ensure that the IUT on receipt of an INIT message with a packet length
smaller than the Chunk length defined, sends an ABORT message or discards
the message.
the data at the tester such that chunk length is greater than the length of
the message being sent to other SUT.
SUT: Server
SCTP_IMH_I_3_9Ensure that the IUT on receipt of a SHUTDOWN-ACK message with invalid
verification tag, discards the message.
tester such that SHUTDOWN-ACK message with invalid verification tag is sent to SUT in
Shutdown Sent state.
SUT: Server
SCTP_Server_Tests/
SCTP_DM
SCTP_Server_Tests/
SCTP_DM/
SCTP_DM_O
SCTP_DM_O_4_2_1Ensure that the IUT on receipt of an INIT message when association
is already established, sends an INIT-Ack message and existing
association is not disturbed.
to SUT when association is established between tester and SUT. Also, source IP
address, destination IP address and port numbers are the same as in the established
association.
SUT: Server
SCTP_Server_Tests/
SCTP_E
SCTP_Server_Tests/
SCTP_E/
SCTP_E_I
SCTP_E_I_6_6Ensure that the IUT on receipt of COOKIE-ECHO message
bundled with error (cause = Unrecognized Parameter),
continues to establish the association.
Arrange the data at the tester such that COOKIE-ECHO bundled with
ERROR (cause = Unrecognized Parameters) is sent to SUT.
SUT: Server
SCTP_Server_Tests/
SCTP_BDC
SCTP_Server_Tests/
SCTP_BDC/
SCTP_BDC_V
SCTP_BDC_V_7_4Ensure that the IUT on receipt of COOKIE-ECHO chunk
bundled with DATA chunks, accepts the packet and responds
with a COOKIE-ACK bundled with a SACK or a single
COOKIE-ACK and then a SACK.
Arrange the data at the tester such that DATA chunks are bundled with
COOKIE-ECHO as the first chunk.
SUT: Server
SCTP_Server_Tests/
SCTP_BDC/
SCTP_BDC_I
SCTP_BDC_I_7_1Ensure that the IUT on receipt of any DATA chunks
bundled with INIT chunk discard this packet.
Arrange the data at the tester such that data chunks are bundled
with INIT message.
section 2.11
SUT: Server
SCTP_Generic_Tests
SCTP_Generic_Tests/
SCTP_AT
SCTP_Generic_Tests/
SCTP_AT/
SCTP_AT_V
SCTP_AT_V_2_2Ensure that the IUT on receipt of an ABORT removes the association. Further message exchanges between
tester and IUT need to take place to verify the removal of the association from outside the SUT.
such that an ABORT message is sent to SUT in it.
SUT: Client or Server
SCTP_AT_V_2_6Ensure that the IUT on receipt of SHUTDOWN-ACK message in Shutdown Sent state
sends a SHUTDOWN COMPLETE message and terminates the association.
tester such that SHUTDOWN-ACK is sent in response to SHUTDOWN message.
SUT: Client or Server
SCTP_AT_V_2_14Ensure that the IUT, if there is still outstanding DATA, receives a SHUTDOWN
that acknowledges the outstanding DATA, sends a SHUTDOWN-ACK.
tester such that there is still outstanding DATA in IUT which has not been acknowledged
by SACK and that the tester sends SHUTDOWN MESSAGE to IUT that acknowledges this DATA.
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_AT/
SCTP_AT_I
SCTP_AT_I_2_3Ensure that the IUT on receipt of an Terminate primitive will send a SHUTDOWN
message to its peer only when all the outstanding DATA has been acknowledged
by the tester.
sent from SUT to the tester. Arrange the data in SUT such that Terminate
primitive is received from upper layers.
SUT: Client or Server
SCTP_AT_I_2_4Ensure that the IUT starts the T2-Shutdown timer and after its expiry a SHUTDOWN message is
sent again.
tester such that no SHUTDOWN-ACK or DATA is sent in response to SHUTDOWN.
SUT: Client or Server
SCTP_AT_I_2_5Ensure that the IUT after retransmitting SHUTDOWN message for ASSOCIATION.MAX.RETRANS
or TimeOut occurs for T5-shutdown-guard timer, removes the association and optionally
sends an ABORT. Further message exchanges between tester and IUT need to take place to
verify the removal of the association from outside the SUT.
tester such that in response to SHUTDOWN no SHUTDOWN-ACK or DATA message is sent.
SUT: Client or Server
SCTP_AT_I_2_7_1Ensure that the IUT, if it is in Shutdown sent state and receives data for transmission
from upper layer, does not send this new data.
such that upper layers send data to transmit when it is in Shutdown sent state.
SUT: Client or Server
SCTP_AT_I_2_7_2Ensure that the IUT, if it is in Shutdown receive state and receives data for transmission
from upper layer, does not send this new data.
such that upper layers send data to transmit when it is in Shutdown receive state.
SUT: Client or Server
SCTP_AT_I_2_7_3Ensure that the IUT, if it is in Shutdown pending state and receives data for transmission
from upper layer, does not send this new data.
such that upper layers send data to transmit when it is in Shutdown pending state.
SUT: Client or Server
SCTP_AT_I_2_7_4Ensure that the IUT, if it is in Shutdown-Ack sent state and receives data for transmission
from upper layer, does not send this new data.
such that upper layers send data to transmit when it is in Shutdown-Ack sent state.
SUT: Client or Server
SCTP_AT_I_2_8Ensure that the IUT, if it is in Shutdown Sent state and receives data,
acknowledges the message and restarts the T2-Shutdown timer.
tester such that after receiving SHUTDOWN message, DATA message is sent to SUT.
SUT: Client or Server
SCTP_AT_I_2_9Ensure that the IUT, if it is in Shutdown Receive state and receives data,
discards the data.
tester such that DATA is sent to SUT after sending SHUTDOWN message. Also in SUT there
is outstanding DATA for which SACK has not come from tester.
SUT: Client or Server
SCTP_AT_I_2_10Ensure that the IUT, if there is still outstanding DATA, does not send a
SHUTDOWN-ACK on reception of a SHUTDOWN (even received multiple times).
tester such that it sends SHUTDOWN message to IUT. The SHUTDOWN should not acknowledge the
last used DATA of the SUT, i.e. that in IUT there is still outstanding DATA which has not been
acknowledged. Then a second SHUTDOWN has to be sent which again does not acknowledge the
last used DATA of the IUT.
SUT: Client or Server
SCTP_AT_I_2_11Ensure that the IUT, after expiry of T2-Shutdown timer, sends a SHUTDOWN-ACK
message again.
tester such that no SHUTDOWN COMPLETE is sent in response to SHUTDOWN-ACK.
SUT: Client or Server
SCTP_AT_I_2_12Ensure that the IUT, after retransmitting SHUTDOWN-ACK message for
ASSOCIATION.MAX.RETRANS times, removes the association and optionally
sends an ABORT.
tester such that no SHUTDOWN COMPLETE is sent in response to SHUTDOWN-ACK.
SUT: Client or Server
SCTP_AT_I_2_13Ensure that the IUT, if it is in Shutdown-Ack Sent state, accept a
SHUTDOWN COMPLETE message and removes the association.
tester such that SHUTDOWN COMPLETE is sent in response to SHUTDOWN-ACK.
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_IMH
SCTP_Generic_Tests/
SCTP_IMH/
SCTP_IMH_I
SCTP_IMH_I_3_7 Ensure that the IUT on receipt of an ABORT message with incorrect
verification tag, discards the message.
Arrange the data at the tester such that ABORT message is sent to
SUT with incorrect verification tag.
SUT: Client or Server
SCTP_IMH_I_3_10Ensure that the IUT on receipt of a SHUTDOWN-COMPLETE message with invalid
verification tag, discards the message.
tester such that SHUTDOWN-COMPLETE message with invalid verification tag is sent to SUT in
Shutdown Ack Sent state.
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_DM
SCTP_Generic_Tests/
SCTP_DM/
SCTP_DM_O
SCTP_DM_O_4_2_2Ensure that the IUT on receipt of an INIT message after sending
a SHUTDOWN-ACK message, discards the INIT message and retransmits
the SHUTDOWN-ACK message.
Arrange the data at the tester such that after sending a SHUTDOWN-ACK
message, discards the INIT message and retransmits the SHUTDOWN-ACK
message.
SUT: Client or Server
SCTP_DM_O_4_4Ensure that the IUT on receipt of a COOKIE-ACK message, after association is
established, discards the COOKIE-ACK message.
Arrange the data at the tester such that COOKIE+ACK message is retransmitted to
SUT after association is established between tester and sut.
SUT: Client or Server
SCTP_DM_O_4_5Ensure that the IUT on receipt of a SHUTDOWN message, after sending a
SHUTDOWN message on its own, sends a SHUTDOWN-ACK message.
Arrange the data at the tester such that SHUTDOWN message is send after
receiving SHUTDOWN message from the other end.
SUT: Client or Server
SCTP_DM_O_4_6_2Ensure that the IUT on receipt of a SHUTDOWN message in closed state, sends
an ABORT message.
sent to SUT which is in closed state.
Reference: RFC 4960/2960, section 9.2
SUT: Client or Server
SCTP_DM_O_4_6_3Ensure that the IUT on receipt of a SHUTDOWN message in Shutdown Sent state,
sends a SHTUDOWN-ACK message and restarts T2-Shutdown timer.
data in SUT such that terminate primitve is received from ULP to terminate the
association. Arrange data at the tester such that SHUTDOWN message is sent to
SUT.
SUT: Client or Server
SCTP_DM_O_4_7_2Ensure that the IUT on receipt of a SHUTDOWN-ACK message, in Established
state, discards the message or sends an ABORT.
Arrange the data at the tester such that SHUTDOWN-ack message is sent to SUT
with correct verification tag.
SUT: Client or Server
SCTP_DM_O_4_7_3Ensure that the IUT on receipt of a SHUTDOWN-ACK message in SHUTDOWN-ACK
sent state, send a SHUTDOWN-COMPLETE message and closes the association.
data at the tester such that SHUTDOWN message is sent to SUT. Also,
SHUTDOWN-ACK message is sent to SUT after receiving SHUTDOWN-ACK message.
SUT: Client or Server
SCTP_DM_O_4_8Ensure that the IUT on receipt of a COOKIE-ECHO message in Established
state, discards the message and current state is not disturbed.
data at the tester such that COOKIE-ECHO message with invalid Message
Authentication Code (MAC) is sent to SUT.
SUT: Client or Server
SCTP_DM_O_4_10Ensure that the IUT on receipt of a data message in Shutdown-Ack sent state,
discards the message and may send an ABORT.
data at the tester such that SHUTDOWN message is sent to SUT. Also,
DATA message is sent from tester to SUT.
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_FH
SCTP_Generic_Tests/
SCTP_FH/
SCTP_FH_V
SCTP_FH_V_5_2Ensure that the IUT on receipt of a HEARTBEAT message, sends a HEARTBEAT-ACK
message with the information carried in the HEARTBEAT message.
data at the tester such that HEARTBEAT message is sent to the SUT.
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_FH/
SCTP_FH_I
SCTP_FH_I_5_1_1Ensure that the IUT when total number of consecutive retransmissions
to a peer exceeds the Association.Max.Retrans, closes the association
and may send an ABORT.
data at the tester such that no SACK is sent in response to DATA received from
SUT.
SUT: Client or Server
SCTP_FH_I_5_1_2Ensure that the IUT on receipt of a SACK from the tester, for a DATA which
has been retransmitted, resets the counter which counts the total
retransmission to an endpoint.
data at the tester such that SACK is sent in response to DATA received from
SUT only when the DATA has been retransmitted for two to three times.
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_FH/
SCTP_FH_O
SCTP_FH_O_5_3_1Ensure that the IUT on receipt of a DATA message, from a transport address
corresponding to which there is no association, sends an ABORT message.
data at the tester such that DATA is sent to the SUT.
SUT: Client or Server
SCTP_FH_O_5_3_2Ensure that the IUT on receipt of an ABORT message from a transport address
corresponding to which there is no association, discards the message.
data at the tester such that ABORT is sent to the SUT.
SUT: Client or Server
SCTP_FH_O_5_3_3Ensure that the IUT on receipt of a SHUTDOWN-ACK message from a transport
address corresponding to which there is no association, sends a
SHUTDOWN COMPLETE message with T_Bit set.
data at the tester such that SHTUDOWN-ACK is sent to the SUT.
SUT: Client or Server
SCTP_FH_O_5_3_4Ensure that the IUT on receipt of an SHUTDOWN COMPLETE message from a
transport address corresponding to which there is no association,
discards the message.
data at the tester such that SHUTDOWN COMPLETE is sent to the SUT.
SUT: Client or Server
SCTP_FH_O_5_3_5Ensure that the IUT on receipt of a COOKIE ECHO message from a
a non-unicast address where there is no association between them,
discards the message.
data at the tester such that COOKIE ECHO is sent to the SUT with non
unicast source address.
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_E
SCTP_Generic_Tests/
SCTP_E/
SCTP_E_O
SCTP_E_O_6_2Ensure that the IUT on receipt of ERROR message with cause Stale
Cookie Error in state other than Cookie Echoed state, discards
the message and association is not disturbed.
Arrange the data at the tester such that ERROR message with cause stale
cookie error is sent.
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_E/
SCTP_E_I
SCTP_E_I_6_3Ensure that the IUT on receipt of DATA message to a non-existing
stream, sends an ERROR message with cause Invalid Stream Identifier
or aborts the association.
Arrange the data at the tester such that a DATA message is sent to
SUT on a stream which is not existing for the association.
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_BDC
SCTP_Generic_Tests/
SCTP_BDC/
SCTP_BDC_V
SCTP_BDC_V_7_6Ensure that the IUT on receipt of SHUTDOWN chunk
bundled with a SACK, accepts the packet and
responds with a SHUTDOWN-ACK.
Arrange the data at the tester such that DATA chunks are bundled with
COOKIE-ACK with COOKIE-ACK as the first chunk.
SUT: Client or Server
SCTP_BDC_V_7_7Ensure that the IUT on receipt of SACK bundled
with DATA chunks accepts the packet and responds
with a SACK for the received DATA chunks.
Arrange the data at the tester such that SACK bundled with DATA
chunks is sent to SUT.
SUT: Client or Server
SCTP_BDC_V_7_8Ensure that the IUT on receipt of a SHUTDOWN-ACK
bundled with DATA chunks discards the packet and
remains in Shutdown sent state or sends an ABORT
or accepts the SHUTDOWN-ACK but ignores the DATA
chunks, which would mean that the IUT has to send
a SHUTDOWN-COMPLETE.
and SUT is in SHUTDOWN-SENT state. Arrange the data at the tester
such that DATA is bundled with SHUTDOWN-ACK message.
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_BDC/
SCTP_BDC_I
SCTP_BDC_I_7_3Ensure that the IUT, on receipt of any DATA chunks bundled with
SHUTDOWN-COMPLETE chunk discards this packet and remains in
SHUTDOWN-ACK sent state or sends an ABORT or accepts the
SHUTDOWN-COMPLETE but ignores the DATA chunks.
SUT is in SHUTDOWN-ACK sent state. Arrange the data at the
tester such that DATA chunks are multiplexed with SHUTDOWN
COMPLETE chunk with SHUTDOWN-COMPLETE as the first chunk.
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_D
SCTP_Generic_Tests/
SCTP_D/
SCTP_D_V
SCTP_D_V_8_1 Ensure that the IUT is able to send Unsegmented user message, if resolving
SCTP packet is less than or equal to MTU size.
the data from user part such that size of the resolving SCTP packet is less
than or equal to MTU size and smaller than the maximum supported size of
user data.
SUT: Client or Server
SCTP_D_V_8_2Ensure that the IUT is able to perform data segmentation and transmission
the large size data from user part such that size exceeds MTU.
SUT: Client or Server
SCTP_D_V_8_3Ensure that the IUT is able to receive segmented data
the segmented data such that SUT receives first, middle and end piece of
segmented data.
SUT: Client or Server
SCTP_D_V_8_4Ensure that the IUT on receipt of a SACK cancels the timer, T3-rtx and
does not increase it.
the data at the tester such that SACK is sent in response of DATA message.
SUT: Client or Server
SCTP_D_V_8_9Ensure that the IUT, before it send new DATA chunks, first transmits any
outstanding DATA chunks, which are marked for retransmission.
the data at the tester such that tester ignores TSN3 and sends SACK with
gap in DATA.
SUT: Client or Server
SCTP_D_V_8_9_AEnsure that the IUT, before it send new DATA chunks, first transmits any
outstanding DATA chunks, which are marked for retransmission.
the data at the tester such that tester ignores TSN3 and sends SACK with
gap in DATA.
SUT: Client or Server
SCTP_D_V_8_10Ensure that the IUT, if it sends DATA to a multihomed endpoint on one
address and receives a SACK from the alternate address in that host,
it accepts the SACK.
such that on reception of a packet containing a DATA chunk, the
packet containing the corresponding SACK chunk is sent with a
source address different from the destination address of the
receive packet containing the DATA chunk.
SUT: Client or Server
SCTP_D_V_8_13Ensure that the IUT can receive DATA equal to maximum User Data size
defined by the upper layer.
the data at the tester such that DATA chunk with size of data equal to the
maximum user data size of the SUT is sent to SUT.
SUT: Client or Server
SCTP_D_V_8_14Ensure that the IUT can send DATA equal to maximum User Data size defined
by the upper layer.
the data from user part such that size is equal to the maximum User Data
size defined by the upper layer.
SUT: Client or Server
SCTP_D_V_8_15Ensure that the IUT on receipt of DATA larger than own User Data size,
send an ABORT with cause "Out of Resources."
the data at the tester such that DATA chunk with size of data larger than
user data size of the SUT is sent to SUT
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_D/
SCTP_D_I
SCTP_D_I_8_5Ensure that the IUT after expiry of the timer, T3-rtx, sends the DATA
message again.
the data at the tester such that no SACK is sent in response of DATA message.
SUT: Client or Server
SCTP_D_I_8_11Ensure that the IUT on receipt of a DATA chunk with no user data, sends an
ABORT with cause "No User Data"
the data at the tester such that DATA chunk with no user data is sent to
SUT.
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_D/
SCTP_D_O
SCTP_D_O_8_6Ensure that the IUT on receipt of duplicate DATA chunks should report this
in a SACK and number of duplicate TSN count should be reset once reported in SACK.
the data at the tester such that it will send duplicate DATA to SUT.
SUT: Client or Server
SCTP_D_O_8_7Ensure that the IUT, if its peers rwnd indicates that the peer has no
buffer space, does not transmit more than one DATA.
the data at the tester such that rwnd=0 is sent in SACK in response to
DATA message.
SUT: Client or Server
SCTP_D_O_8_8Ensure that the IUT, if its peers rwnd indicates that the peer has no
buffer space, does not transmit DATA, until it receives a SACK, where
the rwnd indicates that the peer has buffer space again.
the data at the tester such that rwnd=0 is sent in SACK in response to
DATA message. Data should be in large size so it will be transmitted in
segments.
SUT: Client or Server
SCTP_D_O_8_8_M2UAEnsure that the IUT, if its peers rwnd indicates that the peer has no
buffer space, does not transmit DATA, until it receives a SACK, where
the rwnd indicates that the peer has buffer space again.
the data at the tester such that rwnd=0 is sent in SACK in response to
DATA message. Data should be in large size so it will be transmitted in
segments.
SUT: Client or Server
SCTP_D_O_8_12Ensure that the IUT on receipt of a SACK that contains Cumulative TSN
field less than the current Cumulative TSN Ack point, discards the SACK.
the data at the tester such that SACK chunk with cumulative TSN less than
the cumulative TSN ack point of SUT is sent to SUT.
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_A
SCTP_Generic_Tests/
SCTP_A/
SCTP_A_V
SCTP_A_V_9_1Ensure that the IUT send a SACK for the first DATA chunk it receives
immediately.
the data such that tester sends the first DATA and wait for SACK.
SUT: Client or Server
SCTP_A_V_9_2Ensure that the IUT can acknowledge the reception of multiple DATA
chunks.
the Tester such that it sends multiple DATA chunks bundled in on SCTP
packet.
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_A/
SCTP_A_O
SCTP_A_O_9_3Ensure that the IUT, if it detects a gap in the received data chunk
sequence, sends a SACK immediately where it reports the missing TSN
in the GAP ACK block.
the data such that SUT receive gap in DATA.
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_M
SCTP_Generic_Tests/
SCTP_M/
SCTP_M_I
SCTP_M_I_10_1Ensure that the IUT on receipt of an unrecognized chunk type with
highest order 2 bits set to 11, sends an ERROR with cause
"Unrecognized Chunk type" and a SACK for the DATA chunk
the Tester such that a datagram with reserved chunk type is sent to IUT
bundled with DATA chunk and higher two bits are set to 11.
SUT: Client or Server
SCTP_M_I_10_2Ensure that the IUT on receipt of an unrecognized chunk type with
highest order 2 bits set to 00, discards this SCTP packet and does
not process the DATA chunk.
the data at the tester such that a datagram with reserved chunk type is
sent to IUT bundled with DATA chunk and higher two bits are set to 00.
SUT: Client or Server
SCTP_M_I_10_3Ensure that the IUT on receipt of an unrecognized chunk type with
highest order 2 bits set to 01, discards this SCTP packet and does
not process the DATA chunk. Additionally it has to send an ERROR
with cause "Unrecognized Chunk Type"
the data at the tester such that a datagram with reserved chunk type is
sent to IUT bundled with DATA chunk and higher two bits are set to 01.
SUT: Client or Server
SCTP_M_I_10_4Ensure that the IUT on receipt of an unrecognized chunk type with
highest order 2 bits set to 10, discards this chunk and sends a
SACK for the DATA chunk.
the Tester such that a datagram with reserved chunk type is sent to IUT
bundled with DATA chunk and higher two bits are set to 10.
SUT: Client or Server
SCTP_Generic_Tests/
SCTP_RT
SCTP_Generic_Tests/
SCTP_RT/
SCTP_RT_I
SCTP_RT_I_11_1Ensure that the IUT, if timer T3-rtx expires on a destination address,
increases value of RTO for that address, i.e. increases T3-rtx timer.
the data at the tester such that SACK is not sent for the data received
from SUT.
SUT: Client or Server
SCTP_RT_I_11_2Ensure that the IUT, if timer T3-rtx expires on a destination address,
increases value of RTO for that address.
the data at the tester such that SACK is not sent for the data received.
Reference: RFC 4960/2960 [1], section 6.3.3
SUT: Client or Server
SCTP_RT_I_11_3Ensure that the IUT, if it retransmits DATA to an alternate address,
uses the RTO value of that address and not that of the previous address.
the data at the tester such that SACK is not sent for the data received.
Before sending the DATA note the T3-rtx value corresponding to both IP
addresses.
SUT: Client or Server
SCTP_Loopback_Tests
SCTP_Loopback_GAP_TEST_03Send GAP DATA. Test retransmission
SUT: Firewall
SCTP_Loopback_RAW_TEST_02Send RAW data
SUT: Firewall
SCTP_Loopback_RAW_TEST_TIMED_OUTPUTSSend RAW data
SUT: Firewall
SCTP_Loopback_RAW_Assoc_DATA_ShutdownExample to show sending a complete INIT/INIT_ACK
SUT: Firewall
SCTP_Loopback_DATA_TGENSends SCTP DATA in a loop
SUT: Firewall
SCTP_Loopback_New_TestTest for demonstrating building a new loopback test
Test for demonstrating building a new loopback test
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_AS
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_AS/
SCTP_Loopback_AS_V
SCTP_Loopback_AS_V_1_1_1Ensure the IUT makes a complete association procedure
Configure the IUT to send an INIT to the tester.
SUT: Client
Reference: RFC 4960/2960 [1], sections 5.1[1] and 5.1.6[1]
SCTP_Loopback_AS_V_1_5_1Ensure that the IUT on re-establishing an association to a peer, uses a random Initiate-Tag value in the INIT message
association can be established and terminated between tester and SUT.
Status: Mandatory
SCTP_Loopback_AS_V_1_6_2Ensure that the IUT on receipt of an INIT-ACK message with the listed parameters accepts this message
and responds to it.
tester such that the listed parameters (IPv4 Address Parameter, IPv6 Address Parameter, CookiePreservative
are sent in INIT-ACK message.
SUT: Client
SCTP_Loopback_AS_V_1_7_3 Ensure that the IUT, if there is a mismatch in the Outbound Stream and Inbound Stream parameters in INIT and INIT-ACK message,
either aborts the association or settles with minimum of the two parameters.
at the tester such that INIT-ACK message is sent from tester with MaximumInboundStreams XSUT: Client
SCTP_Loopback_AS_V_1_10_2 Ensure that the IUT on receipt of an INIT-ACK message with no optional IP
addresses sends an COOKIE_ECHO message to the source IP address from which
INIT-ACK was received.
the data at the tester such that no IP addresses are sent in INIT-ACK optional
IP address field.
SUT: Client
SCTP_Loopback_AS_V_1_11_2Ensure that the IUT on receipt of an INIT-ACK message with one or more
IP addresses uses all of these IP addresses plus the IP address from where
INIT-ACK comes combined with the SCTP source port number as the destination
transport address and sends an COOKIE-ECHO message to one of the transport
addresses.
Arrange the data at the tester such that one or more IP addresses are sent
in INIT-ACK message.
SUT: Client
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_AS/
SCTP_Loopback_AS_I
SCTP_Loopback_AS_I_1_2_1Ensure that the IUT, if T1-Init timer expires, transmits the INIT message again
Arrange the data at the tester such that INIT-ACK is never sent in response to INIT message.
SUT: Client
SCTP_Loopback_AS_I_1_2_2Ensure that the IUT, if T1-Cookie timer expires, transmits the COOKIE-ECHO message again
to send an INIT to the tester. Arrange the data at the tester such that COOKIE-ACK is not
sent in response to COOKIE-ECHO message
Status: Mandatory
SUT: Client
Reference: RFC 4960/2960 [1], sections 5.1[1] and 5.1.6[1]
SCTP_Loopback_AS_I_1_3_1Ensure that the IUT, if INIT is retransmitted for MAX_INIT_RETRANS times, stops the initialisation
process.
to the tester. Arrange the data at the tester such that INIT-ACK is never sent in response to INIT message
SUT: Client
Reference: RFC 4960/2960 [1], section 4 (Note 2) [1]
SCTP_Loopback_AS_I_1_3_2Ensure that the IUT, if COOKIE-ECHO message is retransmitted for MAX_INIT_RETRANS times, stops the initialisation process
Arrange the data at the tester such that COOKIE-ACK is never sent in response to COOKIE-ECHO message.
SUT: Client
Status: Mandatory
SCTP_Loopback_AS_I_1_7_4 Ensure that the IUT, if OutboundStreams is found zero in the received INIT-ACK message, destroys its TCB and may send an ABORT message
for that INIT-ACK. Further message exchanges between tester and IUT need to take place to verify the TCB removal from outside the SUT.
the tester such that INIT-ACK message with OutboundStreams equal to 0 is sent from tester.
SUT: Client
SCTP_Loopback_AS_I_1_12_2
Ensure that the IUT on receipt of an INIT-ACK message with Host Name address
and no other IP address sends an ABORT message with error Unresolvable Address.
the data at the tester such that Host Name address is sent to SUT with no other
IP address in INIT-ACK message
SUT: Client
SCTP_Loopback_AS_I_1_14_2Ensure that the IUT on receipt of an INIT-ACK message with Init-Tag equal to
zero destroys the TCB and may send an ABORT.
Arrange the data at the tester such that Initiate-tag field equal to zero is
sent to SUT in INIT-ACK message.
SUT: Client
SCTP_Loopback_AS_I_1_15** NOT SUPPORTED. WOULD REQUIRE 4 NETWORK CARDS. **
establishment.
addresses X and Y. Association is not established between tester and
SUT. Arrange the data at the tester such that no INIT-ACK message is sent
to SUT in Response to an INIT.
SUT: Client
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_AS/
SCTP_Loopback_AS_O
SCTP_Loopback_AS_O_1_9_1Ensure the IUT on receipt of an INIT message for starting an association with
transport addresses which are already in assocation, responds with an INIT-ACK
message.
data at the tester such that INIT message is sent for making an association with
SUT using the same IP addresses.
SUT: MGC
Reference: RFC 4960/2960 [1], sections 5.2.2 and darft ietf[6], section 2.6
SCTP_Loopback_AS_O_1_9_2Ensure the IUT on receipt of an INIT message for starting association with
transport addresses which are not the same as the already established, responds
with an ABORT message with error "restart of an association with new
addresses.
data at the tester such that INIT message is sent for establishing an
association with SUT. The additional transport addresses should contain a
new, not yet used, IP address.
SUT: MGC
Reference: RFC 4960/2960 [1], sections 5.1[1] and 5.1.6[1]
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_AT
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_AT/
SCTP_Loopback_AT_V
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_IMH
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_IMH/
SCTP_Loopback_IMH_I
SCTP_Loopback_IMH_I_3_2 Ensure that the IUT on receipt of an invalid INIT-ACK message with message
length < length of all mandatory parameters, discards the message or may send
an ABORT message.
Pre-condition: Association is not established between tester and SUT. Arrange
the data at the tester such that INIT-ACK message is sent to SUT with message
length less than the length of all mandatory parameters.
Reference:RFC 4960/2960[1], section 5.1
SUT: Client
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_DM
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_DM/
SCTP_Loopback_DM_O
SCTP_Loopback_DM_O_4_1 Ensure that the IUT on receipt of an INIT message after sending
an INIT message on its own, sends an INIT-ACK message.
Arrange the data at the tester such that INIT message is sent to
SUT upon reception of an INIT from the SUT.
SUT: Client
SCTP_Loopback_DM_O_4_3Ensure that the IUT on receipt of a duplicate INIT-ACK message, after sending
a COOKIE-ECHO message, discards the INIT-ACK message.
Arrange the data at the tester such that the same INIT-ACK message is
sent to SUT after receiving COOKIE-ECHO message.
SUT: Client
SCTP_Loopback_DM_O_4_6_1Ensure that the IUT on receipt of a SHUTDOWN message, after sending an
INIT message on its own, discards the SHUTDOWN message.
Arrange the data at the tester such that SHUTDOWN message is sent to SUT after
receiving INIT message from it.
SUT: Client
SCTP_Loopback_DM_O_4_7_1Ensure that the IUT on receipt of a SHUTDOWN-ACK message, in Cookie Wait
state, sends a SHUTDOWN-COMPLETE message and current state is not disturbed.
Arrange the data at the tester such that SHUTDOWN-ack message is sent to SUT after
receiving INIT message from it.
SUT: Client
SCTP_Loopback_DM_O_4_9Ensure the IUT on receipt of a SHUTDOWN COMPLETE message in Cookie wait
state, discards the message.
Arrange the data at the tester such that SHUTDOWN COMPLETE message is
sent to SUT after receiving INIT message from it.
Status: Mandatory
Reference: RFC 4960/2960 [1], sections 9.2
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_FH
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_FH/
SCTP_Loopback_FH_V
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_FH/
SCTP_Loopback_FH_O
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_E
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_E/
SCTP_Loopback_E_O
SCTP_Loopback_E_O_6_1Ensure that the IUT on receipt of ERROR message with cause Stale
Cookie Error in Cookie Echoed state, takes one of the following
actions depending on the implementation:
1) Sends a new INIT message to the tester to generate a new
cookie and reattempt the setup procedure.
2) Discards the TCB and changes the state to closed.
3) Sends a new INIT message to the tester adding a cookie
preservative parameter requesting the extension on lifetime
of cookie.
Arrange the data at the tester such that ERROR message with cause stale
cookie error is sent in response to COOKIE-ECHO message.
SUT: Client
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_E/
SCTP_Loopback_E_I
SCTP_Loopback_E_I_6_4Ensure that the IUT on receipt of INIT-ACK message without a Cookie
parameter, sends an ERROR message with cause Missing Mandatory
Parameter or may send an ABORT or no message at all.
Arrange the data at the tester such that a INIT-ACK is sent to SUT
without Cookie parameter.
SUT: Client
SCTP_Loopback_E_I_6_5Ensure that the IUT on receipt of INIT-ACK message with an
unknown TLV parameter, sends an ERROR message with cause
Unrecognized Parameters.
Arrange the data at the tester such that a INIT-ACK is sent to SUT
with an unknown TLV parameter.
SUT: Client
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_BDC
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_BDC/
SCTP_Loopback_BDC_V
SCTP_Loopback_BDC_V_7_5Ensure that the IUT on receipt of COOKIE-ACK chunk
bundled with DATA chunks, accepts the COOKIE-ACK and
responds with a SACK.
Arrange the data at the tester such that DATA chunks are bundled with
COOKIE-ACK with COOKIE-ACK as the first chunk.
SUT: Client
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_BDC/
SCTP_Loopback_BDC_I
SCTP_Loopback_BDC_I_7_2_discardedEnsure that the IUT on receipt of DATA chunks bundled with
INIT-ACK chunk discards this packet or sends an ABORT or
accepts the INIT-ACK but ignores the DATA chunks.
Arrange the data at the tester such that a data chunks are bundled
with INIT-ACK message.
SUT: Client
SCTP_Loopback_BDC_I_7_2_abortEnsure that the IUT on receipt of DATA chunks bundled with
INIT-ACK chunk discards this packet or sends an ABORT or
accepts the INIT-ACK but ignores the DATA chunks.
Arrange the data at the tester such that a data chunks are bundled
with INIT-ACK message.
SUT: Client
SCTP_Loopback_BDC_I_7_2_ignore_dataEnsure that the IUT on receipt of DATA chunks bundled with
INIT-ACK chunk discards this packet or sends an ABORT or
accepts the INIT-ACK but ignores the DATA chunks.
Arrange the data at the tester such that a data chunks are bundled
with INIT-ACK message.
SUT: Client
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_D
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_D/
SCTP_Loopback_D_V
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_D/
SCTP_Loopback_D_I
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_A
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_A/
SCTP_Loopback_A_V
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_A/
SCTP_Loopback_A_O
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_M
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_M/
SCTP_Loopback_M_I
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_RT
SCTP_Loopback_Tests/
SCTP_Loopback_Client_Tests/
SCTP_Loopback_RT/
SCTP_Loopback_RT_I
SCTP_Loopback_Tests/
SCTP_Loopback_Server_Tests
SCTP_Loopback_Tests/
SCTP_Loopback_Server_Tests/
SCTP_Loopback_AS
SCTP_Loopback_Tests/
SCTP_Loopback_Server_Tests/
SCTP_Loopback_AS/
SCTP_Loopback_AS_V
SCTP_Loopback_AS_V_1_1_2Ensure the IUT can establish a complete association after receiving an INIT from the tester
Arrange the data at the tester such that an INIT is sent to IUT.
SUT: Server
Status: Mandatory
Reference: RFC 4960/2960 [1], sections 5.1 [1] and 5.1.6[1]
SCTP_Loopback_AS_V_1_5_2 Ensure that the IUT on re-establishing an association to a peer, uses a random Initiate-Tag value in the INIT-ACK message
Pre-condition: Association is not established between tester and SUT. Arrange the data at the tester such that normal association
can be established and terminated between tester and SUT.
SUT: Server
SCTP_Loopback_AS_V_1_6_1Ensure that the IUT on receipt of an INIT message with the listed parameters accepts this message
and responds to it.
tester such that the listed parameters (IPv4 Address Parameter, IPv6 Address Parameter, CookiePreservative,
Supported Address Type Parameter) are sent in INIT message.
SUT: Server
SCTP_Loopback_AS_V_1_7_1_AEnsure that the IUT, if there is a mismatch in the Outbound Stream and Inbound Stream parameters
in INIT and INIT-ACK message, either aborts the association or settles with minimum of the two parameters.
of the SUT is Z. Arrange data at the tester such that INIT message is sent from tester with MaximumInboundStreams YSCTP_Loopback_AS_V_1_7_1_B tests aborting the association
SUT: Server
SCTP_Loopback_AS_V_1_7_1_BEnsure that the IUT, if there is a mismatch in the Outbound Stream and Inbound Stream parameters
in INIT and INIT-ACK message, either aborts the association or settles with minimum of the two parameters.
of the SUT is Z. Arrange data at the tester such that INIT message is sent from tester with MaximumInboundStreams YSCTP_Loopback_AS_V_1_7_1_B tests aborting the association
SUT: Server
SCTP_Loopback_AS_V_1_7_5Ensure that the IUT supports at least 2 incoming streams and 2 outgoing streams
at the tester such that INIT message is sent from tester with OutboundStreams and
MaximumInboundStreams set to 2.
SUT: Server
SCTP_Loopback_AS_V_1_10_1 Ensure that the IUT on receipt of an INIT message with no IP addresses
sends an INIT-ACK message to the source IP address from where INIT was
received.
Arrange the data at the tester such that no IP addresses are sent in INIT.
SUT: Server
SCTP_Loopback_AS_V_1_11_1Ensure that the IUT on receipt of an INIT message with one or more IP
addresses sends an INIT-ACK message to the source IP addresses from where
INIT was received and uses all of these IP address plus the IP address
from where INIT comes combined with the SCTP source port number as the
destination transport address.
Arrange the data at the tester such that one or more IP addresses are sent in INIT message.
SUT: Server
SCTP_Loopback_AS_V_1_12_1Ensure that the IUT on receipt of an INIT message with Host Name address and
no other IP address sends an ABORT message with error Unresolvable Address.
the data at the tester such that Host Name address is sent to SUT with no other
IP address in INIT message
SUT: Server
SCTP_Loopback_AS_V_1_13_1Ensure that the IUT on receipt of an INIT message with Supported address field
sends an INIT-ACK message with the address of the type contained in the
Supported address field in the received INIT.
the data at the tester such that Supported Address field is sent in INIT. Also
the SUT is capable of using the address type mentioned in Supported Address field.
SUT: Server
SCTP_Loopback_Tests/
SCTP_Loopback_Server_Tests/
SCTP_Loopback_AS/
SCTP_Loopback_AS_I
SCTP_Loopback_AS_I_1_4Ensure that the IUT remains in closed state if COOKIE-ECHO message is not received
INIT-ACK message. Also let maximum no of association which SUT can establish is n and n-1 of them are already established. Try to make the nth association.
SUT: Server
SCTP_Loopback_AS_I_1_7_2Ensure that the IUT, if OutboundStreams are found zero in the received INIT message,
sends an ABORT message for that INIT. or silently discards the received message.
the tester such that INIT message with OutboundStreams equal to 0 is sent from tester.
SUT: Server
SCTP_Loopback_AS_I_1_8_1Ensure that the IUT on receipt of unrecognised TLV parameters in received INIT message fills them
in the Unrecognised Parameters of the INIT-ACK and continues on processing of further parameters.
such that a datagram with undefined parameter type and MSB two bits in the parameter type equal
to 11 is sent to tester.
SUT: Server
Status: Mandatory
Reference: RFC4960/2960, section 3.3.3.1 / DTS/MTS-00086 v0.0.4 (2004-07)
SCTP_Loopback_AS_I_1_8_2 Ensure that the IUT on receipt of an unrecognized parameter in the INIT-chunk does not process any further parameters and does not report it
a datagram with undefined parameter type and MSB two bits in the parameter type equal to 00 is sent to the IUT
Status: Mandatory
SUT: Server
SCTP_Loopback_AS_I_1_8_3 Ensure that the IUT on receipt of an unrecognized parameter in the INIT-chunk does not process any further
parameters and report it using an Unrecognized Parameters parameter field."
datagram with undefined parameter type and MSB two bits in the parameter type equal to 01 is sent to the IUT.
SUT: Server
SCTP_Loopback_AS_I_1_8_4Ensure that the IUT on receipt of an unrecognized
parameter in the INIT-chunk skips this parameter and does process any further parameters.
tester such that a datagram with undefined parameter type and MSB two bits in the parameter
type equal to 10 is sent to the IUT.
Status: Mandatory
SUT: Server
SCTP_Loopback_AS_I_1_13_2Ensure that the IUT on receipt of an INIT message with Supported address type
which the receiver is incapable of using sends an ABORT message with cause
Unresolvable Address.
the data at the tester such that Supported address type field IPv6 is sent to
SUT in INIT message (END USER PLEASE NOTE: Supported Address Type IPv4 will not
be sent. Your SUT should not support IPv6.). Also
receiver (i.e. SUT) is not capable of using supported address type, i.e ONLY
IPv4.
SUT: Server
SCTP_Loopback_AS_I_1_14_1Ensure that the IUT on receipt of an INIT message with Init-Tag equal to zero
destroys the TCB and may send an ABORT.
Pre-condition: Association is not established between tester and SUT. Arrange
the data at the tester such that Initiate-tag field equal to zero is sent to
SUT in INIT message.
SUT: Server
SCTP_Loopback_Tests/
SCTP_Loopback_Server_Tests/
SCTP_Loopback_IMH
SCTP_Loopback_Tests/
SCTP_Loopback_Server_Tests/
SCTP_Loopback_IMH/
SCTP_Loopback_IMH_I
SCTP_Loopback_IMH_I_3_1 Ensure that the IUT on receipt of an invalid INIT message with message
length < length of all mandatory parameters, discards the message or may
send an ABORT message.
the data at the tester such that INIT message is sent to SUT with message
length less than the length of all mandatory parameters.
SUT: Server
SCTP_Loopback_IMH_I_3_3 Ensure that the IUT on receipt of a COOKIE-ECHO message with invalid
verification tag, discards the COOKIE-ECHO message.
Arrange the data at the tester such that COOKIE-ECHO message with a
different verification tag (Different from what received in INIT-ACK)
is sent in response to INIT-ACK.
SUT: Server
SCTP_Loopback_IMH_I_3_4 Ensure that the IUT on receipt of an INIT message with wrong CRC-32c
checksum, discards the INIT message.
Tester_IP_CDC --> RFC3309_CRC32_Checksum in the System Configuration to FALSE
and restart the test environment.
Arrange data at the tester such that it sends INIT message to SUT with
wrong CRC-32c checksum.
SUT: Server
SCTP_Loopback_IMH_I_3_5 Ensure that the IUT on receipt of a COOKIE-ECHO message with other cookie
than sent in INIT_ACK, discards the message.
the data at the tester such that COOKIE-ECHO message is sent with cookie
different from received cookie in INIT-ACK.
SUT: Server
SCTP_Loopback_IMH_I_3_6Ensure that the IUT on receipt of a COOKIE-ECHO message after lifetime
received in INIT-ACK message has expired, should send an ERROR with cause
“"Stale Cookie Error”".
the data at the tester such that COOKIE-ECHO message is sent after life time
of the received cookie in INIT-ACK message has expired.
SUT: Server
SCTP_Loopback_IMH_I_3_8_A Ensure that the IUT on receipt of an INIT message with a packet length
smaller than the Chunk length defined, sends an ABORT message or discards
the message.
SCTP_Loopback_IMH_I_3_8_B discards the message
the data at the tester such that chunk length is greater than the length of
the message being sent to other SUT.
SUT: Server
SCTP_Loopback_IMH_I_3_8_B Ensure that the IUT on receipt of an INIT message with a packet length
smaller than the Chunk length defined, sends an ABORT message or discards
the message.
SCTP_Loopback_IMH_I_3_8_B discards the message
the data at the tester such that chunk length is greater than the length of
the message being sent to other SUT.
SUT: Server
SCTP_Loopback_IMH_I_3_9Ensure that the IUT on receipt of a SHUTDOWN-ACK message with invalid
verification tag, discards the message.
tester such that SHUTDOWN-ACK message with invalid verification tag is sent to SUT in
Shutdown Sent state.
SUT: Server
SCTP_Loopback_Tests/
SCTP_Loopback_Server_Tests/
SCTP_Loopback_DM
SCTP_Loopback_Tests/
SCTP_Loopback_Server_Tests/
SCTP_Loopback_DM/
SCTP_Loopback_DM_O
SCTP_Loopback_DM_O_4_2_1Ensure that the IUT on receipt of an INIT message when association
is already established, sends an INIT-Ack message and existing
association is not disturbed.
to SUT when association is established between tester and SUT. Also, source IP
address, destination IP address and port numbers are the same as in the established
association.
SUT: Server
SCTP_Loopback_Tests/
SCTP_Loopback_Server_Tests/
SCTP_Loopback_E
SCTP_Loopback_Tests/
SCTP_Loopback_Server_Tests/
SCTP_Loopback_E/
SCTP_Loopback_E_I
SCTP_Loopback_E_I_6_6Ensure that the IUT on receipt of COOKIE-ECHO message
bundled with error (cause = Unrecognized Parameter),
continues to establish the association.
Arrange the data at the tester such that COOKIE-ECHO bundled with
ERROR (cause = Unrecognized Parameters) is sent to SUT.
SUT: Server
SCTP_Loopback_Tests/
SCTP_Loopback_Server_Tests/
SCTP_Loopback_BDC
SCTP_Loopback_Tests/
SCTP_Loopback_Server_Tests/
SCTP_Loopback_BDC/
SCTP_Loopback_BDC_V
SCTP_Loopback_BDC_V_7_4Ensure that the IUT on receipt of COOKIE-ECHO chunk
bundled with DATA chunks, accepts the packet and responds
with a COOKIE-ACK bundled with a SACK or a single
COOKIE-ACK and then a SACK.
Arrange the data at the tester such that DATA chunks are bundled with
COOKIE-ECHO as the first chunk.
SUT: Server
SCTP_Loopback_Tests/
SCTP_Loopback_Server_Tests/
SCTP_Loopback_BDC/
SCTP_Loopback_BDC_I
SCTP_Loopback_BDC_I_7_1Ensure that the IUT on receipt of any DATA chunks
bundled with INIT chunk discard this packet.
Arrange the data at the tester such that data chunks are bundled
with INIT message.
section 2.11
SUT: Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_AT
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_AT/
SCTP_Loopback_AT_V
SCTP_Loopback_AT_V_2_2Ensure that the IUT on receipt of an ABORT removes the association. Further message exchanges between
tester and IUT need to take place to verify the removal of the association from outside the SUT.
such that an ABORT message is sent to SUT in it.
SUT: Client or Server
SCTP_Loopback_AT_V_2_6Ensure that the IUT on receipt of SHUTDOWN-ACK message in Shutdown Sent state
sends a SHUTDOWN COMPLETE message and terminates the association.
tester such that SHUTDOWN-ACK is sent in response to SHUTDOWN message.
SUT: Client or Server
SCTP_Loopback_AT_V_2_14Ensure that the IUT, if there is still outstanding DATA, receives a SHUTDOWN
that acknowledges the outstanding DATA, sends a SHUTDOWN-ACK.
tester such that there is still outstanding DATA in IUT which has not been acknowledged
by SACK and that the tester sends SHUTDOWN MESSAGE to IUT that acknowledges this DATA.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_AT/
SCTP_Loopback_AT_I
SCTP_Loopback_AT_I_2_3Ensure that the IUT on receipt of an Terminate primitive will send a SHUTDOWN
message to its peer only when all the outstanding DATA has been acknowledged
by the tester.
sent from SUT to the tester. Arrange the data in SUT such that Terminate
primitive is received from upper layers.
SUT: Client or Server
SCTP_Loopback_AT_I_2_4Ensure that the IUT starts the T2-Shutdown timer and after its expiry a SHUTDOWN message is
sent again.
tester such that no SHUTDOWN-ACK or DATA is sent in response to SHUTDOWN.
SUT: Client or Server
SCTP_Loopback_AT_I_2_5Ensure that the IUT after retransmitting SHUTDOWN message for ASSOCIATION.MAX.RETRANS
or TimeOut occurs for T5-shutdown-guard timer, removes the association and optionally
sends an ABORT. Further message exchanges between tester and IUT need to take place to
verify the removal of the association from outside the SUT.
tester such that in response to SHUTDOWN no SHUTDOWN-ACK or DATA message is sent.
SUT: Client or Server
SCTP_Loopback_AT_I_2_7_1Ensure that the IUT, if it is in Shutdown sent state and receives data for transmission
from upper layer, does not send this new data.
such that upper layers send data to transmit when it is in Shutdown sent state.
SUT: Client or Server
SCTP_Loopback_AT_I_2_7_2Ensure that the IUT, if it is in Shutdown receive state and receives data for transmission
from upper layer, does not send this new data.
such that upper layers send data to transmit when it is in Shutdown receive state.
SUT: Client or Server
SCTP_Loopback_AT_I_2_7_3Ensure that the IUT, if it is in Shutdown pending state and receives data for transmission
from upper layer, does not send this new data.
such that upper layers send data to transmit when it is in Shutdown pending state.
SUT: Client or Server
SCTP_Loopback_AT_I_2_7_4Ensure that the IUT, if it is in Shutdown-Ack sent state and receives data for transmission
from upper layer, does not send this new data.
such that upper layers send data to transmit when it is in Shutdown-Ack sent state.
SUT: Client or Server
SCTP_Loopback_AT_I_2_8Ensure that the IUT, if it is in Shutdown Sent state and receives data,
acknowledges the message and restarts the T2-Shutdown timer.
tester such that after receiving SHUTDOWN message, DATA message is sent to SUT.
SUT: Client or Server
SCTP_Loopback_AT_I_2_9Ensure that the IUT, if it is in Shutdown Receive state and receives data,
discards the data.
tester such that DATA is sent to SUT after sending SHUTDOWN message. Also in SUT there
is outstanding DATA for which SACK has not come from tester.
SUT: Client or Server
SCTP_Loopback_AT_I_2_10Ensure that the IUT, if there is still outstanding DATA, does not send a
SHUTDOWN-ACK on reception of a SHUTDOWN (even received multiple times).
tester such that it sends SHUTDOWN message to IUT. The SHUTDOWN should not acknowledge the
last used DATA of the SUT, i.e. that in IUT there is still outstanding DATA which has not been
acknowledged. Then a second SHUTDOWN has to be sent which again does not acknowledge the
last used DATA of the IUT.
SUT: Client or Server
SCTP_Loopback_AT_I_2_11Ensure that the IUT, after expiry of T2-Shutdown timer, sends a SHUTDOWN-ACK
message again.
tester such that no SHUTDOWN COMPLETE is sent in response to SHUTDOWN-ACK.
SUT: Client or Server
SCTP_Loopback_AT_I_2_12Ensure that the IUT, after retransmitting SHUTDOWN-ACK message for
ASSOCIATION.MAX.RETRANS times, removes the association and optionally
sends an ABORT.
tester such that no SHUTDOWN COMPLETE is sent in response to SHUTDOWN-ACK.
SUT: Client or Server
SCTP_Loopback_AT_I_2_13Ensure that the IUT, if it is in Shutdown-Ack Sent state, accept a
SHUTDOWN COMPLETE message and removes the association.
tester such that SHUTDOWN COMPLETE is sent in response to SHUTDOWN-ACK.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_IMH
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_IMH/
SCTP_Loopback_IMH_I
SCTP_Loopback_IMH_I_3_7 Ensure that the IUT on receipt of an ABORT message with incorrect
verification tag, discards the message.
Arrange the data at the tester such that ABORT message is sent to
SUT with incorrect verification tag.
SUT: Client or Server
SCTP_Loopback_IMH_I_3_10Ensure that the IUT on receipt of a SHUTDOWN-COMPLETE message with invalid
verification tag, discards the message.
tester such that SHUTDOWN-COMPLETE message with invalid verification tag is sent to SUT in
Shutdown Ack Sent state.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_DM
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_DM/
SCTP_Loopback_DM_O
SCTP_Loopback_DM_O_4_2_2Ensure that the IUT on receipt of an INIT message after sending
a SHUTDOWN-ACK message, discards the INIT message and retransmits
the SHUTDOWN-ACK message.
Arrange the data at the tester such that after sending a SHUTDOWN-ACK
message, discards the INIT message and retransmits the SHUTDOWN-ACK
message.
SUT: Client or Server
SCTP_Loopback_DM_O_4_4Ensure that the IUT on receipt of a COOKIE-ACK message, after association is
established, discards the COOKIE-ACK message.
Arrange the data at the tester such that COOKIE+ACK message is retransmitted to
SUT after association is established between tester and sut.
SUT: Client or Server
SCTP_Loopback_DM_O_4_5Ensure that the IUT on receipt of a SHUTDOWN message, after sending a
SHUTDOWN message on its own, sends a SHUTDOWN-ACK message.
Arrange the data at the tester such that SHUTDOWN message is send after
receiving SHUTDOWN message from the other end.
SUT: Client or Server
SCTP_Loopback_DM_O_4_6_2Ensure that the IUT on receipt of a SHUTDOWN message in closed state, sends
an ABORT message.
sent to SUT which is in closed state.
Reference: RFC 4960/2960, section 9.2
SUT: Client or Server
SCTP_Loopback_DM_O_4_6_3Ensure that the IUT on receipt of a SHUTDOWN message in Shutdown Sent state,
sends a SHTUDOWN-ACK message and restarts T2-Shutdown timer.
data in SUT such that terminate primitve is received from ULP to terminate the
association. Arrange data at the tester such that SHUTDOWN message is sent to
SUT.
SUT: Client or Server
SCTP_Loopback_DM_O_4_7_2Ensure that the IUT on receipt of a SHUTDOWN-ACK message, in Established
state, discards the message or sends an ABORT.
Arrange the data at the tester such that SHUTDOWN-ack message is sent to SUT
with correct verification tag.
SUT: Client or Server
SCTP_Loopback_DM_O_4_7_3Ensure that the IUT on receipt of a SHUTDOWN-ACK message in SHUTDOWN-ACK
sent state, send a SHUTDOWN-COMPLETE message and closes the association.
data at the tester such that SHUTDOWN message is sent to SUT. Also,
SHUTDOWN-ACK message is sent to SUT after receiving SHUTDOWN-ACK message.
SUT: Client or Server
SCTP_Loopback_DM_O_4_8Ensure that the IUT on receipt of a COOKIE-ECHO message in Established
state, discards the message and current state is not disturbed.
data at the tester such that COOKIE-ECHO message with invalid Message
Authentication Code (MAC) is sent to SUT.
SUT: Client or Server
SCTP_Loopback_DM_O_4_10Ensure that the IUT on receipt of a data message in Shutdown-Ack sent state,
discards the message and may send an ABORT.
data at the tester such that SHUTDOWN message is sent to SUT. Also,
DATA message is sent from tester to SUT.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_FH
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_FH/
SCTP_Loopback_FH_V
SCTP_Loopback_FH_V_5_2Ensure that the IUT on receipt of a HEARTBEAT message, sends a HEARTBEAT-ACK
message with the information carried in the HEARTBEAT message.
data at the tester such that HEARTBEAT message is sent to the SUT.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_FH/
SCTP_Loopback_FH_I
SCTP_Loopback_FH_I_5_1_1Ensure that the IUT when total number of consecutive retransmissions
to a peer exceeds the Association.Max.Retrans, closes the association
and may send an ABORT.
data at the tester such that no SACK is sent in response to DATA received from
SUT.
SUT: Client or Server
SCTP_Loopback_FH_I_5_1_2Ensure that the IUT on receipt of a SACK from the tester, for a DATA which
has been retransmitted, resets the counter which counts the total
retransmission to an endpoint.
data at the tester such that SACK is sent in response to DATA received from
SUT only when the DATA has been retransmitted for two to three times.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_FH/
SCTP_Loopback_FH_O
SCTP_Loopback_FH_O_5_3_1Ensure that the IUT on receipt of a DATA message, from a transport address
corresponding to which there is no association, sends an ABORT message.
data at the tester such that DATA is sent to the SUT.
SUT: Client or Server
SCTP_Loopback_FH_O_5_3_2Ensure that the IUT on receipt of an ABORT message from a transport address
corresponding to which there is no association, discards the message.
data at the tester such that ABORT is sent to the SUT.
SUT: Client or Server
SCTP_Loopback_FH_O_5_3_3Ensure that the IUT on receipt of a SHUTDOWN-ACK message from a transport
address corresponding to which there is no association, sends a
SHUTDOWN COMPLETE message with T_Bit set.
data at the tester such that SHTUDOWN-ACK is sent to the SUT.
SUT: Client or Server
SCTP_Loopback_FH_O_5_3_4Ensure that the IUT on receipt of an SHUTDOWN COMPLETE message from a
transport address corresponding to which there is no association,
discards the message.
data at the tester such that SHUTDOWN COMPLETE is sent to the SUT.
SUT: Client or Server
SCTP_Loopback_FH_O_5_3_5Ensure that the IUT on receipt of a COOKIE ECHO message from a
a non-unicast address where there is no association between them,
discards the message.
data at the tester such that COOKIE ECHO is sent to the SUT with non
unicast source address.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_E
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_E/
SCTP_Loopback_E_O
SCTP_Loopback_E_O_6_2Ensure that the IUT on receipt of ERROR message with cause Stale
Cookie Error in state other than Cookie Echoed state, discards
the message and association is not disturbed.
Arrange the data at the tester such that ERROR message with cause stale
cookie error is sent.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_E/
SCTP_Loopback_E_I
SCTP_Loopback_E_I_6_3Ensure that the IUT on receipt of DATA message to a non-existing
stream, sends an ERROR message with cause Invalid Stream Identifier
or aborts the association.
Arrange the data at the tester such that a DATA message is sent to
SUT on a stream which is not existing for the association.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_BDC
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_BDC/
SCTP_Loopback_BDC_V
SCTP_Loopback_BDC_V_7_6Ensure that the IUT on receipt of SHUTDOWN chunk
bundled with a SACK, accepts the packet and
responds with a SHUTDOWN-ACK.
Arrange the data at the tester such that DATA chunks are bundled with
COOKIE-ACK with COOKIE-ACK as the first chunk.
SUT: Client or Server
SCTP_Loopback_BDC_V_7_7Ensure that the IUT on receipt of SACK bundled
with DATA chunks accepts the packet and responds
with a SACK for the received DATA chunks.
Arrange the data at the tester such that SACK bundled with DATA
chunks is sent to SUT.
SUT: Client or Server
SCTP_Loopback_BDC_V_7_8_discardEnsure that the IUT on receipt of a SHUTDOWN-ACK
bundled with DATA chunks discards the packet and
remains in Shutdown sent state or sends an ABORT
or accepts the SHUTDOWN-ACK but ignores the DATA
chunks, which would mean that the IUT has to send
a SHUTDOWN-COMPLETE.
and SUT is in SHUTDOWN-SENT state. Arrange the data at the tester
such that DATA is bundled with SHUTDOWN-ACK message.
SUT: Client or Server
SCTP_Loopback_BDC_V_7_8_abortEnsure that the IUT on receipt of a SHUTDOWN-ACK
bundled with DATA chunks discards the packet and
remains in Shutdown sent state or sends an ABORT
or accepts the SHUTDOWN-ACK but ignores the DATA
chunks, which would mean that the IUT has to send
a SHUTDOWN-COMPLETE.
and SUT is in SHUTDOWN-SENT state. Arrange the data at the tester
such that DATA is bundled with SHUTDOWN-ACK message.
SUT: Client or Server
SCTP_Loopback_BDC_V_7_8_ignoreEnsure that the IUT on receipt of a SHUTDOWN-ACK
bundled with DATA chunks discards the packet and
remains in Shutdown sent state or sends an ABORT
or accepts the SHUTDOWN-ACK but ignores the DATA
chunks, which would mean that the IUT has to send
a SHUTDOWN-COMPLETE.
and SUT is in SHUTDOWN-SENT state. Arrange the data at the tester
such that DATA is bundled with SHUTDOWN-ACK message.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_BDC/
SCTP_Loopback_BDC_I
SCTP_Loopback_BDC_I_7_3_shutdown_ackEnsure that the IUT, on receipt of any DATA chunks bundled with
SHUTDOWN-COMPLETE chunk discards this packet and remains in
SHUTDOWN-ACK sent state or sends an ABORT or accepts the
SHUTDOWN-COMPLETE but ignores the DATA chunks.
SUT is in SHUTDOWN-ACK sent state. Arrange the data at the
tester such that DATA chunks are multiplexed with SHUTDOWN
COMPLETE chunk with SHUTDOWN-COMPLETE as the first chunk.
SUT: Client or Server
SCTP_Loopback_BDC_I_7_3_abortEnsure that the IUT, on receipt of any DATA chunks bundled with
SHUTDOWN-COMPLETE chunk discards this packet and remains in
SHUTDOWN-ACK sent state or sends an ABORT or accepts the
SHUTDOWN-COMPLETE but ignores the DATA chunks.
SUT is in SHUTDOWN-ACK sent state. Arrange the data at the
tester such that DATA chunks are multiplexed with SHUTDOWN
COMPLETE chunk with SHUTDOWN-COMPLETE as the first chunk.
SUT: Client or Server
SCTP_Loopback_BDC_I_7_3_ignoreEnsure that the IUT, on receipt of any DATA chunks bundled with
SHUTDOWN-COMPLETE chunk discards this packet and remains in
SHUTDOWN-ACK sent state or sends an ABORT or accepts the
SHUTDOWN-COMPLETE but ignores the DATA chunks.
SUT is in SHUTDOWN-ACK sent state. Arrange the data at the
tester such that DATA chunks are multiplexed with SHUTDOWN
COMPLETE chunk with SHUTDOWN-COMPLETE as the first chunk.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_D
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_D/
SCTP_Loopback_D_V
SCTP_Loopback_D_V_8_1 Ensure that the IUT is able to send Unsegmented user message, if resolving
SCTP packet is less than or equal to MTU size.
the data from user part such that size of the resolving SCTP packet is less
than or equal to MTU size and smaller than the maximum supported size of
user data.
SUT: Client or Server
SCTP_Loopback_D_V_8_2Ensure that the IUT is able to perform data segmentation and transmission
the large size data from user part such that size exceeds MTU.
When updating MTU_size, also updated TSPX_xUA_Data_frag1 and TSPX_xUA_Data_frag2.
SUT: Client or Server
SCTP_Loopback_D_V_8_3Ensure that the IUT is able to receive segmented data
the segmented data such that SUT receives first, middle and end piece of
segmented data.
When updating MTU_size, also updated TSPX_xUA_Data_frag1 and TSPX_xUA_Data_frag2.
SUT: Client or Server
SCTP_Loopback_D_V_8_4Ensure that the IUT on receipt of a SACK cancels the timer, T3-rtx and
does not increase it.
the data at the tester such that SACK is sent in response of DATA message.
SUT: Client or Server
SCTP_Loopback_D_V_8_9Ensure that the IUT, before it send new DATA chunks, first transmits any
outstanding DATA chunks, which are marked for retransmission.
the data at the tester such that tester ignores TSN3 and sends SACK with
gap in DATA.
SUT: Client or Server
SCTP_Loopback_D_V_8_10Ensure that the IUT, if it sends DATA to a multihomed endpoint on one
address and receives a SACK from the alternate address in that host,
it accepts the SACK.
such that on reception of a packet containing a DATA chunk, the
packet containing the corresponding SACK chunk is sent with a
source address different from the destination address of the
receive packet containing the DATA chunk.
SUT: Client or Server
SCTP_Loopback_D_V_8_13Ensure that the IUT can receive DATA equal to maximum User Data size
defined by the upper layer.
the data at the tester such that DATA chunk with size of data equal to the
maximum user data size of the SUT is sent to SUT.
SUT: Client or Server
SCTP_Loopback_D_V_8_14Ensure that the IUT can send DATA equal to maximum User Data size defined
by the upper layer.
the data from user part such that size is equal to the maximum User Data
size defined by the upper layer.
SUT: Client or Server
SCTP_Loopback_D_V_8_15Ensure that the IUT on receipt of DATA larger than own User Data size,
send an ABORT with cause "Out of Resources."
the data at the tester such that DATA chunk with size of data larger than
user data size of the SUT is sent to SUT
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_D/
SCTP_Loopback_D_I
SCTP_Loopback_D_I_8_5Ensure that the IUT after expiry of the timer, T3-rtx, sends the DATA
message again.
the data at the tester such that no SACK is sent in response of DATA message.
SUT: Client or Server
SCTP_Loopback_D_I_8_11Ensure that the IUT on receipt of a DATA chunk with no user data, sends an
ABORT with cause "No User Data"
the data at the tester such that DATA chunk with no user data is sent to
SUT.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_D/
SCTP_Loopback_D_O
SCTP_Loopback_D_O_8_6Ensure that the IUT on receipt of duplicate DATA chunks should report this
in a SACK and number of duplicate TSN count should be reset once reported in SACK.
the data at the tester such that it will send duplicate DATA to SUT.
SUT: Client or Server
SCTP_Loopback_D_O_8_7Ensure that the IUT, if its peers rwnd indicates that the peer has no
buffer space, does not transmit more than one DATA.
the data at the tester such that rwnd=0 is sent in SACK in response to
DATA message.
SUT: Client or Server
SCTP_Loopback_D_O_8_8Ensure that the IUT, if its peers rwnd indicates that the peer has no
buffer space, does not transmit DATA, until it receives a SACK, where
the rwnd indicates that the peer has buffer space again.
the data at the tester such that rwnd=0 is sent in SACK in response to
DATA message. Data should be in large size so it will be transmitted in
segments.
SUT: Client or Server
SCTP_Loopback_D_O_8_8_M2UAEnsure that the IUT, if its peers rwnd indicates that the peer has no
buffer space, does not transmit DATA, until it receives a SACK, where
the rwnd indicates that the peer has buffer space again.
the data at the tester such that rwnd=0 is sent in SACK in response to
DATA message. Data should be in large size so it will be transmitted in
segments.
SUT: Client or Server
SCTP_Loopback_D_O_8_12Ensure that the IUT on receipt of a SACK that contains Cumulative TSN
field less than the current Cumulative TSN Ack point, discards the SACK.
the data at the tester such that SACK chunk with cumulative TSN less than
the cumulative TSN ack point of SUT is sent to SUT.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_A
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_A/
SCTP_Loopback_A_V
SCTP_Loopback_A_V_9_1Ensure that the IUT send a SACK for the first DATA chunk it receives
immediately.
the data such that tester sends the first DATA and wait for SACK.
SUT: Client or Server
SCTP_Loopback_A_V_9_2Ensure that the IUT can acknowledge the reception of multiple DATA
chunks.
the Tester such that it sends multiple DATA chunks bundled in on SCTP
packet.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_A/
SCTP_Loopback_A_O
SCTP_Loopback_A_O_9_3Ensure that the IUT, if it detects a gap in the received data chunk
sequence, sends a SACK immediately where it reports the missing TSN
in the GAP ACK block.
the data such that SUT receive gap in DATA.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_M
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_M/
SCTP_Loopback_M_I
SCTP_Loopback_M_I_10_1Ensure that the IUT on receipt of an unrecognized chunk type with
highest order 2 bits set to 11, sends an ERROR with cause
"Unrecognized Chunk type" and a SACK for the DATA chunk
the Tester such that a datagram with reserved chunk type is sent to IUT
bundled with DATA chunk and higher two bits are set to 11.
SUT: Client or Server
SCTP_Loopback_M_I_10_2Ensure that the IUT on receipt of an unrecognized chunk type with
highest order 2 bits set to 00, discards this SCTP packet and does
not process the DATA chunk.
the data at the tester such that a datagram with reserved chunk type is
sent to IUT bundled with DATA chunk and higher two bits are set to 00.
SUT: Client or Server
SCTP_Loopback_M_I_10_3Ensure that the IUT on receipt of an unrecognized chunk type with
highest order 2 bits set to 01, discards this SCTP packet and does
not process the DATA chunk. Additionally it has to send an ERROR
with cause "Unrecognized Chunk Type"
the data at the tester such that a datagram with reserved chunk type is
sent to IUT bundled with DATA chunk and higher two bits are set to 01.
SUT: Client or Server
SCTP_Loopback_M_I_10_4Ensure that the IUT on receipt of an unrecognized chunk type with
highest order 2 bits set to 10, discards this chunk and sends a
SACK for the DATA chunk.
the Tester such that a datagram with reserved chunk type is sent to IUT
bundled with DATA chunk and higher two bits are set to 10.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_RT
SCTP_Loopback_Tests/
SCTP_Loopback_Generic_Tests/
SCTP_Loopback_RT/
SCTP_Loopback_RT_I
SCTP_Loopback_RT_I_11_1Ensure that the IUT, if timer T3-rtx expires on a destination address,
increases value of RTO for that address, i.e. increases T3-rtx timer.
the data at the tester such that SACK is not sent for the data received
from SUT.
SUT: Client or Server
SCTP_Loopback_RT_I_11_2Ensure that the IUT, if timer T3-rtx expires on a destination address,
increases value of RTO for that address.
the data at the tester such that SACK is not sent for the data received.
Reference: RFC 4960/2960 [1], section 6.3.3
SUT: Client or Server
SCTP_Loopback_RT_I_11_3*** Not supported in this release. Requires 4 network cards. ***
uses the RTO value of that address and not that of the previous address.
the data at the tester such that SACK is not sent for the data received.
Before sending the DATA note the T3-rtx value corresponding to both IP
addresses.
SUT: Client or Server
SCTP_Loopback_Tests/
SCTP_Loopback_Firewall_Tests
SCTP_Firewall_Test_V_001_H248Test both client and server side of SUT firewall in route mode
Send H.248 DATA on assoc 1, receive on assoc 2 and send SACK
SUT: Firewall
SCTP_Firewall_Test_V_001_SIPTest both client and server side of SUT firewall in route mode
Send SIP DATA on assoc 1, receive on assoc 2 and send SACK
SUT: Firewall
SCTP_Firewall_Test_V_002Test both client and server side of SUT firewall in route mode. Switch link
SUT: Firewall
SCTP_Firewall_Test_V_003Test both client and server side of SUT firewall
client <- server INIT ACK
client -> server COOKIE ECHO
client <- server SHUTDOWN
SUT: Firewall
SCTP_Firewall_Abort_Test_01Test both client and server side of SUT firewall in route mode. Switch link
SUT: Firewall
Misc
SCTP_GAP_TEST_01Send GAP DATA
SUT: Server
SCTP_GAP_TEST_02Send GAP DATA
SUT: Server
SCTP_GAP_TEST_03Send GAP DATA. Test retransmission
SUT: Server
SCTP_GAP_TEST_04Test retransmission at IUT by sending SACK with a GAP on receipt of DATA
SUT: Server
SCTP_DATA_TGENSends SCTP DATA in a loop
SUT:
SCTP_DATA_TOYO_TESTSends SCTP DATA
SUT:
SCTP_Make_Association_Send_Raw_MessageCreate an association, then output raw message
SUT: Server
SCTP_Initialize_For_RAW_MSGInitialize the lower layers of the protocol stack so individual RAW_MSG messages will be sent
SUT: Client or Server
SCTP_RAW_TEST_01Send a raw SCTP message; user-specified data in test
(only need to run once)
SUT: Client or Server
SCTP_RAW_TEST_02Send a specific mal-formed INIT_ACK packet.
Send a specific mal-formed INIT_ACK packet.
SCTP_RAW_TEST_03Send a specific INIT_ACK packet.
Send a specific INIT_ACK packet.
SCTP_RAW_TEST_04Send a specific INIT_ACK packet.
Send a specific INIT_ACK packet.
SCTP_RAW_TEST_05Send a specific INIT_ACK packet.
Send a specific INIT_ACK packet.
SCTP_Test_INIT_TOO_SHORTSend a specific INIT packet that is too short.
Send a specific INIT packet that is too short.
SCTP_Test_INIT_TOO_SHORT_loopbackFor purposes of testing a firewall, sends a specific INIT packet that is too short and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_INIT_TOO_LONGSend a specific INIT packet that is too long.
Send a specific INIT packet that is too long.
SCTP_Test_INIT_TOO_LONG_loopback For purposes of testing a firewall, Send a specific INIT packet that is too long and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_COOKIE_ACK_TOO_SHORTSend a specific COOKIE_ACK packet that is too short.
Send a specific COOKIE_ACK packet that is too short.
SCTP_Test_COOKIE_ACK_TOO_SHORT_loopback_1 For purposes of testing a firewall, sends a specific COOKIE_ACK packet that is too short and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_COOKIE_ACK_TOO_SHORT_loopback_2For purposes of testing a firewall, sends a specific COOKIE_ACK packet that is too short and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_COOKIE_ACK_TOO_LONGSend a specific COOKIE_ACK packet that is too long.
Send a specific COOKIE_ACK packet that is too long.
SCTP_Test_COOKIE_ACK_TOO_LONG_loopback_1 For purposes of testing a firewall, sends a specific COOKIE_ACK packet that is too long and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_COOKIE_ACK_TOO_LONG_loopback_2 For purposes of testing a firewall, sends a specific COOKIE_ACK packet that is too long and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_COOKIE_ACK_TOO_LONG_loopback_3 For purposes of testing a firewall, sends a specific COOKIE_ACK packet that is too long and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_SHUTDOWN_TOO_SHORTSend specific SHUTDOWN packets that are too short.
Send specific SHUTDOWN packets that are too short.
SCTP_Test_SHUTDOWN_TOO_SHORT_loopback_1 For purposes of testing a firewall, sends a specific SHUTDOWN packet that is too short and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_SHUTDOWN_TOO_SHORT_loopback_2 For purposes of testing a firewall, sends a specific SHUTDOWN packet that is too short and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_SHUTDOWN_TOO_LONGSend specific SHUTDOWN packets that are too long.
Send specific SHUTDOWN packets that are too long.
SCTP_Test_SHUTDOWN_TOO_LONG_loopback_1For purposes of testing a firewall, sends a specific SHUTDOWN packet that is too long and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_SHUTDOWN_TOO_LONG_loopback_2For purposes of testing a firewall, sends a specific SHUTDOWN packet that is too long and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_SHUTDOWN_TOO_LONG_loopback_3For purposes of testing a firewall, sends a specific SHUTDOWN packet that is too long and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_SHUTDOWN_TOO_LONG_loopback_4For purposes of testing a firewall, sends a specific SHUTDOWN packet that is too long and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_SHUTDOWN_TOO_LONG_loopback_5For purposes of testing a firewall, sends a specific SHUTDOWN packet that is too long and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_SHUTDOWN_TOO_LONG_loopback_6For purposes of testing a firewall, sends a specific SHUTDOWN packet that is too long and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_ABORT_TOO_SHORTSend a specific ABORT packet that is too short.
Send a specific ABORT packet that is too short.
SCTP_Test_ABORT_TOO_SHORT_loopback_1For purposes of testing a firewall, sends a specific ABORT packet that is too short and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_ABORT_TOO_SHORT_loopback_2For purposes of testing a firewall, sends a specific ABORT packet that is too short and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_ABORT_TOO_LONGSend a specific ABORT packet that is too long.
Send a specific ABORT packet that is too long.
SCTP_Test_ABORT_TOO_LONG_loopback_1 For purposes of testing a firewall, sends a specific ABORT packet that is too long and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_ABORT_TOO_LONG_loopback_2 For purposes of testing a firewall, sends a specific ABORT packet that is too long and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_ABORT_TOO_LONG_loopback_3 For purposes of testing a firewall, sends a specific ABORT packet that is too long and
if the firewall does not allow the packet to pass through, the test will PASS.
SCTP_Test_ABORT_TOO_LONG_2Send a specific ABORT packet that is too long.
Send a specific ABORT packet that is too long.
SCTP_Init_Forward_TSN_Test_V_001Test Forward TSN Supported optional parameter in INIT
SUT: SG
TEST_SCTP_DATA_1Send various ULPs
Send various ULPs
TEST_SIGNAL_INIT_ACK_W_OPTIONAL_PARAMSTest INIT_ACK_W_OPTIONAL_PARAMS codec
Test runs against itself; one as SENDER, other as RECEIVER
Start LISTENER as Server (run Initialize_SCTP_IUT_Server)
Start SENDER as Client (run Initialize_SCTP_IUT_Client)
That establishes the SCTP association.
Start this test in LISTENER (so it's waiting for the SENDER).
Start this test in SENDER.
Final result should be PASS.
TEST_SIGNAL_SHUTDOWN_COMPLETETest SHUTDOWN_COMPLETE codec
Test runs against itself; one as SENDER, other as RECEIVER
Start LISTENER as Server (run Initialize_SCTP_IUT_Server)
Start SENDER as Client (run Initialize_SCTP_IUT_Client)
That establishes the SCTP association.
Start this test in LISTENER (so it's waiting for the SENDER).
Start this test in SENDER.
Final result should be PASS.
TEST_SIGNAL_HEARTBEAT_CONTROL_SIGNALSTest signals to control heartbeats and heartbeat acks; background handling and whether they are received by test suite
Send_Background_Heartbeat
Send_Background_Heartbeat_ACK
Input_Heartbeat
Input_Heartbeat_ACK
settings in SCTP codec.
Configuration:
Test runs in single-PCO mode; only uses PCO1.
No SCTP association should be established.
Start this scenario; result should be PASS.
TEST_SIGNAL_HEARTBEAT_AND_HEARTBEAT_ACKTest signals to control heartbeats and heartbeat acks; background handling and whether they are received by test suite
Send_Background_Heartbeat
Send_Background_Heartbeat_ACK
Input_Heartbeat
Input_Heartbeat_ACK
settings in SCTP codec.
Proper operation of the control signals is required for this scenario to pass.
Test runs in single-PCO mode; only uses PCO1.
No SCTP association should be established.
Start this scenario; result should be PASS.
SCTP_Do_Reset_ConnectionSUT: Client or Server
SUT: Client or Server
SCTP_Send_ABORT_to_PCO1Send ABORT to PCO1 - Must run SCTP_Do_Reset_Connection first!
SUT: Client or Server
SCTP_Send_ABORT_to_PCO2Send ABORT to PCO2 - Must run SCTP_Do_Reset_Connection first!
SUT: Client or Server
SCTP_Loopback_Periodic_ABORTs_PCO1Send ABORTs periodically to PCO1
SUT: Client or Server
SCTP_Loopback_Periodic_ABORTs_PCO2Send ABORTs periodically to PCO2
SUT: Client or Server
SCTP_Loopback_Periodic_ABORTs_SimultaneousSend ABORTs periodically to both PCO1 and PCO2
SUT: Client or Server
SCTP_Loopback_Periodic_ABORTs_AlternatingSend ABORTs periodically, alternating between PCO1 and PCO2
SUT: Client or Server
SCTP_U_Bit_01Set U Flag set to TRUE (1)to check out-of-order message transfer

SUT: Client or Server
SCTP_test
SCTP_Heartbeat_ACK_testConfirm that the tester is able to send a HEARTBEAT_ACK message programmatically
data at the tester such that HEARTBEAT message is sent to the SUT.
SUT: Client or Server
SCTP_Test_Abort_ShutdownTest procedure POSTAMBLE: wait for association, make it, then when SHUTDOWN received, send an ABORT instead of SHUTDOWN_ACK
Reference: internal test
SCTP_RTest_Randomize_Validation_Tag
Confirm that the validation tags are randomized or a specific value, based on configuration file settings.
To run this test:
Run Campaigner
Load the test suite
Select this test
This test may be run repeatedly back-to-back.
TESTTESTER_SCTP_AS_I_1_2_2Test scenario SCTP_AS_I_1_2_2
Test scenario SCTP_AS_I_1_2_2
SCTP_Misc_PCO1_HeartbeatSend a HEARTBEAT on HEARTBEAT_G (PCO1)
SCTP association should be established
SCTP_TGEN_Test_1TGEN testing
SCTP_TGEN_Test_2TGEN testing, 2 associations
SCTP_TGEN_Test_4TGEN testing, 4 associations
Misc_HA
Misc_HA/
Ha_raw_test
Ha_SCTP_Loopback_RAW_Assoc_DATA_ShutdownExample to show sending a complete INIT/INIT_ACK
SUT: Firewall
Ha_SCTP_Loopback_RAW_Assoc_DATA_Shutdown_INVALID_DATA_CHUNK_TYPEExample to show sending a complete INIT/INIT_ACK
SUT: Firewall
Ha_SCTP_Loopback_RAW_Assoc_DATA_Shutdown_INVALID_INITIATE_TAG_IN_INIT_CHUNKExample to show sending a complete INIT/INIT_ACK
SUT: Firewall
Ha_SCTP_Loopback_RAW_Assoc_DATA_Shutdown_INVALID_INOUND_STREAM_COUNT_0_INIT_CHUNKExample to show sending a complete INIT/INIT_ACK
SUT: Firewall
Ha_SCTP_Loopback_RAW_Assoc_DATA_Shutdown_INVALID_DATA_RANGE_CHECKSExample to show sending a complete INIT/INIT_ACK
SUT: Firewall
Ha_SCTP_Loopback_RAW_Assoc_DATA_Shutdown_INVALID_INIT_ACK_NO_COOKIE_PARAMExample to show sending a complete INIT/INIT_ACK
SUT: Firewall
Ha_SCTP_Loopback_RAW_Assoc_DATA_Shutdown_INVALID_INIT_W_IPaddr_0Example to show sending a complete INIT/INIT_ACK
SUT: Firewall

VariableDefault ValueDescription
SECONDARY_ON_SAME_ADAPTERFALSEFALSE: PCOx_1 = ADAPTER 1, PCOx_2 = ADAPTER 2 TRUE: PCO1_1 & PCO1_2 = ADAPTER 1, PCO2_1 & PCO2_2 = ADAPTER 2
N_Adaptors1(null)
N_Sockets1(null)
Adaptor_ID_11Adaptor ID used for testing
Adaptor_ID_22Adaptor ID used for testing
PCO1_Use_Primary_AddressTRUEUse primary or secondary NIC card for this PCO
PCO2_Use_Primary_AddressTRUEUse primary or secondary NIC card for this PCO
PCO3_Use_Primary_AddressTRUEUse primary or secondary NIC card for this PCO
PCO4_Use_Primary_AddressTRUEUse primary or secondary NIC card for this PCO
Src_Dst_On_Same_LANTRUE(null)
Sock1_1st_IPv4_Router_Address(null)(null)
Sock1_2nd_IPv4_Router_Address(null)(null)
Sock2_1st_IPv4_Router_Address(null)(null)
Sock2_2nd_IPv4_Router_Address(null)(null)
Sock3_1st_IPv4_Router_Address(null)(null)
Sock4_1st_IPv4_Router_Address(null)(null)
Sock5_1st_IPv4_Router_Address(null)(null)
Sock6_1st_IPv4_Router_Address(null)(null)
PCO1_Src_IP_Addr"192.168.1.47"Tester IP address for link 1 (primary on NIC 1)
PCO1_Src_IPv6_Addr'00010000000000000000000000000...(null)
PCO1_Dst_IP_Addr"192.168.1.58"SUT IP address for link 1 (primary on NIC 1)
PCO1_Dst_IPv6_Addr'00020000000000000000000000000...(null)
PCO1_Src_Port9900Tester port for link 1 (primary on NIC 1)
PCO1_Dst_Port9900SUT port for link 1 (primary on NIC 1)
PCO1_2_Src_IP_Addr"192.168.5.47"Tester IP address for link 1 (secondary on NIC 2)
PCO1_2_Dst_IP_Addr"192.168.5.58"SUT IP address for link 1 (secondary on NIC 2)
PCO1_2_Src_Port9900Tester port for link 1 (secondary on NIC 2)
PCO1_2_Dst_Port9900SUT port for link 1 (secondary on NIC 2)
PCO2_Src_IP_Addr"192.168.2.51"Tester IP address for link 2 (primary on NIC 1)
PCO2_Dst_IP_Addr"192.168.2.52"SUT IP address for link 2 (primary on NIC 1)
PCO2_Src_Port50001Tester port for link 2 (primary on NIC 1)
PCO2_Dst_Port50001SUT port for link 2 (primary on NIC 1)
PCO2_2_Src_IP_Addr"192.168.5.47"Tester IP address for link 2 (secondary on NIC 2)
PCO2_2_Dst_IP_Addr"192.168.5.58"SUT IP address for link 2 (secondary on NIC 2)
PCO2_2_Src_Port9900Tester port for link 2 (secondary on NIC 2)
PCO2_2_Dst_Port9900SUT port for link 2 (secondary on NIC 2)
PCO3_Src_IP_Addr"192.168.3.51"(null)
PCO3_Dst_IP_Addr"192.168.3.52"(null)
PCO3_Src_Port50001(null)
PCO3_Dst_Port50001(null)
PCO3_2_Src_IP_Addr"192.168.5.47"(null)
PCO3_2_Dst_IP_Addr"192.168.5.58"(null)
PCO3_2_Src_Port9900(null)
PCO3_2_Dst_Port9900(null)
PCO4_Src_IP_Addr"192.168.4.51"(null)
PCO4_Dst_IP_Addr"192.168.4.52"(null)
PCO4_Src_Port50001(null)
PCO4_Dst_Port50001(null)
PCO4_2_Src_IP_Addr"192.168.5.47"(null)
PCO4_2_Dst_IP_Addr"192.168.5.58"(null)
PCO4_2_Src_Port9900(null)
PCO4_2_Dst_Port9900(null)
SCTP_Activation_ModeSCTP_Activation_Mode_Active(null)
IPv4_Addr_UsedTRUESet to TRUE to use optional parameter, IPv4 address in messages
Test_IPv4_Addr"192.168.1.47"Test IPv4 address parameter. Needed for some test scenarios (e.g. SCTP_AS_V_1_6_1). Set to null string to not use this optional parameter in test SCTP_AS_V_1_6_1.
IPv6_Addr_UsedTRUESet to TRUE to use optional parameter, IPv6 address in messages
Test_IPv6_Addr"21DA:D3:0:2F3B:2AA:FF:FE28:9C...Test IPv6 address parameter. Needed for some test scenarios (e.g. SCTP_AS_V_1_6_1). Set to null string to not use this optional parameter in test SCTP_AS_V_1_6_1.
Host_Name_UsedTRUESet to TRUE to use optional parameter, Host Name in messages
Test_Optional_Host_Name""Test Host Name parameter. Needed for some test scenarios (e.g. SCTP_AS_V_1_6_1). Set to null string to not use this optional parameter in test SCTP_AS_V_1_6_1.
Test_Host_Name"testhost.com"Test Host Name parameter. Needed for some test scenarios (e.g. SCTP_AS_V_1_6_1).
Supported_Addr_Type_UsedTRUESet to TRUE to use optional parameter, supported address type in messages
Test_Supported_Addr_Type5Test Supported Address Type parameter. Needed for some test scenarios (e.g. SCTP_AS_V_1_6_1). Set to -1 to not use this optional parameter in test SCTP_AS_V_1_6_1.
Cookie_Preservative_Type_UsedTRUESet to TRUE to use optional parameter, supported address type in messages
Test_Cookie_Preservative2000Test Cookie Preservative parameter. Needed for some test scenarios (e.g. SCTP_AS_V_1_6_1). Set to -1 to not use this optional parameter in test SCTP_AS_V_1_6_1.
Layer_3_ProtocolUse_IPv4Network layer; above Ethernet, default = Use_IPv4
Initiate_Tag_RandomizeUse_Specific_ValueRandomize Verification Tag at test start?
Initiate_Tag_Value123specific value for Verification Tag when we send INIT or INIT_ACK
N_InS336Number of In Streams
N_OutS336Number of Out Streams
PX_Raw_Data'01000024660B72BC0002000000200...(null)
Cookie_Life_Incr-1(null)
T_WAIT_RESPONSE_VAL30000(null)
MAX_INIT_RETRANS_VAL8(null)
T1_INIT_MIN_VAL500(null)
T1_INIT_MAX_VAL1500(null)
Shutdown_Chunk_Qty8wait for this many SHUTDOWNs from IUT, default = 8
Shutdown_Max_Single_Time60000maximum wait for SHUTDOWN to be received, default = 60000 (60 seconds)
Shutdown_Max_Total_Time300000maximum time for *all* SHUTDOWNs to be received, default = 300000 ( 5 minutes)
Shutdown_Tx_Interval1000send SHUTDOWN from IUT (PCO2) after this delay, default = 1000 ( 1 second)
Shutdown_INTERVAL_VAL500maximum wait for SHUTDOWN to be received
Shutdown_CYCLE_VAL1500maximum time for *all* SHUTDOWNs to be received
Shutdown_Ack_RETRANS_VAL8(null)
Shutdown_Ack_INTERVAL_VAL500(null)
Shutdown_Ack_CYCLE_VAL1500(null)
Shutdown_TSN_OFFSET_VAL0This is added to SHUTDOWN Cumulative TSN ACK value default = 0
Cookie_T_MAX_VAL1500The lifetime value of the COOKIE in millisecs.
Max_Retries3(null)
TSPX_Max_Retrans10(null)
MTU_size66The MTU used by the SUT.
Test_Data'01000501000000400001000800000...DATA chunk that is used in tests SCTP_M_I_10_x (x=1 to 4).
Dummy_Data'01000501000000400001000800000...DATA whose size is equal to MTU size.
Max_MTU_size30(null)
Max_Dummy_Data'01000501000000400001000800000...DATA whose size is equal to MTU size.
Over_Max_Dummy_Data'01000501000000400001000800000...DATA whose size is equal to MTU size.
T3_Rtx_Value2000(null)
TSPX_Number_of_DATA_Bundled3(null)
TSPX_ULP3The ULP of the data in the DATA message..
TSPX_xUA_Data'0100030100000008'HxUA DATA in Hex which will be sent in a DATA message.
TSPX_xUA_Data_frag1'01000301'H1st xUA DATA in Hex fragmented which will be sent in a DATA message.
TSPX_xUA_Data_frag2'00000008'H2nd xUA DATA in Hex fragmented which will be sent in a DATA message.
TSPX_IP_Not_Association"192.168.1.62"(null)
T_WAIT_SHORT_VAL1000(null)
TSPX_Non_unicast_IP"224.0.0.1"(null)
T_BIT1(null)
Cause_Code_1_UsedTRUE(null)
Cause_Code_1_Value4(null)
Cause_Code_1_Info""(null)
Cause_Code_2_UsedFALSE(null)
Cause_Code_2_Value1(null)
Cause_Code_2_Info""(null)
MyTestSuiteTesterRole(null)Self-test diagnostics
Sender_Response_Wait_Time4000Self-test diagnostics
Sender_Pause_Time1000Self-test diagnostics
Listener_Wait_Time30000Self-test diagnostics
Wait_Time3000Self-test diagnostics

Copyright © ACATS Forum 2008 on behalf of the test suite author. All rights reserved. Specifications may change subject to requirements.

21 Dec 2009Produced by SAFIRE V20.05.14.01
www.SAFIRE-World.com		 Test Suite Overview