Test IKEv2.EN.R.1.1.11.5: Unrecognized Notify Message Type Part B: Unrecognized Notify Message Type of status 65535 (BASIC)
To verify an IKEv2 device ignores the unrecognized Notify Message Type in IKE messages.
[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 Response (HDR, SAi1, KEi, Ni, N) | | (Packet #1) | | |------------------->| IKE_AUTH request (HDR, SAi2, KEr, Nr) | | (Judgement #1) | | V V
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 #1 UDP Header All fields are same as Common Packet #1 IKEv2 Header All fields are same as Common Packet #1 SA Payload All fields are same as Common Packet #1 KE Payload All fields are same as Common Packet #1 Ni, Nr paylaod Next Payload 41 (Notify) Other fields are same as Common Packet #1 N Payload Next Payload 0 Critical 0 Reserved 0 Payload Length 8 Procotol ID 0 SPI Size 0 Notify Message Type See each part description.
Part B: Unrecognized Notify Message Type of status 65535 (BASIC) 3. TN starts to negotiate with NUT by sending IKE_SA_INIT request with a Notify payload of unrecognized Notify Message Type value.
4. Observe the messages transmitted on Link A.
Part B Step 4: 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.
* None