RE: [Seamoby] Minutes for Meeting at IETF 53

Singh Ajoy-ASINGH1 <ASINGH1@motorola.com> Sun, 21 April 2002 20:19 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 QAA01226 for <seamoby-archive@odin.ietf.org>; Sun, 21 Apr 2002 16:19:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16719; Sun, 21 Apr 2002 16:10:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16688 for <seamoby@optimus.ietf.org>; Sun, 21 Apr 2002 16:10:54 -0400 (EDT)
Received: from motgate3.mot.com (motgate3.mot.com [144.189.100.103]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01130 for <seamoby@ietf.org>; Sun, 21 Apr 2002 16:10:52 -0400 (EDT)
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate3.mot.com (motgate3 2.1) with ESMTP id MAA00881 for <seamoby@ietf.org>; Sun, 21 Apr 2002 12:59:01 -0700 (MST)]
Received: [from il75exm04.cig.mot.com ([136.182.110.113]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id NAA10054 for <seamoby@ietf.org>; Sun, 21 Apr 2002 13:10:41 -0700 (MST)]
Received: by IL75EXM04 with Internet Mail Service (5.5.2654.52) id <JCDJCNWZ>; Sun, 21 Apr 2002 15:10:41 -0500
Message-ID: <A5B4C9A2AD89D411AB3E009027B0DA1E0396C4F3@IL27EXM09.cig.mot.com>
From: Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>
To: 'Eunsoo Shim' <eunsoo@ctr.columbia.edu>, James Kempf <kempf@docomolabs-usa.com>, seamoby@ietf.org
Subject: RE: [Seamoby] Minutes for Meeting at IETF 53
Date: Sun, 21 Apr 2002 15:10:39 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain; charset="iso-8859-1"
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

Eunsoo/James,

We implemented both source as well as target trigger scenarios 
of Low latency handoff draft. In case of source trigger, the 
Pre-trigger indication at source FA provides the BTS id of the 
target BTS to which MN is moving to. The L2 trigger 
handler at the oFA resolves BTS-ID to obtain the IP address
of the nFA. We used static table to resolve IP address from the 
given BTS-ID. Similarly, in case of target trigger, the 
Pre-trigger indication at nFA provides the BTS-ID of 
the source BTS from which the MN is moving from. The L2 trigger
handler at nFA resolves source BTS-ID to obtain the IP address 
of the source FA. Pre-trigger indication is sent from 
radio network controller to foreign agent as soon 
as link layer handoff is detected based upon power
measurement. Hope this helps. 

regards,
ajoy 


-----Original Message-----
From: Eunsoo Shim [mailto:eunsooshim@hotmail.com]
Sent: Sunday, April 21, 2002 9:29 PM
To: James Kempf; seamoby@ietf.org; Singh Ajoy-ASINGH1
Subject: Re: [Seamoby] Minutes for Meeting at IETF 53


James,

I see. Thanks a lot.

Eunsoo
----- Original Message -----
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Eunsoo Shim" <eunsoo@ctr.columbia.edu>; <seamoby@ietf.org>; "Singh
Ajoy-ASINGH1" <ASINGH1@motorola.com>
Sent: Sunday, April 21, 2002 2:43 AM
Subject: Re: [Seamoby] Minutes for Meeting at IETF 53


> > Could you tell us, if possible, how the IP address of the target
> address is
> > discovered in your experiment with the IS-2000 RAN?
>
> The work on the IS-2000 RAN was done by Motorola, Ajoy Singh was the
> technical lead. I've cc'ed him on this response, perhaps he can describe
> how the L2 triggers were implemented.
>
> > Also how can the mobile utilize the BSSid to find the FA or AR address
> > without asking the current AR in 802.11? Don't we need something like
> the
> > CAR discovery protocol eventually? I assume the mobile does not
> receive the
> > Agent Advertisement messages of the target AR in the above question.
>
> Sure. But for experimental purposes, one can simply statically configure
> the access routers or FAs with the mapping.
>
>             jak
>
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
>

_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby