You are here: Home > Publications > RIPE Document Store > Temporary Internet Number Assignment Policies

Changes to Temporary Internet Number Assignment Policies

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-587: ripe-526: This document outlines policies for temporary direct assignments of IPv4/IPv6 address space and Autonomous System (AS) Numbers in the RIPE NCC service region.
delete: <h2> insert: <h2 class="western">

insert: <b class="western"> Abstract insert: </b>

delete: <p> insert: <p class="western">

This document outlines policies for temporary direct assignments of IPv4/IPv6 address space and Autonomous System (AS) Numbers in the RIPE NCC service region.

delete: <h2> insert: <h2 class="western">

insert: <b class="western"> Contents insert: </b>

delete: <p> delete: <span class="anchor-link"> insert: <p class="western">

insert: <a class="anchor-link" href="#1"> insert: <b class="western"> insert: <span> 1.0 delete: <a class="anchor-link" href="#introduction" target="_self" title=""> Introduction delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> insert: </b> insert: </a> insert: </p>

insert: <p class="western">

insert: <b class="western"> insert: <a class="anchor-link" href="#2"> insert: <span> 2.0 delete: <a class="anchor-link" href="#reservation" target="_self" title=""> Internet Registry Number Resource Pool Reservation delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> insert: </span> insert: </a> insert: </b> insert: </p>

insert: <p class="western" style="padding-left: 30px; ">

insert: <b class="western"> insert: <a class="anchor-link" href="#2.1"> insert: <span> 2.1 delete: <a class="anchor-link" href="#procedures" target="_self" title=""> RIPE NCC Assignment Procedures delete: </a> delete: </p> delete: <p> insert: </span> insert: </a> insert: </b> insert: </p>

insert: <p class="western">

insert: <b class="western"> insert: <a class="anchor-link" href="#3"> insert: <span> 3.0 delete: <a class="anchor-link" href="#end-user-terms" target="_self" title=""> End User Term and Limitations delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> insert: </span> insert: </a> insert: </b> insert: </p>

insert: <p class="western" style="padding-left: 30px; ">

insert: <b class="western"> insert: <a class="anchor-link" href="#3.1"> insert: <span> 3.1 delete: <a class="anchor-link" href="#time-limits" target="_self" title=""> Assignment Time Limits delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> insert: </span> insert: </a> insert: </b> insert: </p>

insert: <p class="western" style="padding-left: 30px; ">

insert: <b class="western"> insert: <a class="anchor-link" href="#3.2"> insert: <span> 3.2 delete: <a class="anchor-link" href="#expectations" target="_self" title=""> Realistic Expectations delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> insert: </span> insert: </a> insert: </b> insert: </p>

insert: <p class="western" style="padding-left: 30px; ">

insert: <b class="western"> insert: <a class="anchor-link" href="#3.3"> insert: <span> 3.3 delete: <a class="anchor-link" href="#utilisation-rates" target="_self" title=""> IPv4 Address Utilisation Rate delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> insert: </span> insert: </a> insert: </b> insert: </p>

insert: <p class="western" style="padding-left: 30px; ">

insert: <b class="western"> insert: <a class="anchor-link" href="#3.4"> insert: <span> 3.4 delete: <a class="anchor-link" href="#compliance" target="_self" title=""> Compliance with Other RIPE NCC Assignment Policies delete: </a> delete: </p> delete: <p> insert: </span> insert: </a> insert: </b> insert: </p>

insert: <p class="western">

insert: <b class="western"> insert: <a class="anchor-link" href="#4"> insert: <span> 4.0 delete: <a class="anchor-link" href="#attribution" target="_self" title=""> Attribution delete: <strong> delete: </strong> delete: </a> delete: </p> delete: <p> delete: <a name="introduction"> delete: </a> delete: </p> delete: <h2> insert: </span> insert: </a> insert: </b> insert: </p>

insert: <h2 class="western">

insert: <b class="western"> insert: <a name="1"> insert: </a> 1.0 Introduction insert: </b>

delete: <p> insert: <p class="western">

This policy allows the RIPE NCC to assign number resources for temporary direct assignment purposes and, for this purpose, to reserve pools of IPv4/IPv6 addresses, AS Numbers and any other numbers for which it acts as Regional Internet Registry (RIR).

delete: <p> delete: <a name="reservation"> delete: </a> delete: </p> delete: <h2> insert: <h2 class="western">

insert: <b class="western"> insert: <a name="2"> insert: </a> 2.0 Internet Registry Number Resource Pool Reservation insert: </b>

delete: <p> insert: <p class="western">

The RIPE NCC is authorised to reserve pools of IPv4 addresses, IPv6 addresses, 16-bit AS Numbers and 32-bit AS Numbers for the purpose of direct assignment under this policy.

delete: <p> delete: <a name="procedures"> delete: </a> delete: </p> delete: <h3> insert: <h3 class="western">

insert: <b class="western"> insert: <a name="2.1"> insert: </a> 2.1 RIPE NCC Assignment Procedures insert: </b>

delete: <p> insert: <p class="western">

The RIPE NCC may assign number resources to End Users on a temporary deployment basis for a specific time-limited purpose. Examples of specific purposes include, but are not limited to, academic research and experimental purposes, conferences and other types of events which require network connectivity for short periods of time, and other strictly time-limited projects such as deployment tests for new Internet services and technologies.

Resources issued for temporary assignments must not be used for purposes other than those specified in the application, and they may be returned to the RIPE NCC at any time during the approved assignment period. The number resources will be automatically de-registered and returned to the appropriate reservation pool at the end of the approved assignment period.

The RIPE NCC will register the issued number resources in the RIPE Database for the duration of the assignment and will note the start and end dates of the assignment period for each database object.

delete: <p> delete: <a name="end-user-terms"> delete: </a> delete: </p> delete: <h2> insert: <h2 class="western">

insert: <b class="western"> insert: <a name="3"> insert: </a> 3.0 End User Terms and Limitations insert: </b>

delete: <p> delete: <a name="time-limits"> delete: </a> delete: </p> delete: <h3> insert: <h3 class="western">

insert: <b class="western"> insert: <a name="3.1"> insert: </a> 3.1 Assignment Time Limits insert: </b>

delete: <p> insert: <p class="western">

Depending on the specified purpose of the assignment request, different upper time limits may apply. For conferences and other events of short, fixed duration, the maximum assignment time period will be one month longer seven calendar days more than the scheduled length of the conference/event but no longer than two months one month in any case.

delete: <p> insert: <p class="western">

For longer term projects and research purposes, the number resources may be issued on a temporary basis for a period of up to six calendar months, or one month two calendar weeks longer than the expected life of the project/research/experiment, whichever is shorter.

delete: <p> insert: <p class="western">

In the case where an End User requires number resources for research purposes, and where the research project details are made public upon registration of the number resources by the RIPE NCC, and where the End User commits to making public the results of their research project free of charge and free from disclosure constraints, then the requested number resources may be issued for a period of up to one calendar year.

delete: <p> insert: <p class="western">

At the RIPE NCC's discretion renewal of the registration of the resources may be possible in exceptional circumstances on receipt of a new request that details continuation of the End User's requirements during the extended period. Should this request be denied by the RIPE NCC, an appeal may be made using the RIPE NCC Conflict Arbitration Procedure.

delete: <p> delete: <a name="expectations"> delete: </a> delete: </p> delete: <h3> insert: <h3 class="western">

insert: <b class="western"> insert: <a name="3.2"> insert: </a> 3.2 Realistic Expectations insert: </b>

delete: <p> insert: <p class="western">

Assignments may only be based on realistic expectations recorded on the request form. The RIPE NCC may require the End User to provide documentation or other evidence supporting the End User's assignment request.

delete: <p> delete: <a name="utilisation-rates"> delete: </a> delete: </p> delete: <h3> insert: <h3 class="western">

insert: <b class="western"> insert: <a name="3.3"> insert: </a> 3.3 IPv4 Address Utilisation Rates insert: </b>

delete: <p> The insert: <p class="western">

For short-lived assignments of less than one month, the immediate IPv4 address utilisation rate of an assignment must be such that at least should be no less than 50% of the total space applied for at the time of the assignment will be concurrently used at peak periods during the temporary assignment. delete: </p> delete: <p> delete: <a name="compliance"> delete: </a> delete: </p> delete: <h3> For all other temporary assignments, immediate IPv4 address utilisation should be no less than 25%, and utilisation after one month should be no less than 50%. insert: </p>

insert: <h3 class="western">

insert: <b class="western"> insert: <a name="3.4"> insert: </a> 3.4 Compliance with Other RIPE NCC Assignment Policies insert: </b>

delete: <p> insert: <p class="western">

In all respects not covered by this document, temporary assignment policies are subject to all other RIPE NCC policies regarding standard direct assignment of number resources.

delete: <p> delete: <a name="attribution"> delete: </a> delete: </p> delete: <h2> delete: <a name="attribution"> insert: <h3 class="western">

insert: <a name="4"> 4.0 Attribution delete: </h2> delete: <p> insert: </h3>

insert: <p class="western">

This document is compiled from policies developed by the RIPE community.

delete: <p> insert: <p class="western">

The following people actively contributed by making proposals through the RIPE Policy Development Process:

delete: <p> insert: <p class="western">

Nick Hilliard

RIPE Documents Search