Test IKEv2.EN.I.1.1.3.2: State Synchronization with IKE messages
Part A: (BASIC)
To verify an IKEv2 device synchronizes its state when it receives IKE messages.
* [RFC 4306] - Sections 2.1, 2.2 and 2.4
* 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 #2)
|------------------->| IPSec {Echo Reply}
| | (Judgement #3)
| |
|<-------------------| cryptographically unprotected IKE message
| | (Packet #3)
| |
|<-------------------| IPSec {Echo Request}
| | (Packet #4)
|------------------->| IPSec {Echo Reply}
| | (Judgement #4)
| |
V V
N: USE_TRANSPORT_MODE
| Packet #1 |
See Common Packet #2 |
| Packet #2 |
See Common Packet #4 |
| Packet #3 |
See below |
| Packet #4 |
See Common Packet #20 |
Packet #3: INFORMATIONAL request
| IPv6 Header |
Source Address |
TN1's Global Address on Link A |
| Destination Address |
NUT's Global Address on Link X |
| UDP Header |
Source Port |
500 |
| Destination Port |
500 |
| IKEv2 Header |
IKE_SA Initiator's SPI |
any |
| IKE_SA Responder's SPI |
any |
| Next Payload |
41(N) |
| Major Version |
2 |
| Minor Version |
0 |
| Exchange Type |
37(INFORMATIONAL) |
| X (bits 0-2 of Flags) |
0 |
| I (bit 3 of Flags) |
any |
| V (bit 4 of Flags) |
0 |
| R (bit 5 of Flags) |
0 |
| X (bits 6-7 Flags) |
0 |
| Message ID |
any |
| Length |
any |
| N Payload |
Next Payload |
0 |
| Critical |
0 |
| Reserved |
0 |
| Payload Length |
8 |
| Protocol ID |
3(ESP) |
| SPI Size |
0 |
| Notify Message Type |
11(INVALID_SPI) |
Part A: (BASIC)
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 to NUT.
7. Observe the messages transmitted on Link A.
8. TN1 transmits a cryptographically unprotected INFORMATIONAL request with Notify
payload of type INVALID_ SPI to the NUT.
9. TN1 transmits an Echo Request with IPsec ESP using corresponding algorithms to NUT.
10. 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 Echo Reply with IPsec ESP using corresponding algorithms.
Step 10: Judgment #4
The NUT transmits an Echo Reply with IPsec ESP using corresponding algorithms.
* None.