InvalidParamInHeartbeat.seq - HEARTBEAT chunk is received with invalid parameter length
To check that if HEARTBEAT chunk is received with invalid parameter length, the
endpoint should send ABORT message with a Protocol Violation error cause.
./InvalidParamInHeartbeat.seq [-tooloption ...] -pkt ./InvalidParamInHeartbeat.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 HEARTBEAT message is sent to endpoint B
with invalid parameter length.
Endpoint A Endpoint B ULP
(ESTABLISHED) (ESTABLISHED)
HEARTBEAT ----------------->
(with Invalid Parameter Length)
<----------------- ABORT
(Protocol Violation)
TEST DESCRIPTION:
1. Send HEARTBEAT message from endpoint A to B with invalid parameter length.
Record the message sequence using a signal emulator.
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
3.3.10.13. Protocol Violation (13)
Cause of error
--------------
This error cause MAY be included in ABORT chunks that are sent
because an SCTP endpoint detects a protocol violation of the peer
that is not covered by the error causes described in Section 3.3.10.1
to Section 3.3.10.12. An implementation MAY provide additional
information specifying what kind of protocol violation has been
detected.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause Code=13 | Cause Length=Variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Additional Information /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+