Re: [rrg] Next topic?

jnc@mercury.lcs.mit.edu (Noel Chiappa) Mon, 09 May 2011 18:57 UTC

Return-Path: <jnc@mercury.lcs.mit.edu>
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 B2DC2E0713 for <rrg@ietfa.amsl.com>; Mon, 9 May 2011 11:57:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 TQS2HQXdipQi for <rrg@ietfa.amsl.com>; Mon, 9 May 2011 11:57:13 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 0B827E070E for <rrg@irtf.org>; Mon, 9 May 2011 11:57:12 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 1056D18C0EC; Mon, 9 May 2011 14:57:11 -0400 (EDT)
To: rrg@irtf.org
Message-Id: <20110509185711.1056D18C0EC@mercury.lcs.mit.edu>
Date: Mon, 09 May 2011 14:57:11 -0400
From: jnc@mercury.lcs.mit.edu
Cc: jnc@mercury.lcs.mit.edu
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: Mon, 09 May 2011 18:57:13 -0000

    > From: Tony Li <tli@cisco.com>

    > 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.
    > ...
    > Any proposals of research topics?
    > The floor is open...

Noting the silence, I do have one topic to suggest.

In prior conversations with you, you have suggested that the broad
architectural approach I prefer for path selection - i.e. topology
distribution, with unified path computation (although perhaps 'monolithic'
is a better term than 'unified', since the latter term was used elsewhere
in routing) - is problematic. I don't recall your reasoning exactly (not
that I ever got it in detail, I don't think), IIRC it was something to do
with a combination of:

i) ISPs didn't want to hand out topology information
ii) ISPs like the kind of policies about traffic flow they can impose
	with destination vector architectures
iii) the overhead of path computation needs to be distributed

So perhaps a discussion about what you see as the shortcomings of that
approach, and discussion about whether those issues are or are not
handlable, would be a good thing to do here?

	Noel