T2ShutdownTimeout1.seq - Failure to receive SHUTDOWN-ACK after retransmit times to 'Association.Max.Retrans'
To check that if SHUTDOWN is retransmitted for Association.Max.Retrans
then association is aborted.
./T2ShutdownTimeout1.seq [-tooloption ...] -pkt ./T2ShutdownTimeout1.def
-tooloption : v6eval tool option
See Also: ../common/STD_PKT_COMMON.def
../common/SCTP_COMMON.def
Association is established between endpoint A and B. Arrange the
data in endpoint A such that no SHUTDOWN-ACK is sent in response
to SHUTDOWN.
Endpoint A Endpoint B ULP
(ESTABLISHED) (ESTABLISHED)
<----- Terminate
<---------------- SHUTDOWN
|
| T2-Shutdown
| Timer
|
<---------------- SHUTDOWN
.
. Retransmit x
. times
TEST DESCRIPTION:
1. Try to terminate an association between endpoint A and endpoint B by
sending SHUTDOWN message from endpoint B.Don't send the SHUTDOWN-ACK
or any DATAGRAM from the endpoint A.
2. Check A: If SHUTDOWN message is transmitted for ASSOCIATION.MAX.RETRANS
times without getting an SHUTDOWN-ACK, Association is aborted and
upper layers are reported of this.
None
RFC 4960
9.2. Shutdown of an Association
An endpoint should limit the number of retransmissions of the
SHUTDOWN chunk to the protocol parameter 'Association.Max.Retrans'.
If this threshold is exceeded, the endpoint should destroy the TCB
and MUST report the peer endpoint unreachable to the upper layer (and
thus the association enters the CLOSED state). The reception of any
packet from its peer (i.e., as the peer sends all of its queued DATA
chunks) should clear the endpoint's retransmission count and restart
the T2-shutdown timer, giving its peer ample opportunity to transmit
all of its queued DATA chunks that have not yet been sent.