Subject: [Mip6] [issue50] Identity issue in Home Address auto-configuration by the Mobile Node (from Jari's review)

From: Gerardo <[email-masked]>
Date: Mon, 03 Oct 2005 14:54:23 +0000

New submission from Gerardo <[email-masked]>:

Jari wrote:
>>One potential issue (and this is also an issue in [6]) is
>>that the identity given in EAP-based authentication
>>is not necessarily something that you can tie a long-term
>>home address identity to. For instance, the identity
>>could be a pseudonym (e.g. EAP-SIM), or a privacy NAI (e.g.
>>RFC2486bis). 
>>    

Gerardo:
>I see the issue. I guess the same issue applies to VPN that makes use of
>IKEv2-EAP. How is it handled in that case? Since the AAA server knows
>the long-term identity of the MN, maybe the AAA server may have an
>active role to create the matching between the identity and the HoA.

Jari:
"
Well, there may be AAA ways of communicating this to
the home agent/vpn gateway, such as the use of the
Chargeable-User-Identity attribute, or some IP address
attributes. Some work would be need to study whether
those are sufficient or if something else is needed, and
in case all this would have to be documented somewhere
so that implementors would know what to do.
"

----------
category: Technical
draft: draft-ietf-mip6-bootstrapping-split
messages: 171
nosy: gerardo
priority: Should fix
status: Pending
title: Identity issue in Home Address auto-configuration by the Mobile Node (from Jari's review)

_________________________________________________
Mip6 issue tracker <[email-masked]>
<http://www.mip4.org/issues/tracker/mip6/issue50>
_________________________________________________

_______________________________________________
Mip6 mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/mip6