NAME

  AsconfAckWithNextSeq.seq - ASCONF-ACK chunk is received with the next Sequence Number but no ASCONF Chunk is outstanding

PURPOSE

  To check that if ASCONF-ACK chunk is received with Sequence Number
  equal to next Sequence Number but no ASCONF Chunk is outstanding
  then the endpoint MUST ABORT the association.

SYNOPSIS

  ./AsconfAckWithNextSeq.seq [-tooloption ...] -pkt ./AsconfAckWithNextSeq.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 the date
  in endpoint A such that ASCONF-ACK chunk with Sequence Number equal to
  next Sequence Number is sent to endpoint B.

TEST PROCEDURE

  Endpoint A                           Endpoint B                ULP
  (ESTABLISHED)                        (ESTABLISHED)

  ASCONF-ACK    ----------------->
  (Sequence Number equal to next Sequence Number)
                <-----------------      ABORT

  TEST DESCRIPTION:

  1. Send ASCONF-ACK chunk from endpoint A to B with Sequence Number
     equal to next Sequence Number.
  2. Check A: ABORT chunk should be received at endpoint A.

NOTE

  None

REFERENCE

  RFC 5061

  5.3.  General Rules for Address Manipulation

    When building TLV parameters for the ASCONF Chunk that will add or
    delete IP addresses, the following rules MUST be applied:

    F0)  If an endpoint receives an ASCONF-ACK that is greater than or
         equal to the next Sequence Number to be used but no ASCONF Chunk
         is outstanding, the endpoint MUST ABORT the association.  Note
         that a Sequence Number is greater than if it is no more than
         2^^31-1 larger than the current Sequence Number (using serial
         arithmetic).