NAME

  GEN_InvalidMandParam.seq - Generation of error cause Invalid Mandatory Parameter

PURPOSE

  To check that if INIT chunk is received with one of the mandatory parameters
  is set to an invalid value, the endpoint should responded it with ABORT chunk
  including cause of Invalid Mandatory Parameter.

SYNOPSIS

  ./GEN_InvalidMandParam.seq [-tooloption ...] -pkt ./GEN_InvalidMandParam.def
    -tooloption : v6eval tool option
  See Also: ../common/STD_PKT_COMMON.def
            ../common/SCTP_COMMON.def

PRE-TEST CONDITION

  Association is not established between endpoint A and B. Arrange the
  data in endpoint A such that INIT message with one of the mandatory
  parameters set to an invalid value is sent to endpoint B.

TEST PROCEDURE

  Endpoint A                           Endpoint B                ULP
  (CLOSED)                             (CLOSED)

  INIT          ----------------->
  (with Invalid Mandatory Parameter)
                <-----------------      ABORT
                                        (with Invalid Mandatory Parameter)

  TEST DESCRIPTION:

  1. Attempt to make an association from endpoint A to endpoint B. Send 
     INIT message with one of the mandatory parameters set to an invalid
     value.
     Record the message sequence using a signal emulator.
  2. Check A: INIT message is responded with ABORT including cause of 
     invalid mandatory parameter.

NOTE

  None

REFERENCE

  RFC 4960

  3.3.10.7.  Invalid Mandatory Parameter (7)

    Cause of error
    ---------------

    Invalid Mandatory Parameter: This error cause is returned to the
    originator of an INIT or INIT ACK chunk when one of the mandatory
    parameters is set to an invalid value.

        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        |     Cause Code=7              |      Cause Length=4           |
        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+