Re: [RAM] The mapping problem: rendezvous points?

Tony Li <tli@cisco.com> Fri, 18 May 2007 18:40 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hp7NB-00038M-0h; Fri, 18 May 2007 14:40:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hp7N9-00037o-Md for ram@iab.org; Fri, 18 May 2007 14:40:15 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hp7N8-0007Ct-Bt for ram@iab.org; Fri, 18 May 2007 14:40:15 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 18 May 2007 20:40:10 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l4IIe9W5030205; Fri, 18 May 2007 20:40:09 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l4IIduDT009676; Fri, 18 May 2007 18:40:05 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 18 May 2007 20:40:01 +0200
Received: from [192.168.0.101] ([10.61.66.46]) by xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 18 May 2007 20:40:01 +0200
In-Reply-To: <20070518180916.GF69215@Space.Net>
References: <8F47F550-6224-4AFF-8359-CBA98D3F2FAB@muada.com> <271CF87FD652F34DBF877CB0CB5D16FC054EA470@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com> <62AFA8C7-FDD4-4FF2-B609-966081DDC0D1@cisco.com> <B79E458E-F18C-4617-B953-F311E5623E9A@cisco.com> <271CF87FD652F34DBF877CB0CB5D16FC054EA694@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com> <A590D37E-7DEC-4695-998E-DA12A205F306@cisco.com> <271CF87FD652F34DBF877CB0CB5D16FC054EA741@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com> <47DB1548-B91F-47A0-BF62-FACDA9E7706B@cisco.com> <20070518180916.GF69215@Space.Net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <3BD20378-6BEA-409D-A7E0-D170C0DF247D@cisco.com>
Content-Transfer-Encoding: 7bit
From: Tony Li <tli@cisco.com>
Subject: Re: [RAM] The mapping problem: rendezvous points?
Date: Fri, 18 May 2007 11:39:55 -0700
To: Gert Doering <gert@Space.Net>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 18 May 2007 18:40:01.0639 (UTC) FILETIME=[F1941770:01C7997B]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1200; t=1179513609; x=1180377609; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=tli@cisco.com; z=From:=20Tony=20Li=20<tli@cisco.com> |Subject:=20Re=3A=20[RAM]=20The=20mapping=20problem=3A=20rendezvous=20poi nts? |Sender:=20; bh=Q6DJdTb3y4DlX3k3ePsQLbc4lUGA8HmM3wPWdY0rY9k=; b=mtKlEfSvlf4g/IYoaKHsbqKcEb6XsgypVSzDIi7xBcQULAToi9aebulXuT5Xw4g0UDrp2ktp CmYbwFeyM0lS1yg4GLR5fW5rmSCP88JopLPJkD5WikcuLVieYBptcLpN;
Authentication-Results: ams-dkim-1; header.From=tli@cisco.com; dkim=pass (si g from cisco.com/amsdkim1002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: ram@iab.org
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org

On May 18, 2007, at 11:09 AM, Gert Doering wrote:

> The question is "what do you gain by IP (host) mobility"?


I would also consider solving the triangle routing problem as  
beneficial.


> Non-Geeks tend to do web surfing (short-lived), company VPN'ing (will
> reconnect if the local address changes), e-mailing (short-lived,  
> usually
> accompanied by explicit authentication), and maybe voip (would need to
> re-register, and the ongoing call is lost when actively walking around
> with your notebook pressed to your ear).


I would expect that the last point alone should be significant to folks.


> Mobile IPv6 aka "VoIP connections survive roaming about" sounds like
> a good plan for when we have omnipresent IP connectivity without  
> having
> to manually login to all these different access points - but this  
> is some
> distant future, at least over here.  Which is why there might not  
> be so
> much demand...


You can already wander around cities like Mountain View CA with WiFi  
connectivity.  When WiMax deploys, if even 50% of the hype comes  
true, this is going to become more common.  And EVDO is already doing  
this today.

Tony

_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram