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

Qin Wu <bill.wu@huawei.com> Mon, 15 August 2011 03:06 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 74CE921F86C3 for <hokey@ietfa.amsl.com>; Sun, 14 Aug 2011 20:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.65
X-Spam-Level:
X-Spam-Status: No, score=-2.65 tagged_above=-999 required=5 tests=[AWL=-0.593, BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, 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 jRNu00r5nseW for <hokey@ietfa.amsl.com>; Sun, 14 Aug 2011 20:06:25 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 3467121F86BB for <hokey@ietf.org>; Sun, 14 Aug 2011 20:06:25 -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 <0LPY00M2P8NWB8@szxga03-in.huawei.com> for hokey@ietf.org; Mon, 15 Aug 2011 11:07:08 +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 <0LPY00KIZ8MU5L@szxga03-in.huawei.com> for hokey@ietf.org; Mon, 15 Aug 2011 11:07:08 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml203-edg.china.huawei.com) ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ADE36419; Mon, 15 Aug 2011 11:07:08 +0800 (CST)
Received: from SZXEML412-HUB.china.huawei.com (10.82.67.91) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 15 Aug 2011 11:07:06 +0800
Received: from w53375q (10.138.41.130) by szxeml412-hub.china.huawei.com (10.82.67.91) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 15 Aug 2011 11:07:07 +0800
Date: Mon, 15 Aug 2011 11:07:06 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: hokey@ietf.org
Message-id: <E2176179E7EE45108AD07ED086EB6FB6@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: base64
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <00ec01cc58d5$5fc92d80$1f5b8880$@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: Mon, 15 Aug 2011 03:06:26 -0000

Please find below a review from Richard about draft-ietf-hokey-erp-aak-04.
I forwarded this eMail to the Hokey list. If you reply, please maintain
Richard' eMail address in the recipients list.

Regards!
-Qin
-----邮件原件-----
发件人: young [mailto:young@h3c.com] 
发送时间: 2011年8月12日 16:58
收件人: 'Glen Zorn'; 'hokey@ietf.org'
主题: 答复: [HOKEY] REMINDER: WGLC on draft-ietf-hokey-erp-aak-04

Hi, All:

I have read it and have the following comments.
1)  The document also specifies a method by which the SAP may send the
   identities of neighboring attachment points to the peer in the EAP-
   Initiate/Re-auth-Start message. 
[Richard] 
The are two kinds of CAP discovery model:The CAPs could be found by SAP or
by MH.
Why not specify both cases?

2) The peer sends an early-authentication request message (EAP-Initiate/
   Re-auth with the 'E' flag set) containing the keyName-NAI, the NAS-
   Identifier, rIK and sequence number.  
[Richard] 
The question is similar to the first one. It seemed that the text suggests
the CAP list must be offered by the SAP. 
In the real application , It is possible that: The CAP list offered by the
SAP is a reference or Mandatory.
Also, MH could have a CAP list by itself and may refer or use the CAP list
provided by the SAP. 
I suggest the draft would consider such cases and give some descriptions.

3)  This document only discusses the case of distributing the key to a
single CAP.
[Richard] it would let the draft only supports very limited scenarios. In
some cases like unstable Wireless signal, the MH have to rapidly 
Shift among several CAPs. In order to ensure the user experience, it is
possible that AAK is installed on the several 
CAPs before the MH's hand over.  

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

Regards
Richard

-----邮件原件-----
发件人: hokey-bounces@ietf.org [mailto:hokey-bounces@ietf.org] 代表 Glen
Zorn
发送时间: 2011年8月4日 19:31
收件人: hokey@ietf.org
主题: [HOKEY] REMINDER: WGLC on draft-ietf-hokey-erp-aak-04

At the hokey WG session during IETF 81 last week, the beginning of a three
week Working Group Last Call for this document was announced.
However, it appears that no-one mentioned this fact on the mailing list :-(,
so the Last Call will be extended to 25 August.

A URL for this document is
http://www.ietf.org/id/draft-ietf-hokey-erp-aak-04.txt.  Please note that
the draft is only 15 pages long, including boilerplate, so reading it should
not be a major task.  Reply to this message with any comments (including
statements such as "I read it and it's fine").  Thank you.