Draft document
This policy proposal has been accepted
The new RIPE Document is: ripe-635
How to read this draft document:
This document relates to the policy proposal 2014-11, “Language Clarification for “Allocating/Assigning Resources to the RIPE NCC”. If approved, it will modify ripe-476. 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 describes how the RIPE NCC can allocate/assign resources to itself.
1.0 Introduction
The RIPE NCC is an independent association and serves as one of five Regional Internet Registries (RIRs). Its service region incorporates Europe, the Middle East, and Central Asia. The RIPE NCC is responsible for the allocation and assignment of Internet Protocol (IP) address space, Autonomous System Numbers (ASNs) and the management of reverse domain names within this region.
1.1 Scope
This document describes the policy for allocating or assigning resources to the RIPE NCC. This policy applies to all resources, current and future, allocated to the RIPE NCC, its subsidiaries or affiliates. This document does not describe any specific resource or a policy restricted to a specific resource; it does however impact how the resource-specific policies should be interpreted when applied to the RIPE NCC as the entity requesting resources. This document does not describe or impact any policy where it is applied to regular LIRs.
2.0 RIPE NCC as a Resource Holder
|
Any resources allocated/assigned to the RIPE NCC will be registered in the RIPE Database. All policies set for allocating or assigning resources to LIRs apply equally to the RIPE NCC. The RIPE NCC as a resource holder should fulfil the same basic requirements also expected of normal LIRs, such as returning unused resources. As an exception from normal LIRs, RIPE NCC as a resource holder is exempted from signing any of the normal contracts required for number resource allocation/assignment. While the RIPE NCC will still handle most of the tasks involved with allocating/assigning resources itself, it will not approve the validity of its own requests. |
Any resources allocated/assigned to the RIPE NCC will be registered in the RIPE Database. All policies set for allocating or assigning resources to LIRs apply equally to the RIPE NCC. The RIPE NCC as a resource holder must fulfil the same basic requirements also expected of normal LIRs, such as returning unused resources. As an exception from normal LIRs, RIPE NCC as a resource holder is exempted from signing any of the normal contracts required for number resource allocation/assignment. While the RIPE NCC will still handle most of the tasks involved with allocating/assigning resources itself, it will not approve the validity of its own requests. |
3.0 Pool of Arbiters
Defined in the RIPE Document, RIPE NCC Conflict Arbitration Procedure, the pool of arbiters has been appointed by the RIPE NCC Executive Committee (and approved by the General Meeting). The arbiters' function is to mediate in any conflict between the RIPE NCC and one of its members. In addition to executing the RIPE NCC Conflict Arbitration Procedure, the pool of arbiters will also evaluate the validity of all requests for resources made by the RIPE NCC.
4.0 Evaluating a Request
When an assignment/allocation request is received, it is processed by the RIPE NCC IP Resource Analysts (IPRAs) who will give a formal written opinion on whether the request is consistent with current assignment/allocation guidelines. This opinion is evaluated by a majority of the pool of arbiters (of which there is an odd number), who are entitled to approve the request only if the IPRA team find that the request is consistent with current rules.
Both the IPRA recommendation and the reasoning of the pool of arbiters will be announced publicly. For the purpose of evaluating, the request will be treated as if it were filed by a regular LIR.
If the request is approved, the resources will then be allocated/assigned by the RIPE NCC to the RIPE NCC and registered in the RIPE Database.
5.0 Conflict Resolution
Should either or both the RIPE NCC IPRAs and the pool of arbiters reject a request, or if the request cannot be granted by applying the standard LIR policies, the RIPE NCC can file a request to the RIPE Plenary Meeting to have its case heard. It is then up to the RIPE Plenary to decide whether the request should be granted or not. At no point can the RIPE NCC allocate/assign resources to itself without prior consent of either the pool of arbiters or the RIPE Plenary.