<div dir="ltr">I can't quite imagine a scenario that would merit an 8.3 transfer of reserved pool IP space. I think the community is better served to encourage reserved pool address holders to return the space back to the reserved pool if the need they originally requested the address space for no longer exists. As such, I prefer the original policy text.<div><br></div><div>I'd be open to changing my opinion if someone could explain a scenario where an 8.3 transfer is preferable to requesting space from the free pool.</div><div><br></div><div>Cheers,</div><div>Christoph</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 5 May 2016 at 12:11, 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 style="word-wrap:break-word">Speaking strictly for myself and not as a member of the AC…<div><br></div><div>I still fail to see the need for this. Here are the scenarios I can see:</div><div><br></div><div>1.<span style="white-space:pre-wrap"> </span>Transfer of an operating environment to a new organization through merger/acquisition/reorg:</div><div><br></div><div><span style="white-space:pre-wrap"> </span>This would be handled in 8.2 and there is no restriction on these blocks in 8.2</div><div><span style="white-space:pre-wrap"> </span>transfers.</div><div><br></div><div>2.<span style="white-space:pre-wrap"> </span>Creation of a new operational environment which needs resources and qualifies:</div><div><br></div><div><span style="white-space:pre-wrap"> </span>Since these reserved pools still have resources available, I see no reason to support</div><div><span style="white-space:pre-wrap"> </span>their transfer through 8.3 or 8.4.</div><div><br></div><div>I think the proposed change would be mostly harmless, but I also feel that it serves no useful purpose and would complicate policy unnecessarily.</div><div><br></div><div>Further, unlike larger blocks of resources, these blocks are assigned in very small chunks and for a very specific purpose. Once that purpose no longer exists, their return should be straightforward and we as a community should be able to expect voluntary return of these addresses as they cannot be monetized, cannot be transferred, and cannot be repurposed. (At least not without violating policy).</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Owen</div></font></span><div><br><div><blockquote type="cite"><div><div class="h5"><div>On May 5, 2016, at 07:59 , Andrew Dul <<a href="mailto:andrew.dul@quark.net" target="_blank">andrew.dul@quark.net</a>> wrote:</div><br></div></div><div><div><div class="h5">
<div bgcolor="#FFFFFF" text="#000000"><p>Hello,</p><p>As part of the discussions at ARIN 37 the community considered
updates to the proposed draft policy that would allow
organizations to transfer, within ARIN, reserved pool resources
provided that they met the criteria to obtain a block from a
reserved pool. <br>
</p><p>Based upon this feedback we are proposing to update the draft
policy text as follows. The AC welcomes your feedback on this
proposed text and any other feedback on this draft policy.</p><p>Thanks,</p><p>Andrew<br>
</p><p><br>
</p>
<b>Original</b><strong> Policy statement:</strong><p>Add to Section 8.3 and Section 8.4 under the "Conditions on
source of the transfer:"</p><p>Address resources from a reserved pool (including those
designated in Section 4.4 and 4.10) are not eligible for transfer.</p><p><b><strong>Updated </strong></b><strong>Policy statement:</strong>
</p><p>Add to Section 8.3 under the "Conditions on recipient of the
transfer:"</p><p>Address resources from a reserved pool (including those
designated in Section 4.4 and 4.10) shall only be transferred to
organizations which meet the current criteria of the reserved pool
from which the resource was obtained.</p>
Add to Section 8.4 under the "Conditions on source of the transfer:"
<p>Address resources from a reserved pool (including those
designated in Section 4.4 and 4.10) are not eligible for transfer.</p>
</div></div></div>
_______________________________________________<span class=""><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.</span></div></blockquote></div><br></div></div><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" rel="noreferrer" 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></blockquote></div><br></div>