Test IKEv2.EN.I.1.3.4.1: INVALID_SPI Part A (ADVANCED)
To verify an IKEv2 device properly handles ESP packet with invalid SPI.
* [RFC 4306] - Sections 3.10.1
* Network Topology Connect the devices according to the Common Topology. * Configuration In each part, configure the devices according to the Common Configuration. * Pre-Sequence and Cleanup Sequence IKEv2 on the NUT is disabled after each part.
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) | | |<-------------------| IPsec {Echo Request} | | (Packet #3) | | |------------------->| INFORMATIONAL request (HDR, SK {N(INVALID_SPI)}) | | (Packet #3) | | V V
N: USE_TRANSPORT_MODE
Packet #1 See Common Packet #2 Packet #2 See Common Packet #4 Packet #3 See Common Packet #19
This packet has an invalid SPI value
(the properly netotiated value plus 1).
Part A (ADVANCED) 1. NUT starts to negotiate with TN1 by sending IKE_SA_INIT request. 2. Observe the messages transmitted on Link A. 3. TN1 responds with an IKE_SA_INIT response to the NUT. 4. Observe the messages transmitted on Link A. 5. After reception of IKE_AUTH request from the NUT, TN1 responds with an IKE_AUTH response to the NUT 6. TN1 transmits an Echo Request with IPsec ESP using corresponding algorithms. The message's SPI is set to the value of the SPI negotiated in the initial exchange plus 1. 7. Observe the messages transmitted on Link A.
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 with a Notify payload of type INVALID_SPI. The Notify payload includes the SPI value which is transmitted at Step 6.
* None.