Test IKEv2.EN.R.1.1.4.3: Unrecognized payload types and critical bit is not set Part D: Invalid payload type 255 (BASIC)
To verify an IKEv2 device ignores invalid payload types when the invalid type payload's critical bit is not set.
* [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, 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) | | |<-------------------| CREATE_CHILD_SA request (HDR, SK {N, N+, SA, Ni, TSi, TSr}) | | (Judgement #3) |------------------->| CREATE_CHILD_SA response (HDR, SK {P, N+, SA, Nr, TSi, TSr}) | | (Packet #3) | | V V P: Payload with an invalid payload type N: REKEY_SA N+: USE_TRANSPORT_MODE
Packet #1 See Common Packet #1 Packet #2 See Common Packet #3 Packet #3 See below
Packet #3: CREATE_CHILD_SA request
IPv6 Header All fields are same as Common Packet #13 Payload UDP Header All fields are same as Common Packet #13 Payload IKEv2 Header All fields are same as Common Packet #13 Payload E Payload Next Payload Invalid payload type value Other fields are same as Common Packet #13 Invalid Payload Next Payload 41(N) Critical 0 Reserved 0 Payload Length 4 N Payload All fields are same as Common Packet #13 Payload N Payload All fields are same as Common Packet #13 Payload SA Payload All fields are same as Common Packet #13 Payload Ni, Nr paylaod All fields are same as Common Packet #13 Payload TSi Payload All fields are same as Common Packet #13 Payload TSr Payload All fields are same as Common Packet #13 Payload
Part D: Invalid payload type 255 (BASIC) 19. TN1 starts to negotiate with NUT by sending IKE_SA_INIT request. 20. Observe the messages transmitted on Link A. 21. After reception of IKE_SA_INIT response from the NUT, TN1 transmits an IKE_AUTH request to the NUT. 22. Observe the messages transmitted on Link A. 23. TN1 transmits a CREATE_CHILD_SA request including a payload with invalid payload type to the NUT. The E payload's IKE Header Next Payload field is set to 255 and the invalid payload's critical flag is not set. The request includes a Notify Payload of type REKEY_SA and rekeyed CHILD_SA's SPI value in the SPI field to the NUT. 24. Observe the messages transmitted on Link A.
Part D Step 20: 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 22: 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 24: Judgment #3 The NUT transmits a CREATE_CHILD_SA response including "ENCR_3DES", "AUTH_HMAC_SHA1_96" and "No Extended Sequence Numbers" as proposed algorithms.
* None.