Re: Last Call: 'Considerations on the IPv6 Host density Metric' to Informational RFC (draft-huston-hd-metric)

Steven Blake <slblake@petri-meat.com> Mon, 05 June 2006 12:36 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnEKH-0003Ey-MP; Mon, 05 Jun 2006 08:36:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fmkbl-00070G-HG; Sun, 04 Jun 2006 00:53:01 -0400
Received: from server26.tchmachines.com ([69.50.221.207]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fmkbk-0007tt-4v; Sun, 04 Jun 2006 00:53:01 -0400
Received: from cpe-066-057-103-013.nc.res.rr.com ([66.57.103.13]) by server26.tchmachines.com with esmtpa (Exim 4.52) id 1Fmkbl-0008If-RD; Sun, 04 Jun 2006 00:53:02 -0400
From: Steven Blake <slblake@petri-meat.com>
To: Geoff Huston <gih@apnic.net>
In-Reply-To: <6.2.0.14.2.20060604101610.02d4ea08@kahuna.telstra.net>
References: <1149305596.24519.142.camel@tachyon> <6.2.0.14.2.20060604101610.02d4ea08@kahuna.telstra.net>
Content-Type: text/plain
Date: Sun, 04 Jun 2006 00:52:55 -0400
Message-Id: <1149396775.13858.54.camel@tachyon>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 (2.2.3-4.fc4)
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server26.tchmachines.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - petri-meat.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
X-Mailman-Approved-At: Mon, 05 Jun 2006 08:36:53 -0400
Cc: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'Considerations on the IPv6 Host density Metric' to Informational RFC (draft-huston-hd-metric)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

On Sun, 2006-06-04 at 10:39 +1000, Geoff Huston wrote:

> At 01:33 PM 3/06/2006, Steven Blake wrote:
> >I am concerned about the conclusion reached in this document (that HD
> >ratios > 0.8 and closer to 0.94 should be considered when making address
> >allocations to larger providers).
> 
> 
> This is a topic of interest both to the IETF and to regional addressing 
> policy fora, and some care needs to be taken in reaching an understanding 
> of relative roles.
> 
> As compared to your opening statement relating to the conclusion of this 
> document, I must correct you  by noting that this document makes NO 
> specific recommendation as to an optimal HD Ratio value to be used in the 
> context of a threshold address utilization efficiency metric. This document 
> provides a refinement to the work reported in RFC1715, RFC 3177 and RFC 
> 3194 that recommended the use of an HD Ratio of 0.8 for assessment of 
> threshold address utilization efficiencies in an address allocation 
> context. The refinement proposed in this document is, and I quote:
> 
>    "This study concludes that consideration should be given to the
>     viability of specifying a higher HD-Ratio value as representing a
>     more relevant model of internal network structure, internal routing
>     and internal address aggregation structures in the context of IPv6
>     network deployment."
> 
> Your representation as to the document's conclusions is simply not 
> supported by the document itself.

Geoff,

I don't understand why you think my paraphrase of your document's
conclusions (including the quoted text above) is unfair or inaccurate.

What is the concern that would make such consideration (of specifying a
higher HD ratio) worthwhile?  I assume that it is address allocation
inefficiency with HD = 0.80, as suggested in your comments on Figure 4,
and the implied risk (which you have described in much more detail
elsewhere) that IPv6 unicast address space is a resource at plausible
risk of being exhausted at some point in the future, without changes to
the HD ratio.  Am I mistaken?

I've read your arguments elsewhere that we are at risk of allocating
a /1 - /4 worth of space in the next 60 years under current polices. I
don't find your arguments convincing, and further, I'm not convinced
that this would pose some sort of catastrophe, rather than the
achievement of a steady state.  And even if it is a real risk, then a
switch to /56 allocations for residential/SOHO is a preferable solution
to increasing HD, because we don't know what the design for an internet-
sized IGP would look like.

I am concerned that this document sends the wrong message to providers,
and I fear that their likely reaction to the perceived risk of tighter
allocation policies by the RIRs with be more harmful to the IPv6
internet that the potential risk of address space exhaustion.


Regards,

// Steve


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf