Title

  Test IKEv2.EN.I.1.3.2.2: Stop of retransmission of INFORMATIONAL request
  Part A: (BASIC)

Purpose

  To verify an IKEv2 device stops retransmission when it receives the corresponding response.

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)
    |                    | (Packet #1)
    |------------------->| IKE_SA_INIT Response (HDR, SAr1, KEr, Nr)
    |                    | (Judgement #1)
    |                    |
    |<-------------------| IKE_AUTH request (HDR, SK {IDi, AUTH, N, SAi2, TSi, TSr})
    |                    | (Packet #2)
    |------------------->| IKE_AUTH Response (HDR, SK {IDr, AUTH, N, SAr2, TSi, TSr})
    |                    | (Judgement #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)
    |<-------------------| INFORMATIONAL response (HDR, SK {})
    |                    | (Packet #3)
    |                    |
    |                    * wait for the event of a timeout
    |                    |
    |--------X           | never send INFORMATIONAL request (HDR, SK {}) 
    |                    | (Judgement #5)
    |                    |
    V                    V


 N: USE_TRANSPORT_MODE

Packet #1	See Common Packet #2
Packet #2	See Common Packet #4
Packet #3	See Common Packet #18

  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 transmits an Echo Request with invalid SPI.
       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.
      10. After reception of an INFORMATIONAL request from the NUT, TN1 responds with an
          INFORMATIONAL response to the NUT.
      11. TN1 waits for the event of a timeout on NUT.
      12. Observe the messages transmitted on Link B.

Observable Result

  Part A
    Step 2: Judgment #1
      The NUT transmits an IKE_SA_INIT request including "ENCR_3DES",
      "PRF_HMAC_SHA1", "AUTH_HMAC_SHA1_96" and "D-H group 2" as proposed
      algorithms.
  
    Step 4: Judgment #2
      The NUT transmits an IKE_AUTH request including "ENCR_3DES",
      "AUTH_HMAC_SHA1_96" and "No Extended Sequence Numbers" as proposed algorithms.
  
    Step 7: Judgment #3
      The NUT transmits an INFORMATIONAL request including a Notify Payload of type
      INVALID_SPI.
  
    Step 9: Judgment #4
      The NUT retransmits an INFORMATIONAL request including a Notify Payload of type
      INVALID_SPI.
  
    Step 12: Judgment #5
      The NUT never retransmits an INFORMATIONAL request including a Notify Payload of
      type INVALID_SPI.

Possible Problems

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