Re: [rrg] TARA and voluntary adoption

Robin Whittle <> Sun, 06 December 2009 10:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 964553A6844 for <>; Sun, 6 Dec 2009 02:23:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.538
X-Spam-Status: No, score=-1.538 tagged_above=-999 required=5 tests=[AWL=0.357, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id I4gP7Lu4pDk3 for <>; Sun, 6 Dec 2009 02:23:31 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 6E2D23A6403 for <>; Sun, 6 Dec 2009 02:23:31 -0800 (PST)
Received: from [] ( []) by (Postfix) with ESMTP id 134CC175B09; Sun, 6 Dec 2009 21:23:21 +1100 (EST)
Message-ID: <>
Date: Sun, 06 Dec 2009 21:23:27 +1100
From: Robin Whittle <>
Organization: First Principles
User-Agent: Thunderbird (Windows/20090812)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [rrg] TARA and voluntary adoption
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 06 Dec 2009 10:23:32 -0000

Short version:  Nothing Heiner has written makes me think TARA
                is complete, is suitable for scalable routing or
                could be adopted widely on a voluntary basis.

Hello Heiner,

You wrote:

> Below I have inserted the text of a preceding email you might have read
> already.

OK, you wrote this a day or two ago:

This involves a new addressing scheme and protocols which are not
suitable for voluntary adoption.  There are people on this list who
are interested in discussing such things, but I only discuss those
which could be voluntarily adopted - which means no new addressing
systems or protocols, at least as far as hosts are concerned.

However, I don't see how geographic addressing helps with anything,
how it would work with physically mobile systems, or how you cope
with multiple sites in multi-storey buildings sharing the same
latitude and longitude.

> The hereby proposed location identifiers (or tokens, or names, or
> attributes) are aggregatable like no other scheme and can indeed be used
> to develop a routing architecture which aggregates the internet topology
> such that it contains parts thereof the more reduced (sparsed) the more 
> remote they are.

I don't see how these can be aggregated.  Geographic location has
little or nothing to do with network topology.

> I haven't received any on-list response so far. 

Probably because your proposal is regarded as extremely incomplete
and/or unsuited to the scalable routing problem.

> Since Bill Herrin
> brought up the commercial relation argument people are convinced that
> restrictions due to business relations of the ISPs can only be
> communicated implicitly (i.e. by distance vector technique) and cannot
> be communicated explicitly. Because I think that can be done for sure, I
> think that can be considered later, i.e. is not a non-starter argument
> at all. 
> Instead, routing technology should be addressed in the first place.E.g.
> Hierarchical routing.
> I could imagine that the term hierarchical routing excites every one.
> But I needs to be done properly.
> I have my doubts that both hierarchical routing as well as geo-location
> based routing have ever been discussed adequately. Stretch is not the
> only bad aspect of all the "well-known" and in my opinion wrong
> hierarchical models. I also presented the Istanbul-argument which shows
> how important a "SLIDING hierarchy" is.
> Allegeably "we are thru the geo-location options". Has there anyone ever
> discussed the difference between a big sized flat network and a big
> sized network which shapes a globe ?

None of this makes me think your proposal is complete, suitable for
scalable routing or could be adopted widely on a voluntary basis.

  - Robin