Re: [rrg] Next topic?

heinerhummel@aol.com Wed, 11 May 2011 05:15 UTC

Return-Path: <HeinerHummel@aol.com>
X-Original-To: rrg@ietfa.amsl.com
Delivered-To: rrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D32FE0675 for <rrg@ietfa.amsl.com>; Tue, 10 May 2011 22:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.739
X-Spam-Level:
X-Spam-Status: No, score=-0.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dbmSS4mkrGus for <rrg@ietfa.amsl.com>; Tue, 10 May 2011 22:15:33 -0700 (PDT)
Received: from imr-mb02.mx.aol.com (imr-mb02.mx.aol.com [64.12.207.163]) by ietfa.amsl.com (Postfix) with ESMTP id 1FEDAE0671 for <rrg@irtf.org>; Tue, 10 May 2011 22:15:33 -0700 (PDT)
Received: from imo-da04.mx.aol.com (imo-da04.mx.aol.com [205.188.169.202]) by imr-mb02.mx.aol.com (8.14.1/8.14.1) with ESMTP id p4B5FUGu023981; Wed, 11 May 2011 01:15:30 -0400
Received: from HeinerHummel@aol.com by imo-da04.mx.aol.com (mail_out_v42.9.) id 9.d2b.77167cd9 (55835); Wed, 11 May 2011 01:15:25 -0400 (EDT)
Received: from smtprly-dc01.mx.aol.com (smtprly-dc01.mx.aol.com [205.188.170.1]) by cia-md06.mx.aol.com (v129.10) with ESMTP id MAILCIAMD063-d1c64dca1b6917a; Wed, 11 May 2011 01:15:25 -0400
Received: from web-mmc-d08 (web-mmc-d08.sim.aol.com [205.188.103.98]) by smtprly-dc01.mx.aol.com (v129.10) with ESMTP id MAILSMTPRLYDC017-d1c64dca1b6917a; Wed, 11 May 2011 01:15:21 -0400
References: <06B61955-CA9F-4CE7-9DA3-6DA8ECF6CD07@cisco.com><4DC90101.50403@it.uc3m.es> <8CDDD1056BE3DA2-1160-DD4@webmail-m046.sysops.aol.com> <26E5D1C5D5365D47B147E5E62FC7358502D9D4B9@FIESEXC035.nsn-intra.net>
To: hannu.flinck@nsn.com, rrg@irtf.org
Date: Wed, 11 May 2011 01:15:21 -0400
X-AOL-IP: 95.91.105.21
In-Reply-To: <26E5D1C5D5365D47B147E5E62FC7358502D9D4B9@FIESEXC035.nsn-intra.net>
X-MB-Message-Source: WebUI
MIME-Version: 1.0
From: heinerhummel@aol.com
X-MB-Message-Type: User
Content-Type: multipart/alternative; boundary="--------MB_8CDDDB18FA094E1_18DC_28F74_web-mmc-d08.sysops.aol.com"
X-Mailer: Webmail 33668-STANDARD
Received: from 95.91.105.21 by web-mmc-d08.sysops.aol.com (205.188.103.98) with HTTP (WebMailUI); Wed, 11 May 2011 01:15:21 -0400
Message-Id: <8CDDDB18F9970B8-18DC-14A0C@web-mmc-d08.sysops.aol.com>
X-AOL-SENDER: HeinerHummel@aol.com
Subject: Re: [rrg] Next topic?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/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: Wed, 11 May 2011 05:15:34 -0000

Hannu, 
please admit that Columbus routing is part of multipath forwarding and I will admit that I deliberately obstained from submitting a 01-version of the TARA-draft that contained in detail how to do Columbus routing based on TARA.


I don't know the secret why DV is such sacrosanct but I know for sure that enhancements for routing via more and more remote nodes would blow up DV.


Offlist I received comments about what to do with so many alternative paths, when provided. Indeed, they need to be utilized for the overall benefit
(traffic balancing, congestion avoidance, congestion handling). This however would need a rearview mirror i.e. knowledge about upstream paths from where the traffic comes from. Again: not possible based on DV.


Heiner







-----Ursprüngliche Mitteilung----- 
Von: Flinck, Hannu (NSN - FI/Espoo) <hannu.flinck@nsn.com>
An: heinerhummel@aol.com; marcelo@it.uc3m.es; rrg@irtf.org
Verschickt: Di., 10. Mai. 2011, 14:05
Thema: RE: [rrg] Next topic?



Based on my reading of TARA it was all about geographical addressing.
 
-          Hannu 
 

From: rrg-bounces@irtf.org [mailto:rrg-bounces@irtf.org] On Behalf Of ext heinerhummel@aol.com
Sent: Tuesday, May 10, 2011 1:01 PM
To: marcelo@it.uc3m.es; rrg@irtf.org
Subject: Re: [rrg] Next topic?

 
Obviously no one, because this was a main goal of ignored TARA: multipath forwarding based on a network graph which is composed of  

inter- AND intra-network links and which  not only comprises  ECMPs but also  detouring paths  via equidistant or even more remote routers.

 

Heiner
 

-----Ursprüngliche Mitteilung----- 
Von: marcelo bagnulo braun <marcelo@it.uc3m.es>
An: rrg@irtf.org
Verschickt: Di., 10. Mai. 2011, 11:10
Thema: Re: [rrg] Next topic?

Hi, 
 
What about doing some work in multi-path routing in the inter-domain? 
i.e. enabling a router to use multiple paths with potential different characteristics to forward packets across domains. 
Would people find this topic interesting? 
 
regards, marcelo 
 
 
El 08/05/11 19:18, Tony Li escribió: 
> Hi all, 
> 
> It's time to start the conversation about where the RRG is headed. Towards that end, I'd like to open the floor for the discussion of topics. Any _research_ topic within the broad area of routing and addressing is appropriate. 
> 
> I propose the following process: we hold this discussion this month, trying to identify relevant topics. Each topic should have a succinct statement of its goals. At the end of the month, we poll to determine the interest level in the various topics. Those that seem to have critical mass are recommended to the IRTF Chair for consideration. 
> 
> The default answer, if no topic has critical mass, is for the RG to go on hiatus. 
> 
> Any questions or comments on the process? 
> 
> Any proposals of research topics? 
> 
> The floor is open... 
> 
> Tony 
> 
> _______________________________________________ 
> rrg mailing list 
> rrg@irtf.org 
> http://www.irtf.org/mailman/listinfo/rrg ;
> 
 
_______________________________________________ 
rrg mailing list 
rrg@irtf.org 
http://www.irtf.org/mailman/listinfo/rrg ;