NAME

  InitWithZeroTag.seq - INIT chunk is received with initiate tag set to zero


PURPOSE

  To check that if INIT chunk is received with initiate tag set to zero, the
  endpoint should responded it with ABORT chunk.


SYNOPSIS

  ./InitWithZeroTag.seq [-tooloption ...] -pkt ./InitWithZeroTag.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 initiate tag set to
  zero is sent to endpoint B.


TEST PROCEDURE

  Endpoint A                           Endpoint B                ULP
  (CLOSED)                             (CLOSED)
  INIT          ----------------->
  (with initiate tag set to zero)
                <-----------------      ABORT
  TEST DESCRIPTION:
  1. Attempt to make an association from endpoint A to endpoint B. Send 
     INIT message with initiate tag set to zero.
     Record the message sequence using a signal emulator.
  2. Check A: INIT message is responded with ABORT.


NOTE

  None


REFERENCE

  RFC 4960
  3.3.2.  Initiation (INIT) (1)
    Initiate Tag: 32 bits (unsigned integer)
      The receiver of the INIT (the responding end) records the value of
      the Initiate Tag parameter.  This value MUST be placed into the
      Verification Tag field of every SCTP packet that the receiver of
      the INIT transmits within this association.
      The Initiate Tag is allowed to have any value except 0.  See
      Section 5.3.1 for more on the selection of the tag value.
      If the value of the Initiate Tag in a received INIT chunk is found
      to be 0, the receiver MUST treat it as an error and close the
      association by transmitting an ABORT.