Hey Seth,<div>I purposely left that out because there really are green field v6 networks that would not otherwise qualify for an allocation. (props again to Jordi!)</div><div>It seems to me the $$ required to get a v6 allocation, and the gear to run it, if you don't already have v4 is enough to prohibit gaming the system.</div>
<div>Thanks!</div><div>Stacy<br><br><div class="gmail_quote">On Wed, Sep 2, 2009 at 9:49 AM, Morgan Sackett <span dir="ltr"><<a href="mailto:msackett@verilan.com">msackett@verilan.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I think adding this sort of requirement is disadvantageous to newer small networks trying to obtain IP space, especially those looking to do IPv6 only. It will also force the policy to require modification as the available v4 space runs out.<div>
<div></div><div class="h5"><br>
<br>
On Sep 2, 2009, at 9:40 AM, Seth Mattinen wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Member Services wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Draft Policy 2009-7<br>
Open Access To IPv6<br>
<br>
Version/Date: 31 August 2009<br>
<br>
Policy statement:<br>
<br>
1) Remove “by advertising that connectivity through its single<br>
aggregated address allocation” from article 3 of section 6.5.1.1<br>
<br>
2) Remove article 4 of section 6.5.1.1, “be an existing, known ISP in<br>
the ARIN region or have a plan for making at least 200 end-site<br>
assignments to other organizations within 5 years” in its entirety.<br>
<br>
Rationale:<br>
<br>
It is acknowledged that these concepts have been put before the<br>
community in the past. However, with the wisdom of actual operational<br>
experience, the necessity of promoting IPv6 adoption throughout our<br>
region, and emerging native v6 only network models, it becomes obvious<br>
that these modifications to the NRPM are necessary. Removing the 200 end<br>
site requirement enables smaller, but no less important and viable,<br>
networks access to IPv6. Removing the ‘known ISP’ requirement<br>
enfranchises new, native v6 businesses that can drive innovation and<br>
expansion in the Internet industry, as well as other industries.<br>
Removing the requirement for a single aggregate announcement benefits<br>
the NRPM itself, as it has been decided by the community that it should<br>
not contain routing advice.<br>
<br>
Timetable for implementation: immediately upon BoT ratification<br>
<br>
#####<br>
#####<br>
<br>
Staff Assessment<br>
<br>
Proposal: Open Access to IPv6 (proposal #90)<br>
<br>
Proposal Version (Date) 21 May 2009<br>
<br>
Date Assessment Due: 05 Aug 2009<br>
<br>
1. Proposal Summary (Staff Understanding)<br>
<br>
This policy proposal would modify NRPM section 6.5.1.1 by removing all<br>
or part of two initial criteria from the the existing IPv6 policy: the<br>
requirement to advertise the single aggregate and the requirement to<br>
plan on making 200 end site assignments to customers or be a known ISP<br>
in the ARIN region. The only remaining criteria to qualify for an IPv6<br>
allocation are to be an LIR/ISP, not be an end site, and plan on<br>
providing IPv6 connectivity to organizations and assigning them IPv6<br>
address space.<br>
<br>
</blockquote>
<br>
I SUPPORT this policy.<br>
<br>
If there is concern of gaming/abusing this, then I suggest adding a<br>
clause requiring an existing IPv4 number resource from ARIN in order to<br>
obtain your /32.<br>
<br>
-- <br>
Seth Mattinen <a href="mailto:sethm@rollernet.us" target="_blank">sethm@rollernet.us</a><br>
Roller Network LLC<br>
_______________________________________________<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/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>
</blockquote>
<br></div></div>
Morgan Sackett<br>
VP of Engineering<br>
<br>
VeriLAN Event Services, Inc.<br>
215 SE Morrison Street<br>
Portland, OR 97214<br>
<br>
Tel: 503 907-1415<br>
Fax: 503 224-8833<br>
<br>
<a href="mailto:msackett@verilan.com" target="_blank">msackett@verilan.com</a><br>
<a href="http://www.verilan.com" target="_blank">www.verilan.com</a><br>
<br>
<br>
This e-mail contains proprietary information and may be confidential. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this message is strictly prohibited. If you received this message in error, please delete it immediately.<div>
<div></div><div class="h5"><br>
<br>
<br>
<br>
<br>
_______________________________________________<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/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></div>