[address-policy-wg] DRAFT: allocating resources to the RIPE NCC

Hi Brett,

I only intended the policy to be retroactive in the sense that all
resources allocated to the NCC should be (re)registered under the
eu.ripencc handle. I have no intention whatsoever to have a look again
at all resources that have been previously allocated - if they are
unnecessary surely the NCC would have already returned them, right ? :-)

I'll think about a change in the text to clarify this.

Thanks for your feedback!

Best,

Remco

-----Original Message-----
From: B C [mailto:brettlists at gmail.com] 
Sent: woensdag 17 december 2008 21:41
To: Remco van Mook; address-policy-wg at ripe.net
Subject: Re: [address-policy-wg] DRAFT: allocating resources to the RIPE
NCC

Remco,

One question springs to mind initially:

>This policy applies to all resources, current and future, allocated
>to the RIPE NCC, its subsidiaries or affiliates.

So presumably this means all current allocations that have been made
to the NCC will be subject to external approval, what happens where
the arbiter does not approve those current allocations? Presumably the
NCC will need to return them and if so under what timescale? I think
we need to be careful that we don't cause operational difficulties
here.

Brett

On Wed, Dec 10, 2008 at 8:05 PM, Remco van Mook
<Remco.vanMook at eu.equinix.com> wrote:
> Dear all,
>
> Please find below my first attempt at a policy for allocating
resources
> to the NCC. I think it should be a separate ripe document. Please let
me
> know what you think and where it needs some more polishing. I want to
> publish the formal proposal soon, so the policy can potentially be
> adopted well in time for the next RIPE meeting.
>
> Best,
>
> Remco
>
>
> Number:                 (assigned by the RIPE NCC)
> Policy Proposal Name:   Allocating resources to the RIPE NCC
> Author:
> name:                           Remco van Mook
> email:                  remco at eu.equinix.com
> organisation:           Equinix
>
> Proposal Version:               1.0
>
> Submission Date:                TBD
>
> Suggested RIPE WG for discussion and publication: address policy
>
> Proposal Type:          new
>
> Policy Term:            permanent
>
> Summary of proposal:
> This proposal sets the way in which the RIPE NCC can get resources
> allocated to itself.
>
> Policy text:
> Current (if modify):
> none
>
> New:
>
> Abstract:
> This document describes how the RIPE NCC can get resources allocated
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 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 to the RIPE NCC will be registered in the RIPE
> database under the LIR identity of 'eu.ripencc'. All policies set for
> allocating resources to LIRs apply equally to the RIPE NCC. RIPE NCC
as
> a resource holder should fulfill the same basic requirements that are
> also expected of normal LIRs, such as returning unused resources.
Since
> the RIPE NCC cannot sign a contract with itself, the requirement for
an
> explicit contract as set by various policies does not apply for this
> particular case. While the RIPE NCC will still handle the
administrative
> tasks involved with allocating resources itself, it will not evaluate
> the validity of their own requests.
>
> 3.0 Pool of Arbiters
> Defined in ripe-174, the pool of Arbiters has been appointed by the
RIPE
> NCC Executive Committee (and approved by the AGM). The arbiters
function
> is to mediate in a 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
> The evaluation of an allocation request made by the RIPE NCC will be
> done by a team of at least 3 of the arbiters. The arbiters will
respond
> to any new request within one month. For the purpose of evaluating,
the
> request will be treated as if it was filed by a normal LIR. If the
> request is approved, the resources will then be allocated by the RIPE
> NCC and registered in the RIPE database.
>
> 5.0 Conflict resolution
> Should 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 resources to itself
> without prior consent of either the pool of arbiters or the RIPE
> plenary.
>
>
>
> Rationale:
> All resource-holders in the RIPE NCC service area are now being
required
> to have a contractual relationship with the RIPE NCC, directly or
> indirectly. There is however one entity that cannot sign a contract
with
> the RIPE NCC - the NCC itself. This policy cleans up the current
variety
> in which the NCC has allocated resources to itself and sets a standard
> way for the RIPE NCC to get further resources allocated. For all means
> and purposes the RIPE NCC will be treated as a LIR and will follow the
> same policies as a LIR; however the role the RIPE NCC has in analysing
> and evaluating any request by an LIR is instead done by members of the
> pool of arbiters.
>
> Arguments supporting the proposal
> Currently there is no standard way for the RIPE NCC to get resources
> allocated. This has so far led to an inconsistent picture between the
> various resource types; a lot of ad hoc policies and exemptions. This
> needs to be cleaned up. One way to look at it is that every single
> resource allocated to the RIPE NCC is a conflict of interest between
the
> RIPE NCC and ALL of its members. Therefore it makes sense that the
same
> people who arbitrate conflicts between RIPE NCC and its members
evaluate
> the requests for resources as filed by the RIPE NCC.
>
>
> Arguments opposing the proposal
> None.
>
>
> This email is from Equinix Europe Limited or one of its
associated/subsidiary companies. This email, and any files transmitted
with it, contains information which is confidential, may be legally
privileged and is solely for the use of the intended recipient. If you
have received this email in error, please notify the sender and delete
this email immediately.  Equinix Europe Limited. Registered Office:
Quadrant House, Floor 6, 17 Thomas More Street, Thomas More Square,
London E1W 1YW. Registered in England and Wales No. 6293383.
>
>