ShutWithNotSendTSN.seq - SHUTDOWN is received with TSN greater than the Cumulative TSN Ack point
To check that if SHUTDOWN is received with TSN greater than the Cumulative
TSN Ack point, endpoint should respond with the ABORT message with "Protocol
Violation" error cause.
./ShutWithNotSendTSN.seq [-tooloption ...] -pkt ./ShutWithNotSendTSN.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 data
in endpoint A such that SHUTDOWN chunk with TSN greater than the
Cumulative TSN Ack point is sent to endpoint B.
Endpoint A Endpoint B ULP
(ESTABLISHED) (ESTABLISHED)
SHUTDOWN ----------------->
(with TSN greater than the Cumulative TSN Ack point)
<---------------- ABORT
(Protocol Violation)
TEST DESCRIPTION:
1. Send SHUTDOWN chunk from endpoint A to B with TSN greater than
the Cumulative TSN Ack point.
2. Check A: ABORT should be received at endpoint A.
3. Check B: Error cause in ABORT is set to "Protocol Violation".
None
RFC 4960
9.2. Shutdown of an Association
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.
Once an endpoint has reached the SHUTDOWN-RECEIVED state, it MUST NOT
send a SHUTDOWN in response to a ULP request, and should discard
subsequent SHUTDOWN chunks.
If there are still outstanding DATA chunks left, the SHUTDOWN
receiver MUST continue to follow normal data transmission procedures
defined in Section 6, until all outstanding DATA chunks are
acknowledged; however, the SHUTDOWN receiver MUST NOT accept new data
from its SCTP user.