Re: [rrg] IPv4 & IPv6 routing scaling problems

HeinerHummel@aol.com Sun, 14 February 2010 20:10 UTC

Return-Path: <HeinerHummel@aol.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 988263A6870 for <rrg@core3.amsl.com>; Sun, 14 Feb 2010 12:10:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.302
X-Spam-Level:
X-Spam-Status: No, score=-2.302 tagged_above=-999 required=5 tests=[AWL=0.296, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 L4fHynoMGDAE for <rrg@core3.amsl.com>; Sun, 14 Feb 2010 12:10:01 -0800 (PST)
Received: from imr-ma05.mx.aol.com (imr-ma05.mx.aol.com [64.12.100.31]) by core3.amsl.com (Postfix) with ESMTP id 0FF4D28C0FD for <rrg@irtf.org>; Sun, 14 Feb 2010 12:10:00 -0800 (PST)
Received: from imo-ma04.mx.aol.com (imo-ma04.mx.aol.com [64.12.78.139]) by imr-ma05.mx.aol.com (8.14.1/8.14.1) with ESMTP id o1EKBPdS024513; Sun, 14 Feb 2010 15:11:25 -0500
Received: from HeinerHummel@aol.com by imo-ma04.mx.aol.com (mail_out_v42.9.) id 2.bcc.6715fbd9 (45328); Sun, 14 Feb 2010 15:11:21 -0500 (EST)
Received: from magic-m21.mail.aol.com (magic-m21.mail.aol.com [172.20.22.194]) by cia-mc05.mx.aol.com (v127.7) with ESMTP id MAILCIAMC054-b1104b7858e9326; Sun, 14 Feb 2010 15:11:21 -0500
From: HeinerHummel@aol.com
Message-ID: <1fd7b.112816d7.38a9b2e9@aol.com>
Date: Sun, 14 Feb 2010 15:11:21 -0500
To: paul@jakma.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_1fd7b.112816d7.38a9b2e9_boundary"
X-Mailer: 9.0 SE for Windows sub 5021
X-AOL-ORIG-IP: 95.91.134.11
X-AOL-IP: 172.20.22.194
X-AOL-SENDER: HeinerHummel@aol.com
Cc: rrg@irtf.org
Subject: Re: [rrg] IPv4 & IPv6 routing scaling problems
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Feb 2010 20:10:02 -0000

 
In einer eMail vom 14.02.2010 17:00:37 Westeuropäische Normalzeit schreibt  
paul@jakma.org:

Hi,

I've only just stumbled across your TARA stuff, and am  reading 
through your mails. Re "Forget DV!", and double-plus to  that!


Well, then try to convince me while viewing the following:
I was told that an average route  contains about 20 hops. Imagine a  
chessboard like grid however with 10x10 rows and columns instead of 8x8.  Imagine 
each DFZ-router has only 4 neighboring DFZ-routers (which is  certainly less 
than in reality).Imagine the ingress at the upper left corner and  the 
egress at the lower right corner. Then there are (20 over 10) = 20x19x...x11  / 
(1x2x3....x10) = 184 758 shortest paths in-between.
 
Consider that there are more than 10,000 egress DFZ-routers ! 184 756 times 
 10 000 = 1 847 560 000 shortest routes. However there are multitudes  
thereof, if you envisioned (loopfree of course) detours as well! And if you  
envisioned that DFZ routers have more than 4 neighbor nodes (BTW, can  anyone 
provide useful valid figures so that we can discuss density issues and  
aspects?)
 
What a nonsense of algorithm !!! DV is a holy cow from the early  90's!
 
Please convince me, why provisioning and managing all these routes would be 
 reasonable? 
Particularly, when you can do it without!  
 
Heiner