ShutInEstab1.seq - Stop accepting new data from its SCTP user in SHUTDOWN-RECEIVED State
To check that if endpoint is in SHUTDOWN-RECEIVED state then the endpoint
should stop accepting new data from its SCTP user.
./ShutInEstab1.seq [-tooloption ...] -pkt ./ShutInEstab1.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 SHUTDOWN message is sent to endpoint
B after receiving DATA message from it.
Endpoint A Endpoint B ULP
(ESTABLISHED) (ESTABLISHED)
<----- Send
<----------------- DATA
SHUTDOWN ----------------->
DATA ----------------->
<----------------- SACK
SACK ----------------->
<----- Send
DATA will not be sent
TEST DESCRIPTION:
1. Attempt to terminate an association from endpoint A to endpoint
B by sending SHUTDOWN.
Record the message sequence using a signal emulator.
2. Send data from ULP while in SHUTDOWN-RECEIVED state.
3. Check A: DATA will not be sent.
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.
Upon reception of the SHUTDOWN, the peer endpoint shall
- enter the SHUTDOWN-RECEIVED state,
- stop accepting new data from its SCTP user, and
- verify, by checking the Cumulative TSN Ack field of the chunk,
that all its outstanding DATA chunks have been received by the
SHUTDOWN sender.