Re: [Dime] Rechartering:draft-sarikaya-dimeradext-prefix-auth-ps-00.txt
Frank Xia <xiayangsong@huawei.com> Thu, 17 July 2008 18:23 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 922BE3A6B30; Thu, 17 Jul 2008 11:23:30 -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 9E4813A6B05 for <dime@core3.amsl.com>; Thu, 17 Jul 2008 11:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.322
X-Spam-Level:
X-Spam-Status: No, score=-2.322 tagged_above=-999 required=5 tests=[AWL=0.276, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 17pvkI7Gx5JR for <dime@core3.amsl.com>; Thu, 17 Jul 2008 11:23:28 -0700 (PDT)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by core3.amsl.com (Postfix) with ESMTP id B79F83A68C8 for <dime@ietf.org>; Thu, 17 Jul 2008 11:23:28 -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 <0K45008SPXS0Q9@usaga04-in.huawei.com> for dime@ietf.org; Thu, 17 Jul 2008 13:24:00 -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 <0K4500H92XRZA1@usaga04-in.huawei.com> for dime@ietf.org; Thu, 17 Jul 2008 13:24:00 -0500 (CDT)
Date: Thu, 17 Jul 2008 13:23:59 -0500
From: Frank Xia <xiayangsong@huawei.com>
To: Julien Bournelle <julien.bournelle@gmail.com>
Message-id: <001801c8e83a$48499c30$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> <00de01c8e824$3ddcb400$5c0c7c0a@china.huawei.com> <5e2406980807171108i5850daadk58f58d406b703176@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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: dime-bounces@ietf.org
Errors-To: dime-bounces@ietf.org
Hi Julien IMO, If you are arguing the necessity of the IP renumbering, I think we can stop discussing on the topic of lifetime of prefix, because we have fundamental disagreement on this issue. BR Frank ----- Original Message ----- From: "Julien Bournelle" <julien.bournelle@gmail.com> To: "Frank Xia" <xiayangsong@huawei.com> Cc: <dime@ietf.org>; "Behcet Sarikaya" <sarikaya@ieee.org> Sent: Thursday, July 17, 2008 1:08 PM Subject: Re: [Dime] Rechartering:draft-sarikaya-dimeradext-prefix-auth-ps-00.txt > Hi Frank, > > I think we are little bit looping since I have the impression that we > already had this discussion. However, see my reply inline. > > On Thu, Jul 17, 2008 at 5:45 PM, Frank Xia <xiayangsong@huawei.com> wrote: >> Hi Julien >> >> Let talk about a specific issue which is dealt with in the draft. >> >> Current prefix definition RFC4005 has no lifetime which >> is necessary for IPv6 renumbering. >> There is the same issue with RADIUS (RFC4818). > > Maybe the reason is that the lifetime of the prefix is implicit and > is the same as the lifetime of the network access authorization. > I may be wrong but I don't see why we would do "hard" renumbering. > I mean that if we want to do renumbering there will be a transition period > during which the obsolete and the new prefix will be in place. > > Do you have a specific deployment scenarios in mind ? > > Regards, > > 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
- [Dime] Rechartering: draft-sarikaya-dimeradext-pr… Hannes Tschofenig
- Re: [Dime] Rechartering: draft-sarikaya-dimeradex… Julien Bournelle
- Re: [Dime] Rechartering: draft-sarikaya-dimeradex… Behcet Sarikaya
- Re: [Dime] Rechartering: draft-sarikaya-dimeradex… Julien Bournelle
- Re: [Dime] Rechartering: draft-sarikaya-dimeradex… Behcet Sarikaya
- Re: [Dime] Rechartering:draft-sarikaya-dimeradext… Frank Xia
- Re: [Dime] Rechartering:draft-sarikaya-dimeradext… Frank Xia
- Re: [Dime] Rechartering:draft-sarikaya-dimeradext… Julien Bournelle
- Re: [Dime] Rechartering:draft-sarikaya-dimeradext… Julien Bournelle
- Re: [Dime] Rechartering:draft-sarikaya-dimeradext… Frank Xia
- Re: [Dime] Rechartering:draft-sarikaya-dimeradext… Frank Xia
- Re: [Dime] Rechartering: draft-sarikaya-dimeradex… Glen Zorn
- Re: [Dime] Rechartering: draft-sarikaya-dimeradex… Behcet Sarikaya