NAME

  DupInitAckInEstab.seq - Unexpected INIT-ACK chunk is received in ESTABLISHED state


PURPOSE

  To check that if INIT-ACK chunk is received in ESTABLISHED state then
  the endpoint should silently discard a received INIT-ACK chunk.


SYNOPSIS

  ./DupInitAckInEstab.seq [-tooloption ...] -pkt ./DupInitAckInEstab.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-ACK message is sent to endpoint B
  in ESTABLISHED state.


TEST PROCEDURE

  Endpoint A                           Endpoint B                ULP
  (ESTABLISHED)                        (ESTABLISHED)
  INIT-ACK      ----------------->      Silently discard
  TEST DESCRIPTION:
  1. Send INIT-ACK message after the association between them is setuped.
  2. Check A: INIT-ACK message received in ESTABLISHED state is discarded.
  3. Check B: Current state is not disturbed and an association can be 
     completed between A and B.


NOTE

  None


REFERENCE

  RFC 4960
  5.2.3.  Unexpected INIT ACK
    If an INIT ACK is received by an endpoint in any state other than the
    COOKIE-WAIT state, the endpoint should discard the INIT ACK chunk.
    An unexpected INIT ACK usually indicates the processing of an old or
    duplicated INIT chunk.