Intra-RIR transfer policy proposal

Legend
Added
Deleted

Summary of Proposal:

Presently the allocation period for all allocations and transfers from within the RIPE NCC service region is 3 month. While this makes sense for new RIPE allocations, where there is a shortage of supply, in the case of transfers often the source is from a larger dormant block held by an LIR. It makes sense to increase the period of use for transfers to better match the quantity that is available and needed from this larger supply pool.

Policy Text

Current

[Following text is to be modified from the RIPE Policy Document “IPv4 ~~“IPv4~~ Address Allocation and Assignment Policies for the RIPE NCC Service Region”, ~~Region Link: http://www.ripe.net/ripe/docs/ipv4-policies ”,~~ if the proposal reaches consensus. This will result in a new policy section.]

5.5 Transfers of Allocations

Any LIR is allowed to re-allocate complete or partial blocks of IPv4 address space that were previously allocated to them by either the RIPE NCC or the IANA. Such address space must not contain any block that is assigned to an End User.

Address space may only be re-allocated to another LIR that is also a member of the RIPE NCC. The block that is to be re-allocated must not be smaller than the minimum allocation block size at the time of re-allocation. An LIR may only receive a transferred allocation after their need is evaluated and approved by the RIPE NCC, following the policies set for receiving further allocations within RIPE region (see the Section 5.3 Additional Allocations of this document).

[…]

New

[Following text will replace section 5.5 in the RIPE Policy Document “IPv4 ~~“IPv4~~ Address Allocation and Assignment Policies for the RIPE NCC Service Region”, ~~Region Link: http://www.ripe.net/ripe/docs/ipv4-policies ”,~~ if the proposal reaches consensus. This will result in a new policy section. NOTE: added a new third paragraph.]

5.5 Transfers of Allocations

Other than for an additional allocation, for the purpose of determining need, a period of 24 months is used in evaluating a transferred allocation.

[…]

Rationale:

a. Arguments Supporting the Proposal

24 month period will allow the block size to more closely match the block size available for transfer from the provider
24 month period will allow the block size to match the needs of the requestor and allow the requestor to do 2 years network planning with more certainty.

b. Arguments Opposing the Proposal

New allocation period of 3 months will differ from the transfer period of 24 months and may confuse requestors (until new allocations run out).

Note: In order to provide additional information related to the proposal, details of an impact analysis carried out by the RIPE NCC are documented below. The projections presented in this analysis are based on existing data and should be viewed only as an indication of the possible impact that the policy might have if the proposal is accepted and implemented.

A. RIPE NCC's Understanding of the Proposed Policy

The RIPE NCC understands that the policy proposal intends to change the allocation period for IPv4 transfers. If the proposal is accepted, this period will increase to 24 months.

B. Impact of Policy on Registry and Addressing System

Address/Internet Number Resource Consumption: