Re: [rrg] IPv4 & IPv6 routing scaling problems

HeinerHummel@aol.com Fri, 12 February 2010 19:53 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 8DDBB28C1E8 for <rrg@core3.amsl.com>; Fri, 12 Feb 2010 11:53:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.962
X-Spam-Level:
X-Spam-Status: No, score=-1.962 tagged_above=-999 required=5 tests=[AWL=0.321, BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_MILLIONSOF=0.315]
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 R4pJ++Lj2wJm for <rrg@core3.amsl.com>; Fri, 12 Feb 2010 11:53:00 -0800 (PST)
Received: from imr-da03.mx.aol.com (imr-da03.mx.aol.com [205.188.105.145]) by core3.amsl.com (Postfix) with ESMTP id 2684B28C1E1 for <rrg@irtf.org>; Fri, 12 Feb 2010 11:53:00 -0800 (PST)
Received: from imo-ma01.mx.aol.com (imo-ma01.mx.aol.com [64.12.78.136]) by imr-da03.mx.aol.com (8.14.1/8.14.1) with ESMTP id o1CJs520032089; Fri, 12 Feb 2010 14:54:06 -0500
Received: from HeinerHummel@aol.com by imo-ma01.mx.aol.com (mail_out_v42.9.) id 9.ce6.514acf6f (34923); Fri, 12 Feb 2010 14:54:01 -0500 (EST)
Received: from magic-m25.mail.aol.com (magic-m25.mail.aol.com [172.20.22.198]) by cia-da03.mx.aol.com (v127.7) with ESMTP id MAILCIADA038-886b4b75b1d8365; Fri, 12 Feb 2010 14:54:00 -0500
From: HeinerHummel@aol.com
Message-ID: <fd46.7b2783b4.38a70bd8@aol.com>
Date: Fri, 12 Feb 2010 14:54:00 -0500
To: jnc@mercury.lcs.mit.edu, rrg@irtf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_fd46.7b2783b4.38a70bd8_boundary"
X-Mailer: 9.0 SE for Windows sub 5021
X-AOL-ORIG-IP: 95.91.134.11
X-AOL-IP: 172.20.22.198
X-AOL-SENDER: HeinerHummel@aol.com
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: Fri, 12 Feb 2010 19:53:01 -0000

 
In einer eMail vom 12.02.2010 16:27:41 Westeuropäische Normalzeit schreibt  
jnc@mercury.lcs.mit.edu:

Well, in  their defense, I can understand people wanting more features from 
 the
routing. Unfortuntely, IMO that basic architecture is not well-suited  to
adding lots of advanced features (all the easy, low-hanging, ones  have
probably already been picked), but changing to a different one is  going to 
be
a horrendous undertaking.





..which is not true. In a previous email I pointed out how little  
BGP-enhancement it takes to advertise TARA-links.
 
With respect to the new issue "growing number of paths":
TARA would even provide millions of additional routes without any  costs:
i.e. detouring routes via nodes that are even more remote from the  
destination,i.e. via nodes towards which the current router would forward the  
(received) BGP-UPDATE message. 
The extended multitude of paths is not a menace, instead it is something  
that can be provisioned for free.
 
Can anyone explain why knowing a huge number of paths should be superior  
than knowing the network topology? Don't say that the network topology would 
be  too big. I have shown many times that a set of different zooms will do.
 
A corner stone of TARA is the computation of consistent topologies for  the 
various zooms (just by knowing the standardized scale ratio). 
_http://www.ietf.org/proceedings/74/slides/grow-6.pdf_ 
(http://www.ietf.org/proceedings/74/slides/grow-6.pdf)   refers to Route Reflectors (and what they cause). I 
do observe: IETF- routing  experts only know to deal with either full mesh 
overlay networks or with  star-overlay networks (e.g.RR).  But not how to 
provide properly skimmed  representative overlay networks of any scale ratio 
in-between:-(
 
Heiner
 
 
 
------------------------------from a previous email on 25th January  
2010-----------------------------
 
 
TARA-goals: 
1)Scalability:
Table size: 64800 entries (1 per geopatch) + 3600 meta-table entries + n  
times 60 entries (in the worst case) with n TARA-routers inside the own  
geopatch
Update churn: tending to zero.
The scalability issue will be eliminated once and forever
2) Multicast to millions of receivers (imagine TVoIP of the opening  
olympique celebration to hundred millions of receivers - admitted, TARA  would be 
the basis, a better than today's MC is needed (and could be  developed), too 
3)Traffic engineering:
Enables all kind of detouring Multipath (not just ECMP) while  
recongizing,any dead-end path.
Enables congestion handling for  all kind of streams, in particular  voice 
and live-TV streams whose transmission rates cannot be  slowed down, based 
on a communication between the congested and the respective  upstream 
neighbor network.(i.e. provides a rearview mirror)
Enables time-of-day routing.
Abolishes loops.Would overcome the TTL-mechanism which appears to be a  
relict from the stone age.
4) Mobility:
Enables  Mobility  solutions without a home agent or rendez-vous  server.
Well scoped ANYWHERE-cast using well-scoped broadcast mechanism (better  
than  flooding)
Hence will certainly enable services which are still unknown today
5) Moore's Law: Will increase the speed of the next hop retrieval by factor 
 20 i.e. enable Moore's law applicability - even in cases where the best 
next hop  is be replaced by some other (e.g. detouring) next hop.
6) Will enable stretch-1 and disable the Istanbul-effect
7) Clean slate:
Will overcome the orthogonality between intra- and inter-domain  routing.
Will overcome the either-or thinking between network-based versus  
user-based
8)Multihoming:
Enables Multihoming (just like all the other proposed solutions)
9) Enables Multi-addressing (IPv4, IPv6 just like LISP, eventually more:  
HIT, names, E164 without enum ?! )
   because the transit router uses the TARA-locator, doesn't look  at the 
other address;
10) Eliminates the IPv4 depletion issue, because of 7): IPv4 must be  
locally unique only. PI or PA? All are PI effectively.
11) Provides a strategy for incremental deployment
 
12) Provides a new realm for working on IP technology in the future.