Test IKEv2.EN.I.1.1.10.2: Sending CERTREQ Payload
Part A: (ADVANCED)
To verify an IKEv2 device transmits CERTREQ payload and handles CERT payload properly.
[RFC 4306] - Sections 1.2 and 3.7
* 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 |
| Local |
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)
| | (Packet #1)
| |
|------------------->| IKE_AUTH request (HDR, SK {IDi, CERTREQ, AUTH, N, SAi2, TSi, TSr})
| | (Judgement #2)
| |
V V
N+: USE_TRANSPORT_MODE
| Packet #1 |
See Common Packet #2 |
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. TN1 responds with an IKE_SA_INIT response 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 CERTREQ payload which contains 4
(X.509 Certificate - Signature) as Certificate Encoding.
* None