InitAckWithZeroMIS.seq - INIT-ACK chunk is received with number of inbound streams set to zero
To check that if INIT-ACK chunk is received with number of inbound streams
set to zero, the endpoint should responded it with ABORT chunk including
cause of invalid mandatory parameter.
./InitAckWithZeroMIS.seq [-tooloption ...] -pkt ./InitAckWithZeroMIS.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 number of inbound
streams set to zero is sent to endpoint B.
Endpoint A Endpoint B ULP
(CLOSED) (CLOSED)
<----- Associate
<----------------- INIT
INIT-ACK ----------------->
(with MIS = 0)
<----------------- ABORT
(Invalid Mandatory Parameter)
TEST DESCRIPTION:
1. Attempt to make an association from endpoint A to endpoint B. Send
INIT-ACK message with number of inbound streams 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)
Number of Inbound Streams (MIS): 16 bits (unsigned integer)
Defines the maximum number of streams the sender of this INIT ACK
chunk allows the peer end to create in this association. The
value 0 MUST NOT be used.
Note: There is no negotiation of the actual number of streams but
instead the two endpoints will use the min(requested, offered).
See Section 5.1.1 for details.
Note: A receiver of an INIT ACK with the MIS value set to 0 SHOULD
destroy the association discarding its TCB.