[DRAFT] Experimental Internet Resource Allocations & Assignments
Philip Smith, Cisco
Geoff Huston, Telstra
Table of Contents
- 1.0 Introduction
- 2.0 Defining the Experiment
- 3.0 Publication
- 4.0 Non-commercial Basis
- 5.0 Period of the Temporary Resource Registration
- 6.0 Registration
- 7.0 Making the Request
- 8.0 Nota Bene
Organisations often require deployment tests for new Internet services and technologies. These require numbering resources for the duration of the test.
The policy goal of resource conservation is of reduced importance when resources are issued on a temporary basis.
This document formalises the policy whereby the RIPE NCC registers numbering resources issued on a temporary basis for Internet experiments.
An organisation receiving numbering resources must document the experiment. This may be in the form of a current IETF Experimental RFC (http://www.ietf.org/rfc/rfc2026.txt see Sec. 4.2.1) or an “experiment proposal” detailing the resources required and the activities to be carried out.
For experiments requiring IP address space the assignment size will be equal to the existing minimum allocation size on the date the request is received. For Autonomous System Number (ASN) requests a single ASN will be assigned. Where the experiment requires a variation to this rule it should be noted in the resource request.
The experiment proposal must be made public (e.g. published on web site), upon registration of the resources by the RIPE NCC. Following the conclusion of the experiment the results must be published free of charge and free from disclosure constraints.
Resources issued for an experiment must not be used for commercial purposes.
The resources will be issued on a temporary basis for a period of one year. Renewal of the resources registration is possible on receipt of a new request that details any continuation of the experiment during the extended period.
The resources issued cannot be used for a commercial service following the conclusion of the experiment.
The RIPE NCC will register the resources issued in the RIPE Whois Database.
The request must be made by a Local Internet Registry (LIR) using the appropriate request form for the resource found at:
Upon acceptance of this draft document by the RIPE community, the text will be incorporated into the IPv4, IPv6 and ASN policy documents available from the RIPE Document Store at: