<p dir="ltr">Question: how often does Arin staff encounter this anomaly if I can call it that?</p>
<p dir="ltr">RD</p>
<div class="gmail_quote">On Apr 11, 2016 12:00 PM, <<a href="mailto:arin-ppml-request@arin.net">arin-ppml-request@arin.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send ARIN-PPML mailing list submissions to<br>
<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<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>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:arin-ppml-request@arin.net">arin-ppml-request@arin.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:arin-ppml-owner@arin.net">arin-ppml-owner@arin.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of ARIN-PPML digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Revision to Text of Draft Policy ARIN-2015-2 (Christian Tacit)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 11 Apr 2016 14:50:32 +0000<br>
From: Christian Tacit <<a href="mailto:ctacit@tacitlaw.com">ctacit@tacitlaw.com</a>><br>
To: "<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>
Subject: [arin-ppml] Revision to Text of Draft Policy ARIN-2015-2<br>
Message-ID: <9851d5ee8a334febaf54742028e5bb1b@S05-MBX03-12.S05.local><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Dear Community Members:<br>
I am writing to advise of additional changes made today to the text of Draft Policy ARIN-2015-2.<br>
In the Staff and Legal analysis obtained, General Counsel expressed concerns about the proposed definitions of "affiliated" and "control". In light of these concerns and other efforts to simplify the text further, I have amended the text once again. The new amendments achieve the same intent as the previous language using much simpler and more concise language. The revised draft proposal is:<br>
<br>
"Problem Statement:<br>
<br>
Organizations that obtain a 24 month supply of IP addresses via the transfer market and then have an unexpected change in business plan are unable to move IP addresses to the proper RIR within the first 12 months of receipt.<br>
<br>
Policy statement:<br>
Replace 8.4, bullet 4, to read:<br>
"Source entities within the ARIN region must not have received a transfer, allocation, or assignment of IPv4 number resources from ARIN for the 12 months prior to the approval of a transfer request, unless either the source and recipient entities own or control each other or are under common ownership or control. This restriction does not include M&A transfers."<br>
Comments: Organizations that obtain a 24 month supply of IP addresses via the transfer market and then have an unexpected change in business plan are unable to move IP addresses to the proper RIR within the first 12 months of receipt. The need to move the resources does not flow from ARIN policy, but rather from the requirement of certain registries outside the ARIN region to have the resources moved in order to be used there.<br>
The intention of this change is to allow organizations to perform inter-RIR transfers of space received via an 8.3 transfer regardless of the date transferred to ARIN. A common example is that an organization acquires a block located in the ARIN region, transfers it to ARIN, then 3 months later, the organization announces that it wants to launch new services out of region. Under current policy, the organization is prohibited from moving some or all of those addresses to that region's Whois if there is a need to move them to satisfy the rules of the other region requiring the movement of the resources to that region in order for them to be used there. Instead, the numbers are locked in ARIN's Whois. It's important to note that 8.3 transfers are approved for a 24 month supply, and it would not be unheard of for a business model to change within the first 12 months after approval. The proposal also introduces a requirement for an affiliation relationship between the source and r<br>
ecipient entity, based on established corporate law principles, so as to make it reasonably likely that eliminating the 12 month anti-flip period in that situation will meet the needs of organizations that operate networks in more than one region without encouraging abuse.<br>
a. Timetable for implementation: Immediate<br>
b. Anything else: N/A"<br>
Chris Tacit<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.arin.net/pipermail/arin-ppml/attachments/20160411/d3ecf3f6/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.arin.net/pipermail/arin-ppml/attachments/20160411/d3ecf3f6/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
ARIN-PPML mailing list<br>
<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a><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>
<br>
End of ARIN-PPML Digest, Vol 130, Issue 18<br>
******************************************<br>
</blockquote></div>