IETF Logo Mail Archive

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

Glen Zorn <glenzorn@gmail.com> Tue, 30 August 2011 15:32 UTC

Return-Path: <glenzorn@gmail.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 247CD21F8CC0 for <hokey@ietfa.amsl.com>; Tue, 30 Aug 2011 08:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 E0GIKRHz9WDs for <hokey@ietfa.amsl.com>; Tue, 30 Aug 2011 08:32:56 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7965C21F8CBE for <hokey@ietf.org>; Tue, 30 Aug 2011 08:32:56 -0700 (PDT)
Received: by vws12 with SMTP id 12so3594186vws.31 for <hokey@ietf.org>; Tue, 30 Aug 2011 08:34:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=eOanOXoHJSaOwOpbkZmuyFiTv3UxBAuTY1JcOE95CZ8=; b=kdhJrK/aui/0hU0yebxmtmbbQdzfRMfl6sOVJOR0jHppYJKOva+YfnQqkQksDPS/9C 1KcKOstJ+TmgN81ATNbDcfh0ccLUIQIx2a8CCeL4JTEgn6BXmJ2kvl+UIJMaEWR3mHH6 H86Ax/gmPrff8qNxVaHnYLD2546eWKybyVUWY=
Received: by 10.52.23.52 with SMTP id j20mr1607300vdf.24.1314718463718; Tue, 30 Aug 2011 08:34:23 -0700 (PDT)
Received: from [192.168.1.98] (ppp-124-120-231-171.revip2.asianet.co.th [124.120.231.171]) by mx.google.com with ESMTPS id o7sm2157601vcv.34.2011.08.30.08.34.19 (version=SSLv3 cipher=OTHER); Tue, 30 Aug 2011 08:34:22 -0700 (PDT)
Message-ID: <4E5D02F9.6030206@gmail.com>
Date: Tue, 30 Aug 2011 22:34:17 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
References: <00ec01cc58d5$5fc92d80$1f5b8880$@com> <E2176179E7EE45108AD07ED086EB6FB6@china.huawei.com> <CAProHAR_3wMdn8o4Gbe7YfMogj2JhddfKLmNnxeQ+LSPcVFd7g@mail.gmail.com> <4E5360B6.20605@gmail.com> <C94CE4E0D71C4412AE37B1446A7D5857@china.huawei.com> <C0E0A32284495243BDE0AC8A066631A88AA1B9@szxeml526-mbs.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A88AA1B9@szxeml526-mbs.china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "hokey@ietf.org" <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: Tue, 30 Aug 2011 15:32:57 -0000

On 8/30/2011 5:01 AM, Tina TSOU wrote:

...

>>> 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.
> [TT] Qin, may I suggest you to create another I-D to describe this additional issue?

The simplest thing to do, I think, would be to change the NAS-Identifier
to a Diameter name, which are guaranteed to be globally unique.  It
doesn't really seem like a new draft is necessary.

...

v2.8.7 | Report a Bug | By Email