Re: [rrg] Constraints due to the need for widespread voluntary adoption

HeinerHummel@aol.com Tue, 01 December 2009 11:44 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 60C7F3A6819 for <rrg@core3.amsl.com>; Tue, 1 Dec 2009 03:44:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.059
X-Spam-Level:
X-Spam-Status: No, score=-2.059 tagged_above=-999 required=5 tests=[AWL=0.224, 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 lvHHlb8VA0Qn for <rrg@core3.amsl.com>; Tue, 1 Dec 2009 03:43:59 -0800 (PST)
Received: from imr-da05.mx.aol.com (imr-da05.mx.aol.com [205.188.105.147]) by core3.amsl.com (Postfix) with ESMTP id 662AD3A681C for <rrg@irtf.org>; Tue, 1 Dec 2009 03:43:59 -0800 (PST)
Received: from imo-da02.mx.aol.com (imo-da02.mx.aol.com [205.188.169.200]) by imr-da05.mx.aol.com (8.14.1/8.14.1) with ESMTP id nB1Bha8e008323; Tue, 1 Dec 2009 06:43:36 -0500
Received: from HeinerHummel@aol.com by imo-da02.mx.aol.com (mail_out_v42.5.) id o.c43.552818ce (29678); Tue, 1 Dec 2009 06:43:34 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <c43.552818ce.38465b66@aol.com>
Date: Tue, 01 Dec 2009 06:43:34 -0500
To: pfrejborg@gmail.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1259667814"
X-Mailer: 9.0 SE for Windows sub 5021
X-AOL-SENDER: HeinerHummel@aol.com
Cc: rrg@irtf.org, rw@firstpr.com.au
Subject: Re: [rrg] Constraints due to the need for widespread voluntary adoption
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: Tue, 01 Dec 2009 11:44:00 -0000

In einer eMail vom 01.12.2009 11:54:32 Westeuropäische Normalzeit schreibt  
pfrejborg@gmail.com:

On Tue,  Dec 1, 2009 at 11:42 AM,  <HeinerHummel@aol.com> wrote:
>  Your (and other's) future routing architecture depends heavily on the
>  continued existence of non-IP / telephone network architecture. You  
mention
> millions (billions ?) of mobile handsets and are afraid of  their 
prefixes.
> All I hear is mapping, mapping, mapping: enum-mapping,  RLOC-mapping...
>
Heiner,

I have taken another approach, going  after the flat address structure
and introducing a hierarchy level on top  of the old one. No mapping is
needed.
Well, a routable namespace (as is used by TARA) could be the base for even  
time-of-day routing.
Look, TV-multicast with millions of receivers e.g. multicasting a soccer  
final for 90 minutes would bring immense traffic load, which needs to be  
well-balanced.
 
Today in Sueddeutsche Zeitung an article about smart grid powerline network 
 mentions that Cisco sees a 100 times bigger network here to come compared 
with  the internet. But so far, the reaction wrt TARA's abolishing the  
scalability problem even if it were 1000 times bigger was that the task is  only 
to reduce the problem.
 
 
Patte wrote: 
And I share your concern about having a mapping  database for routing
information - guess it would be the main target in a  cyberwar
situation, either by hacking it or change the legislation in a  wartime
situation to take control of the database (?) - the question is, is  it
possible for one nation to take down another nation's  Internet
infrastructure by getting access to the mapping database??
Note!  This is an open question since I haven't studied the mapping
solutions in  detail

-- patte



Yes,  LISP's distributed database is either no reduction of the  routing 
churn (if too broad) and otherwise a huge polticial problem - both  in case of 
a cyberwar attack as well as due to the potential threat as to  decline 
service. The EU's Galileo initiative is not because GPS isn't good  enough but 
because its service  could be denied by the political  owner.
Imho, this is the most severe non-starter argument. Thank you for  sharing 
this concern.
 
Heiner