Re: [rrg] draft-narten-radir-problem-statement-05.txt

Thomas Narten <narten@us.ibm.com> Thu, 25 February 2010 21:03 UTC

Return-Path: <narten@us.ibm.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 175643A8593 for <rrg@core3.amsl.com>; Thu, 25 Feb 2010 13:03:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.183
X-Spam-Level:
X-Spam-Status: No, score=-4.183 tagged_above=-999 required=5 tests=[AWL=-1.584, BAYES_00=-2.599]
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 CD5lh343Ls9h for <rrg@core3.amsl.com>; Thu, 25 Feb 2010 13:03:41 -0800 (PST)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by core3.amsl.com (Postfix) with ESMTP id 1278E28C150 for <rrg@irtf.org>; Thu, 25 Feb 2010 13:03:41 -0800 (PST)
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e39.co.us.ibm.com (8.14.3/8.13.1) with ESMTP id o1PKwBVD007308 for <rrg@irtf.org>; Thu, 25 Feb 2010 13:58:11 -0700
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id o1PL5ZrL155816 for <rrg@irtf.org>; Thu, 25 Feb 2010 14:05:38 -0700
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.3/8.13.1/NCO v10.0 AVout) with ESMTP id o1PL5V1S001746 for <rrg@irtf.org>; Thu, 25 Feb 2010 14:05:31 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-49-153-63.mts.ibm.com [9.49.153.63]) by d03av02.boulder.ibm.com (8.14.3/8.13.1/NCO v10.0 AVin) with ESMTP id o1PL5U5j001660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Feb 2010 14:05:31 -0700
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.3/8.12.5) with ESMTP id o1PL5Txg024100; Thu, 25 Feb 2010 16:05:29 -0500
Message-Id: <201002252105.o1PL5Txg024100@cichlid.raleigh.ibm.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
In-reply-to: <4B86E051.7000800@joelhalpern.com>
References: <201002180040.o1I0eAr0027055@cichlid.raleigh.ibm.com> <4B7C94D5.6040102@joelhalpern.com> <201002242206.o1OM6O4J023229@cichlid.raleigh.ibm.com> <4B86E051.7000800@joelhalpern.com>
Comments: In-reply-to "Joel M. Halpern" <jmh@joelhalpern.com> message dated "Thu, 25 Feb 2010 15:40:49 -0500."
Date: Thu, 25 Feb 2010 16:05:29 -0500
From: Thomas Narten <narten@us.ibm.com>
Cc: rrg@irtf.org
Subject: Re: [rrg] draft-narten-radir-problem-statement-05.txt
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: Thu, 25 Feb 2010 21:03:42 -0000

> What you propose to add is good.  But, the text in 4.6 as written claims 
> "It is possible to extrapolate what the size of the IPv6 routing table 
> would be if wide spread adoption of IPv6 occurred..."

Ah. Is your issue more narrow in the sense that this statement is
misleading?

The extrapolation is intended for "today" not for "next year" or "ten
years from now".

You must be assuming that the exising pressures that contribute to
problems will get worse (I tend to agree!). But, that doesn't really
have anything to do with IPv6. I.e., IPv6 doesn't make those pressures
stronger or lesser.  They will also get worse with IPv4.

> the extrapolation that then takes place assumes that the same factors 
> that currently constrain IPv4 sizes would constrain IPvb6 sizes, and 
> that seems extremely unlikely.  Hence, this extrapolation is very 
> optimistic, and misleading to the reader.

How about if I change the statement as follows:

OLD:

   It is possible to extrapolate what the size of the IPv6 Internet
   routing table would be if widespread IPv6 adoption occurred, from the
   current IPv4 Internet routing table.  

NEW:

   It is possible to extrapolate what the size of the IPv6 Internet
   routing table might look like today, from the current IPv4 Internet
   routing table, if widespread IPv6 adoption were to occur
   "instantaneously",

Then, at the end of the paragraph add something like:

   Of course, this estimate is based on a current snapshot of IPv4
   routing activity. Unless the pressures described elsewhere in this
   document are reduced, the actual table size would be larger.

Would that address your concern?   

Thomas