IETF Logo Mail Archive

Re: [Dime] Diameter Prefix Delegation Application

"Julien Bournelle" <julien.bournelle@gmail.com> Fri, 13 June 2008 12:29 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 6996D3A676A; Fri, 13 Jun 2008 05:29:06 -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 F369B3A676A for <dime@core3.amsl.com>; Fri, 13 Jun 2008 05:29:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 07F8VbQ35Vf2 for <dime@core3.amsl.com>; Fri, 13 Jun 2008 05:29:04 -0700 (PDT)
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.235]) by core3.amsl.com (Postfix) with ESMTP id CF41C3A63CB for <dime@ietf.org>; Fri, 13 Jun 2008 05:29:03 -0700 (PDT)
Received: by wr-out-0506.google.com with SMTP id 37so2649930wra.17 for <dime@ietf.org>; Fri, 13 Jun 2008 05:29:33 -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=XWxv0gzRXVdrHcj+bamlvjdfARDrjq6cHh4eOS9Cf40=; b=sK48JvWldnpVbeY84cloEO3gGsEBNStntda6NdYE7OL0sz7qKLiR736RCVXq4F7FFv NsvTeikoTfpYPq7orN6/mXn09cKCOD4XZ8AehKFWFnwdOvqcYCtYxL05A5Yh/h9n8ygT YlEpuwcqw4wrOKa2PSDgy4zPOUAd0b5ASdE/E=
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=QoaFva/q0MzD7lrBBC+/7hOnT3q9vTuo91ZUeoPuhhc7+VIDuDFYGsvLRUR+77XRSW KsV/5T0RAOHWPfVLVcHHsvTqHWeBJkAnI9mdCFMqBgvNacXna2En3QiqfYM+v7ctQDrt azHFtiKIA/Vd2G5LC5JYD4X/LSZJJa3tpwbnE=
Received: by 10.100.215.5 with SMTP id n5mr4095492ang.99.1213360173144; Fri, 13 Jun 2008 05:29:33 -0700 (PDT)
Received: by 10.100.211.17 with HTTP; Fri, 13 Jun 2008 05:29:33 -0700 (PDT)
Message-ID: <5e2406980806130529n7b56949dl2cdb58e804d3d640@mail.gmail.com>
Date: Fri, 13 Jun 2008 14:29:33 +0200
From: Julien Bournelle <julien.bournelle@gmail.com>
To: Glen Zorn <glenzorn@comcast.net>
In-Reply-To: <007b01c8cd49$bf65b6c0$3e312440$@net>
MIME-Version: 1.0
Content-Disposition: inline
References: <20080613080846.17720@gmx.net> <007b01c8cd49$bf65b6c0$3e312440$@net>
Cc: SpawnRR@gmx.de, 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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dime-bounces@ietf.org
Errors-To: dime-bounces@ietf.org

hi all,

 I second Glen's comments.

 Moreover, after a quick look to the Problem Statement draft, I think
that for section 4.1 (AR) and section 4.2 you can delegate prefix
during the network access authentication/authorization phase. For NEMO
case, I thought that DHCPv6
or even IKEv2 may be used.

 Regards,

 Julien

On Fri, Jun 13, 2008 at 1:34 PM, Glen Zorn <glenzorn@comcast.net> wrote:
> 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).  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.
>
>>
>> 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
>
_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime

v2.23.0 | Report a Bug | By Email