RE: [Seamoby] Minutes for Meeting at IETF 53

"Hemant Chaskar" <hchaskar@hotmail.com> Tue, 16 April 2002 21:39 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 RAA23450 for <seamoby-archive@odin.ietf.org>; Tue, 16 Apr 2002 17:39:05 -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 RAA15544; Tue, 16 Apr 2002 17:25:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA15518 for <seamoby@ns.ietf.org>; Tue, 16 Apr 2002 17:25:44 -0400 (EDT)
Received: from hotmail.com (f198.law7.hotmail.com [216.33.237.198]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21893 for <seamoby@ietf.org>; Tue, 16 Apr 2002 17:25:40 -0400 (EDT)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 16 Apr 2002 14:25:13 -0700
Received: from 63.78.179.6 by lw7fd.law7.hotmail.msn.com with HTTP; Tue, 16 Apr 2002 21:25:12 GMT
X-Originating-IP: [63.78.179.6]
From: Hemant Chaskar <hchaskar@hotmail.com>
To: Karim.El-Malki@era.ericsson.se, kempf@docomolabs-usa.com, seamoby@ietf.org
Subject: RE: [Seamoby] Minutes for Meeting at IETF 53
Date: Tue, 16 Apr 2002 21:25:12 +0000
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"
Message-ID: <F1984U1xYrbDJL3VGMd00000b8c@hotmail.com>
X-OriginalArrivalTime: 16 Apr 2002 21:25:13.0009 (UTC) FILETIME=[31B3A210:01C1E58D]
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

Hi Karim:

See at the end of email:


>From: "Karim El-Malki (ERA)" <Karim.El-Malki@era.ericsson.se>
>To: "'James Kempf'" <kempf@docomolabs-usa.com>,   Hemant Chaskar  
><hchaskar@hotmail.com>, seamoby@ietf.org
>Subject: RE: [Seamoby] Minutes for Meeting at IETF 53
>Date: Tue, 16 Apr 2002 20:55:09 +0200
>
>  > > >[The Issue]
>  > > >It seems that the minutes indicate that people have
>  > somehow come to a
>  > > >conclusion that there is no need for access routers to
>  > divulge that
>  > they
>  > > >are
>  > > >geographically adjancent to themselves via the IP
>  > infrastructure. The
>  > > >minutes also seem to indicate that the mobile alone should be the
>  > only way
>  > > >to pass addresses of CARs to source ARs.
>  > > >
>  > > >[Technical Questions]
>  > > >O.K. If this is true then how will a mobile pass this
>  > information to
>  > their
>  > > >source AR if the mobile only has one NIC and that NIC is
>  > only capable
>  > of
>  > > >listening to one media at once?
>  > >
>  > > [HC] I agree that this is a genuine technical problem. What I would
>  > really
>  > > like to understand is whether the above is a relevant case for CAR
>  > discovery
>  > > or we simply neglect it and focus only on two physical interfaces
>  > case. I
>  > > raised this question before, but we have not had much discussion on
>  > it. In
>  > > any case, address translation part of CARD will be required in this
>  > case for
>  > > fast handoff support.
>  > >
>  >
>  > In a single interface handoff situation, Layer 2 typically
>  > delivers the
>  > AP or AR L2 identifier to which the MN will be handed over. This
>  > information is required (by the MIP fast handover algorithms) at the
>  > MN's AR. So the issue is fairly simple: the AR must be able to do
>  > reverse address translation in order that it can contact the
>  > other AR.
>
>This is not really applicable to Mobile-Initiated MIP Fast Handoff.
>In Mobile-initiated we consider the useful case where the MN can recover
>the CAR IP address/es from the L2 trigger. The MN then sends a Proxy
>Router Solicitation (RtSolPr) to its curent AR containing one or more CAR
>IP addresses. This means that the source AR already gets the CAR addresses.
>So we can do without the AR doing translation or discovering geographical
>adjacency. The MN can pass these CAR address/es to the source AR for both
>single and multiple-interface MNs. So I think that the conclusion from the
>meeting is compatible with MIP Fast Handoffs.
>
>/Karim

[HC] I am wondering, if this useful case is genral enough. In other words, 
can MN always get IP addresses from AP beacons (or L2 triggers) without 
having to acquire connectivity with AP. More so, in single NIC case.

Also, could you please say what conclusion you are referring to.

Hemant


_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com


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