[ncc-services-wg] New RIPE NCC Procedural Document Available

Dear Hank,

Thanks for your email.

In answer to your first scenario: In order to move an independent 
Internet resource assigned to an End User to another sponsoring LIR, the 
new sponsoring LIR must submit an End User Assignment Agreement and the 
registration documents of the End User's organisation. This ensures that 
the new sponsoring LIR and the end user are aware of the changes.

This is described in procedure document ripe-475 
(http://www.ripe.net/ripe/docs/ripe-475.html), 3.1 (Transfer between 
Sponsoring LIRs). We are aware that this document also states that such 
requests "must come from either the current or the new sponsoring LIR". 
However, the old sponsoring LIR only needs to confirm that they agree 
with these changes. Having a resource marked as "Not My End User" is 
seen as a confirmation in this case. The RIPE NCC will inform both the 
former and new sponsoring LIR when the requested updates have been 
processed. Because the End Users know with which LIR they will sign an 
agreement, the best option is to have the new sponsoring LIR contact the 
RIPE NCC and provide the necessary documentation.

End Users who are not going to sign an agreement with the current 
sponsoring LIR are responsible finding a new sponsoring LIR and signing 
an agreement with that LIR. The new sponsoring LIR then needs to provide 
the required documents to the RIPE NCC who will evaluate the 
documentation, approve it and move the resource to the new sponsoring LIR.

Resources for which no documentation was submitted at the end of Phase 2 
will become part of Phase 3 of the policy implementation where the RIPE 
NCC will contact the resource holders directly.

In answer to your second scenario: If you've marked a resource as "Not 
my End User" after communicating to the resource holder and informing 
them that they will need to sign an agreement with a sponsoring LIR of 
their choice, there is nothing else you have to do.

Regarding the resources which are no longer in use, please note that 
confirmation from the resource holder that they agree to release the 
resource is still required, especially if it turns out that the 
resources are actually still in use. Additionally, there might be other 
reasons why a PI prefix is not visible in the global routing table.

If there is no reply from the end user after a certain period of time 
(90 days), the resources are de-registered. This is described in 
procedure document ripe-475, 4 (De-registering of Independent Internet 
Number Resources).

As per community feedback received during the recent 2007-01 update 
presentation at RIPE 60, the RIPE NCC will draft a procedure for Phase 3 
of the policy implementation and send it to the RIPE NCC Services 
Working Group Mailing List before starting the Phase 3 implementation.

I hope that this has clarified the matter. Please let me know if you 
have any further questions.


Kind regards,

Arne Kiessling
IP Resource Analyst
RIPE NCC


Hank Nussbacher wrote:
> At 16:53 16/07/2009 +0200, Andrea Cima wrote:
> 
>> [Apologies for duplicate emails]
>>
>> Dear Colleagues,
>>
>> The RIPE NCC has published a new RIPE NCC procedural document:
>> ripe-475, "Independent Internet Number Resources ­ Contractual
>> Relationship Changes between sponsoring LIR and End User"
>>
>> This document describes the steps to be taken when there are changes in
>> the contractual relationship between the End User of independent
>> Internet number resources and the sponsoring Local Internet Registry
>> (LIR). It also describes the scenarios in which the RIPE NCC may
>> de-register independent Internet number resources and what happens to
>> those resources once they are de-registered.
>>
>> The new document is available at:
>> http://www.ripe.net/ripe/docs/ripe-475.html
> 
> I'd like to once again raise this issue which I did a year ago and did 
> not get sufficient answers.  Here are two scenerios that are happening:
> 
> - scenerio 1: I have marked a resource as "not my end user", yet RIPE 
> responds as follows when I request that they move the resource from my 
> LIR to the new sponsoring LIR:
> "We haven't received any documentation yet.
> Please inform the End User of ASxxxxx to ask from their new LIR to
> submit the transfer request in a new ticket in
> enduser-contract at ripe.net."
> I think after a year and about a dozen emails to the old user and the 
> new sponsoring LIR I have gone beyond my responsibility on this matter.  
> What does RIPE intend to do with those resources that the new sponsoring 
> LIR or the end user just can't be bothered to do the registration 
> change?  If I mark a resource as "not my end user", why are they asking 
> "please inform the end user..."
> 
> - scenerio 2: I have marked a resource as "not my end user" and have 
> heard from the end user that they have walked away from the resource.  I 
> have requested that RIPE delete this resource yet the answer I get from 
> RIPE is
> "We did not receive any reply from the End User, so we
> can not return ASxxxx to the free pool without their confirmation.
> We will send another reminder to the End User."
> The end user will never respond since they no longer exist or don't care 
> to respond.  At what point will RIPE reclaim the resource?
> 
> I think there should be clear written procedures for these cases.
> 
> Regards,
> Hank
>