Re: [Mip4] RFC3344biz Dynamic HoA bug ?

Bjorn Andersson <bjorn@iki.fi> Thu, 25 March 2004 07:28 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06657 for <mip4-archive@odin.ietf.org>; Thu, 25 Mar 2004 02:28:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6PHh-000496-Mx for mip4-archive@odin.ietf.org; Thu, 25 Mar 2004 02:28:14 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2P7SDcQ015931 for mip4-archive@odin.ietf.org; Thu, 25 Mar 2004 02:28:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6PHg-00048s-2u for mip4-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 02:28:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06541 for <mip4-web-archive@ietf.org>; Thu, 25 Mar 2004 02:28:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B6PHc-00073C-00 for mip4-web-archive@ietf.org; Thu, 25 Mar 2004 02:28:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B6PFK-0006ZG-00 for mip4-web-archive@ietf.org; Thu, 25 Mar 2004 02:25:49 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1B6PCh-0005yM-00 for mip4-web-archive@ietf.org; Thu, 25 Mar 2004 02:23:03 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1B6PCi-00070K-J5 for mip4-web-archive@ietf.org; Thu, 25 Mar 2004 02:23:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6PCg-00025v-Em; Thu, 25 Mar 2004 02:23:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6PCc-00024G-DO for mip4@optimus.ietf.org; Thu, 25 Mar 2004 02:22:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05679 for <mip4@ietf.org>; Thu, 25 Mar 2004 02:22:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B6PCY-0005wP-00 for mip4@ietf.org; Thu, 25 Mar 2004 02:22:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B6PAf-0005Vy-00 for mip4@ietf.org; Thu, 25 Mar 2004 02:20:58 -0500
Received: from fep01-0.kolumbus.fi ([193.229.0.41] helo=fep01-app.kolumbus.fi) by ietf-mx with esmtp (Exim 4.12) id 1B6P8y-000577-00 for mip4@ietf.org; Thu, 25 Mar 2004 02:19:12 -0500
Received: from yin.bjorns.net ([212.246.227.197]) by fep01-app.kolumbus.fi with ESMTP id <20040325071912.DHRO4029.fep01-app.kolumbus.fi@yin.bjorns.net>; Thu, 25 Mar 2004 09:19:12 +0200
Received: from bjorn by yin.bjorns.net with local (Exim 3.35 #1 (Debian)) id 1B6P9W-000568-00; Thu, 25 Mar 2004 09:19:46 +0200
Date: Thu, 25 Mar 2004 09:19:46 +0200
From: Bjorn Andersson <bjorn@iki.fi>
To: O'Neill Alan <A.ONeill@flarion.com>
Cc: mip4@ietf.org
Subject: Re: [Mip4] RFC3344biz Dynamic HoA bug ?
Message-ID: <20040325071946.GA19418@yin.bjorns.net>
References: <F4410B91C6CC314F9582B1A8E91DC92852B9EF@ftmail2000>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <F4410B91C6CC314F9582B1A8E91DC92852B9EF@ftmail2000>
Sender: mip4-admin@ietf.org
Errors-To: mip4-admin@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

On Wed, Mar 24 2004, at 21:03:26 -0500, O'Neill Alan wrote:
> A MN places 0.0.0.0 into the Home Address field of the RREQ to trigger
> assignment by the Home Agent. The address allocation lifetime is assumed to
> be the MIP binding lifetime because no other information exists, and
> permanent allocations are of course not good. However, what then happens when
> the MN returns home ?

This has been discussed before on this list and I think that this is
really a problem that we should solve before we have n proprietery
solutions. Good that you brought up the discussion again! There
have been at least two drafts that have been addressing this
problem. Without any further digging I found these:
- draft-glass-mobileip-agent-dhcp-proxy
- draft-thuel-mobileip-tt

> The MN cancels the binding, and according to the spec ceases to use MIP
> signaling. However, if the address lifetime is tied to the binding lifetime
> then the MN just lost its address. I assume this might not have been spotted
> before because we are mostly focusing on cellular systems where the MN has a
> virtual home network, and hence cannot ever get home, but given the scope of
> RFC3344 this 'hole', if people concur, needs to be filled. The following
> options spring to mind.

I have been focusing on non-cellular systems for a number of years and
come across this problem several times in real deployment scenarios. So
far this can only be solved with proprietery solutions and I really
support standardizing a solution. Something along the lines with your
proposed HALG/HALR sounds reasonable. I think this is the way to go.

  Bjorn

-- 
Bjorn Andersson <bjorn@iki.fi>
PGP id 5AFC144B

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/