Hi,
With IKEv2 EAP authentication, there are 3 identities involved
1) IDi - IKEv2 initiator identity sent in msg-3
2) EAP identity that gateway (IKE2 responder) can request from the
client (IKEv2 initiator)
3) Authenticated EAP identity that third party EAP server provides to
the gateway (IKEv2
On Nov 10, 2009, at 1:40 PM, Amjad Inamdar (amjads) wrote:
Hi,
With IKEv2 EAP authentication, there are 3 identities involved
1) IDi - IKEv2 initiator identity sent in msg-3
2) EAP identity that gateway (IKE2 responder) can request from the
client (IKEv2 initiator)
3) Authenticated EAP identi
Hi Yaov,
Thanks for your reply. Please see my comments inline.
-Original Message-
From: Yoav Nir [mailto:y...@checkpoint.com]
Sent: Tuesday, November 10, 2009 5:29 PM
To: Amjad Inamdar (amjads)
Cc: ipsec@ietf.org
Subject: Re: [IPsec] Clarification on identities involved in IKEv2
EAPauth
The identity types are local policy. We don't want to prohibit particular
types, even if they are uncommon.
--Paul Hoffman, Director
--VPN Consortium
___
IPsec mailing list
IPsec@ietf.org
https://www.ietf.org/mailman/listinfo/ipsec
Hi,
Is there any windows API for IKEV2.If so please send me link.
On Wed, Nov 11, 2009 at 2:24 AM, Paul Hoffman wrote:
> The identity types are local policy. We don't want to prohibit particular
> types, even if they are uncommon.
>
> --Paul Hoffman, Director
> --VPN Consortium
> ___
Have a look at the following Windows 7 IKEv2 HOWTO:
http://wiki.strongswan.org/wiki/strongswan/Windows7
Best regards
Andreas Steffen
shaik abdulla wrote:
> Hi,
> Is there any windows API for IKEV2.If so please send me link.
==
