Draft Policy ARIN-2014-15: Allow Inter-RIR ASN Transfers [Archived]
OUT OF DATE?
Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.
Status: Abandoned
Tracking Information
Discussion Tracking
Mailing List:
Formal introduction on PPML on 16 May 2014
Origin - ARIN-prop-205
Draft Policy - 16 May 2014
Revised with staff/legal assessment - 28 July 2014
Abandoned by the AC - 15 October 2014
ARIN Public Policy Meeting:
ARIN Advisory Council:
AC Shepherds:
Scott Leibrand, David Farmer
ARIN Board of Trustees:
Revisions:
Implementation:
Draft Policy ARIN-2014-15
Allow Inter-RIR ASN Transfers
Revised: 19 June 2014
Problem Statement:
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.
Policy Statement:
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
##########
ARIN Staff and Legal Assessment
Proposal: ARIN-2014-15: Allow Inter-RIR ASN Transfers
Date of Assessment: 1 July 2014
- Summary (Staff Understanding)
This proposal would:
allow inter-RIR transfer of AS numbers
enforce the 12 month waiting period only on resources of the same type exempt resources received via M&A transfer
- Comments
A. ARIN Staff Comments
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.
B. ARIN General Counsel - Legal Assessment
“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.”
- Resource Impact
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:
Future impact from RPKI implementation could involve either some kind of RIR<->IANA<->RIR coordination system or ERX for ASNs
Updated guidelines and internal procedures
Staff training
- Proposal/Draft Policy Text Assessed
Draft Policy ARIN-2014-15 Allow Inter-RIR ASN Transfers
Revised: 19 June 2014
Problem Statement:
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.
Policy Statement:
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
Older version
Draft Policy ARIN-2014-15
Allow Inter-RIR ASN Transfers
Date: 16 May 2014
Problem Statement:
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.
Policy Statement:
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 “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 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
OUT OF DATE?
Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.