EchoWithBadChunkLength.seq - ECN-ECHO chunk is received with invalid chunk length
To check that if ECN-ECHO chunk is received with invalid chunk length, the
endpoint should response with ABORT message.
./EchoWithBadChunkLength.seq [-tooloption ...] -pkt ./EchoWithBadChunkLength.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 ECN-ECHO chunk with invalid chunk length is
sent to endpoint A.
Endpoint A Endpoint B ULP
(ESTABLISHED) (ESTABLISHED)
ECN_CWR ----------------->
(with invalid chunk length)
<---------------- ABORT
TEST DESCRIPTION:
1. Send ECN_ECHO chunk with invalid chunk length from endpoint A to
endpoint B.
2. Check A: ABORT message will be sent to response ECN_ECHO chunk from
endpoint B.
None
RFC 4960
Appendix A. Explicit Congestion Notification
CWR:
[RFC3168] details a specific bit for a sender to send in the header
of its next outbound TCP segment to indicate to its peer that it has
reduced its congestion window. This is termed the CWR bit. For
SCTP, the same indication is made by including the CWR chunk. This
chunk contains one data element, i.e., the TSN number that was sent
in the ECNE chunk. This element represents the lowest TSN number in
the datagram that was originally marked with the CE bit.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Chunk Type=13 | Flags=00000000| Chunk Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Lowest TSN Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: The CWR is considered a Control chunk.