Re: [IPsec] Clarification on identities involved in IKEv2EAP authentication

Yoav Nir <ynir@checkpoint.com> Wed, 11 November 2009 13:52 UTC

Return-Path: <ynir@checkpoint.com>
X-Original-To: ipsec@core3.amsl.com
Delivered-To: ipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB79028C1B4 for <ipsec@core3.amsl.com>; Wed, 11 Nov 2009 05:52:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZtE7O2UsRB6Q for <ipsec@core3.amsl.com>; Wed, 11 Nov 2009 05:52:43 -0800 (PST)
Received: from dlpdemo.checkpoint.com (dlpdemo.checkpoint.com [194.29.32.54]) by core3.amsl.com (Postfix) with ESMTP id 8124528C1A9 for <ipsec@ietf.org>; Wed, 11 Nov 2009 05:52:42 -0800 (PST)
X-CheckPoint: {4AFABEA1-0-14201DC2-FFFF}
Received: by dlpdemo.checkpoint.com (Postfix, from userid 105) id 6DEE12AC002; Wed, 11 Nov 2009 15:53:06 +0200 (IST)
Received: from michael.checkpoint.com (michael.checkpoint.com [194.29.32.68]) by dlpdemo.checkpoint.com (Postfix) with ESMTP id 3CCFD29C01C; Wed, 11 Nov 2009 15:53:06 +0200 (IST)
X-CheckPoint: {4AFABE9E-0-14201DC2-FFFF}
Received: from il-ex01.ad.checkpoint.com (localhost [127.0.0.1]) by michael.checkpoint.com (8.12.10+Sun/8.12.10) with ESMTP id nABDr5c6006861; Wed, 11 Nov 2009 15:53:05 +0200 (IST)
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Wed, 11 Nov 2009 15:53:08 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: "Srinivasu S R S Dhulipala (srinid)" <srinid@cisco.com>
Date: Wed, 11 Nov 2009 15:53:02 +0200
Thread-Topic: [IPsec] Clarification on identities involved in IKEv2EAP authentication
Thread-Index: Acpi1kw291b4GgRjTrOgPf4P8xKyKA==
Message-ID: <39008D85-3D9B-4B8B-A9FA-C4C91658630E@checkpoint.com>
References: <1CFAB1B15A6C1142BD1FC07D1CA82AB2015F102B@XMB-BGL-417.cisco.com> <4C814C81-70C3-4597-B279-FED18230331C@checkpoint.com> <3A8C969225424C4D8E6BEE65ED8552DA4C446E@XMB-BGL-41C.cisco.com>
In-Reply-To: <3A8C969225424C4D8E6BEE65ED8552DA4C446E@XMB-BGL-41C.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/signed; micalg=sha1; boundary="Apple-Mail-10-467508548"; protocol="application/pkcs7-signature"
MIME-Version: 1.0
Cc: "ipsec@ietf.org" <ipsec@ietf.org>, "Amjad Inamdar \(amjads\)" <amjads@cisco.com>
Subject: Re: [IPsec] Clarification on identities involved in IKEv2EAP authentication
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2009 13:52:43 -0000

On Nov 11, 2009, at 3:39 PM, Srinivasu S R S Dhulipala (srinid) wrote:
> 
>> 2) If not same, what purpose should each of the above identities serve
> 
>   1) mainly used as a hint for the gateway as to which AAA server to
> choose
>   2) It's the AAA server that may request the identity, and it's
> internal to AAA. It doesn't play in IKE
> 
> [SRINI] Does this imply that gateway SHOULD not send EAP identity
> request to the client,
>            we see that one 3rd party IKEv2 client is sending IP address
> as IDi, from which we can't
>            take any hints. Moreover, the same client is expecting an
> EAP-ID request to be sent,
>            else EAP is failing.
>            I've started another thread about why did we demote "SHOULD"
> to "should" if the gateway is
>            Not supposed to send EAP-identity request to the client. I
> think we should promote it back.

The gateway never sends any EAP identity requests at all. If such a request exists, it is sent by the AAA server. The gateway serves only as a pass-through.

For that reason, there is typically no reason for the gateway to inspect the contents of the EAP payload.