InitAckWithZeroTag.seq - INIT-ACK chunk is received with initiate tag set to zero
To check that if INIT-ACK chunk is received with initiate tag set to
zero, the endpoint should responded it with ABORT chunk including
cause of invalid mandatory parameter.
./InitAckWithZeroTag.seq [-tooloption ...] -pkt ./InitAckWithZeroTag.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 the
data in endpoint A such that INIT-ACK message with initiate tag set
to zero is sent to endpoint B.
Endpoint A Endpoint B ULP
(CLOSED) (CLOSED)
<----- Associate
<----------------- INIT
INIT-ACK ----------------->
(with initiate tag = 0)
<----------------- ABORT
(Invalid Mandatory Parameter)
TEST DESCRIPTION:
1. Attempt to make an association from endpoint A to endpoint B. Send
INIT-ACK message with initiate tag set to zero.
Record the message sequence using a signal emulator.
2. Check A: INIT-ACK message is responded with ABORT including cause of
invalid mandatory parameter.
None
RFC 4960
3.3.3. Initiation Acknowledgement (INIT ACK) (2)
Initiate Tag: 32 bits (unsigned integer)
The receiver of the INIT ACK records the value of the Initiate Tag
parameter. This value MUST be placed into the Verification Tag
field of every SCTP packet that the INIT ACK receiver transmits
within this association.
The Initiate Tag MUST NOT take the value 0. See Section 5.3.1 for
more on the selection of the Initiate Tag value.
If the value of the Initiate Tag in a received INIT ACK chunk is
found to be 0, the receiver MUST destroy the association
discarding its TCB. The receiver MAY send an ABORT for debugging
purpose.