Draft Policy ARIN-2017-9: Clarification of Initial Block Size for IPv4 ISP 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.

Draft Policy ARIN-2017-9: Clarification of Initial Block Size for IPv4 ISP Transfers

Status: Abandoned by the ARIN Advisory Council

Tracking Information

Discussion Tracking

Mailing List:

Formal introduction on PPML on 21 November 2017

Origin - ARIN-prop-244

Draft Policy - 21 November 2017

Abandoned - 23 April 2018

Public Policy Mailing List

ARIN Public Policy Meeting:

ARIN Advisory Council:

AC Shepherds:
David Farmer, John Springer

ARIN Board of Trustees:

Revisions:

Revised - 24 January 2018

Implementation:

Version Date: 24 January 2018

Problem Statement:

It was noted in the ARIN 40 Policy Experience Report, that there is an inconsistency in the initial block size for ISPs. Section 4.2.2 notes that the initial ISP block size should be /21 whereas the initial block size in 8.5.4 is noted as “minimum transfer size” which is effectively a /24. This causes ISP organizations to be approved for different initial block size depending on if they first apply for a transfer directly under section 8 or if they apply for a block under section 4. This policy is intended to clarify this issue, by setting a consistent ISP initial IPv4 block size. It was noted that ARIN staff current operational practice is to allow qualified ISPs an initial /21 for Section 8 transfers when they first apply and are approved under section 4. If an organization applies under section 8 first they are initially qualified for a /24; larger allocations require additional documentation as noted in 8.5.5.

Policy statement:

Replace section 8.5.4;

8.5.4. Initial block

Organizations without direct assignments or allocations from ARIN qualify for the transfer of an initial IPv4 block, a /24 for assignments or a /24 up to a /21 for allocations.

Comments:

Timetable for implementation: Immediate

Anything Else:

The ARIN 40 Policy Experience Report is available at;

Slides: https://www.arin.net/vault/participate/meetings/reports/ARIN_40/PDF/PPM/sweeting-policy-experience.pdf

Transcript: https://www.arin.net/vault/participate/meetings/reports/ARIN_40/ppm1_transcript.html#anchor_5

Video: https://www.youtube.com/watch?v=QVsfVMG_6fA

Slides 10 - 13, located in the video from 6:30 to 8:30, are the relevant portion of the report, questions from the audience follow.

##########

Earlier Version

##########

Version Date: 21 November 2017

**Problem Statement: **

It was noted at the ARIN 40 Policy Experience Report, that there is an inconsistency in the initial block size for ISPs. Section 4.2.2 notes that the initial ISP block size should be /21 whereas the initial block size in 8.5.4 is noted as “minimum transfer size” which is effectively a /24. The intent of the new 8.5.4 was to match the previous policy. This policy is intended to clarify this issue. It was noted that ARIN staff current operational practice is to allow ISPs an initial /21 for Section 8 transfers.

**Policy statement: **

Add the following to 8.5.4

ISP organizations without direct assignments or allocations from ARIN qualify for an initial allocation of up to a /21.

Comments:

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.