Re: [HOKEY] Change proposal for ERP-AAK - 1: NAS-IdentifierRedefining
Zhen Cao <zehn.cao@gmail.com> Fri, 14 October 2011 14:11 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 ADF1621F858C for <hokey@ietfa.amsl.com>; Fri, 14 Oct 2011 07:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.079
X-Spam-Level:
X-Spam-Status: No, score=-3.079 tagged_above=-999 required=5 tests=[AWL=0.520, 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 vxSmQfF6YM8w for <hokey@ietfa.amsl.com>; Fri, 14 Oct 2011 07:11:16 -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 0CC7321F8591 for <hokey@ietf.org>; Fri, 14 Oct 2011 07:11:15 -0700 (PDT)
Received: by iabn5 with SMTP id n5so2695963iab.31 for <hokey@ietf.org>; Fri, 14 Oct 2011 07:11:15 -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=f2JQJoXiU6j5Yl3pl+LHUYjvj9vMgeoIEaMgqxKu7Fc=; b=kpCb7xP8e28lVko+D25cRHRiYr+YoBMF0gjY2hXXEhopUsZkRB2LHAA1TXex2vNtqo 6pXtHy5/loMNY5ZlSNEmRK5Hdrc1Mkegkc+bv8reXUI/Pd77PLwH7Njpd+r5YSpD+k4u ypfFZC2lREbnUpI2/s5aUDp1hO2KbJIdNFxdU=
MIME-Version: 1.0
Received: by 10.42.123.212 with SMTP id t20mr16335276icr.12.1318601475633; Fri, 14 Oct 2011 07:11:15 -0700 (PDT)
Received: by 10.42.170.74 with HTTP; Fri, 14 Oct 2011 07:11:15 -0700 (PDT)
In-Reply-To: <A2647DC343AA48C3B7D14B27288FF480@china.huawei.com>
References: <95CC197B44CD4AC99B19D541035AA7E3@china.huawei.com> <4E8C47AF.8060201@gmail.com> <CAProHAR_XfdXUeYWRXPeED4E-eM7baFgv7gDXw-bfmRott=56w@mail.gmail.com> <4E93D32A.8070005@gmail.com> <CAProHASt336kjgsRCkE2X6=hEk_muSn043n-1sQSeYDvPYgSxw@mail.gmail.com> <A2647DC343AA48C3B7D14B27288FF480@china.huawei.com>
Date: Fri, 14 Oct 2011 22:11:15 +0800
Message-ID: <CAProHASz0RboqosEYud1yXUm-xGQCV5o41KXR9YRxRZYtKZN3Q@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: Qin Wu <bill.wu@huawei.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-IdentifierRedefining
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: Fri, 14 Oct 2011 14:11:16 -0000
understand now. From this respect, the new TLV is indeed needed. Thank you for the clarification. On Wed, Oct 12, 2011 at 2:29 PM, Qin Wu <bill.wu@huawei.com> wrote: > This is not a problem. > Since NAI-Identifier defined in RFC2865 is not general either and only used in > Access-Request packet to the RADIUS Server, however in our use case, > we need a TLV for SAP to carry CAP lists to the server that may be in another > domain which is quite different from original usage of NAI-Identifier specified in RFC2865. > Therefore it worth having a new TLV to fix this issue. > > Regards! > -Qin > ----- Original Message ----- > From: "Zhen Cao" <zehn.cao@gmail.com> > To: "Glen Zorn" <glenzorn@gmail.com> > Cc: <hokey@ietf.org> > Sent: Tuesday, October 11, 2011 1:30 PM > Subject: Re: [HOKEY] Change proposal for ERP-AAK - 1: NAS-IdentifierRedefining > > > 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 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