<div dir="ltr">+1 to what Owen said or to put it another way...<div><br></div><div style>This draft suggests both conservation and aggregation are conflicting goals </div><div style>that need the appropriate balance. The appropriate balance is not defined </div>
<div style>here but a little guidance is given, and it is expected that current (and future) </div><div style>ARIN policy will consider this and attempt to strike the appropriate balance. </div><div style><br></div><div style>
It provides advice that specifics of the protocol such as the size address number </div><div style>space, or availability will influence where the proper balance is. </div>"...because the IPv6 number space is orders of magnitude larger than the IPv4 <div>
number space, the scale tips away from efficient utilization towards hierarchical </div><div>aggregation for IPv6 number resources."<div style><br></div><div style>The community has already decided that End Sites should get a minimum of an </div>
<div style>IPv6 /48 as a direct allocation from ARIN, if they have a justified need for PI space. </div><div style><br></div><div style>In other words a single IPv6 host, connected to a single IPv6 router with a </div><div style>
globally unique ASN and multi-homed to two providers is considered </div><div style>sufficient justification of need for a PI IPv6 block, and thus qualifies </div><div style>the organization for a /48.</div></div><div style>
<br></div><div style>For ISP assignments to end-site /64 up to a /48 is supported, and /48 is </div><div style>encouraged, and can be done with no utilization penalty. </div><div style><br></div><div style>I don't see a conflict here.</div>
<div style><br></div><div style>__Jason</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 4, 2013 at 10:55 PM, Owen DeLong <span dir="ltr"><<a href="mailto:owen@delong.com" target="_blank">owen@delong.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>
> For example: Pay for quantity of resources. Or: demonstration<br>
> of meaningful plan to utilize resources.<br>
><br>
<br>
</div>Please explain to me how you distinguish between current "needs-basis"<br>
IPv6 policy and "demonstration of meaningful plan to utilize".<br>
<div class="im"><br>
> When we are talking about resources you might need in 5 years; this<br>
> is not about "needs basis", but about reasonable future<br>
> projections.<br>
><br>
<br>
</div>The term needs basis as applied to current IPv6 policy is basically that.<br>
<br>
While you can make the argument that it isn't technically "need", but rather<br>
"reasonable anticipation of need", it is what is in place today and what we<br>
tend to mean when we refer to "needs basis".<br>
<div class="im"><br>
> Characterizing opponents as "vocal minority with an agenda"<br>
> in that manner is so disingenuous...<br>
<br>
</div>I will point out that this particular claim has been made by both sides of this debate against the other.<br>
<span class="HOEnZb"><font color="#888888"><br>
Owen<br>
</font></span><div class="HOEnZb"><div class="h5"><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">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">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>