<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Feb 5, 2010, at 9:23 AM, Bob Atkins wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div bgcolor="#ffffff" text="#000000">John,<br><br>If I may interject. Your statement:<br><br> '...whereas the effort to process a request for an additional IPv4 or IPv6 allocation can be very, very large, depending on the size of the previous allocation and organization of the request supporting materials.'<br><br>Is <i><u><b>way</b></u></i> over the top in regards to IPv6 allocations. The cost for an IPv6 allocation is about as close to $0 as one can get from a management standpoint. The sheer magnitude of available IPv6 address space is such that if all you had was an automated website without any form of controls - we would all be long dead before even a small portion of the IPv6 address space had been delegated - even if you had practically every person on planet earth applying for space.<br></div></blockquote><div><br></div>For initial allocations, I agree 100%. The criteria for an *initial* IPv6 </div><div>allocation are quite modest, and hence it should relatively simply to</div><div>process and assign.</div><div><br><blockquote type="cite"><div bgcolor="#ffffff" text="#000000">Generally, I am pleased with the IPv6 allocation fees being waived currently - it is quite simply why we applied for an IPv6 block. However, when I look at what is being proposed for IPv6 address charges - they are outrageous when you take into consideration that IPv6 is a virtually unlimited resource. IPv6 is a license for ARIN to print money. We are all going to be operating with IPv4 and IPv6 address space for a <i><u><b>long</b></u></i> time - that very fact will substantially increase ARIN's revenue based on the current fee structure. As a small ISP I find this very fact very troubling. Just as the market is eating itself alive from competitive pressure - when we must spend more in ARIN fees, equipment and training to deploy IPv6 and it will be virtually impossible to for us to recover any additional revenue from the use and delegation (to our customers) of IPv6 space. ARIN is maintaining what I call an IPv4 <i><u><b>scarcity</b></u></i> fee structure for IPv6 space which is totally at odds with the monumental amount of address space that is available.<br></div></blockquote><div><br></div>Given the size of the IPv6 allocations, and present need-basis </div><div>requirements that must be assessed before an *additional* </div><div>allocation, it is quite likely that an ISP that comes in with an </div><div>*additional* allocation request would presently need to supply </div><div>a very significant amount of documentation that would need</div><div>to be reviewed. I'm not saying this is "good" or "bad", but </div><div>simply reflects what actions ARIN will need to take based on </div><div>present policy. If this is recovered via ongoing fee schedule,</div><div>then everyone will pay their share regardless of whether they</div><div>make additional IPv6 requests or not. If it is transaction-based,</div><div>then just the party asking for the additional block will be paying</div><div>for those costs.</div><div><div bgcolor="#ffffff" text="#000000"><br></div><blockquote type="cite"><div bgcolor="#ffffff" text="#000000">IPv6 fees for a /32 should be about $100/year - at most! Larger blocks could be sold on an economy of scale basis rather than a linear multiplier of the cost of a /32 block. The entire process should be fully automated - requiring minimal support staff. An even better solution would be to create some competition in the IPv6 address management arena by allowing the existence of multiple IPv6 registrars in the same way that is done for domain names.<br></div></blockquote><br></div><div>One of the reasons that ARIN is investing significantly </div><div>in automation is precisely to aim for lower costs (and </div><div>hence lower fees) for those items which can be </div><div>automated. The current roadmap is available online </div><div>here: <<a href="https://www.arin.net/knowledge/roadmap.html">https://www.arin.net/knowledge/roadmap.html</a>> </div><div>Automation of maintenance will go far in reducing the</div><div>ongoing costs and allowing fee schedules which meet</div><div>expectations of the community.</div><div><br></div><div>/John</div><div><br></div><div>John Curran</div><div>President and CEO</div><div>ARIN</div></body></html>