GEN_MissingParameter.seq - Generation of error cause Missing Mandatory Parameter
To check that if a INIT-ACK chunk is received with missing mandatory parameter, the endpoint should send ABORT message with cause Missing Mandatory Parameter.
./GEN_MissingParameter.seq [-tooloption ...] -pkt ./GEN_MissingParameter.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-ACK chunk with missing mandatory parameter is sent to endpoint B.
Endpoint A Endpoint B ULP (ESTABLISHED) (ESTABLISHED)
<----- Associate <----------------- INIT
INIT-ACK -----------------> (with Missing Mandatory Parameter) <----------------- ABORT (with Missing Mandatory Parameter)
TEST DESCRIPTION:
1. Send INIT-ACK chunk from endpoint A to B with missing mandatory parameter. 2. Check A: ABORT should be received at endpoint A. 3. Check B: Error cause in ABORT is set to "Missing Mandatory Parameter".
None
RFC 4960
3.3.10.2. Missing Mandatory Parameter (2)
Cause of error ---------------
Missing Mandatory Parameter: Indicates that one or more mandatory TLV parameters are missing in a received INIT or INIT ACK.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Cause Code=2 | Cause Length=8+N*2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Number of missing params=N | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Missing Param Type #1 | Missing Param Type #2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Missing Param Type #N-1 | Missing Param Type #N | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Number of Missing params: 32 bits (unsigned integer)
This field contains the number of parameters contained in the Cause-Specific Information field.
Missing Param Type: 16 bits (unsigned integer)
Each field will contain the missing mandatory parameter number.