NAME

  InvalidParamInAbort.seq - ABORT chunk is received with invalid parameter length


PURPOSE

  To check that if ABORT chunk is received with invalid parameter length, the
  endpoint should discard the packet.


SYNOPSIS

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


PRE-TEST CONDITION

  Association is established between endpoint A and B. Arrange data
  in endpoint A such that ABORT message is sent to endpoint B with
  invalid parameter length.


TEST PROCEDURE

  Endpoint A                           Endpoint B                ULP
  (ESTABLISHED)                        (ESTABLISHED)
  ABORT         ----------------->      Silently Discard
  (with Invalid Parameter Length)
  TEST DESCRIPTION:
  1. Send ABORT message from endpoint A to B with invalid parameter length.
     Record the message sequence using a signal emulator.
  2. Check A: ABORT message is discarded and no other actions are taken. 
  3. Check B: Was the message sequence as above.


NOTE

  None


REFERENCE

  RFC 4960
  3.3.7.  Abort Association (ABORT) (6)
    The ABORT chunk is sent to the peer of an association to close the
    association.  The ABORT chunk may contain Cause Parameters to inform
    the receiver about the reason of the abort.  DATA chunks MUST NOT be
    bundled with ABORT.  Control chunks (except for INIT, INIT ACK, and
    SHUTDOWN COMPLETE) MAY be bundled with an ABORT, but they MUST be
    placed before the ABORT in the SCTP packet or they will be ignored by
    the receiver.
    If an endpoint receives an ABORT with a format error or no TCB is
    found, it MUST silently discard it.  Moreover, under any
    circumstances, an endpoint that receives an ABORT MUST NOT respond to
    that ABORT by sending an ABORT of its own.