Test IKEv2.EN.I.1.1.11.5: Unrecognized Notify Message Type of Status Part A (BASIC)
To verify an IKEv2 device ignores the unrecognized Notify Message Type intended for reporting status.
[RFC 4306] - Sections 3.10.1
* 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, SAr1, KEi, Ni) | | (Judgement #1) |<-------------------| IKE_SA_INIT Response (HDR, SAr1, KEr, Nr, N+) | | (Packet #1) | | |------------------->| IKE_AUTH request (HDR, SK {IDi, CERT, AUTH, N, SAi2, TSi, TSr}) | | (Judgement #2) | | V V
N: USE_TRANSPORT_MODE N+: Notify Payload with unrecognized Notify Message Type
Packet #1 See below
Packet #1: IKE_SA_INIT request
IPv6 Header All fields are same as Common Packet #2 UDP Header All fields are same as Common Packet #2 IKEv2 Header All fields are same as Common Packet #2 SA Payload All fields are same as Common Packet #2 KE Payload All fields are same as Common Packet #2 Ni, Nr paylaod Next Payload 41 (Notify) Other fields are same as Common Packet #2 N Payload Next Payload 0 Critical 0 Reserved 0 Payload Length 8 Procotol ID 0 SPI Size 0 Notify Message Type 65535
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 with a Notify payload of unrecognized Notify Message Type value. 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" as proposed algorithms.
* None