GEN_InvalidParamLen.seq - Generation of error cause Protocol Violation (Invalid Parameter Length)
To check that if INIT chunk is received with invalid parameter
length then the endpoint should send ABORT message with cause
Protocol Violation.
./GEN_InvalidParamLen.seq [-tooloption ...] -pkt ./GEN_InvalidParamLen.def
-tooloption : v6eval tool option
See Also: ../common/STD_PKT_COMMON.def
../common/SCTP_COMMON.def
Association is not established between endpoint A and B. Arrange
data in endpoint A such that INIT chunk with invalid parameter
length is sent to endpoint B.
Endpoint A Endpoint B ULP
(CLOSED) (CLOSED)
INIT ----------------->
(with Invalid Parameter Length)
<----------------- ABORT
(Protocol Violation)
TEST DESCRIPTION:
1. Send INIT chunk from endpoint A to B with invalid parameter
length.
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 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+