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

"Julien Bournelle" <julien.bournelle@gmail.com> Thu, 17 July 2008 18:12 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 40CCD3A6998; Thu, 17 Jul 2008 11:12:26 -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 CAE3F3A6998 for <dime@core3.amsl.com>; Thu, 17 Jul 2008 11:12:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_35=0.6]
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 L44jNFVLKAjD for <dime@core3.amsl.com>; Thu, 17 Jul 2008 11:12:24 -0700 (PDT)
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.225]) by core3.amsl.com (Postfix) with ESMTP id BFCDA3A6903 for <dime@ietf.org>; Thu, 17 Jul 2008 11:12:23 -0700 (PDT)
Received: by wr-out-0506.google.com with SMTP id 37so34014wra.17 for <dime@ietf.org>; Thu, 17 Jul 2008 11:12:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=fE0z+NZC3QV32Ach2ryBtW5a4DJYKRszO2vYuRQFj+Q=; b=b8aFsjf5Gjv7lLGAsaoyyrOluDF+O4xLkFL1JdycDgAkzWrCxG1M/kU30Wkklx0Xq7 2DKmMW8I7/9OLHwURDXzaF9josH5373pHTuFqbTpLlEyY/CV6pMB1YU/5gEZp4t6xXUr 8HKxvj86fgFNLFttP0BIIKCvoAQJwec/p+Ss8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=cVor5Zm0NweuZId4b81fo/uZwq79FB6SThIzmHvM/m4KmCmoGzZUpMh6sf5ayka+++ fEcF0pix82+zroR7tE1mIJE2VzE1bZy1mSI1Lu9EJqBbSdIikavAJgv432OWRmQWJfAH x4lAeaT+A8XJXqKKREdiCmS2W3iJXPcrBkLUU=
Received: by 10.100.197.3 with SMTP id u3mr4538798anf.102.1216318374132; Thu, 17 Jul 2008 11:12:54 -0700 (PDT)
Received: by 10.100.211.17 with HTTP; Thu, 17 Jul 2008 11:12:54 -0700 (PDT)
Message-ID: <5e2406980807171112h132c1b99od94dce56cfec6c86@mail.gmail.com>
Date: Thu, 17 Jul 2008 20:12:54 +0200
From: Julien Bournelle <julien.bournelle@gmail.com>
To: Frank Xia <xiayangsong@huawei.com>
In-Reply-To: <012201c8e82a$1469d610$5c0c7c0a@china.huawei.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <447547.52534.qm@web84306.mail.re1.yahoo.com> <5e2406980807170120m43f3f495veefced2d18df9f84@mail.gmail.com> <012201c8e82a$1469d610$5c0c7c0a@china.huawei.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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dime-bounces@ietf.org
Errors-To: dime-bounces@ietf.org

Hi again,

On Thu, Jul 17, 2008 at 6:27 PM, Frank Xia <xiayangsong@huawei.com> wrote:
> 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.

 For the PMIP6 case, we wrote an I-D:

 http://tools.ietf.org/id/draft-korhonen-dime-pmip6-03.txt

 which hopefully should become a WG item.

 And as you will see, we have some exchange between LMA and AAA but right before
we have some exchanges between MAG and the AAA.

 So even in this case, I wouldn't say that it is only Prefix
Delegation Authorization which
is needed but a whole application to do AAA in the PMIPv6 case.

 Julien


>
>
> 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