<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
On Oct 11, 2014, at 12:59 PM, John Curran <<a href="mailto:jcurran@arin.net">jcurran@arin.net</a>> wrote:<br>
<div>
<blockquote type="cite">
<div>
<div class="BodyFragment"><font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
Until such time as IPv4 address blocks are being actively returned by <br>
organizations (seeking to lower their fees), there is no impact to ARIN's <br>
receipts. After that point, ARIN's annual ISP billings drop from approx <br>
$12.5 million to zero as increasing number of IPv4 resources are returned. <br>
While costs are expected to be lower at that time, some billing adjustment <br>
would certainly be necessary.</div>
</span></font></div>
</div>
</blockquote>
<br>
</div>
<div>Regarding the potential need to revisit the fee structure in a post-IPv4 world,</div>
<div>depending on the IPv6 long-term revenues - </div>
<div><br>
</div>
<div>I did some followup modeling just to see what revenues look like presently</div>
<div>in a world where all ISPs obtain an IPv6 allocation and return their IPv4 </div>
<div>resources. </div>
<div><br>
</div>
<div>Under the present fee structure, at the point of full IPv4 return the present</div>
<div>$13.6M ISP revenues would drop to approx $5.7M annually; under the </div>
<div>realigned IPv4 proposal the ISP revenues at full IPv4 return would be </div>
<div>approximately $3.0M annually. </div>
<div><br>
</div>
<div>End-user fees (IPv4, IPv6, and ASN maintenance) are approximately $2M </div>
<div>today; in a full IPv4 return situation, this would drop by approximately $560K</div>
<div>annually.</div>
<div><br>
</div>
<div>FYI,</div>
<div>/John</div>
<div><br>
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
<div><br>
</div>
<br>
</body>
</html>