Re: [HOKEY] Change proposal for ERP-AAK - 1: NAS-Identifier Redefining
Zhen Cao <zehn.cao@gmail.com> Tue, 11 October 2011 05:30 UTC
Return-Path: <zehn.cao@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 99DB621F8B6E for <hokey@ietfa.amsl.com>;
Mon, 10 Oct 2011 22:30:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.949
X-Spam-Level:
X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[AWL=0.650,
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 jaflfloI-+rB for
<hokey@ietfa.amsl.com>; Mon, 10 Oct 2011 22:30:51 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com
[209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1323F21F8B3A for
<hokey@ietf.org>; Mon, 10 Oct 2011 22:30:51 -0700 (PDT)
Received: by iaby26 with SMTP id y26so10074451iab.31 for <hokey@ietf.org>;
Mon, 10 Oct 2011 22:30:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
bh=FSr2afig9Hl/tZOlmGD/BAX5NGxmiNju6t43OzvO7N8=;
b=P1qLJTVKrfLrnYiiOUCbhbR3qZpuGWh/RsCiib1+j9Sq8JKz7A+VVC1WgmWtsQDV2w
VyC5rbArT51WBWPD+6paaJmiyB8YFgitEohUKWRxws5S3Jmm5eb4IqUxPgL4Y6qULHze
PUqOXv2qytcF5fpp0s9k3w/8jFJBnFaGOHPTQ=
MIME-Version: 1.0
Received: by 10.42.159.1 with SMTP id j1mr22912978icx.20.1318311049370;
Mon, 10 Oct 2011 22:30:49 -0700 (PDT)
Received: by 10.42.170.74 with HTTP; Mon, 10 Oct 2011 22:30:49 -0700 (PDT)
In-Reply-To: <4E93D32A.8070005@gmail.com>
References: <95CC197B44CD4AC99B19D541035AA7E3@china.huawei.com>
<4E8C47AF.8060201@gmail.com>
<CAProHAR_XfdXUeYWRXPeED4E-eM7baFgv7gDXw-bfmRott=56w@mail.gmail.com>
<4E93D32A.8070005@gmail.com>
Date: Tue, 11 Oct 2011 13:30:49 +0800
Message-ID: <CAProHASt336kjgsRCkE2X6=hEk_muSn043n-1sQSeYDvPYgSxw@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: Glen Zorn <glenzorn@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: hokey@ietf.org
Subject: Re: [HOKEY] Change proposal for ERP-AAK - 1: NAS-Identifier Redefining
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, 11 Oct 2011 05:30:51 -0000
CAS-Identity would be a new concept and need Type for the TLV, and it may be not general enough. I am afraid IETF would be conservative to agree with this, given we have way to circumvent. On Tue, Oct 11, 2011 at 1:24 PM, Glen Zorn <glenzorn@gmail.com> wrote: > On 10/9/2011 9:39 AM, Zhen Cao wrote: > >> I think we should be careful adding more semantics to the current >> tools, otherwise it takes longer to converge. > > Sorry, I don't understand. > >> >> How about re-use the NAS-Id and in the string part, make it a >> FQDN-alike way, then that depends on the implementation only. >> >> On Wed, Oct 5, 2011 at 8:03 PM, Glen Zorn <glenzorn@gmail.com> wrote: >>> On 9/29/2011 4:20 PM, Qin Wu wrote: >>> >>>> Hi, >>>> As we discussed on the list to draft-ietf-hokey-erp-aak, NAS Identifier >>>> defined in the section 5.32 of RFC2865 >>>> is not appropriate to be used in the inter-realm hanover case. Since >>>> CAP(s) and/or SAP are not global identifier >>>> and the value they are choosing may conflict with each other, therefore >>>> I propose to redefine NAS-Identifier, >>>> in other words, abandon using NAS-Identifer in the >>>> draft-ietf-hokey-erp-aak-05, instead, replace it with CAP-Identifier >>>> as belows: >>>> >>>> " >>>> >>>> CAP-Identifier: This is carried in a TLV >>>> >>>> payload. The type is TBD. This attribute contains a string >>>> identifying the Candidate Access Points prior to the >>>> >>>> arrival of the MH at the Candidate Access Network (CAN).It is used by >>>> the SAP to advertise the identifier(s) of >>>> >>>> CAP(s) to the peer and EA server. >>>> >>>> " >>> >>> OK, but this needs a format specification (FQDN might be good). >>> >>>> >>>> Regards! >>>> -Qin >>>> >>>> >>>> _______________________________________________ >>>> 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
- [HOKEY] Change proposal for ERP-AAK - 1: NAS-Iden… Qin Wu
- Re: [HOKEY] Change proposal for ERP-AAK - 1: NAS-… Glen Zorn
- Re: [HOKEY] Change proposal for ERP-AAK - 1: NAS-… Qin Wu
- Re: [HOKEY] Change proposal for ERP-AAK - 1: NAS-… Zhen Cao
- Re: [HOKEY] Change proposal for ERP-AAK - 1: NAS-… Zhen Cao
- Re: [HOKEY] Change proposal for ERP-AAK - 1: NAS-… Glen Zorn
- Re: [HOKEY] Change proposal for ERP-AAK - 1: NAS-… Qin Wu
- Re: [HOKEY] Change proposal for ERP-AAK - 1: NAS-… Zhen Cao