(racoon 957) Some Questions about development of Racoon2

Hello,
My name is Kohki Ohhira (RICOH Co., Ltd.) in Japan.



We've examined to usage of racoon2.
In addition, we want to use some function which haven't implemented yet 
as below.

If do you have some implementation plans or estimation of below function,
please teach the plans or estimation.


- Digital CA identification
We want to identificate with PSK and Digital Certificate in IKEv2.
Is the implementation of Digital Certificate identification planed 
in racoon2 project? If the plan is exist, please teach estimation of
release timing.


- DPD (Dead peer Detection) function
Perhaps, racoon2 have function of ansering to the DPD message.
Does racoon2 also sends the DPD message?
If racoon2 sends DPD messages, how timing will it send messages?


- EAP based authentication
We want to personal identificate with EAP-based user autnentication in IKEv2.
Is the implementation of EAP based authentication planed in this project?
If the plan is exist, please teach estimation of release timing.


- problem of IPv6 Link Local envirionment
We are trying the experimental communication from racoon2 to Windows Vista
in IPv6 Link-Local environment. But we can't good result of system 
when we initiate from racoon2.
Should we express the Scope ID? If we should, how should we set the Scope ID?


- problem of SA-bundle problem
We were tried the experimental communication between racoon2 and XP 
with SA-bundle in IKEv1. IF we make initiate from Windows XP, 
we can also get a good result. 
However, if we make initiate from racoon2, we will get error messages
as below JPG file.(proto_id_error.JPG)
Is this problem a well-known ?


======================
Additional Information 

We're also tring to communicate with OpenIKEv2.
But we found OpenIKEv2 is not correct initial communication.

A racoon2 and NetNucleus perform correct procedure as below.
sequence No
1	ISAKMP IKE_SA_INIT  Key Exchange
2	ISAKMP IKE_SA_INIT  Key Exchange
3	ISAKMP IKE_AUTH     Identification -I 
4	ISAKMP IKE_AUTH     Identification -R 

However, OpenIKEv2(0.93) performs in correct message order as below.

1	ISAKMP IKE_SA_INIT  Key Exchange
2	ISAKMP IKE_SA_INIT  Key Exchange
3	ISAKMP IKE_AUTH     Notifycation
4	ISAKMP IKE_AUTH     Notifycation

So, if you will try to OpenIKEv2, you should know this problem.


--
 | Kohki Ohhira <[email protected]>
 | Software R&D Group  Ricoh Co., Ltd.