NAME

  HB_SendToIdleAddr.seq - HEARTBEAT message is sent periodically to an idle active station

PURPOSE

  To check that when a destination transport address is idle for
  a long time then HEARTBEAT message is sent to that address.

SYNOPSIS

  ./HB_SendToIdleAddr.seq [-tooloption ...] -pkt ./HB_SendToIdleAddr.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 A and B such that no DATA or control chunk
  is exchanged between them.

TEST PROCEDURE

  Endpoint A                           Endpoint B                ULP
  (ESTABLISHED)                        (ESTABLISHED)

        No message is exchanged within current
                   Heartbeat period
                <-----------------   HEARTBEAT

  HEARTBEAT-ACK ----------------->

  TEST DESCRIPTION:

  1. From an endpoint in established state, do not send any message to 
     another endpoint within the current Heartbeat period. 
  2. Check A: HEARTBEAT message is sent to its peer.

NOTE

  None

REFERENCE

  RFC 4960

  8.3.  Path Heartbeat

    By default, an SCTP endpoint SHOULD monitor the reachability of the
    idle destination transport address(es) of its peer by sending a
    HEARTBEAT chunk periodically to the destination transport
    address(es).  HEARTBEAT sending MAY begin upon reaching the
    ESTABLISHED state and is discontinued after sending either SHUTDOWN
    or SHUTDOWN-ACK.  A receiver of a HEARTBEAT MUST respond to a
    HEARTBEAT with a HEARTBEAT-ACK after entering the COOKIE-ECHOED state
    (INIT sender) or the ESTABLISHED state (INIT receiver), up until
    reaching the SHUTDOWN-SENT state (SHUTDOWN sender) or the SHUTDOWN-
    ACK-SENT state (SHUTDOWN receiver).