IETF Logo Mail Archive

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

Eliot Lear <lear@cisco.com> Wed, 09 May 2007 07:16 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 1HlgPb-0005XR-Ij; Wed, 09 May 2007 03:16:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlgPZ-0005XH-On for ram@iab.org; Wed, 09 May 2007 03:16:33 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlgPY-0005Nn-Fs for ram@iab.org; Wed, 09 May 2007 03:16:33 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 09 May 2007 09:16:32 +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 l497GVeV012642; Wed, 9 May 2007 09:16:31 +0200
Received: from adsl-247-5-fixip.tiscali.ch (ams3-vpn-dhcp4517.cisco.com [10.61.81.164]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l497GVlZ017619; Wed, 9 May 2007 07:16:31 GMT
Message-ID: <46417548.4010702@cisco.com>
Date: Wed, 09 May 2007 09:16:24 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
MIME-Version: 1.0
To: Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: [RAM] The mapping problem: rendezvous points?
References: <8F47F550-6224-4AFF-8359-CBA98D3F2FAB@muada.com> <271CF87FD652F34DBF877CB0CB5D16FC054EA470@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com> <62AFA8C7-FDD4-4FF2-B609-966081DDC0D1@cisco.com> <271CF87FD652F34DBF877CB0CB5D16FC054EA593@WIN-MSG-21 <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>
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC054EA741@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=479; t=1178694991; x=1179558991; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20Re=3A=20[RAM]=20The=20mapping=20problem=3A=20rendezvous=20poi nts? |Sender:=20; bh=HFUu59ZvRivGVrIN6kJrkFv/ajN0lw4QGUgBHuAn9Eo=; b=DqeEZKRXmihkWjcFTdGomm/IQytSMiUoGvJkSDIoyLjBldvoYlmNeywaDkVK5keeOJxwzG2d tx2h1NCiwt37nWGgVJU2U75CUWd7l32xqZm2PnGuGn6CogQIDNdzX5Fc;
Authentication-Results: ams-dkim-1; header.From=lear@cisco.com; dkim=pass (s ig from cisco.com/amsdkim1002 verified; );
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: Tony Li <tli@cisco.com>, 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

Dave Thaler wrote:
> Mobility incents _some_ hosts to change... but just the ones that are
> mobile.
> That's why Mobile IPv6 has an easier deployment model than say HIP...
> with MIPv6 someone who changes still gets benefit (with help from a 
> Home Agent) when talking to arbitrary correspondent nodes.  The
> correspondent nodes aren't strongly incented to change, and don't have
> to.
>   

Which may explain why mobility hasn't been IPv6's "killer app".

Eliot

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

v2.23.0 | Report a Bug | By Email