Bill,<div><br></div><div>I think what the ARIN staff was saying was not that prop 131 conflicts with the "mandatory returns" in 2009-3 because there are no mandatory returns in 2009-3 but 131 makes it so there are no blocks to be voluntarily returned in 2009-3. </div>
<div><br></div><div>2009-3 specifically states, "<span class="Apple-style-span" style="font-family: arial, helvetica, sans-serif; font-size: 10px; line-height: 18px; ">Each RIR through their respective chosen policies and strategies may<br>
recover IPv4 address space which is under their administration and<br>designate any such space for return to the IANA. Each RIR shall at<br>quarterly intervals return any such designated address space to the IANA<br>in aggregated blocks of /24 or larger, for inclusion in the recovered<br>
IPv4 pool."</span><br><br><div class="gmail_quote">This is not mandatory return. 131 specifically says that ARIN will make recovered legacy space available for distribution within the ARIN region. If it passes then it conflicts with 2009-3 because there would be no blocks that could be designated for return to IANA.</div>
<div class="gmail_quote"><br></div><div class="gmail_quote">131 also conflicts with current ARIN operational practice. That practice has been that ARIN does give back any /8s that it recovers or that are returned. This is not mandated this is just operational practice as far as I know. </div>
<div class="gmail_quote"><br></div><div class="gmail_quote">I hope this helps.</div><div class="gmail_quote"><br></div><div class="gmail_quote">Thanks!</div><div class="gmail_quote">----Cathy</div><div class="gmail_quote">
<br></div><div class="gmail_quote">On Fri, Feb 18, 2011 at 3:46 PM, William Herrin <span dir="ltr"><<a href="mailto:bill@herrin.us">bill@herrin.us</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">On Fri, Feb 18, 2011 at 5:29 PM, Kevin Kargel <<a href="mailto:kkargel@polartel.com">kkargel@polartel.com</a>> wrote:<br>
> IMHO a policy that *allows* return of blocks to IANA upon<br>
> request by IANA would be ok. I am not in favor of policy<br>
> that *requires* return of blocks whether IANA wants them or not.<br>
<br>
</div>Hi Kevin,<br>
<br>
That matches my understanding of the already-board-approved draft<br>
policy 2009-3. However, when evaluating proposal 131, ARIN staff<br>
offered a radically different interpretation of 2009-3. Their<br>
interpretation is that an ARIN policy which prevents the return of<br>
legacy addresses to IANA (prop 131 version 3) conflicts with the<br>
mandatory returns to IANA in draft policy 2009-3.<br>
<br>
Hence proposal 135 which, in my opinion, does not alter 2009-3 in any<br>
way. It merely clarifies the intended interpretation of 2009-3's<br>
language.<br>
<div class="im"><br>
Regards,<br>
Bill Herrin<br>
<br>
<br>
<br>
--<br>
William D. Herrin ................ <a href="mailto:herrin@dirtside.com">herrin@dirtside.com</a> <a href="mailto:bill@herrin.us">bill@herrin.us</a><br>
3005 Crane Dr. ...................... Web: <<a href="http://bill.herrin.us/" target="_blank">http://bill.herrin.us/</a>><br>
Falls Church, VA 22042-3004<br>
_______________________________________________<br>
</div><div><div></div><div class="h5">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></div>