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

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 25 February 2010 23:30 UTC

Return-Path: <jmh@joelhalpern.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 E50073A8588 for <rrg@core3.amsl.com>; Thu, 25 Feb 2010 15:30:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.513
X-Spam-Level:
X-Spam-Status: No, score=-3.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 1kJxXcjYcsey for <rrg@core3.amsl.com>; Thu, 25 Feb 2010 15:30:18 -0800 (PST)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 3833A3A83EA for <rrg@irtf.org>; Thu, 25 Feb 2010 15:30:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id E6F42430064; Thu, 25 Feb 2010 15:32:30 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.102] (pool-71-161-51-31.clppva.btas.verizon.net [71.161.51.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTPSA id 4FBB9430063; Thu, 25 Feb 2010 15:32:30 -0800 (PST)
Message-ID: <4B87088C.6040100@joelhalpern.com>
Date: Thu, 25 Feb 2010 18:32:28 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
References: <201002180040.o1I0eAr0027055@cichlid.raleigh.ibm.com> <4B7C94D5.6040102@joelhalpern.com> <201002242206.o1OM6O4J023229@cichlid.raleigh.ibm.com> <4B86E051.7000800@joelhalpern.com> <201002252105.o1PL5Txg024100@cichlid.raleigh.ibm.com>
In-Reply-To: <201002252105.o1PL5Txg024100@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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 23:30:19 -0000

Yes, thank you.  That would address my concern.  I was reading 
"extrapolate ... would look like" in a broader sense than you intended.
Yours,
Joel

Thomas Narten wrote:
>> 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   
>