NAME

  ErrorWithChunkUnknown.seq - ERROR chunk is received with Unrecognized Chunk Type to reporting ASCONF Chunk Type did not recognize

PURPOSE

  To check that if ERROR chunk is received to reporting ASCONF Chunk Type
  did not recognize then the endpoint should not send any further ASCONF
  Chunks and MUST stop its T-4 timer.

SYNOPSIS

  ./ErrorWithChunkUnknown.seq [-tooloption ...] -pkt ./ErrorWithChunkUnknown.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 data
  in Endpoint B such that ASCONF message with Add IP Address is sent to
  Endpoint A.

TEST PROCEDURE

  Endpoint A                           Endpoint B                ULP
  (ESTABLISHED)                        (ESTABLISHED)

                                                   <-----    Asconf
                <-----------------      ASCONF
                                        (Add IP Address)
   ERROR        ----------------->
   (Unrecognized Chunk Type)

  TEST DESCRIPTION:

  1. Sending ASCONF message with Add IP Address Parameter from endpoint
     B to A.
     Record the message sequence using a signal emulator.
  2. Send ERROR message with Error Cause Unrecognized Chunk Type reporting
     that it did not recognize the ASCONF Chunk Type from endpoint A to B.
  3. Check A: Endpoint B should not send any further ASCONF Chunks and
     MUST stop its T-4 timer.

NOTE

  None

REFERENCE

  RFC 5061

  5.1.  ASCONF Chunk Procedures

    A8)  If there is no response(s) to specific TLV parameter(s), and no
         failures are indicated, then all request(s) are considered
         successful.

    A9)  If the peer responds to an ASCONF with an ERROR Chunk reporting
         that it did not recognize the ASCONF Chunk Type, the sender of
         the ASCONF MUST NOT send any further ASCONF Chunks and MUST stop
         its T-4 timer.