Recommended Draft Policy ARIN-2016-3: Alternative simplified criteria for justifying small IPv4 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

Tracking Information

Discussion Tracking

Mailing List:

Formal introduction on PPML on 24 May 2016

Origin - ARIN-prop-228

Draft Policy -24 May 2016

Recommended: 21 February 2017

Moved to Last Call: 10 April 2017

Recommended to Board: 23 May 2017

Adopted by Board - 22 June 2017

Implemented by staff - 8 August 2017

Public Policy Mailing List

ARIN Public Policy Meeting:

ARIN Advisory Council:

AC Shepherds:
David Huberman, Owen DeLong

ARIN Board of Trustees:

Revisions:

Revised: 11 September 2016

Revised: 31 January 2017

Implementation:

21 February 2017

Recommended Draft Policy ARIN-2016-3: Alternative simplified criteria for justifying small IPv4 transfers

Version Date: 21 February 2017

AC’s Statement of Conformance with ARIN’s Principles of Internet Number Resource Policy

This proposal is technically sound and enables fair and impartial number policy by allowing transfers to specified recipients of blocks of a certain size to occur without a needs assessment performed by ARIN staff. The Staff and Legal Assessment raised no material issues, and there has been consistent support on both the mailing list and at the Dallas ARIN meeintg for incorporating this mechanism into NRPM.

Problem Statement:

ARIN transfer policy currently inherits all its demonstrated need requirements for IPv4 transfers from NRPM sections 4. Because that section was written primarily to deal with free pool allocations, it is much more complicated than is really necessary for transfers.

This proposal allows organizations using 80% of their current space to double their current holdings via 8.3 or 8.4 specified transfers, up to a /16 equivalent.

Policy Statement:

Add a new section:

8.5.7 Alternative Additional IPv4 Address Block Criteria

In lieu of 8.5.5 and 8.5.6, organizations may qualify for additional IPv4 address blocks by demonstrating 80% utilization of their currently allocated space. If they do so, they qualify to receive one or more transfers up to the total size of their current ARIN IPv4 address holdings, with a maximum size of /16.

An organization may qualify via 8.5.7 for a total of a /16 equivalent in any 6 month period.

##########

Earlier Version

##########

Draft Policy ARIN-2016-3: Alternative simplified criteria for justifying small IPv4 transfers

Version Date: 31 January 2017

Problem Statement:

ARIN transfer policy currently inherits all its demonstrated need requirements for IPv4 transfers from NRPM sections 4. Because that section was written primarily to deal with free pool allocations, it is much more complicated than is really necessary for transfers.

This proposal allows organizations using 80% of their current space to double their current holdings via 8.3 or 8.4 specified transfers, up to a /16 equivalent.

Policy text:

Add a new section:

8.5.7 Alternative Additional IPv4 Address Block Criteria

In lieu of 8.5.5 and 8.5.6, organizations may qualify for additional IPv4 address blocks by demonstrating 80% utilization of their currently allocated space. If they do so, they qualify to receive one or more transfers up to the total size of their current ARIN IPv4 address holdings, with a maximum size of /16.

An organization may only qualify under 8.5.7 once every 6 months.

##########

ARIN STAFF & LEGAL ASSESSMENT

Draft Policy ARIN-2016-3

ALTERNATIVE SIMPLIFIED CRITERIA FOR JUSTIFYING SMALL IPv4 TRANSFERS

Date of Assessment: 07 February 2017

  1. Summary (Staff Understanding)

*NOTE: This assessment was completed with the knowledge that 2016-05 will be implemented prior to this policy change being implemented.

Draft Policy 2016-3 allows for organizations to receive up to at least twice the size aggregate of their current holdings (up to and including a /16) through an 8.3 or 8.4 specified transfer, as long as they can show 80% utilization of their current holdings. Organizations would only be able to qualify for this option once every six months. Organizations would still be able to qualify under the current policy by showing their 24 month need.

  1. Comments

A. ARIN Staff Comments: This policy could be implemented as written.

B. ARIN General Counsel – Legal Assessment

* Does not create material legal issues.

* Counsel questions whether ‘small’ is accurate, and should be deleted.

  1. Resource Impact

Implementation of this policy would have minimal resource impact. It is estimated that implementation would 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

  1. Proposal / Draft Policy Text Assessed

Draft Policy ARIN-2016-3: Alternative simplified criteria for justifying small IPv4 transfers

Version Date: 31 January 2017

Problem Statement:

ARIN transfer policy currently inherits all its demonstrated need requirements for IPv4 transfers from NRPM sections 4. Because that section was written primarily to deal with free pool allocations, it is much more complicated than is really necessary for transfers.

This proposal allows organizations using 80% of their current space to double their current holdings via 8.3 or 8.4 specified transfers, up to a /16 equivalent.

Policy text:

Add a new section:

8.5.7 Alternative Additional IPv4 Address Block Criteria

In lieu of 8.5.5 and 8.5.6, organizations may qualify for additional IPv4 address blocks by demonstrating 80% utilization of their currently allocated space. If they do so, they qualify to receive one or more transfers up to the total size of their current ARIN IPv4 address holdings, with a maximum size of /16.

An organization may only qualify under 8.5.7 once every 6 months.

END

##########

Earlier Version

##########

Draft Policy ARIN-2016-3: Alternative simplified criteria for justifying small IPv4 transfers

Version Date: 11 September 2016

Problem Statement:

ARIN transfer policy currently inherits all its demonstrated need requirements for IPv4 transfers from NRPM sections 4. Because that section was written primarily to deal with free pool allocations, it is much more complicated than is really necessary for transfers. This proposal allows organizations using 80% of their current space to double their current holdings via 8.3 or 8.4 specified transfers, up to a /16 equivalent.

In section 8.3, replace:

The recipient must demonstrate the need for up to a 24-month supply of IP address resources under current ARIN policies and sign an RSA.

with:

The recipient must sign an RSA and either:

  • Demonstrate 80% utilization of their currently allocated space to qualif to receive one or more transfers up to the total size of their current ARIN IPv4 address holdings, with a maximum size of /16; or

  • Demonstrate the need for up to a 24-month supply of IP address space under current ARIN policies.

In section 8.4, replace:

Recipients within the ARIN region must demonstrate the need for up to a 24-month supply of IPv4 address space.

with:

Recipients within the ARIN region must either:

  • Demonstrate 80% utilization of their currently allocated space to qualify to receive one or more transfers up to the total size of their current ARIN IPv4 address holdings, with a maximum size of /16; or

  • Demonstrate the need for up to a 24-month supply of IPv4 address space under current ARIN policies.

Comments:

Timetable for implementation: immediate

Anything else

Notes on interaction with existing IPv4 assignment policy:

Organizations requiring a transfer larger than a /16 may either: transfer a /16 at a time, and re-certify 80% utilization before receiving each new /16, or continue to qualify under NRPM 4.2 or 4.3, which allows an organization to qualify for a 24-month supply of IPv4 space via transfer.

An organization holding a /22 and a /20 which are 80% utilized can qualify for one or more transfers over a two year period up to a /22 plus a /20 (up to 5120 IPs). After two years, or at any time that an organization wants more than the amount of transfer space approved, the organization can re-certify 80% utilization and get a new doubling window.

##########

Earlier Version

##########

Draft Policy ARIN-2016-3: Alternative simplified criteria for justifying small IPv4 transfers

Version Date: 24 May 2016

Problem Statement:

ARIN transfer policy currently inherits all its demonstrated need requirements for IPv4 transfers from NRPM sections 4. Because that section was written primarily to deal with free pool allocations, it is much more complicated than is really necessary for transfers.

This proposal allows organizations using 80% of their current space to double their current holdings via 8.3 or 8.4 specified transfers, up to a certain size, such as /12 or /16. Existing section 4 need demonstration rules would continue to apply to organizations who request more than a [/12 | /16] of space.

Policy statement:

In section 8.3, replace:

The recipient must demonstrate the need for up to a 24-month supply of IP address resources under current ARIN policies and sign an RSA.

with:

The recipient must sign an RSA and either:

 Demonstrate 80% utilization of their currently allocated space to qualify to receive one or more transfers up to the total size of their current ARIN IPv4 address holdings, with a maximum size of [/12 | /16], or

 Demonstrate the need for up to a 24-month supply of IP address resources under current ARIN policies.

In section 8.4, replace:

Recipients within the ARIN region must demonstrate the need for up to a 24-month supply of IPv4 address space.

with:

Recipients within the ARIN region must either:

 Demonstrate 80% utilization of their currently allocated space to qualify to receive one or more transfers up to the total size of their current ARIN IPv4 address holdings, with a maximum size of [/12 | /16], or   
  Demonstrate the need for up to a 24-month supply of IPv4 address space under current ARIN policies.

Timetable for implementation: immediate

Anything else:

The [/12 | /16] notation for the cap is intended to offer some suggestions about what the cap should be. It is our intention that this will be replaced with a single value prior to this becoming a recommended draft.

Notes on interaction with existing IPv4 assignment policy:

Organizations requiring a transfer larger than a [/12 | /16] may either: transfer a [/12 | /16] at a time, and re-certify 80% utilization before receiving each new [/12 | /16], or continue to qualify under NRPM 4.2 or 4.3, which allows an organization to qualify for a 24-month supply of IPv4 space via transfer. (That means, for example, that an organization that has used a /13 in less than a year would ordinarily qualify to receive a /12 via transfer.)

An organization holding a /22 and a /20 which are 80% utilized can qualify for one or more transfers over a two year period up to a /22 plus a /20 (up to 5120 IPs). After two years, or at any time that an organization wants more than the amount of transfer space approved, the organization can re-certify 80% utilization and get a new doubling window.

#####################################################################################

ARIN STAFF & LEGAL ASSESSMENT

Draft Policy ARIN-2016-3

ALTERNATIVE SIMPLIFIED CRITERIA FOR JUSTIFYING SMALL IPv4 TRANSFERS

Date of Assessment: 23 September 2016

1. Summary (Staff Understanding)

Draft Policy 2016-3 allows for organizations to double the size of their current IPv4 holdings (up to and including a /16) through an 8.3 or 8.4 specified transfer without a needs assessment being conducted by ARIN staff, as long as they can demonstrate 80% utilization of their current holdings. Organizations would still be able to qualify under the current policy by showing their 24 month need.

2. Comments

A. ARIN Staff Comments:

*This policy could be implemented as written.

B. ARIN General Counsel – Legal Assessment

*This policy presents no material legal issues.

3. Resource Impact

Implementation of this policy would have minimal resource impact. It is estimated that implementation would 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

4. Proposal / Draft Policy Text Assessed

Draft Policy ARIN 2016-3: Alternative Simplified Criteria for Justifying Small IPv4 Transfers

Date: 11 September 2016

Problem Statement:

ARIN transfer policy currently inherits all its demonstrated need
requirements for IPv4 transfers from NRPM sections 4. Because that section
was written primarily to deal with free pool allocations, it is much more
complicated than is really necessary for transfers. This proposal allows
organizations using 80% of their current space to double their current
holdings via 8.3 or 8.4 specified transfers, up to a /16 equivalent.

In section 8.3, replace:
The recipient must demonstrate the need for up to a 24-month supply of IP
address resources under current ARIN policies and sign an RSA.

with:

The recipient must sign an RSA and either:

  • Demonstrate 80% utilization of their currently allocated space to qualify
    to receive one or more transfers up to the total size of their current ARIN
    IPv4 address holdings, with a maximum size of /16; or

  • Demonstrate the need for up to a 24-month supply of IP address space under
    current ARIN policies.

In section 8.4, replace:

Recipients within the ARIN region must demonstrate the need for up to a
24-month supply of IPv4 address space.

with:

Recipients within the ARIN region must either:

  • Demonstrate 80% utilization of their currently allocated space to qualify
    to receive one or more transfers up to the total size of their current ARIN
    IPv4 address holdings, with a maximum size of /16; or

  • Demonstrate the need for up to a 24-month supply of IPv4 address space
    under current ARIN policies.

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.