[Mip4] Clarification for Dynamic HA assignment draft

Pete McCann <mccap@lucent.com> Tue, 05 August 2003 19:35 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25721 for <mip4-archive@odin.ietf.org>; Tue, 5 Aug 2003 15:35:58 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19k7am-0004s2-4X for mip4-archive@odin.ietf.org; Tue, 05 Aug 2003 15:35:32 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h75JZWVu018722 for mip4-archive@odin.ietf.org; Tue, 5 Aug 2003 15:35:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19k7al-0004rt-Us for mip4-web-archive@optimus.ietf.org; Tue, 05 Aug 2003 15:35:31 -0400
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25693 for <mip4-web-archive@ietf.org>; Tue, 5 Aug 2003 15:35:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19k7aH-0004qd-2N; Tue, 05 Aug 2003 15:35:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19k7aG-0004qO-Gy for mip4@optimus.ietf.org; Tue, 05 Aug 2003 15:35:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25666 for <mip4@ietf.org>; Tue, 5 Aug 2003 15:34:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19k7aF-0005Bb-00 for mip4@ietf.org; Tue, 05 Aug 2003 15:34:59 -0400
Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19k7aE-0005BY-00 for mip4@ietf.org; Tue, 05 Aug 2003 15:34:58 -0400
Received: from nwsgpa.ih.lucent.com (h135-1-121-22.lucent.com [135.1.121.22]) by auemail1.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h75JYFU19706; Tue, 5 Aug 2003 14:34:15 -0500 (CDT)
Received: from mccap-1.lucent.com by nwsgpa.ih.lucent.com (8.11.6+Sun/EMS-1.5 sol2) id h75JYEV07637; Tue, 5 Aug 2003 14:34:14 -0500 (CDT)
Received: from [127.0.0.1] (helo=MCCAP-1.lucent.com) by mccap-1.lucent.com with esmtp (Exim 4.04) id HJ5VOW-0000WS-00; Tue, 05 Aug 2003 15:34:08 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <16176.1711.242248.694789@gargle.gargle.HOWL>
Date: Tue, 05 Aug 2003 14:34:07 -0500
From: Pete McCann <mccap@lucent.com>
To: Alpesh <alpesh@cisco.com>
Cc: mkulkarn@cisco.com, kleung@cisco.com, mip4@ietf.org
In-Reply-To: <3F30037C.4090807@cisco.com>
References: <3F30037C.4090807@cisco.com>
X-Mailer: VM 7.14 under 21.5 (beta14) "cassava" XEmacs Lucid
Content-Transfer-Encoding: 7bit
Subject: [Mip4] Clarification for Dynamic HA assignment draft
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi, Alpesh,

I think we should attempt to be compatible with the functionality
specified in the Mobile IPv4 Diameter specification, which is inside
Section 1.4 of draft-ietf-aaa-diameter-mobileip-14.txt:

1.4  Allocation of Home Agent in Foreign Network

   The Diameter Mobile IP application allows a home agent to be
   allocated in a foreign network, as required in [MIPREQ, CDMA2000].
   When a foreign agent detects that the mobile node has a home agent
   address equal to 0.0.0.0 or 255.255.255.255 in the Registration
   Request message, it MUST add a MIP-Feature-Vector AVP with the Home-
   Agent- Requested flag set to one. If the home agent address is equal
   to 255.255.255.255, then the foreign agent also MUST set the Home-
   Address-Allocatable-Only-in-Home-Realm flag equal to one. If the home
   agent address is set to 0.0.0.0, the foreign agent MUST set the Home-
   Address-Allocatable-Only-in-Home-Realm flag equal to zero.

So yes, both values are used to request dynamic home agent, however,
one of them (255.255.255.255) indicates a preference for home realm
based HA while the other (0.0.0.0) represents that the MS doesn't care
whether the HA is in the home or visited realms.

-Pete


Alpesh writes:
 > Pete:
 > 
 > This is regarding your comment/observation in last IETF while Kent
 > was presenting the Dynamica HA assignment framework draft.
 > 
 > Currently, we are proposing to use either 0.0.0.0 or 255.255.255.255
 > as the HA address to indicate dynamic HA assignment. I cross-checked
 > IS-835C and they use these addresses interchangeably.
 > 
 > You mentioned that some other draft is trying to separate the meaning of
 > all zero and all ones. My concern is that, it the meaning is not already 
 > defined,
 > should we rely on that draft? We want to accomodate the 3GPP2 model and
 > since they are using both values to mean dynamic HA assignment, we want to
 > go on that path.
 > 
 > In future, if different meanings get assigned to each value, we can 
 > probably change
 > our draft.
 > 
 > Do you have comments/suggestions??
 > 
 > -a


_______________________________________________
Mip4 mailing list
Mip4@ietf.org
https://www.ietf.org/mailman/listinfo/mip4