Draft of Temporary Internet Number Assignment Policies
This policy proposal has been accepted and has been implemented
The new RIPE Document is: ripe-801
How to read this draft document:
This document relates to RIPE policy proposal 2023-02 “Minimum Size for IPv4 Temporary Assignments” If approved, it will modify ripe-587, “Temporary Internet Number Assignment Policies”.
To show you how the new document would be different to the old one, we have highlighted any new text or changes to the existing text.
We indicate changes to existing text in the document like this:
| ORIGINAL TEXT | NEW TEXT |
|---|---|
|
The text from the current policy document that will be replaced is displayed here. |
The proposed text change will be displayed here. |
Abstract
This document outlines policies for temporary direct assignments of IPv4/IPv6 address space and Autonomous System (AS) Numbers in the RIPE NCC service region.
Contents
1.0 Introduction
2.0 Internet Registry Number Resource Pool Reservation
2.1 RIPE NCC Assignment Procedures
3.0 End User Term and Limitations
3.3 IPv4 Address Utilisation Rate
3.4 Compliance with Other RIPE NCC Assignment Policies
4.0 Attribution
1.0 Introduction
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).
2.0 Internet Registry Number Resource Pool Reservation
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.
2.1 RIPE NCC Assignment Procedures
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.
3.0 End User Terms and Limitations
3.1 Assignment Time Limits
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 than the scheduled length of the conference/event but no longer than two months in any case.
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 longer than the expected life of the project/research/experiment, whichever is shorter.
| 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. |
Number resources requested for research purposes may be issued for a period of up to one calendar year when both the following conditions are met:
|
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.
3.2 Realistic Expectations
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.
3.3 IPv4 Address Utilisation Rates
| The utilisation rate of an assignment must be such that at least 50% of the total space applied for at the time of the assignment will be concurrently used at peak periods during the assignment. |
The default assignment size is a /24. Assignments smaller than a /24 can be made upon request. The utilisation rate of an assignment larger than a /24 must be such that at least 50% of the total space applied for at the time of the assignment will be concurrently used at peak periods during the assignment. A request for more than a /24 for research purposes may be justified by routing requirements when both the following conditions are met:
|
3.4 Compliance with Other RIPE NCC Assignment Policies
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.
4.0 Attribution
This document is compiled from policies developed by the RIPE community.
The following people actively contributed by making proposals through the RIPE Policy Development Process:
| Nick Hilliard | Nick Hilliard (ripe-526, ripe 587), Edwin Verheul, Elvis Daniel Velea |