NAME

  BundledAsconfChunks.seq - ASCONF chunk is received bundled with other ASCONF chunk


PURPOSE

  To chech that if ASCONF chunk is received bundled with other ASCONF chunk
  then the endpoint should process the next ASCONF chunk after processing
  the first ASCONF chunk.


SYNOPSIS

  ./BundledAsconfChunks.seq [-tooloption ...] -pkt ./BundledAsconfChunks.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 chunk which is bundled with other ASCONF
  chunk is sent to endpoint B.


TEST PROCEDURE

  Endpoint A                           Endpoint B                ULP
  (ESTABLISHED)                        (ESTABLISHED)
  ASCONF + ASCONF ----------------->
                  <-----------------    ASCONF-ACK + ASCONF-ACK
  TEST DESCRIPTION:
  1. Send ASCONF chunk bundled with other ASCONF chunk from
     endpoint A to B.
  2. Check A: ASCONF-ACK chunk should be received to response
     both the ASCONF chunks at endpoint A.


NOTE

  None


REFERENCE

  RFC 4960
  5.1.1.  Congestion Control of ASCONF Chunks
    In defining the ASCONF Chunk transfer procedures, it is essential
    that these transfers MUST NOT cause congestion within the network.
    To achieve this, we place these restrictions on the transfer of
    ASCONF Chunks:
    C2)  An ASCONF Chunk may be bundled with any other chunk type
         including other ASCONF Chunks.  If bundled with other ASCONF
         Chunks, the chunks MUST appear in sequential order with respect
         to their Sequence Number.
    C3)  An ASCONF-ACK Chunk may be bundled with any other chunk type
         including other ASCONF-ACK Chunks.  If bundled with other
         ASCONF-ACK Chunks, the chunks MUST appear in sequential order
         with respect to their Sequence Number.