<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>RE: [arin-ppml] ARIN-prop-156 Update 8.3 to allow inter-RIRtransfers</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Thanks Geoff.<BR>
Thought that needed to be clear. Appreciate your support of the conversation.<BR>
bd<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Geoff Huston [<A HREF="mailto:gih@apnic.net">mailto:gih@apnic.net</A>]<BR>
Sent: Wed 8/24/2011 10:29 PM<BR>
To: Bill Darte<BR>
Cc: Paul Wilson; ARIN PPML<BR>
Subject: Re: [arin-ppml] ARIN-prop-156 Update 8.3 to allow inter-RIRtransfers<BR>
<BR>
Hi Bill,<BR>
<BR>
As you are asking about the projections on <A HREF="http://www.potaroo.net/tools/ipv4/">http://www.potaroo.net/tools/ipv4/</A> so I can answer that. The projections for exhaustion in that model assume NO further returns of address space, and only includes the existing free pool.<BR>
<BR>
The model accumulates all available space, and attributes it to the RIR who has the administrative responsibility for that address block. The table of available space per RIR is reported on that report. The model then generates an allocation model using historical allocation data, and uses this allocation model to forward project consumption of the current pool of available space for each RIR.<BR>
<BR>
regards,<BR>
<BR>
Geoff<BR>
<BR>
<BR>
<BR>
<BR>
On 25/08/2011, at 1:06 PM, Bill Darte wrote:<BR>
<BR>
> Hi Paul,<BR>
><BR>
> Thanks Paul.... question...<BR>
> Does the projections you point to for a long tailed ARIN runout include only existing free pool or is it considering the potential legacy returns that could be consumed only within the ARIN region assuming not Inter-RIR transfer capability?<BR>
><BR>
> Best,<BR>
> bd<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>