ARIN-2018-1: Allow Inter-regional 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: Implemented 7 March 2019

Tracking Information

Discussion Tracking

Mailing List:

Formal introduction on PPML on 31 January 2018

Proposal - ARIN-prop-250

Draft Policy - 31 January 2018

Recommended - 23 April 2018

Moved to Last Call - 10 October 2018

Moved to Board - 20 November 2018

Adopted - 13 December 2018

Public Policy Mailing List

ARIN Public Policy Meeting:

ARIN Advisory Council:

AC Shepherds:
Alison Wood, Chris Tacit

ARIN Board of Trustees:

13 December 2018

Revisions:

Implementation:

7 March 2019

Version Date: 31 January 2018

AC Assessment of Conformance with the Principles of Internet Number Resource Policy:

With the combination of positive community feedback and communication from IANA, the ARIN AC chose to recommend moving 2018-1 to a Recommended Draft state. Previous concerns with RPKI are no longer an issue and are not a barrier to inter-RIR ASN transfers.

Problem Statement:

There is a need to allow RIR transfers of ASNs with RIRs with an equivalent transfer policy.

P** olicy Statement:**

Change the first sentence in section 8.4 from:

“Inter-regional transfers may take place only via RIRs who agree to the transfer and share reciprocal, compatible, needs-based policies.”

To:

“Inter-regional transfers of IPv4 number resources and ASNs may take place only via RIRs who agree to the transfer and share reciprocal, compatible needs-based policies.”

Comments:

Timetable for implementation: Immediate

##########

ARIN STAFF & LEGAL ASSESSMENT

Draft Policy ARIN-2018-1

Allow Inter-regional ASN Transfers

Date of Assessment: 19 February 2018

1. Summary (Staff Understanding)

Draft Policy 2018-1 NRPM section 8.4 adds the ability for ARIN staff to transfer ASNs between RIRs thatshare reciprocal, compatible, needs-based policies.

2. Comments

A. ARIN Staff Comments

* This is a very straight forward change to NRPM8.4. Inter-RIR Transfers to Specified Recipients and easy to implement. Once implemented ARIN staff will be able to approve ASN transfers both into and out of the ARIN region to RIRs that share reciprocal, compatible, needs-based policies. As of this date that would include APNIC and RIPE NCC.

* In our previous assessment ofDraft Policy ARIN-2014-15 Allow Inter-RIR ASN Transfers, we noted minimal work was necessary with the exception of the RPKI. Today, the RPKI TA contains all AS numbers(a change to the RPKI commonly referred to as 0/0), making RPKI a non-issue with regard to inter-RIR transfers. However, inter-RIR transfersof AS numbers would greatly complicate any future implementation of an RPKI Global Trust Anchor (GTA) if that were ever to occur.

* During the previous assessment transfers were not fully automated within ARIN’s registry system. ARIN’s systems now conduct transfers via ARIN Online, a facility giving ARIN proper audit trails and the generation of publicly available transfer log (used by third parties to monitor ARIN’s transfer activity). These automated processes will need to be modified to accommodate Inter-RIR transfers, with an estimated effort of between 1 and 2 months.

B. ARIN General Counsel – Legal Assessment

* No material legal risk in this policy

3. Resource Impact

Implementation of this policy would have minimal impact.It is estimated that implementation could occur within 3 months after ratification by the ARIN Board of Trustees. The following would be needed in order to implement:

* Updated guidelines and internal procedures

* Staff training

* Between 1 and 2 months of engineering workwill be required

4. Proposal/Draft Policy Text Assessed

Draft Policy 2018-1: Allow Inter-regional ASN Transfers s