Re: [lisp] Fwd: [rrg] [GROW] Operational experience with cache basedmapping ID

"Tony Li" <tony.li@tony.li> Wed, 19 November 2008 22:05 UTC

Return-Path: <lisp-bounces@ietf.org>
X-Original-To: lisp-archive@ietf.org
Delivered-To: ietfarch-lisp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 460B53A6931; Wed, 19 Nov 2008 14:05:52 -0800 (PST)
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 F3C733A6895 for <lisp@core3.amsl.com>; Wed, 19 Nov 2008 14:05:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 tgVOla4ntJBr for <lisp@core3.amsl.com>; Wed, 19 Nov 2008 14:05:50 -0800 (PST)
Received: from QMTA08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by core3.amsl.com (Postfix) with ESMTP id 189DF3A6931 for <lisp@ietf.org>; Wed, 19 Nov 2008 14:05:48 -0800 (PST)
Received: from OMTA10.westchester.pa.mail.comcast.net ([76.96.62.28]) by QMTA08.westchester.pa.mail.comcast.net with comcast id h6JZ1a0040cZkys58A56L6; Wed, 19 Nov 2008 22:05:06 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA10.westchester.pa.mail.comcast.net with comcast id hA5H1a0095Up7oj3WA5Pzn; Wed, 19 Nov 2008 22:05:41 +0000
X-Authority-Analysis: v=1.0 c=1 a=TVWgmFCExroA:10 a=FNakoZbbzAkA:10 a=dPgqzdiQVlC3C5L0NmEA:9 a=zXbWG3Xgw3vJsnNHNiQA:7 a=Mq1Mhn8XhAi-S4IGNCW-9c9k3BUA:4 a=gJcimI5xSWUA:10
From: Tony Li <tony.li@tony.li>
To: 'Dino Farinacci' <dino@cisco.com>
References: <49245EB4.8080905@cisco.com> <6990CD85-954E-43AD-AFAA-DDA50EEB64AD@cisco.com> <AFF1022D2EA14137AF7057B76D05F436@ad.redback.com> <7B8EA86D-DF59-467B-90F7-32E23969038E@cisco.com> <DD37B0A4BD6346A1A7A77D5103C5430D@ad.redback.com> <6565616F-9AB7-484F-A5F1-C1B2E6D2C07C@cisco.com>
Date: Wed, 19 Nov 2008 16:04:49 -0600
Message-ID: <85D6D346B2CA4954B2A61748A73DF3BA@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <6565616F-9AB7-484F-A5F1-C1B2E6D2C07C@cisco.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Thread-index: AclKi8v81DNIEWE3TW2QA6vM02ZrXAABcW/g
Cc: lisp@ietf.org
Subject: Re: [lisp] Fwd: [rrg] [GROW] Operational experience with cache basedmapping ID
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: lisp-bounces@ietf.org
Errors-To: lisp-bounces@ietf.org

 
Dino,


|Tony, you know how hierarchy works. You follow coarse prefixes as you  
|go up and more specifics as you go down. See draft-meyer-lisp- 
|cons-04.txt for details. And refer to the VA stuff Paul is working on.


I do indeed know how hierarchy works.  I know that a caching element in a
hierarchy that overruns its working set is going to thrash.  I know that you
can only scale if you distribute the work (in this case caching) down the
hierarchy towards the leaves.  I know that redirecting those requests
upwards is simply going to cause the collapse of higher layers. 

I also know that it's trivial to attack caches through a random walk of the
namespace.  I also know that it's trivial to trigger that remotely if there
is any way to get a response to a random incoming source.  

I know that any proposal needs to address these issues, not duck them.


|> Second, there have been numerous alternatives discussed: full map,  
|> DHT, and
|> hybrids.
|
|Right, and I think many of these are misunderstood because they are  
|not brought to the level of detail to find the bugs.


I think that many people are not willing to have the architectural
discussions necessary because they find it more fun to jump into the
architecturally irrelevant details.

Tony

_______________________________________________
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp