Re: [HOKEY] REMINDER: WGLC on draft-ietf-hokey-erp-aak-04

There is some mis-understanding. I am sorry for the ambiguity.

By "inter-realm", it means "inter roaming domain", RFC5296 supports it
and it is also in scope.

I thought it meant "inter-AAA", and RFC5296 does not support that.

Thanks for helping me understand this.

On Thu, Sep 29, 2011 at 11:17 AM, Qin Wu <bill.wu@huawei.com> wrote:
> Hi, Tena and all:
> ----- Original Message -----
> From: "Tina TSOU" <Tina.Tsou.Zouting@huawei.com>
> To: "Glen Zorn" <glenzorn@gmail.com>; "Zhen Cao" <zehn.cao@gmail.com>
> Cc: <hokey@ietf.org>
> Sent: Thursday, September 29, 2011 10:27 AM
> Subject: Re: [HOKEY] REMINDER: WGLC on draft-ietf-hokey-erp-aak-04
>
>
>> Hi Glen et al,
>> Comments are in line...
>>
>>
>> Best Regards,
>> Tina TSOU
>> http://tinatsou.weebly.com/contact.html
>>
>>
>> -----Original Message-----
>> From: hokey-bounces@ietf.org [mailto:hokey-bounces@ietf.org] On Behalf Of Glen Zorn
>> Sent: Tuesday, August 23, 2011 1:12 AM
>> To: Zhen Cao
>> Cc: hokey@ietf.org
>> Subject: Re: [HOKEY] REMINDER: WGLC on draft-ietf-hokey-erp-aak-04
>>
>> On 8/23/2011 12:33 PM, Zhen Cao wrote:
>>
>> ...
>>
>>>> 4) The realm in the keyName-NAI field is used to locate the peer's ERP/AAK
>>>> server
>>>> [Richard] what would happen if the SAP does not know the ERP/AAK server
>>>> indicated by the keyName-NAI
>>
>> Routing of EAP messages (encapsulated, in this case, in Diameter) is
>> always a function of the AAA infrastructure., I think.
>>
>>>
>>> Inter-realm handover is not in scope.
>>
>> Really?  I would think that that would be the only really useful purpose
>> of ERP-AAK...
>> [TT: RFC5296 supports ERP with the home ER server. In that case, one can say RFC5296 supports Inter-realm handover.]
>
> [Qin]: RFC5296 does support ERP with home ER server. This is referred to as Explicit ERP Bootstrapping in RFC5296.
> However comparing between Implicit ERP Bootstrapping with Explicit ERP Bootstrapping, there is not so much benefit to
> use Explicit Bootstrapping. Becos Explicit Bootstrapping needs another additonal round exchange beween home ER server
> and Home EAP sever. In my understanding,Explict Boostrapping is only used when there is no local ER server and rRK
> does not exprire yet.
>
> However if rRK expire, you need to trigger EAP-method exchange to generate a new EMSK to derive a new rRK.
> Becos of this, we proposed to abandon using Explicit bootstapping in RFC5296bis. but that haven't formed consesus yet.
>
> Currently, ERP-AAK still put referenc to old version ERP (RFC5296), therefore I agree what Glen said.
> But as I mentioned in this thread, we need to revise NAI-Identitifer to support inter-realm handover.
>
>
>
>> ...
>> _______________________________________________
>> HOKEY mailing list
>> HOKEY@ietf.org
>> https://www.ietf.org/mailman/listinfo/hokey
>> _______________________________________________
>> HOKEY mailing list
>> HOKEY@ietf.org
>> https://www.ietf.org/mailman/listinfo/hokey
>

-- 
Best regards,
Zhen