No objections here. As far as I can tell the only substantive change (other than codifying existing practice) is the requirement that "The new entity must sign an RSA covering all transferred resources." That seems like a (minor) improvement in policy.<div>
<br></div><div>-Scott</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 10, 2012 at 2:44 PM, David Farmer <span dir="ltr"><<a href="mailto:farmer@umn.edu" target="_blank">farmer@umn.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Depending on the traditions you follow, the holidays are or very soon will be upon us; Nevertheless, please look at the following text and provide your comments to the AC.<br>
<br>
BE ADVISED, the AC is likely to consider sending this text to last call at its meeting next week. Please let us know your opinion, even if it is you simply support or not the text as written.<br>
<br>
Thanks and Happy Holidays.<div class="HOEnZb"><div class="h5"><br>
<br>
On 11/26/12 15:25 , Chris Grundemann wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I made some updates based on feedback received here, the new text is as follows:<br>
<br>
----8<----8<----<br>
Replace the first paragraph of section 8.2 with the following (second<br>
paragraph remains unchanged):<br>
<br>
ARIN will consider requests for the transfer of number resources in<br>
the case of mergers and acquisitions under the following conditions:<br>
<br>
* The new entity must provide evidence that they have acquired assets<br>
that use the resources transferred from the current registrant. ARIN<br>
will maintain an up-to-date list of acceptable types of documentation.<br>
* The current registrant must not be involved in any dispute as to the<br>
status of the transferred resources.<br>
* The new entity must sign an RSA covering all transferred resources.<br>
* The transferred resources will be subject to ARIN policies.<br>
* The minimum transfer size is the smaller of the original allocation<br>
size or the applicable minimum allocation size in current policy.<br>
----8<----8<----<br>
<br>
Cheers,<br>
~Chris<br>
<br>
<br>
On Mon, Nov 19, 2012 at 9:39 PM, Owen DeLong <<a href="mailto:owen@delong.com" target="_blank">owen@delong.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On Nov 19, 2012, at 7:56 PM, Jimmy Hess <<a href="mailto:mysidia@gmail.com" target="_blank">mysidia@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 11/19/12, Owen DeLong <<a href="mailto:owen@delong.com" target="_blank">owen@delong.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
IOW, I want to avoid extending the more lenient 8.2 provisions to a sale<br>
where someone buys $100,000 worth of IP addresses and $20,000 worth of<br>
hardware and then sells the hardware to $SCRAP_DEALER just to keep the<br>
addresses.<br>
</blockquote>
<br>
IP addresses don't belong to hardware; IP addresses belong to IP<br>
interfaces, attached to hardware, in order to provide connectivity to<br>
a network node for communicating or offering a service. A change<br>
of hardware does not imply that the need for the logical IP interface<br>
goes away. If you send a router to a scrap dealer, that doesn't<br>
mean all the networks it routed necessarily go away.<br>
<br>
</blockquote>
<br>
The above statement was short-hand to explain my intent, not an absolute<br>
statement implying that addresses were attached directly to hardware.<br>
Put it back in context with what I was responding to.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
What about cases, where the acquiring organization finds the hardware<br>
_belongs_ with $TRASH_COLLECTION or $SCRAP_DEALER due to the<br>
obsolescence of said decrepit hardware, and after acquiring, they<br>
will make a non-disruptive reallocation of the hardware used to<br>
provide IT services? Probably by re-consolidating on new<br>
hardware.<br>
<br>
</blockquote>
<br>
The policy language I proposed would not preclude this.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
That kind of restructuring does not make renumbering reasonable<br>
and doesn't belong under 8.3.<br>
</blockquote>
<br>
Agreed. However, I want to make sure that 8.2 does not get abused to<br>
back-door 8.3 style transfers by adding hardware to the mix and pretending<br>
it is an acquisition of a working network.<br>
<br>
Owen<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>
</blockquote>
<br>
<br>
<br>
</blockquote>
<br>
<br>
-- <br></div></div><div class="im HOEnZb">
==============================<u></u>==================<br>
David Farmer Email: <a href="mailto:farmer@umn.edu" target="_blank">farmer@umn.edu</a><br>
Office of Information Technology<br>
University of Minnesota<br>
2218 University Ave SE Phone: <a href="tel:1-612-626-0815" value="+16126260815" target="_blank">1-612-626-0815</a><br>
Minneapolis, MN 55414-3029 Cell: <a href="tel:1-612-812-9952" value="+16128129952" target="_blank">1-612-812-9952</a><br>
==============================<u></u>==================<br></div><div class="HOEnZb"><div class="h5">
______________________________<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></div>