IETF Logo Mail Archive

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

Qin Wu <bill.wu@huawei.com> Mon, 29 August 2011 08:13 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: hokey@ietfa.amsl.com
Delivered-To: hokey@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0A5121F8584 for <hokey@ietfa.amsl.com>; Mon, 29 Aug 2011 01:13:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.968
X-Spam-Level:
X-Spam-Status: No, score=-4.968 tagged_above=-999 required=5 tests=[AWL=1.631, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n7799AeiV9O8 for <hokey@ietfa.amsl.com>; Mon, 29 Aug 2011 01:13:53 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 24AD021F857D for <hokey@ietf.org>; Mon, 29 Aug 2011 01:13:53 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LQO007MTK8ZF3@szxga04-in.huawei.com> for hokey@ietf.org; Mon, 29 Aug 2011 16:14:59 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LQO00AA0K8ZYT@szxga04-in.huawei.com> for hokey@ietf.org; Mon, 29 Aug 2011 16:14:59 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml208-edg.china.huawei.com) ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ADL84632; Mon, 29 Aug 2011 16:14:59 +0800 (CST)
Received: from SZXEML409-HUB.china.huawei.com (10.82.67.136) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 29 Aug 2011 16:14:56 +0800
Received: from w53375q (10.138.41.130) by szxeml409-hub.china.huawei.com (10.82.67.136) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 29 Aug 2011 16:14:56 +0800
Date: Mon, 29 Aug 2011 16:14:56 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Glen Zorn <glenzorn@gmail.com>, Zhen Cao <zehn.cao@gmail.com>
Message-id: <C94CE4E0D71C4412AE37B1446A7D5857@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <00ec01cc58d5$5fc92d80$1f5b8880$@com> <E2176179E7EE45108AD07ED086EB6FB6@china.huawei.com> <CAProHAR_3wMdn8o4Gbe7YfMogj2JhddfKLmNnxeQ+LSPcVFd7g@mail.gmail.com> <4E5360B6.20605@gmail.com>
Cc: hokey@ietf.org
Subject: Re: [HOKEY] REMINDER: WGLC on draft-ietf-hokey-erp-aak-04
X-BeenThere: hokey@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: HOKEY WG Mailing List <hokey.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hokey>, <mailto:hokey-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hokey>
List-Post: <mailto:hokey@ietf.org>
List-Help: <mailto:hokey-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hokey>, <mailto:hokey-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 08:13:53 -0000

Hi,
----- Original Message ----- 
From: "Glen Zorn" <glenzorn@gmail.com>
To: "Zhen Cao" <zehn.cao@gmail.com>
Cc: "Qin Wu" <bill.wu@huawei.com>om>; <young@h3c.com>om>; <hokey@ietf.org>
Sent: Tuesday, August 23, 2011 4:11 PM
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.

[Qin]: Absolutely.

> 
>> 
>> Inter-realm handover is not in scope.
> 
> Really?  I would think that that would be the only really useful purpose
> of ERP-AAK...

[Qin]: The current version doesn't cover inter-realm handover. But it doesn't mean
ERP-AAK specified in this document can not support inter-realm handover. The problem
to support inter-realm handover in my mind is NAI-Identifier is not global identity.
In some case, CAP or SAP may share the same NAI-Identitifier, in such case, how does 
the AAA distinguish between CAP and SAP with the same NAI-Identifier?
If this document intend to expand scope, this issue should be fixed first.

> ...
>

v2.8.7 | Report a Bug | By Email