ErrorInShutRecv.seq - ERROR chunk is received in SHUTDOWN-RECEIVED state
To check that if ERROR chunk is received in SHUTDOWN-RECEIVED state then the
endpoint should discarded the ERROR chunk.
./ErrorInShutRecv.seq [-tooloption ...] -pkt ./ErrorInShutRecv.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 B such that terminate primitive is received from
ULP to terminate the association. Arrange data in endpoint A such
that SHUTDOWN message is sent to endpoint B.
Endpoint A Endpoint B ULP
(ESTABLISHED) (ESTABLISHED)
<----------------- DATA
SHUTDOWN ----------------->
<----------------- DATA
(retransmit)
ERROR -----------------> Discarded
<----------------- DATA
(retransmit)
TEST DESCRIPTION:
1. Try to terminate the association between endpoint A and B by sending
terminate primitive from ULP. While endpoint B is in SHUTDOWN-RECEIVED
state, send ERROR message from endpoint A.
2. Check A: ERROR message received in SHUTDOWN-RECEIVED state is discarded.
None
RFC 4960
3.3.10. Operation Error (ERROR) (9)
An endpoint sends this chunk to its peer endpoint to notify it of
certain error conditions. It contains one or more error causes. An
Operation Error is not considered fatal in and of itself, but may be
used with an ABORT chunk to report a fatal condition. It has the
following parameters:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 9 | Chunk Flags | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ one or more Error Causes /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Chunk Flags: 8 bits
Set to 0 on transmit and ignored on receipt.
Length: 16 bits (unsigned integer)
Set to the size of the chunk in bytes, including the chunk header
and all the Error Cause fields present.