<div dir="ltr">For context, this revision just brings the policy in line with what was discussed at the PPC, addressing a concern raised with the previous iteration of this policy (that transferring ASN resources should not block receipt of IPv4 resources, or vice versa).<div>
<br></div><div>-Scott</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 28, 2014 at 2:26 PM, ARIN <span dir="ltr"><<a href="mailto:info@arin.net" target="_blank">info@arin.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Draft Policy ARIN-2014-15<br>
Allow Inter-RIR ASN Transfers<br>
<br>
ARIN-2014-15 has been revised.<br>
<br>
Draft Policy ARIN-2014-15 is below and can be found at:<br>
<a href="https://www.arin.net/policy/proposals/2014_15.html" target="_blank">https://www.arin.net/policy/<u></u>proposals/2014_15.html</a><br>
<br>
We are also attaching a staff assessment.<br>
<br>
You are encouraged to discuss the merits and your concerns of Draft<br>
Policy 2014-15 on the Public Policy Mailing List.<br>
<br>
The AC will evaluate the discussion in order to assess the conformance<br>
of this draft policy with ARIN's Principles of Internet Number Resource<br>
Policy as stated in the PDP. Specifically, these principles are:<br>
<br>
* Enabling Fair and Impartial Number Resource Administration<br>
* Technically Sound<br>
* Supported by the Community<br>
<br>
The ARIN Policy Development Process (PDP) can be found at:<br>
<a href="https://www.arin.net/policy/pdp.html" target="_blank">https://www.arin.net/policy/<u></u>pdp.html</a><br>
<br>
Draft Policies and Proposals under discussion can be found at:<br>
<a href="https://www.arin.net/policy/proposals/index.html" target="_blank">https://www.arin.net/policy/<u></u>proposals/index.html</a><br>
<br>
Regards,<br>
<br>
Communications and Member Services<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
## * ##<br>
<br>
<br>
Draft Policy ARIN-2014-15<br>
Allow Inter-RIR ASN Transfers<br>
<br>
Revised: 19 June 2014<br>
<br>
Problem Statement:<br>
<br>
We already allow transfer of ASNs within the ARIN region. Recently APNIC implemented a policy allowing for Inter-regional ASN transfers to RIRs with reciprocal policies. This change in language would allow for ASN transfers to and from the APNIC region.<br>
<br>
Policy Statement:<br>
<br>
Add "or ASNs to be transferred, as" to the first bullet point under Conditions on source of the transfer, so that it reads: "The source entity must be the current rights holder of the IPv4 address resources or ASNs to be transferred, as recognized by the RIR responsible for the resources, and not be involved in any dispute as to the status of those resources."<br>
<br>
Change "IPv4 number resources" to "that same resource type (IPv4 number resources or ASNs)", so that the fourth bullet point reads: "Source entities within the ARIN region must not have received a transfer, allocation, or assignment of that same resource type (IPv4 number resources or ASNs) from ARIN for the 12 months prior to the approval of a transfer request. This restriction does not include M&A transfers."<br>
<br>
Timetable for implementation: Immediate<br>
<br>
##########<br>
<br>
ARIN Staff and Legal Assessment<br>
<br>
Proposal: ARIN-2014-15: Allow Inter-RIR ASN Transfers<br>
<br>
Date of Assessment: 1 July 2014<br>
<br>
1. Summary (Staff Understanding)<br>
<br>
This proposal would:<br>
• allow inter-RIR transfer of AS numbers<br>
• enforce the 12 month waiting period only on resources of the same type exempt resources received via M&A transfer<br>
<br>
2. Comments<br>
<br>
A. ARIN Staff Comments<br>
<br>
The impact of inter-RIR transfers of ASNs on ARIN from both an operational and development perspective are nominal today, but pose an unknown (but at least moderate) impact over the medium-term due to potentially significant impacts for additional requirements and/or specifications necessary for RPKI support of inter-RIR ASN transfers.<br>
<br>
B. ARIN General Counsel - Legal Assessment<br>
<br>
"The only material legal risk relates to the RPKI issue and policy consideration can take place as continued work by the management and staff of ARIN may be able to fully address this concern before the community considers the policy matter in Baltimore."<br>
<br>
3. Resource Impact<br>
<br>
This policy would have minimal to moderate resource impact from an implementation aspect. It is estimated that implementation would occur within 3 - 9 months after ratification by the ARIN Board of Trustees. The following would be needed in order to implement:<br>
<br>
Future impact from RPKI implementation could involve either some kind of RIR<->IANA<->RIR coordination system or ERX for ASNs<br>
Updated guidelines and internal procedures<br>
Staff training<br>
<br>
4. Proposal/Draft Policy Text Assessed<br>
<br>
Draft Policy ARIN-2014-15 Allow Inter-RIR ASN Transfers<br>
Revised: 19 June 2014<br>
<br>
Problem Statement:<br>
We already allow transfer of ASNs within the ARIN region. Recently APNIC implemented a policy allowing for Inter-regional ASN transfers to RIRs with reciprocal policies. This change in language would allow for ASN transfers to and from the APNIC region.<br>
<br>
Policy Statement:<br>
Add "or ASNs to be transferred, as" to the first bullet point under Conditions on source of the transfer, so that it reads: "The source entity must be the current rights holder of the IPv4 address resources or ASNs to be transferred, as recognized by the RIR responsible for the resources, and not be involved in any dispute as to the status of those resources." Change "IPv4 number resources" to "that same resource type (IPv4 number resources or ASNs)", so that the fourth bullet point reads: "Source entities within the ARIN region must not have received a transfer, allocation, or assignment of that same resource type (IPv4 number resources or ASNs) from ARIN for the 12 months prior to the approval of a transfer request. This restriction does not include M&A transfers." Timetable for implementation: Immediate<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.</blockquote></div><br></div>