RE: [Seamoby] Minutes for Meeting at IETF 53

"Hemant Chaskar" <hchaskar@hotmail.com> Tue, 16 April 2002 15:07 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 LAA07458 for <seamoby-archive@odin.ietf.org>; Tue, 16 Apr 2002 11:07:01 -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 KAA21259; Tue, 16 Apr 2002 10:57:16 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA21232 for <seamoby@ns.ietf.org>; Tue, 16 Apr 2002 10:57:14 -0400 (EDT)
Received: from hotmail.com (f255.law7.hotmail.com [216.33.236.133]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07190 for <seamoby@ietf.org>; Tue, 16 Apr 2002 10:57:09 -0400 (EDT)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 16 Apr 2002 07:56:42 -0700
Received: from 63.78.179.5 by lw7fd.law7.hotmail.msn.com with HTTP; Tue, 16 Apr 2002 14:56:42 GMT
X-Originating-IP: [63.78.179.5]
From: Hemant Chaskar <hchaskar@hotmail.com>
To: seamoby@ietf.org
Subject: RE: [Seamoby] Minutes for Meeting at IETF 53
Date: Tue, 16 Apr 2002 14:56:42 -0000
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"
Message-ID: <F255Na0yYZdqQGMTM63000060bb@hotmail.com>
X-OriginalArrivalTime: 16 Apr 2002 14:56:42.0730 (UTC) FILETIME=[EBB154A0:01C1E556]
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 Glenn:

See some comments below:


>From: "Glenn Morrow"<gmorrow@nortelnetworks.com>
>To: seamoby@ietf.org
>Subject: RE: [Seamoby] Minutes for Meeting at IETF 53
>Date: Mon, 15 Apr 2002 15:55:47 -0500
>
>Excuse me for not being at the WG meeting due to a conflict but I do have
>some comments on the meeting minutes.
>
>[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.

>
>Even if the NIC can handle multiple technologies what if it can't do the
>multiple technologies simulateneously?

----clip-----------------------
>
>[Non-technical commentary - atheism]
>The end to end thing is always a good thing to think of BUT keep in mind
>that they only reason you do things to the network if to do something the
>hosts can't do or its less expensive to deploy. Nobody ever wants to add
>something to the network if they can avoid it. I just think that this might
>be one of those cases when you can't avoid it. The IP addresses are not L2
>stuff.

[HC] Also, in handoff philosophy in general, access routers do maintain 
state and transfer it from AR to AR, for example context transfer. If that 
is OK with end-to-end principle, then it seems that CARD protocol whose 
operations are confined to ARs (and of course MNs) on the periphery of the 
network should fit in the principle as well.

>
>[Administrative Commentary]
>If the WG just doesn't want to deal with the administrative hassle of 
>making
>network based CAR discovery automatic or zero-conf-like similar to dynamic
>routing, then just say all we want to do is make this configurable at this
>time or spin it off into another WG that does want to agree on a way to
>dynamically convey this information. Also as I recall, the early 
>antagonists
>of dynamic routing also said it wouldn't scale. Gee you could also pawn it
>off on AAA. Whoaa - hot potata - hot patata.
>
>Keep in mind the excuses and needs for dynamic routing are analogous to the
>excuses and needs for dynamic CAR discovery. i.e. sometimes you need it and
>want it and sometimes ya don't.
>
>Hope this helps,
>
>Glenn
>
>[Solve it for routers and the hosts are a breeze]
>p.s. you'll probably bump into the same problem again in the Monet WG where
>the correct thing to do should be pretty blatent.


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.


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