Re: [Seamoby] Minutes for Meeting at IETF 53

"Eunsoo Shim" <eunsooshim@hotmail.com> Thu, 18 April 2002 05: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 BAA18006 for <seamoby-archive@odin.ietf.org>; Thu, 18 Apr 2002 01:21:28 -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 BAA15819; Thu, 18 Apr 2002 01:08:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA15764 for <seamoby@ns.ietf.org>; Thu, 18 Apr 2002 01:08:21 -0400 (EDT)
Received: from hotmail.com (oe22.law4.hotmail.com [216.33.148.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17838 for <seamoby@ietf.org>; Thu, 18 Apr 2002 01:08:18 -0400 (EDT)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 17 Apr 2002 22:07:50 -0700
X-Originating-IP: [211.192.81.212]
Reply-To: Eunsoo Shim <eunsoo@ctr.columbia.edu>
From: Eunsoo Shim <eunsooshim@hotmail.com>
To: Behcet Sarikaya <behcet.sarikaya@alcatel.com>, seamoby@ietf.org
References: <795A014AF92DD21182AF0008C7A404320DFBF085@esealnt117> <OE25GMX5qK7QaaC4omk00002592@hotmail.com> <3CBDE497.4000809@alcatel.com>
Subject: Re: [Seamoby] Minutes for Meeting at IETF 53
Date: Thu, 18 Apr 2002 14:12:54 -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: <OE22qZV7NhGtK25DgRb00000b3d@hotmail.com>
X-OriginalArrivalTime: 18 Apr 2002 05:07:50.0529 (UTC) FILETIME=[FCE2CF10:01C1E696]
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

Hi, Behcet,

Thanks for the information.
My understanding is that the low latency handoff proposal ASSUMES or
REQUIRES that such L2 triggers are available. Then the question would be how
such L2 triggers containing the IP address of the nFA could be generated. I
don't think we have a general solution for the problem yet. So I don't think
we can say "Look! we have L2 triggers that provide the IP address of the
target access router." yet.

I understand the need to design a way to get L2 ID to IP address mapping was
one of the major motivations for the CAR discovery protocol while we know
that the MN can get the L2 ID of the new base station from the L2 beacons.
Actually the CAR discovery protocol could be used to construct the L2
trigger message required/assumed in the draft.

Regards,

Eunsoo
----- Original Message -----
From: "Behcet Sarikaya" <behcet.sarikaya@alcatel.com>
To: <seamoby@ietf.org>
Sent: Wednesday, April 17, 2002 2:09 PM
Subject: Re: [Seamoby] Minutes for Meeting at IETF 53


>
>
> Eunsoo Shim wrote:
>
> >Hi, Karim,
> >
> >What kind of L2 triggers provide the IP address(es) of the target
> >(candidate) access routers?
> >
>
http://ietf.org/internet-drafts/draft-ietf-mobileip-lowlatency-handoffs-v4-0
3.txt
> states that the triggers L2-MT and L2-ST and L2-LU have nFA IP address
> as parameters.
> Hope this helps.
>
> --behcet
>
>
>
>
> _______________________________________________
> 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