Recommended Draft Policy ARIN-2021-4

Clarifications to Sections 6.5.2.1, 8.3, 8.4 and 8.5.6

Status: Pending Board of Trustees Review
Shepherds: Alyssa Quinn, Andrew Dul

Current Text (2 May 2022)

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

This Draft Policy is fair, impartial, and technically sound. The intent of this policy is to clarify the language in sections 6.5.2.1, 8.3, and 8.4 with respect to ASN-only transactions and the term “number resources”. It also clarifies that Section 8.5.6 refers specifically to IPv4.

Problem Statement:

The current language in Sections 6.5.2.1, 8.3 and 8.4 is not clear regarding ASN-only transactions as well as the term “number resources”. The current language in Section 8.5.6 is not clear with regard to additional IPv4 space.

Policy statement:

In section 6.5.2.1 g.,

Replace

”Partial returns of any IPv6 allocation that results in less than a /36 of holding are not permitted regardless of the ISP’s current or former IPv4 number resource holdings.”

with

”Partial returns of any IPv6 allocation that results in less than a /36 of holding are not permitted regardless of the ISP’s current or former IPv4 address holdings.”

In section 8.3,

Replace

“In addition to transfers under section 8.2, IPv4 numbers resources and ASNs may be transferred according to the following conditions.”

with

“In addition to transfers under section 8.2, IPv4 addresses or ASNs may be transferred according to the following conditions.”

Replace

“The source entity must be the current registered holder of the IPv4 address resources, and not be involved in any dispute as to the status of those resources.”

with

“The source entity must be the current registered holder of the IPv4 addresses or ASNs and not be involved in any dispute as to the status of those resources.”

In Section 8.4:

Replace

“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.”

with

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

Replace

“The source entity must be the current rights holder of the IPv4 address resources recognized by the RIR responsible for the resources, and not be involved in any dispute as to the status of those resources.”

with

“The source entity must be the current rights holder of the IPv4 addresses or ASN recognized by the RIR responsible for the resources, and not be involved in any dispute as to the status of those resources.”

In Section 8.5.6:

Replace

“Organizations with direct assignments or allocations from ARIN must have efficiently utilized at least 50% of their cumulative IPv4 address blocks in order to receive additional space. This includes all space reassigned to their customers.”

with

“Organizations with direct assignments or allocations from ARIN must have efficiently utilized at least 50% of their cumulative IPv4 address blocks in order to receive additional IPv4 addresses. This includes all IPv4 space reassigned to their customers.”

Comments:

These changes were originally included in ARIN-edit-2021-1. Staff and Legal review of ARIN-edit-2021-1 on June 14, 2021 indicated that some changes were not editorial in nature. The editorial changes went forward in ARIN-edit-2021-1 and the non-editorial changes are included here.

Timetable for Implementation: Immediate

Staff Understanding

ARIN-2021-4 encapsulates the non-editorial changes pointed out in ARIN-edit-2021-1. It offers clarifications to ASN-only transaction language, use of “number resources,” and resource type in Section 8.5.6.

If the intent is indeed to standardize “IPv4 addresses,” staff recommends changing “in order to receive additional IPv4 space” to read “in order to receive additional IPv4 addresses.” The AC shepherds may also wish to correct another instance of “IPv4 number,” in Section 6.5.2.1., bullet g.

Additionally, staff suggests correcting the second change in 8.4 to read “The source entity must be the current rights holder of the IPv4 addresses or ASNs…” to align with other plural references to ASNs.

The Draft Policy text is clear and understandable.

Implementable as Written?: Yes

Impact on ARIN Registry Operations and Services:

None.

Legal Review:

No material legal issue.

Implementation Timeframe Estimate: Three months

Implementation Requirements:

  • Staff training
  • Updates to public documentation
  • Updates to internal procedures and guidelines

Proposal/Draft Policy Text Assessed: 20 January 2022

History and Earlier Versions

History
Action Date
Proposal 17 August 2021
Draft Policy 24 August 2021
Revised 20 January 2022
Recommended 2 March 2022
Last Call 2 May 2022
Advanced to the Board of Trustees 19 May 2022