Test IKEv2.EN.R.1.1.4.5: Invalid Order Payloads Part A: (BASIC)
To verify an IKEv2 device properly handles IKE message with invalid order payloads.
* [RFC 4306] - Sections 2.5
* 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, Ni, KEi) | | (Packet #1) |---------X | IKE_SA_INIT response (HDR, SAr1, KEr, Nr) | | (Judgement #1) | | V V
Packet #1 See Common Packet #1
KEi payload and Ni payload replace each other.
Part A (BASIC) 1. TN starts to negotiate with NUT by sending IKE_SA_INIT request. 2. Observe the messages transmitted on Link A.
Part A Step 2: Judgment #1 The NUT never transmits an IKE_SA_INIT response including "ENCR_3DES", "PRF_HMAC_SHA1", "AUTH_HMAC_SHA1_96" and "D-H group 2" as accepted algorithms.
* None.