Re: [Seamoby] Minutes for Meeting at IETF 53

"Eunsoo Shim" <eunsooshim@hotmail.com> Thu, 25 April 2002 04:36 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 AAA17861 for <seamoby-archive@odin.ietf.org>; Thu, 25 Apr 2002 00:36:45 -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 AAA22874; Thu, 25 Apr 2002 00:17: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 AAA22847 for <seamoby@ns.ietf.org>; Thu, 25 Apr 2002 00:17:50 -0400 (EDT)
Received: from hotmail.com (oe73.law4.hotmail.com [216.33.148.169]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17622 for <seamoby@ietf.org>; Thu, 25 Apr 2002 00:17:49 -0400 (EDT)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 24 Apr 2002 21:17:16 -0700
X-Originating-IP: [66.122.105.22]
Reply-To: Eunsoo Shim <eunsoo@ctr.columbia.edu>
From: Eunsoo Shim <eunsooshim@hotmail.com>
To: Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>, James Kempf <kempf@docomolabs-usa.com>, seamoby@ietf.org
References: <A5B4C9A2AD89D411AB3E009027B0DA1E0396C4F3@IL27EXM09.cig.mot.com>
Subject: Re: [Seamoby] Minutes for Meeting at IETF 53
Date: Wed, 24 Apr 2002 21:22:17 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Message-ID: <OE73OlvX6D96doCekp8000006bf@hotmail.com>
X-OriginalArrivalTime: 25 Apr 2002 04:17:16.0983 (UTC) FILETIME=[15A4AC70:01C1EC10]
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

Thanks, Ajoy.
That's helpful.

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


> 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