<div dir="ltr">Certainly ARIN has prevented an organization from getting additional space <div style>if their currently held space is under utilized (even if it is legacy space).</div><div style><br></div><div style>ARIN certainly has used a slow start model, rather than giving potentially</div>
<div style>overly large allocations / assignments when there is not a good foundation</div><div style>of a year's worth of growth to justify the size block requested.</div><div style><br></div><div style>These two practices help to sustain IPv4. </div>
<div style><br></div><div style>The application need based justification to transfers is an attempt</div><div style>to continue these sustainable practices.</div><div style><br></div><div style>It sounds like whatever concerns people have about the depletion </div>
<div style>of the free pool, can also be applied to the depletion of sufficiently</div><div style>large blocks of IPv4 available at a reasonable / affordable price on </div><div style>the transfer market.</div><div style>
<br></div><div style>The only way I see out of this is if there is more that enough supply </div><div style>for everyone to purchase all the addresses they need to sustain</div><div style>their growth until there is wide spread IPv6 adoption.</div>
<div style><br></div><div style>One way to encourage this is to require real IPv6 deployment along</div><div style>with IPv4 transfers. Say require 10% of the customer base to be IPv6 </div><div style>capable prior to approving a transfer, and require a plan to get 40% </div>
<div style>of the customer base IPv6 capable in one year, and 80% in two years.</div><div style><br></div><div style>Choose whatever numbers seem right for the community 1%, 30%, 70%?</div><div style><br></div><div style>
___Jason</div><div style><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 11, 2013 at 3:48 PM, Mike Burns <span dir="ltr"><<a href="mailto:mike@nationwideinc.com" target="_blank">mike@nationwideinc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We already have a reclamation process; see NRPM 12 and the enabling<br>
</blockquote>
language in the RSA. ARIN hasn't used it much/any to date except in<br>
cases of suspected fraud, which IMHO is a dereliction of its duty, but<br>
it _has_ been used. Therefore, any proposal to "begin" using it would<br>
be moot.<br>
<br></div>
Hi Stephen,<br>
<br>
A boogeyman.<br>
ARIN will revoke if you don't pay your bill, though.<br>
I have asked on this list for any evidence of ARIN ever revoking addresses for utilization and was met by crickets.<br>
Hard to reconcile with a principle which demands conservation of all addresses.<div class="HOEnZb"><div class="h5"><br>
<br>
Regards,<br>
Mike<br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/<u></u>listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><font color="#555555" face="'courier new', monospace"><div><span style="color:rgb(0,0,0);font-family:arial"><font color="#555555" face="'courier new', monospace">_______________________________________________________<br>
</font><div><font face="'courier new', monospace">Jason Schiller|NetOps|<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>|571-266-0006</font></div><div><font face="'courier new', monospace"><br>
</font></div></span></div></font>
</div>