Recommended Draft Policy ARIN-2020-5

Clarify and Update Requirements for Allocations to Downstream Customers

Status: Recommended for adoption
Shepherds: Kat Hunter, Rob Seastrom

Current Text (22 July 2020)

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

This Draft Policy is fair, impartial, and technically sound. This draft policy replaces outdated RFC2050 references in Sections 4.2.3.4.1. and 4.2.3.6. with references to the end user assignment utilization requirements in Section 4.3.3.

Problem Statement:

A recent Policy Experience Report demonstrated the fact that the existing Section 4.2.3.6 references RFC2050, which is obsolete, and is not synchronized with utilization requirements carried in Section 4.3.3, specifically the utilization rate.

Policy Statement:

Given that RFC7020, which supercedes RFC2050, no longer carries specific utilization requirements for downstream customers of ISPs, its reference may be removed from Section 4.2.3.6, instead referencing 4.3.3 (currently, 50% utilization within 24 months) to harmonize the utilization requirements of both ISPs and their downstream customers.

Removing these references from Section 4.2.3.6 will simplify the language of that section.

Replace sections 4.2.3.4.1 and sections 4.2.3.6 with the following text:

4.2.3.4.1. Utilization

A downstream customer requesting address space from an upstream ISP must document a plan to the allocating ISP for their utilization to conform to Section 4.3.3. Reassignment and reallocation information for prior allocations must show that each customer meets the 80% utilization criteria and must be available via SWIP / a distributed service which meets the standards set forth in section 3.2 prior to your issuing them additional space.

4.2.3.6. Reassignments to Multihomed Downstream Customers

If a downstream customer has a requirement to multihome, that requirement alone will serve as justification for a /24 allocation. Downstream customers must provide contact information for all of their upstream providers to the ISP from whom they are requesting a /24, and utilize a border routing protocol between the customer and the ISP. Customers may receive a /24 from only one of their upstream providers under this policy without providing additional justification. ISPs may demonstrate they have made an assignment to a downstream customer under this policy by supplying ARIN with the information they collected from the customer, as described above, or by identifying the AS number of the customer.

Timetable for Implementation: Immediate

Summary (Staff Understanding)

ARIN-2020-5 replaces RFC2050 references in Sections 4.2.3.4.1. and 4.2.3.6. with references to the End user assignment utilization requirements in Section 4.3.3.

Comments

ARIN Staff Comments

ARIN-2020-5 would align requirements for downstream customers with existing ARIN End user policy and remove outdated RFC2050 references, which have been a source of confusion in the past.

This text is clear and understandable, and can be implemented as written.

ARIN General Counsel – Legal Assessment

No material legal issue.

Resource Impact

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

  • Staff training
  • Updated guidelines and internal procedures
  • Standard documentation updates

Proposal/Draft Policy Text Assessed: 22 July 2020 Version

History and Earlier Versions

History
Action Date
Proposal 19 May 2020
Draft Policy 23 June 2020
Revised 22 July 2020

Advisory Council

Board of Trustees

ARIN Public Policy Meetings