[Dime] Diameter query for mobility anchor resolution
Marco Liebsch <liebsch@nw.neclab.eu> Fri, 10 July 2009 14:59 UTC
Return-Path: <Marco.Liebsch@nw.neclab.eu>
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 E5BA43A6E57 for <dime@core3.amsl.com>; Fri, 10 Jul 2009 07:59:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 jxA2h0-jae-e for <dime@core3.amsl.com>; Fri, 10 Jul 2009 07:59:45 -0700 (PDT)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id D229428C347 for <dime@ietf.org>; Fri, 10 Jul 2009 07:59:07 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id D385C2C02047C for <dime@ietf.org>; Fri, 10 Jul 2009 16:59:35 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MF946vXC2j+U for <dime@ietf.org>; Fri, 10 Jul 2009 16:59:35 +0200 (CEST)
Received: from VENUS.office (mx2.office [192.168.24.15]) by smtp0.neclab.eu (Postfix) with ESMTP id B53A52C0203FF for <dime@ietf.org>; Fri, 10 Jul 2009 16:59:30 +0200 (CEST)
Received: from [10.1.2.175] ([10.1.2.175]) by VENUS.office with Microsoft SMTPSVC(6.0.3790.3959); Fri, 10 Jul 2009 16:59:30 +0200
Message-ID: <4A575744.108@nw.neclab.eu>
Date: Fri, 10 Jul 2009 16:59:16 +0200
From: Marco Liebsch <liebsch@nw.neclab.eu>
User-Agent: Thunderbird 2.0.0.9 (X11/20071115)
MIME-Version: 1.0
To: dime@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Jul 2009 14:59:30.0740 (UTC) FILETIME=[07351F40:01CA016F]
Subject: [Dime] Diameter query for mobility anchor resolution
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/mail-archive/web/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>
X-List-Received-Date: Fri, 10 Jul 2009 14:59:46 -0000
Hello, during last IETF, I got the chance to present an idea about mobility anchor resolution by means of a Diameter Server query (draft-liebsch-dime-pmip6-lmaresolve-00.txt). One use case I referred to was the resolution of mobile nodes' Home Network Prefix into the routable address of its mobility anchor. Such function is needed to coordinate route optimization in Proxy Mobile IPv6 where state information of mobile nodes can be distributed between multiple mobility anchors. During the meeting we discussed also the possibility to add a general query mechanism to Diameter to support such resolution. Regarding the example use case from above, the NetExt WG has been formed now and has route optimization (aka localized routing) on its charter. Two individual drafts for localized routing refer to the need of anchor resolution: http://www.ietf.org/internet-drafts/draft-loureiro-netext-pmipv6-ro-00.txt http://www.ietf.org/internet-drafts/draft-wu-netext-local-ro-02.txt Since DIME is about to update its charter, I'd like to point to the abovementioned topic again, which may be of interest to the group. marco
- [Dime] Diameter query for mobility anchor resolut… Marco Liebsch