IETF Logo Mail Archive

Re: [Dime] Rechartering:draft-sarikaya-dimeradext-prefix-auth-ps-00.txt

Frank Xia <xiayangsong@huawei.com> Thu, 17 July 2008 16:27 UTC

Return-Path: <dime-bounces@ietf.org>
X-Original-To: dime-archive@megatron.ietf.org
Delivered-To: ietfarch-dime-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 191F03A68C8; Thu, 17 Jul 2008 09:27:33 -0700 (PDT)
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6B6C3A68C8 for <dime@core3.amsl.com>; Thu, 17 Jul 2008 09:27:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.572
X-Spam-Level:
X-Spam-Status: No, score=0.572 tagged_above=-999 required=5 tests=[AWL=-3.020, BAYES_00=-2.599, EXTRA_MPART_TYPE=1, HTML_MESSAGE=0.001, J_CHICKENPOX_35=0.6, MY_CID_AND_ARIAL2=1.46, MY_CID_AND_STYLE=1.54, MY_CID_ARIAL_STYLE=1.58, T_TVD_FW_GRAPHIC_ID1=0.01]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id neViLRCxSJh0 for <dime@core3.amsl.com>; Thu, 17 Jul 2008 09:27:30 -0700 (PDT)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by core3.amsl.com (Postfix) with ESMTP id 63A4C3A68B4 for <dime@ietf.org>; Thu, 17 Jul 2008 09:27:30 -0700 (PDT)
Received: from huawei.com (usaga04-in [172.18.9.16]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K45008QMSEPQ9@usaga04-in.huawei.com> for dime@ietf.org; Thu, 17 Jul 2008 11:28:02 -0500 (CDT)
Received: from X24512z ([10.124.12.92]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0K4500HPTSEOA1@usaga04-in.huawei.com> for dime@ietf.org; Thu, 17 Jul 2008 11:28:01 -0500 (CDT)
Date: Thu, 17 Jul 2008 11:27:59 -0500
From: Frank Xia <xiayangsong@huawei.com>
To: Julien Bournelle <julien.bournelle@gmail.com>, Glen Zorn <glenzorn@comcast.net>
Message-id: <012201c8e82a$1469d610$5c0c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-Priority: 3
X-MSMail-priority: Normal
References: <447547.52534.qm@web84306.mail.re1.yahoo.com> <5e2406980807170120m43f3f495veefced2d18df9f84@mail.gmail.com>
Cc: dime@ietf.org
Subject: Re: [Dime] Rechartering:draft-sarikaya-dimeradext-prefix-auth-ps-00.txt
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1026617752=="
Sender: dime-bounces@ietf.org
Errors-To: dime-bounces@ietf.org

Hi Julien

Julien wrote" We are already able to
 deliver Prefix during network access AAA 
(e.g. NASREQ or EAP Diameter
 Application). And I may be wrong 
but I don't see the need for a specific
application for this."

The solution you refered to is tied to authentication.
In some scenarios, prefix delegation is independent
of  authentication.

The following is a case in in proxy mobile IPv6
1) MN initiates access authentication. 
    MAG (mobile access gateway) is as the authenticator.
2)MAG sends PBU(Proxy Binding Update) 
   to LMA (Local Mobile Anchor). In this message,
   PBU asks for a prefix for the MN
3)LMA uses Diameter for dynamical prefix requesting
4)LMA sends the prefix to the MAG.  



BR
Frank

----- Original Message ----- 
From: "Julien Bournelle" <julien.bournelle@gmail.com>
To: "Behcet Sarikaya" <sarikaya@ieee.org>
Cc: <dime@ietf.org>
Sent: Thursday, July 17, 2008 3:20 AM
Subject: Re: [Dime] Rechartering:draft-sarikaya-dimeradext-prefix-auth-ps-00.txt


> Hi behcet,
> 
> On Wed, Jul 16, 2008 at 5:15 PM, Behcet Sarikaya
> <behcetsarikaya@yahoo.com> wrote:
>> Hi Julien,
>>
>> ----- Original Message ----
>> From: Julien Bournelle <julien.bournelle@gmail.com>
>> To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
>> Cc: dime@ietf.org
>> Sent: Wednesday, July 16, 2008 3:14:15 AM
>> Subject: Re: [Dime] Rechartering:
>> draft-sarikaya-dimeradext-prefix-auth-ps-00.txt
>>
>> Hi,
>>
>> On Tue, Jul 15, 2008 at 8:29 PM, Hannes Tschofenig
>> <Hannes.Tschofenig@gmx.net> wrote:
>>> Document:
>>>
>>> http://www.ietf.org/internet-drafts/draft-sarikaya-dimeradext-prefix-auth-ps-00.txt
>>>
>>> * Who is able to be editor of the document?
>>>
>>> * Who is interested to help the editor with the work on the draft by
>>> co-authoring it?
>>>
>>> * Who is able to provide reviews?
>>>
>>> * Who is unable to actively help with a specific document but supports the
>>> work?
>>>
>>> * Are there concerns regarding this document?
>>
>> As I said previously in the ML. I'm not convinced by this I-D. Basically
>> I don't see the need for a specific Diameter Application for Prefix
>> Delegation.
>>
>> [behcet] The new draft is about Prefix Authorization. Prefix Authorization
>> is well within AAA domain capabilities. Are you saying no to this?
> 
> I don't want to reenter in this discussion since we already did it :)
> 
> I'm not convinced by your Problem Statement. We are already able to
> deliver Prefix during network access AAA (e.g. NASREQ or EAP Diameter
> Application). And I may be wrong but I don't see the need for a specific
> application for this.
> 
> Regards,
> 
> Julien
> 
> 
>>
>> Regards,
>>
>> Behcet
>>
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime
>

_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime

v2.23.0 | Report a Bug | By Email