Re: [rrg] Recommendation and what happens next

Russ White <russ@cisco.com> Mon, 08 March 2010 01:57 UTC

Return-Path: <russ@cisco.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 C9ADC3A681C for <rrg@core3.amsl.com>; Sun, 7 Mar 2010 17:57:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 KZMzRRZes30T for <rrg@core3.amsl.com>; Sun, 7 Mar 2010 17:57:35 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id C07EF3A67E1 for <rrg@irtf.org>; Sun, 7 Mar 2010 17:57:34 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAO7ok0tAZnwM/2dsb2JhbACbI3OgCJdDhHgEgxeGXg
X-IronPort-AV: E=Sophos;i="4.49,599,1262563200"; d="scan'208";a="91029419"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 08 Mar 2010 01:57:37 +0000
Received: from [127.0.0.1] (rtp-russwh-8712.cisco.com [10.116.137.179]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o281vbiB029468; Mon, 8 Mar 2010 01:57:37 GMT
Message-ID: <4B945997.9080704@cisco.com>
Date: Sun, 07 Mar 2010 20:57:43 -0500
From: Russ White <russ@cisco.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Tony Li <tony.li@tony.li>
References: <C7B951B7.4F5D%tony.li@tony.li>
In-Reply-To: <C7B951B7.4F5D%tony.li@tony.li>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 08 Mar 2010 08:14:11 -0800
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Recommendation and what happens next
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: Mon, 08 Mar 2010 01:57:35 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> Yes, a path.  Not necessarily a single proposal, but a clear plan.  From the
> charter:
> 
>     The group will produce ... a recommendation for a routing and addressing
>     architecture.
> 
> It doesn't say "a set of possible architectures" or "some vague things that
> we could do".  
> 
> Again, our job is to make a decision and that's what we're going to do.

One thing that might be _nice_ is to have some idea of what the future
of routing, in general, looks like under each proposal. In other words,
does the proposal allow future changes in the routing system through
incremental deployment of new ideas and techniques, or does it place us
in the position of forcing "flag days?" As architectures become more
complex on the machine side, they also tend to become more brittle in
general.

A second thing might be to address mobility. How does each proposal deal
with host level mobility, since this is obviously a direction in the
Internet at large (whether we like it or not, mobile phones and other
such devices are going to rely increasingly on the Internet, which
may--or may not--place a larger burden on the routing system).

A third thing might be to address whether or not any of the solutions
proposed actually resolves the problem seen in the field--IE, describing
what the problem is and why it exists (I've mostly seen hand waving to
this point about the size of the global table, and projections against
the future size of that table, but nothing that says why the table is
growing at this rate, other than the blanket statement of "dual homing,"
which doesn't really answer the question at all), and how each solution
specifically resolves the problem. Since I don't tend to think the
problem is "dual homing," since that problem is "solvable" in other ways
that don't require a redesign of the entire Internet routing architecture.

Don't know how far we'll go on these sorts of things, but it would
certainly help increase the ability of folks to assess the work if we
could consider them in some way.

Russ
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuUWZcACgkQER27sUhU9OTtCACfd9VDYUH+cDXYxEKNKD7JnY+T
sfQAoMWBFQq5sAAL91yAzQFjrY5MicvT
=w3Yl
-----END PGP SIGNATURE-----