Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers

Dino Farinacci <dino@cisco.com> Tue, 22 September 2009 05:53 UTC

Return-Path: <dino@cisco.com>
X-Original-To: lisp@core3.amsl.com
Delivered-To: lisp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B0A0B3A67B5 for <lisp@core3.amsl.com>; Mon, 21 Sep 2009 22:53:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.503
X-Spam-Level:
X-Spam-Status: No, score=-6.503 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oOdx1MEA0ZHI for <lisp@core3.amsl.com>; Mon, 21 Sep 2009 22:53:39 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id BA92E3A67F3 for <lisp@ietf.org>; Mon, 21 Sep 2009 22:53:39 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEABsDuEqrR7MV/2dsb2JhbAC9K4hQAY8uBYQb
X-IronPort-AV: E=Sophos;i="4.44,429,1249257600"; d="scan'208";a="393344971"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 22 Sep 2009 05:54:41 +0000
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n8M5sgof007263; Mon, 21 Sep 2009 22:54:42 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id n8M5sgFl003704; Tue, 22 Sep 2009 05:54:42 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 21 Sep 2009 22:54:42 -0700
Received: from [192.168.1.2] ([10.21.126.66]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 21 Sep 2009 22:54:42 -0700
Message-Id: <BB865D5F-B644-4557-97E7-24B6D1FC5895@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <4AB84057.4000906@joelhalpern.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 21 Sep 2009 22:54:41 -0700
References: <20090922030534.828906BE631@mercury.lcs.mit.edu> <4AB84057.4000906@joelhalpern.com>
X-Mailer: Apple Mail (2.936)
X-OriginalArrivalTime: 22 Sep 2009 05:54:42.0128 (UTC) FILETIME=[2DD84500:01CA3B49]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1618; t=1253598882; x=1254462882; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[lisp]=20LISP=20Interworking=3A=20=20Pr oxy=20Egress=20Tunnel=20Routers |Sender:=20; bh=x9IkMWawmfjxjGmJXG+vUC/+lsBd+MuyfsiYYEKMRxI=; b=AhIpCxfCVTvPgA3ECh+xdoDRTVVfHBbQ/I2RNtyhI007flzGhqDkk2saNq vdk8zub24/c51/DgEFZdJxpXwogAGITN4Yh4PfPog1XIAEIf+HQpekyvYGx3 9iaAAgB6MGLVkNm/n5rxoOH40UcHd5V+yj4y8WoeyMeJjMrNzRsXs=;
Authentication-Results: sj-dkim-1; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "lisp@ietf.org" <lisp@ietf.org>
Subject: Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lisp>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Sep 2009 05:53:40 -0000

> At least in theory, we get to replace several multi-homed sites,  
> each with their own PI address with a single PITR advertisement for  
> their EID block.
>
> Obviosuly, there is going to be some period of time when folks won't  
> trust the PITRs, etc...  But at least that is a theory which, if I  
> could believe the PITR deployment story, lead towards reduction.

Trust?

I don't have to trust all the routers that are getting this email  
message to you, but I do have to depend on them. On different for PTRs  
or PETRs.

Dino

>
> Yours,
> Joel
>
> Noel Chiappa wrote:
>>    > the PITR advertises in BGP a short prefix for a large block of  
>> EIDs.
>> Right, I forgot about that.
>> The problem with doing that is that if EIDs in that block are  
>> scattered,
>> topologically, you'll wind up with longer paths. TANSTAAFL...  
>> Course, that is
>> only true for traffic from non-LISP sites..
>>    > If it does not do this, then during transition (half of  
>> forever), we
>>    > get an increase in routing table size instead of a decrease.
>> Routing table size is a whole discussion in itself.
>> Even with a certain amount of reduction of splittage, you still  
>> wind up
>> needing to advertize both EIDs _and_ RLOCs, i.e. potentially more  
>> stuff. I'd
>> been hoping to be able to, before long, get to a situation where  
>> parts of the
>> network did not include all of (legacy-addresses, EIDs, RLOCs).
>> 	Noel
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp