Test IKEv2.EN.R.1.2.6.5: Receiving Multiple Transform Part C: Multiple Extended Sequecnce Numbers (BASIC)
To verify an IKEv2 device properly handles a CREATE_CHILD_SA request with multiple transform to rekey IKE_SA.
* [RFC 4306] - Sections 2.7, 2.8 and 3.3
* 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) | | (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) | | |<-------------------| CREATE_CHILD_SA request (HDR, SK {SA, Ni}) | | (Packet #3) |------------------->| CREATE_CHILD_SA response (HDR, SK {SA, Nr}) | | (Judgement #3) | | V V
N: USE_TRANSPORT_MODE
Packet #1 See Common Packet #1 Packet #2 See Common Packet #3 Packet #3 See below
From part A to part D, TN1 transmits an IKE_SA_INIT request including a SA payload
which contains the transforms as follows:
IKE_SA_INIT exchanges Algorithms Encryption PRF Integrity D-H Group Part C ENCR_3DES PRF_HMAC_SHA1 AUTH_AES_XCBC_96
AUTH_HMAC_SHA1_96Group 2
* Packet #2: IKE_AUTH request
IPv6 Header Same as the common packet #11 UDP Header Same as the common packet #11 IKEv2 Header Same as the common packet #11 SA Proposals Other fields are same as the common packet #11 SA Proposals See SA Table below Ni, Nr Payload Same as the Common Packet #11
Proposal #1 SA Proposal Next Payload 0 (last) Reserved 0 Proposal Length 44 Proposal # 1 Proposal ID 1 (IKE) SPI Size 0 # of Transforms 5 SA Transform Next Payload 3 (more) Reserved 0 Transform Length 8 Transform Type According to above configuration Reserved 0 Transform ID According to above configuration SA Transform Next Payload 3 (more) Reserved 0 Transform Length 8 Transform Type 1 (ENCR) Reserved 0 Transform ID 3 (3DES) SA Transform Next Payload 3 (more) Reserved 0 Transform Length 8 Transform Type 2 (PRF) Reserved 0 Transform ID 2 (HMAC_SHA1) SA Transform Next Payload 3 (more) Reserved 0 Transform Length 8 Transform Type 3 (INTEG) Reserved 0 Transform ID 2 (HMAC_SHA1_96) SA Transform Next Payload 0 (last) Reserved 0 Transform Length 8 Transform Type 4 (D-H) Reserved 0 Transform ID 2 (1024 MODP Group)
Part C: Multiple Extended Sequecnce Numbers (BASIC) 13. TN1 starts to negotiate with NUT by sending IKE_SA_INIT request. 14. Observe the messages transmitted on Link A. 15. After reception of IKE_SA_INIT response from the NUT, TN1 transmits an IKE_AUTH request to the NUT. 16. Observe the messages transmitted on Link A. 17. TN1 transmits a CREATE_CHILD_SA request including a Notify Payload of type REKEY_SA and rekeyed CHILD_SA's SPI value in the SPI field to the NUT. 18. Observe the messages transmitted on Link A.
Part C Step 14: 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 16: 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 18: Judgment #3 The NUT transmits a CREATE_CHILD_SA response including "ENCR_3DES", "PRF_HMAC_SHA1", "AUTH_HMAC_SHA1_96" and "D-H group 2" as proposed algorithms.
* None.