Test IKEv2.EN.I.1.1.10.1: Sending CERT Payload Part A: (ADVANCED)
To verify an IKEv2 device handles CERTREQ payload and transmits CERT payload properly.
[RFC 4306] - Sections 1.2 and 3.8
* Network Topology Connect the devices according to the Common Topology. * Configuration In each part, configure the devices according to the following IKE peer configuration.
Authentication Method Remote X.509 Certificate - Signature
* 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, CERTREQ) | | (Packet #1) | | |------------------->| IKE_AUTH request (HDR, SK {IDi, CERT, AUTH, N, SAi2, TSi, TSr}) | | (Judgement #2) | | V V
N+: USE_TRANSPORT_MODE
Packet #1 See below
Packet #1: IKE_SA_INIT response
IPv6 Header Same as Common Packet #2 UDP Header Same as Common Packet #2 IKEv2 Header Same as Common Packet #2 SA Payload Same as Common Packet #2 KE Payload Same as Common Packet #2 Nr Payload Next Payload 38 (CERTREQ) Other fields are same as the Common Packet #2 CERTREQ Payload See below
CERTREQ Payload Next Payload 0 Critical 0 Reserved 0 Payload Length Any Certificate Encoding 4 (X.509 Certificate - Signature) Certificate Authority Any
Part A: (ADVANCED) 1. NUT starts to negotiate with TN1 by sending IKE_SA_INIT request. 2. Observe the messages transmitted on Link A. 3. After reception of IKE_SA_INIT request from the NUT, TN1 responds with an IKE_SA_INIT response with a CERTREQ payload to the NUT. 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 with a CERT payload which contains 4 (X.509 Certificate - Signature) as Certificate Encoding and the NUT's certificate as Certificate Data.
* None