Test IKEv2.EN.I.1.1.6.6: Sending Multiple Proposals for CHILD_SA Part A: (ADVANCED)
To verify an IKEv2 device properly transmits IKE_AUTH request with multiple proposals for CHILD_SA.
* [RFC 4306] - Sections 2.7 and 3.3
* Network Topology Connect the devices according to the Common Topology. * Configuration In each part, configure the devices according to the following configuration.
IKE_AUTH exchanges Algorithms Proposal Protocol ID Encryption Integrity ESN Part A Proposal #1 ESP ENCR_3DES AUTH_HMAC_SHA1_96 NoESN Proposal #2 ESP ENCR_AES_CBC AUTH_AES_XCBC_96 ESN
* 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) | | V V N: USE_TRANSPORT_MODE
Packet #1 See Common Packet #2
Part A: (ADVANCED) 1. TN1 starts to negotiate with NUT by sending IKE_SA_INIT request. 2. Observe the messages transmitted on Link A. 3. After reception of IKE_SA_INIT response from the NUT, TN1 transmits an IKE_AUTH request including a SA payload as described above to the NUT. 4. 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" in SA Proposal #1 (ESP) and then "ENCR_AES_CBC", "AUTH_AES_XCBC_96" and "Extended Sequence Numbers" in SA Proposal #2 (ESP) as accepted algorithms.
* None.