This policy proposal has been accepted
The new RIPE Document is: ripe-528

Post-depletion IPv4 address recycling

This proposal intends to define better how the address management of returned IPv4 address space will be performed when the final /8 policy comes into effect.

Summary of proposal:

This proposal intends to define better how the address management of returned IPv4 address space will be performed when the final /8 policy comes into effect.

Policy text:

Current

[Following text is to be replaced in the RIPE Policy Document IPv4 Address Allocation and Assignment Policy for the RIPE NCC Service Region, if the proposal reaches consensus. This would result in a new policy section.]

 

5.6 Use of last /8 for PA Allocations

The following policies come into effect as soon as RIPE NCC is required to make allocations from the final /8 it receives from the IANA. From then on the distribution of IPv4 address space will only be done as follows:

  1. Allocations for LIRs from the last /8
    On application for IPv4 resources LIRs will receive IPv4 addresses according to the following:
    a. LIRs may only receive one allocation from this /8. The size of the allocation made under this policy will be exactly one /22.
    b. LIRs receive only one /22, even if their needs justify a larger allocation.
    c. LIRs may apply for and receive this allocation once they meet the criteria to receive IPv4 address space according to the allocation policy in effect in the RIPE NCC service region at the time of application.
    d. Allocations will only be made to LIRs if they have already received an IPv6 allocation from an upstream LIR or the RIPE NCC.

  2. Unforeseen circumstances
    a. A /16 will be held in reserve for some future uses, as yet unforeseen. The Internet is a disruptive technology and we cannot predict what might happen. Therefore it is prudent to keep a /16 in reserve, just in case some future requirement makes a demand of it. In the event that this /16 remains unused at the time the remaining /8 covered by this policy has been distributed, it returns to the pool to be distributed as per clause 1.

 

New

[Following text will replace section 5.6 of the RIPE Policy Document IPv4 Address Allocation and Assignment Policy for the RIPE NCC Service Region, if the proposal reaches consensus. This would result in a new policy section. NOTE: added only point 3. and 4. to the section 5.6]

 

5.6 Use of last /8 for PA Allocations

The following policies come into effect as soon as RIPE NCC is required to make allocations from the final /8 it receives from the IANA. From then on the distribution of IPv4 address space will only be done as follows:

  1. Allocations for LIRs from the last /8
    On application for IPv4 resources LIRs will receive IPv4 addresses according to the following:
    a. LIRs may only receive one allocation from this /8. The size of the allocation made under this policy will be exactly one /22.
    b. LIRs receive only one /22, even if their needs justify a larger allocation.
    c. LIRs may apply for and receive this allocation once they meet the criteria to receive IPv4 address space according to the allocation policy in effect in the RIPE NCC service region at the time of application.
    d. Allocations will only be made to LIRs if they have already received an IPv6 allocation from an upstream LIR or the RIPE NCC.

  2. Unforeseen circumstances

    a. A /16 will be held in reserve for some future uses, as yet unforeseen. The Internet is a disruptive technology and we cannot predict what might happen. Therefore it is prudent to keep a /16 in reserve, just in case some future requirement makes a demand of it. In the event that this /16 remains unused at the time the remaining /8 covered by this policy has been distributed, it returns to the pool to be distributed as per clause 1.

  3. Post-depletion Address Recycling

    This section only applies to address space that is returned to the RIPE NCC and that will not be returned to the IANA but re-issued by the RIPE NCC itself.

    a. Any address space that is returned to the RIPE NCC will be covered by the same rules as the address space intended in clause 1.

    b. Minimum allocation sizes for the relevant /8 blocks will be updated if necessary.

  4. Insufficient address space

    a. In case an allocation of a single /22 as per clause 1 can no longer be made, multiple allocations up to an equivalent of a /22 in address space will be made to fulfill a request.

 

Rationale

a. Arguments supporting the proposal

This proposal aims to clarify what happens to IPv4 address space that is returned to the RIPE NCC after the final /8 policy kicks in. The existing text already allows for an explanation that would reflect the proposed change under 3) but this is important enough to be unambiguous in actual policy text. The text also leaves room for returned address space to be returned to IANA. In addition, the text under 4) also releases blocks smaller than a /22 to be utilized in the final /8 policy, to prevent RIPE NCC from being stuck with address space that it does not have policy for.

Sections 1 and 2 of article 5.6 (so the original accepted final /8 policy) remain as-is.

 

b. Arguments opposing the proposal

None.

 

Impact Analysis:

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 proposal adds clarification to the scope of section 5.6 of ripe-527, as defined in the accepted policy proposal 2010-02.

It does not intend to change the policy the RIPE NCC will follow when starting to allocate from the last /8 address space.

Therefore the RIPE NCC draws the same conclusions already expressed in the Impact Analysis for the proposal 2010-02, available at

http://www.ripe.net/ripe/policies/proposals/2010-02

B. Impact of Policy on Registry and Addressing System

Address/Internet Number Resource Consumption:

After analysing the data that is currently available, the RIPE NCC does not anticipate that any significant impact will be caused if this proposal is implemented.

Fragmentation/Aggregation:

After analysing the data that is currently available, the RIPE NCC does not anticipate that any significant impact will be caused if this proposal is implemented.

C. Impact of Policy on RIPE NCC Operations/Services

Registration Services:

After analysing the data that is currently available, the RIPE NCC does not anticipate that any significant impact will be caused if this proposal is implemented

Billing/Finance Department:

After analysing the data that is currently available, the RIPE NCC does not anticipate that any significant impact will be caused if this proposal is implemented

RIPE Database:

After analysing the data that is currently available, the RIPE NCC does not anticipate that any significant impact will be caused if this proposal is implemented.

D. Legal Impact of Policy

After analysing the data that is currently available, the RIPE NCC does not anticipate that the implementation of this proposed policy will cause any significant legal implications