IETF Logo Mail Archive

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

Behcet Sarikaya <behcetsarikaya@yahoo.com> Thu, 17 July 2008 15:01 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 4CED93A686B; Thu, 17 Jul 2008 08:01:56 -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 2522B3A6914 for <dime@core3.amsl.com>; Thu, 17 Jul 2008 08:01:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.264
X-Spam-Level:
X-Spam-Status: No, score=-2.264 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
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 HGAQNtavEmYZ for <dime@core3.amsl.com>; Thu, 17 Jul 2008 08:01:54 -0700 (PDT)
Received: from web84314.mail.re1.yahoo.com (web84314.mail.re1.yahoo.com [69.147.74.193]) by core3.amsl.com (Postfix) with SMTP id C32843A68FF for <dime@ietf.org>; Thu, 17 Jul 2008 08:01:53 -0700 (PDT)
Received: (qmail 1529 invoked by uid 60001); 17 Jul 2008 15:02:25 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=PQ2X2hyCTav4kUt9xNy/c7NZiYHrgdYCtoN/EFG5LoJaiiEPLxCgCWH2IDlFy/v8CTPbKwdg1fWBgTLtRFb4/nJXaP16PS75qPX49d0RYyGXfHonhHDPqnW3AN32ObyXEc618VTUNTmuxRb0t3M5lW9dmiKO7y0OtVLTfg3/EgM=;
Received: from [72.164.184.70] by web84314.mail.re1.yahoo.com via HTTP; Thu, 17 Jul 2008 08:02:24 PDT
X-Mailer: YahooMailRC/975.45 YahooMailWebService/0.7.199
Date: Thu, 17 Jul 2008 08:02:24 -0700
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: Julien Bournelle <julien.bournelle@gmail.com>
MIME-Version: 1.0
Message-ID: <84211.910.qm@web84314.mail.re1.yahoo.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
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
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="===============0724176829=="
Sender: dime-bounces@ietf.org
Errors-To: dime-bounces@ietf.org

Hi Julien,
  The current mechanism was defined with a certain architecture in mind. It simply does not apply to so many new cases that have recently emerged all in mobile networks. We need a new application because of this.
  I would like to explain this in my presentation if I get a slot in Dublin.

Regards,

Behcet


----- Original Message ----
From: Julien Bournelle <julien.bournelle@gmail.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
Cc: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>; dime@ietf.org
Sent: Thursday, July 17, 2008 3:20:53 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

v2.23.0 | Report a Bug | By Email