[Dime] Fw: Diameter Prefix Delegation Application
Behcet Sarikaya <behcetsarikaya@yahoo.com> Mon, 16 June 2008 15:40 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 9C5783A682A; Mon, 16 Jun 2008 08:40:21 -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 411523A697C for <dime@core3.amsl.com>; Mon, 16 Jun 2008 08:40:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[AWL=-0.226, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_41=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 xv+Iw6jSSbej for <dime@core3.amsl.com>; Mon, 16 Jun 2008 08:40:19 -0700 (PDT)
Received: from web84303.mail.re1.yahoo.com (web84303.mail.re1.yahoo.com [69.147.74.182]) by core3.amsl.com (Postfix) with SMTP id C113C3A682A for <dime@ietf.org>; Mon, 16 Jun 2008 08:40:18 -0700 (PDT)
Received: (qmail 20443 invoked by uid 60001); 16 Jun 2008 15:40:56 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID; b=q3hGmZ2ABp9IhbBv3+nY1byztyNPyGM3E8+FuokVAIa7lYDQai5MdIAm8w/oAJ2oZsT8AtV7Fy7UjQTrR0TURtAk4k7aznd6SYHsPSYuDsoWXjO26ujbH2shfbKFlTN2DgA2k7u+iKPzgWsZo16tL7ZqmOR1zhzCmLlj6i3edts=;
X-YMail-OSG: 4xBK3isVM1nX6Lrv90jA0.N0mVD1kQIo4Bn6qlSidHCIV3FROoYKg55xr_Xa9g09azkevKhkOYN8iNWB_Y7SZ2qoOGi7dfV3niJzPjCZ2Z5dlbNZsnFMMZ7jPFg-
Received: from [206.16.17.212] by web84303.mail.re1.yahoo.com via HTTP; Mon, 16 Jun 2008 08:40:56 PDT
X-Mailer: YahooMailRC/975.45 YahooMailWebService/0.7.185
Date: Mon, 16 Jun 2008 08:40:56 -0700
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: dime@ietf.org
MIME-Version: 1.0
Message-ID: <300142.18400.qm@web84303.mail.re1.yahoo.com>
Subject: [Dime] Fw: Diameter Prefix Delegation Application
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="===============0752799167=="
Sender: dime-bounces@ietf.org
Errors-To: dime-bounces@ietf.org
forwarding to dime list. ----- Forwarded Message ---- From: Behcet Sarikaya <behcetsarikaya@yahoo.com> To: Glen Zorn <glenzorn@comcast.net> Sent: Monday, June 16, 2008 10:36:49 AM Subject: Re: [Dime] Diameter Prefix Delegation Application Hi Glen, Prefixes are used to subnet a given network. The address assignment comes next based on the prefix. Subneting a network is done by the network administration/management. draft-sarikaya-dime-prefix-delegation-ps suggests that AAA can be used in prefix delegation (from a delegating server to a requesting server) just like AAA is currently being used for address assignment. More details like per-MN prefix use in cellular links are in the draft. Regards, Behcet ----- Original Message ---- From: Glen Zorn <glenzorn@comcast.net> To: Frank Xia <xiayangsong@huawei.com> Cc: SpawnRR@gmx.de; dime@ietf.org; Jouni.korhonen@teliasonera.com Sent: Sunday, June 15, 2008 2:48:15 AM Subject: Re: [Dime] Diameter Prefix Delegation Application Frank Xia [mailto:xiayangsong@huawei.com] writes: > > Hi Frank, > > > > see inline, > > > > On Fri, Jun 13, 2008 at 5:58 PM, Frank Xia <xiayangsong@huawei.com> > wrote: > >> Hi Julien > >> > >> Thank for your comments! > >> > >> Just as IPv4 address management needs not only > >> DHCPv4 solution but also AAA mechanisms, > >> IPv6 prefix management as an extension of > >> address mangement also needs corresponding > >> facilitis. > > > > we already have some facilities. That was the point of my mail. > > Frank=>Diameter Prefix Delegation application is a > complementary not exclusive solution to > the current existing facilitis. It is useful for a variety of > deployment > scenarios which are possible beyond our reasoning imagination. > > Here is my argument, why do we need AAA solution for IPv4 > address management while there is a DHCP method? What do you mean by "IPv4 address management"? It is possible for both RADIUS & Diameter to assign IPv4 addresses to user machines but that is hardly "management" as I understand the term. Are there other capabilities of which I am unaware? ... > A operator wants to renumber it networks( although > this is not a frequent practice). All the subscribers should > replace their old prefixes by new advertised prefixes. Just my point: Diameter is _not_ a general purpose network management protocol & shouldn't become one. > During renumbering time(a couple of hours or days), > old application sessions continue using old IP addresses > while new application sessions begin to use new IP addresses > > The following are some references on renumbering. The question isn't whether renumbering is a problem, it's if Diameter is the right solution to that problem. Just because you have a hammer doesn't mean that everything is a nail :-)... ... _______________________________________________ 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
- Re: [Dime] Diameter Prefix Delegation Application Behcet Sarikaya
- [Dime] Diameter Prefix Delegation Application SpawnRR
- Re: [Dime] Diameter Prefix Delegation Application Glen Zorn
- Re: [Dime] Diameter Prefix Delegation Application Julien Bournelle
- Re: [Dime] Diameter Prefix Delegation Application Frank Xia
- Re: [Dime] Diameter Prefix Delegation Application Frank Xia
- Re: [Dime] Diameter Prefix Delegation Application Julien Bournelle
- Re: [Dime] Diameter Prefix Delegation Application Frank Xia
- Re: [Dime] Diameter Prefix Delegation Application Glen Zorn
- [Dime] Fw: Diameter Prefix Delegation Application Behcet Sarikaya
- Re: [Dime] Diameter Prefix Delegation Application Frank Xia
- Re: [Dime] Diameter Prefix Delegation Application Glen Zorn
- Re: [Dime] Diameter Prefix Delegation Application Behcet Sarikaya
- Re: [Dime] Diameter Prefix Delegation Application Glen Zorn
- Re: [Dime] Diameter Prefix Delegation Application Behcet Sarikaya
- Re: [Dime] Diameter Prefix Delegation Application Julien Bournelle
- Re: [Dime] Diameter Prefix Delegation Application Glen Zorn
- Re: [Dime] Diameter Prefix Delegation Application Frank Xia
- Re: [Dime] Diameter Prefix Delegation Application Behcet Sarikaya
- Re: [Dime] Diameter Prefix Delegation Application Glen Zorn
- Re: [Dime] Diameter Prefix Delegation Application Frank Xia
- Re: [Dime] Diameter Prefix Delegation Application Glen Zorn
- Re: [Dime] Diameter Prefix Delegation Application Behcet Sarikaya
- Re: [Dime] Diameter Prefix Delegation Application Julien Bournelle
- Re: [Dime] Diameter Prefix Delegation Application Glen Zorn
- Re: [Dime] Diameter Prefix Delegation Application Behcet Sarikaya
- Re: [Dime] Diameter Prefix Delegation Application Glen Zorn
- Re: [Dime] Diameter Prefix Delegation Application Behcet Sarikaya
- Re: [Dime] Diameter Prefix Delegation Application Behcet Sarikaya
- Re: [Dime] Diameter Prefix Delegation Application Glen Zorn