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

Tony Li <tli@cisco.com> Wed, 09 May 2007 17:28 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 1HlpxY-0005bT-5Q; Wed, 09 May 2007 13:28:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlpxX-0005Z3-5A for ram@iab.org; Wed, 09 May 2007 13:28:15 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlpxV-0001w4-QW for ram@iab.org; Wed, 09 May 2007 13:28:15 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-4.cisco.com with ESMTP; 09 May 2007 10:28:09 -0700
X-IronPort-AV: i="4.14,510,1170662400"; d="scan'208"; a="58878459:sNHT44645481"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l49HS9Pw023920; Wed, 9 May 2007 10:28:09 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l49HS8Ei009169; Wed, 9 May 2007 17:28:08 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 9 May 2007 10:28:08 -0700
Received: from [192.168.0.100] ([10.21.121.82]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 9 May 2007 10:28:08 -0700
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC054EA741@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
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>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <47DB1548-B91F-47A0-BF62-FACDA9E7706B@cisco.com>
Content-Transfer-Encoding: 7bit
From: Tony Li <tli@cisco.com>
Subject: Re: [RAM] The mapping problem: rendezvous points?
Date: Wed, 09 May 2007 10:28:05 -0700
To: Dave Thaler <dthaler@windows.microsoft.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 09 May 2007 17:28:08.0309 (UTC) FILETIME=[68EA6A50:01C7925F]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2041; t=1178731689; x=1179595689; c=relaxed/simple; s=sjdkim2002; 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=r67/ncOpFJ2fDL3TR3mDEktvpgFexwnx2BdNVQj0wjA=; b=cictAttqJMVqkfIrfDGK7CMKxVFRC9l0NnOsiadm8GL6S5GCX0IOJ2wJdv9a8KxFxU1QNLww 6gMPnYX8tSpdbKST9gKEw/I/gslWElCkqee9E5qFXLmFc3lii4dW7Tod;
Authentication-Results: sj-dkim-2; header.From=tli@cisco.com; dkim=pass (sig from cisco.com/sjdkim2002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
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

Dave,

> Renumbering doesn't incent the host to change.  As I mentioned in the
> Intarea presentation, renumbering requires MANY components to change
> (hosts, firewalls, IDS's, enterprise inventory applications, etc.)


Understood, but perhaps I'm being unclear.  I'm referring to removing  
the *need* to renumber by making site addressing independent of the  
provider.  Specifically, if we do a locator/ID split properly and  
propagate it through the architecture, then filtering mechanisms can  
be done based on identifier and not locator.  Subsequent renumbering  
events then become cheaper.

This is a significant benefit to the site, and thus is a significant  
incentive to the host.

I should also note that this argument holds as long as the loc/ID  
mechanism has any functionality within the site.  If the LISP ITR/ETR  
is anywhere within the site, for example, this is relevant.


> Changing hosts by themselves doesn't solve anything... we learned this
> from IPv6.


Correct.  That's what we're here to fix, in my perspective.  We need  
to change the network architecture and just changing the routing  
plane without a coordinated change from the hosts doesn't do that.


> Mobility incents _some_ hosts to change... but just the ones that are
> mobile.


I heard that something like 60% of all computers being sold today are  
laptops.  Given WiFi, EVDO, WiMax, etc., I would think that the host  
would want to make the best possible use of mobility.  And fixing 60%  
of the systems out there seems like incentive.


> 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.


No argument, but it seems like the suboptimality introduced by the  
triangle routing problem might provide some encouragement to change  
the host.

Tony

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