InitWithBadTag.seq - INIT chunk is received with the Verification Tag not set to 0
To check that if INIT chunk is received with the Verification Tag not
set to 0, the enpoint should responds it with ABORT message.
./InitWithBadTag.seq [-tooloption ...] -pkt ./InitWithBadTag.def
-tooloption : v6eval tool option
See Also: ../common/STD_PKT_COMMON.def
../common/SCTP_COMMON.def
Association not established between endpoint A and B. Arrange the data
in endpoint A such that an INIT message is sent to endpoint B with
Verification Tag not set to 0 in it.
Endpoint A Endpoint B ULP
(ESTABLISHED) (ESTABLISHED)
INIT ----------------->
(with Verification Tag not set to 0)
<----------------- ABORT
TEST DESCRIPTION:
1. From endpoint A, send INIT message with no zero Verification Tag
endpoint B, when there is no association between them.
2. Check A: INIT message will be silently discarded.
3. Check B: State of endpoint B is not disturbed.
None
RFC 4960
8.4. Handle "Out of the Blue" Packets
3) If the packet contains an INIT chunk with a Verification Tag set
to '0', process it as described in Section 5.1. If, for whatever
reason, the INIT cannot be processed normally and an ABORT has to
be sent in response, the Verification Tag of the packet
containing the ABORT chunk MUST be the Initiate Tag of the
received INIT chunk, and the T bit of the ABORT chunk has to be
set to 0, indicating that the Verification Tag is NOT reflected.
8.5.1. Exceptions in Verification Tag Rules
A) Rules for packet carrying INIT:
- The sender MUST set the Verification Tag of the packet to 0.
- When an endpoint receives an SCTP packet with the Verification
Tag set to 0, it should verify that the packet contains only an
INIT chunk. Otherwise, the receiver MUST silently discard the
packet.