Title


  Test IKEv2.EN.I.1.3.2.1: Retransmission of INFORMATIONAL request
  Part A: (BASIC)

Purpose

  To verify an IKEv2 device properly retransmits INFORMATIONAL request

References

  * [RFC 4306] - Sections 1.1.2, 1.4 and 2.1

Test Setup

  * Network Topology
      Connect the devices according to the Common Topology.
  * Configuration
      In each part, configure the devices according to the Common Configuration. In
      addition, set retransmission timer to 1 second.
  * Pre-Sequence and Cleanup Sequence
      IKEv2 on the NUT is disabled after each part.

Procedure


   NUT                  TN1
(End-Node)           (End-Node)
    |                    |
    |------------------->| IKE_SA_INIT request (HDR, SAi1, KEi, Ni)
    |                    | (Judgement #1)
    |<-------------------| IKE_SA_INIT Response (HDR, SAr1, KEr, Nr)
    |                    | (Packet #1)
    |                    |
    |------------------->| IKE_AUTH request (HDR, SK {IDi, AUTH, N, SAi2, TSi, TSr})
    |                    | (Judgement #2)
    |<-------------------| IKE_AUTH Response (HDR, SK {IDr, AUTH, N, SAr2, TSi, TSr})
    |                    | (Packet #2)
    |                    |
    |                    * wait until receiving liveness check
    |                    |
    |------------------->| INFORMATIONAL request (HDR, SK {})
    |                    | (Judgement #3)
    |                    |
    |                    * wait for the event of a timeout
    |                    |
    |------------------->| INFORMATIONAL request (HDR, SK {})
    |                    | (Judgement #4)
    |                    |
    V                    V


 N: USE_TRANSPORT_MODE

Packet #1 See Common Packet #2

Packet #2 See Common Packet #4

  Part A: (BASIC)
     1. TN1 starts to negotiate with NUT by sending IKE_SA_INIT request.
     2. Observe the messages transmitted on Link B.
     3. After reception of IKE_SA_INIT response from the NUT, TN1 transmits an IKE_AUTH
         request to the NUT.
     4. Observe the messages transmitted on Link B.
     5. TN1 waits for reception of IKE_AUTH response from the NUT.
     6. TN1 waits for reception of INFROMATIONAL request for liveness check from the NUT.
     7. Observe the messages transmitted on Link B.
     8. TN1 waits for the event of a timeout on NUT.
     9. Observe the messages transmitted on Link B.

Observable Result

  Part A
       Step 2: Judgment #1
       The NUT transmits an IKE_SA_INIT response including "ENCR_3DES",
       "PRF_HMAC_SHA1", "AUTH_HMAC_SHA1_96" and "D-H group 2" as accepted
       algorithms.

       Step 4: Judgment #2
       The NUT transmits an IKE_AUTH response including "ENCR_3DES",
       "AUTH_HMAC_SHA1_96" and "No Extended Sequence Numbers" as accepted algorithms.

       Step 7: Judgment #3
       The NUT transmits an INFORMATIONAL request followed by an Encrypted payload with no
       payloads contained in it.

       Step 9: Judgment #4
       The NUT transmits an INFORMATIONAL request followed by an Encrypted payload with no
       payloads contained in it. And the request has the same Message ID value as the Message ID
       value received at Step 7.

Possible Problems

  * Each NUT has the different retransmission timers. If it is imposibble to configure the
    retransmission timer, modifying tester is required.

`Packet #1`	`See Common Packet #2`
`Packet #2`	`See Common Packet #4`