IETF Logo Mail Archive

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

Qin Wu <bill.wu@huawei.com> Sat, 08 October 2011 02:26 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 3170921F8B7E for <hokey@ietfa.amsl.com>; Fri, 7 Oct 2011 19:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.624
X-Spam-Level:
X-Spam-Status: No, score=-5.624 tagged_above=-999 required=5 tests=[AWL=0.975, 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 VDt3CbHoMxP2 for <hokey@ietfa.amsl.com>; Fri, 7 Oct 2011 19:26:27 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 8CF8E21F8B74 for <hokey@ietf.org>; Fri, 7 Oct 2011 19:26:27 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSQ00HNW6XGTU@szxga03-in.huawei.com> for hokey@ietf.org; Sat, 08 Oct 2011 10:29:40 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSQ0012D6XGGU@szxga03-in.huawei.com> for hokey@ietf.org; Sat, 08 Oct 2011 10:29:40 +0800 (CST)
Received: from szxeml201-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AEC62444; Sat, 08 Oct 2011 10:29:39 +0800
Received: from SZXEML404-HUB.china.huawei.com (10.82.67.59) by szxeml201-edg.china.huawei.com (172.24.2.39) with Microsoft SMTP Server (TLS) id 14.1.270.1; Sat, 08 Oct 2011 10:29:30 +0800
Received: from w53375q (10.138.41.130) by szxeml404-hub.china.huawei.com (10.82.67.59) with Microsoft SMTP Server (TLS) id 14.1.270.1; Sat, 08 Oct 2011 10:29:29 +0800
Date: Sat, 08 Oct 2011 10:29:28 +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: <4C7AD6701AA9493B80198B8D6EA22E29@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="iso-8859-1"
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> <C0E0A32284495243BDE0AC8A066631A88D856F@szxeml526-mbs.china.huawei.com> <997C5C6550674EBC826DBEBFC533F3D8@china.huawei.com> <CAProHASjNbupHon99kcxwoi7DawHaEKL2bHm4rh-OSb3Bj3C9Q@mail.gmail.com> <4E880C3E.6010101@gmail.com>
Cc: hokey@ietf.org, Tina TSOU <Tina.Tsou.Zouting@huawei.com>
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: Sat, 08 Oct 2011 02:26:28 -0000

Hi,
----- Original Message ----- 
From: "Glen Zorn" <glenzorn@gmail.com>
To: "Zhen Cao" <zehn.cao@gmail.com>
Cc: "Qin Wu" <bill.wu@huawei.com>; "Tina TSOU" <Tina.Tsou.Zouting@huawei.com>; <hokey@ietf.org>
Sent: Sunday, October 02, 2011 3:01 PM
Subject: Re: [HOKEY] REMINDER: WGLC on draft-ietf-hokey-erp-aak-04


> On 9/29/2011 11:00 AM, Zhen Cao wrote:
>> 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.
> 
> I'm not sure what "inter-AAA" means, but more fundamentally I'm not sure
> why what RFC 5296 supports or doesn't support is relevant.  IMHO, either
> ERP-AAK is a new EAP type (which I think it should be) or it's just a
> minor (& not especially useful) enhancement to ERP, in which case it
> should be just rolled into RFC 5296bis.

[Qin]: That's a good question. The initial motivation to put it as a enhancement to ERP
is to reuse ERP architecture to reduce to deploy new functionality, however AAK
apparently addresses the use case described in RFC5836, which is whole different from ERP. 
and deserve having different semantics from ERP.

> ...

v2.23.0 | Report a Bug | By Email