NAME

  AsconfAckWithAddSuccess.seq - ASCONF-ACK chunk is received with Success Indication parameter indicating Add IP Address success


PURPOSE

  To check that if ASCONF-ACK chunk is received with Success Indication
  parameter indicating Add IP Address success then the endpoint should
  consider the address part of the existing association.


SYNOPSIS

  ./AsconfAckWithAddSuccess.seq [-tooloption ...] -pkt ./AsconfAckWithAddSuccess.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 date
  in endpoint B such that ASCONF chunk with Add IP Address Parameter
  is sent to endpoint A.


TEST PROCEDURE

  Endpoint A                           Endpoint B                ULP
  (ESTABLISHED)                        (ESTABLISHED)
                                                  <-----    Asconf
                <-----------------      ASCONF
                                        (Add IP Address X)
  ASCONF-ACK    ----------------->
  (Success Indication)
  HEARTBEAT     ----------------->
  (IP Address X)
                <-----------------      HEARTBEAT-ACK
                                        (IP Address X)
  TEST DESCRIPTION:
  1. Sending ASCONF message with Delete IP Address Parameter from
     endpoint B to A.
     Record the message sequence using a signal emulator.
  2. Send ASCONF-ACK message with Success Indication parameter
     indicating Add IP Address success from endpoint A to B.
  3. Check A: Endpoint B should consider the address part of the
     existing association.


NOTE

  None


REFERENCE

  RFC 5061
  4.2.1.  Add IP Address
          0                   1                   2                   3
          0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |        Type = 0xC001          |    Length = Variable          |
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |               ASCONF-Request Correlation ID                   |
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |                       Address Parameter                       |
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     ASCONF-Request Correlation ID: 32 bits
     This is an opaque integer assigned by the sender to identify each
     request parameter.  The receiver of the ASCONF Chunk will copy this
     2-bit value into the ASCONF Response Correlation ID field of the
     ASCONF-ACK response parameter.  The sender of the ASCONF can use this
     same value in the ASCONF-ACK to find which request the response is
     for.  Note that the receiver MUST NOT change this 32-bit value.
     Address Parameter: TLV
     This field contains an IPv4 or IPv6 address parameter as described in
     Section 3.3.2.1 of [RFC4960].  The complete TLV is wrapped within
     this parameter.  It informs the receiver that the address specified
     is to be added to the existing association.  This parameter MUST NOT
     contain a broadcast or multicast address.  If the address 0.0.0.0 or
     ::0 is provided, the source address of the packet MUST be added.