Re: [Seamoby] Minutes for Meeting at IETF 53

"Eunsoo Shim" <eunsooshim@hotmail.com> Sun, 21 April 2002 04:21 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 AAA12523 for <seamoby-archive@odin.ietf.org>; Sun, 21 Apr 2002 00:21:26 -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 AAA28612; Sun, 21 Apr 2002 00:02:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA28579 for <seamoby@optimus.ietf.org>; Sun, 21 Apr 2002 00:02:14 -0400 (EDT)
Received: from hotmail.com (oe18.law4.hotmail.com [216.33.148.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12411 for <seamoby@ietf.org>; Sun, 21 Apr 2002 00:02:13 -0400 (EDT)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 20 Apr 2002 21:01:42 -0700
X-Originating-IP: [211.192.81.212]
Reply-To: Eunsoo Shim <eunsoo@ctr.columbia.edu>
From: Eunsoo Shim <eunsooshim@hotmail.com>
To: James Kempf <kempf@docomolabs-usa.com>, seamoby@ietf.org
References: <795A014AF92DD21182AF0008C7A404320DFBF085@esealnt117> <OE25GMX5qK7QaaC4omk00002592@hotmail.com> <000201c1e763$d05710f0$4c6015ac@T23KEMPF>
Subject: Re: [Seamoby] Minutes for Meeting at IETF 53
Date: Sun, 21 Apr 2002 13:06:46 -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: <OE18o9tjxqxPs68K8rB00003937@hotmail.com>
X-OriginalArrivalTime: 21 Apr 2002 04:01:42.0773 (UTC) FILETIME=[3F288A50:01C1E8E9]
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

James,

Thanks for the information.

Could you tell us, if possible, how the IP address of the target address is
discovered in your experiment with the IS-2000 RAN?
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.
Regards,

Eunsoo

----- Original Message -----
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Eunsoo Shim" <eunsoo@ctr.columbia.edu>; "Karim El-Malki (ERA)"
<Karim.El-Malki@era.ericsson.se>; "'Hemant Chaskar'" <hchaskar@hotmail.com>;
<seamoby@ietf.org>
Sent: Thursday, April 18, 2002 8:08 AM
Subject: Re: [Seamoby] Minutes for Meeting at IETF 53


> > What kind of L2 triggers provide the IP address(es) of the target
> > (candidate) access routers?
> > Would you mind providing some examples?
> > Thanks.
> >
>
> There are no specific examples today of commerial link layers that do
> this, but we have done some experiments involving modifying the IS-2000
> RAN to support triggers. It works extremely well.
>
> Also, it's possible to generate a "trigger" of sorts by forcing handoff
> on certain 802.11 cards that provide to application software the BSSids
> for access points the mobile can hear. The mobile can utilize the BSSid
> to find the FA or AR address, or it can send it to the AR to find the
> address.
>
>             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