Re: [Dime] Diameter Prefix Delegation Application

Frank Xia <xiayangsong@huawei.com> Fri, 13 June 2008 15:42 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 A91433A69AA; Fri, 13 Jun 2008 08:42:14 -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 6FDCE3A69AA for <dime@core3.amsl.com>; Fri, 13 Jun 2008 08:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.332
X-Spam-Level:
X-Spam-Status: No, score=-2.332 tagged_above=-999 required=5 tests=[AWL=0.266, 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 0spkypSyDPDD for <dime@core3.amsl.com>; Fri, 13 Jun 2008 08:42:11 -0700 (PDT)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by core3.amsl.com (Postfix) with ESMTP id 40B8B3A698D for <dime@ietf.org>; Fri, 13 Jun 2008 08:42:11 -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 <0K2E00FFORN5AF@usaga04-in.huawei.com> for dime@ietf.org; Fri, 13 Jun 2008 10:42:42 -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 <0K2E0034NRN3Q8@usaga04-in.huawei.com> for dime@ietf.org; Fri, 13 Jun 2008 10:42:41 -0500 (CDT)
Date: Fri, 13 Jun 2008 10:42:39 -0500
From: Frank Xia <xiayangsong@huawei.com>
To: Glen Zorn <glenzorn@comcast.net>, SpawnRR@gmx.de
Message-id: <002201c8cd6c$1d498a60$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: <20080613080846.17720@gmx.net> <007b01c8cd49$bf65b6c0$3e312440$@net>
Cc: dime@ietf.org, Jouni.korhonen@teliasonera.com
Subject: Re: [Dime] Diameter Prefix Delegation Application
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="utf-8"
Content-Transfer-Encoding: base64
Sender: dime-bounces@ietf.org
Errors-To: dime-bounces@ietf.org

Hi  Glen

Thank for your comments,  and we will consider
your concerns when updating.

As to prefix management, there are two ways in
the industry (3GPP/3GPP2/WiMAX), that is,
DHCP(RFC3633) and AAA.

However, there is not a whole prefix delegation
solution which is supposed to include
allocating/renewing/releasing operation.
Even worse, no current AAA prefix solution
supports  IPv6 renumbering.

So we propose the Diameter prefix manage
application to deal with the problem.

Please aslo refer to my inline reply..

BR
Frank

----- Original Message ----- 
From: "Glen Zorn" <glenzorn@comcast.net>
To: <SpawnRR@gmx.de>
Cc: <dime@ietf.org>; <sarikaya@ieee.org>; <xiayangsong@huawei.com>; 
<Jouni.korhonen@teliasonera.com>
Sent: Friday, June 13, 2008 6:34 AM
Subject: RE: [Dime] Diameter Prefix Delegation Application


SpawnRR@gmx.de writes:

> Hi all,
>
> Is there already a draft regarding a new Diameter Prefix Delegation
> application? Could somebody provide me with some links to related
> drafts, please? I have already read the problem statement draft
> (http://www.ietf.org/internet-drafts/draft-sarikaya-dime-prefix-
> delegation-ps-01.txt) but I couldn't find further information.

Looking over the referenced draft, it seems AFAICT to be an inappropriate 
use of Diameter.  I can't find any evidence of actual AAA usage or even a 
user -- it seems that the author wants to use Diameter just as a transport 
for arbitrary prefixes (I'm certainly willing to be corrected on that point, 
however).
Frank=>The Diameter application also includes allocating/renewing/releasing 
prefix operation.

I'm led to believe this because of the following statement "[RFC4818] 
designs Delegated-IPv6-Prefix attribute which is used for delegating 
prefixes.  However in [RFC4818], the recommended usage scenario is AAA 
server configures the delegating server with some prefixes and then DHCP 
Prefix Delegation [RFC3633] can be used to delegate these prefixes to the 
requesting router.  Also Delegated-IPv6-Prefix carries a number of prefixes 
only.  Lifetime values for each prefix can not be carried."  I can't think 
of a reason, if the delegated prefixes were for a human user, why the 
lifetime of the prefixes would not be just as long as the user session.
Frank=>If the user is always on line  and it is also necessary to
renumber user address because of  resource optimization,
regulation policy and so on, it is better to decouple user's session time
and user's IP address lifetime

>
> The Diameter Prefix Delegation application is a very interesting thing,
> and I’m thinking about to set up a own draft on this topic.
>
> Best regards,
>
>
> Rafael
>
> --
> Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
> Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
> _______________________________________________
> 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