[ncc-services-wg] Destruction of trust

Sander,

I, amongst others, am really pleased that policy regarding the legacy resource holders is starting to emerge.

Nigel

-----Original Message-----
From: ncc-services-wg-bounces at ripe.net [mailto:ncc-services-wg-bounces at ripe.net] On Behalf Of Sander Steffann
Sent: 10 August 2012 11:54
To: Andrew de la Haye
Cc: ncc-services-wg at ripe.net; Andrew de la de la Haye; Nigel Titley; Rogier Spoor
Subject: Re: [ncc-services-wg] Destruction of trust

Hi Andrew,

> Sorry for the late reply, however holiday period started on our side. 

No problem!

> As you point out, ripe-453 is a RIPE Policy that requires a contractual agreement between End Users of Provider Independent address and the RIPE NCC, either through a sponsoring LIR or directly with the RIPE NCC.
> 
> The legacy address space project that the RIPE NCC is engaged in lies completely outside the scope of that policy. For the legacy address space project, the RIPE NCC requires a different contract between the legacy address space holder and a sponsoring LIR.

Ah, I think I looked at the wrong contract template then. Thank you for clearing this up!

> This contract establishes that both parties agree on the correctness of the information provided by the legacy address space holder. This contract should not be the one used for ripe-453.

I think the problem here is that there is no clear policy on how to deal with ERX/Legacy space and its holders. A group of ERX/Legacy resource holders and I have been working on a policy proposal on this subject. We will (real soon now) submit the first version to this working group so that we can fill this gap and make sure that we have clear policy for all the resources that RIPE NCC handles.

Thanks,
Sander