Abstract

This is a procedural document that describes the steps to be taken when there are changes in the

The RIPE NCC assigns independent Internet number resources to End Users provided they have signed a contract with a sponsoring LIR or with the RIPE NCC.

This document describes the modifications that might be made to a contractual relationship between the a sponsoring LIR and an End User of independent Internet number resources and the sponsoring Local Internet Registry (LIR). The document also describes the scenarios in which the RIPE NCC may de-register independent Internet number resources.

for various reasons, including the case of a complete or partial transfer of these independent Internet number resource records, as well as the possible consequences of such changes or of failure to communicate these changes to the RIPE NCC.

This document does not describe the procedure to be followed in the case of a transfer of independent Internet number resources from the RIPE NCC service region to the service region of another RIR or vice versa. This procedure is described in the RIPE NCC procedural document, “Inter-RIR Transfer of Internet Number Resources Link: /publications/docs/ripe-651/ ”.This document does not describe any procedures applicable to contractual relationship changes for

independent Internet number resource users who have signed a contract with the RIPE NCC.

Table of Contents

1.0 Introduction Link: #1.0

2.0 Ownership and Legal Name Changes Link: #2.0

2.1 End User Organisation Changes Ownership Link: #2.1

2.2 End User Organisation Changes Name Link: #2.2

3.0 Transfer of Contractual Relationship Link: #3.0

3.1 Transfer between Sponsoring LIRs Link: #3.1

3.2 Transfer from Sponsoring LIR to the RIPE NCC Link: #3.2

4.0 De-registering of Independent Internet Number Resources Link: #4.0

This section is replaced by the RIPE NCC organisational document “Closure of LIR and Deregistration of Internet Number Resources Link: http://www.ripe.net/publications/docs/closure ”.

4.1 Closure of Sponsoring LIR Link: #4.1

This section is replaced by the RIPE NCC organisational document “Closure of LIR and Deregistration of Internet Number Resources Link: http://www.ripe.net/publications/docs/closure ”.

4.2 Violation of RIPE Policy, Law or Contract Link: #4.2

This section is replaced by the RIPE NCC organisational document “Closure of LIR and Deregistration of Internet Number Resources Link: http://www.ripe.net/publications/docs/closure ”.

4.3 Contract Expired and Not Renewed / Ceased and Not Transferred Link: #4.3

1.0 Introduction

In October 2008, the RIPE Community accepted a policy change which states that

users of independent Internet number resources who have a contractual relationship

must be established between an End User and a sponsoring LIR or the RIPE NCC before the End User can receive independent Internet number resources.

In order to fulfil its mandate of manager of independent Internet number resources, the RIPE NCC requires End Users and LIRs to inform the RIPE NCC in case of changes to their contractual relationship.

The procedures listed in this document are subject to RIPE policies.

2.0 Ownership and Legal Name Changes

The RIPE NCC requires Sponsoring LIRs to maintain a proper registration of End User's legal organisation changes

directly with the RIPE NCC.

2.1 End User Organisation Changes Ownership

If the ownership of the organisation changes but the legal operating name is continued, the RIPE NCC does not have to be notified.

2.2 End User Organisation Changes Name

When an End User that has been assigned Nor does it describe the deregistration of independent Internet number resources

changes its legal operating name, the RIPE NCC must be notified.

In all cases, a new contract must be signed between the renamed End User organisation and the sponsoring LIR in order to guarantee a legitimate handover of the existing rights and obligations.

A copy of this contract, a revised extract of the Trade Register and proof of change from an authorised person must be provided to the RIPE NCC.

3.0 Transfer of Contractual Relationship

If the contractual agreement between the End User of independent Internet number resources and the sponsoring LIR ceases, for any reason, the contractual changes must be communicated to the RIPE NCC.

3.1 Transfer between Sponsoring LIRs

If the End User decides to change sponsoring LIR, this change must be communicated to the RIPE NCC.

The request must come from either the current or the new sponsoring LIR. The RIPE NCC will need confirmation from both LIRs before it can proceed with the transfer, unless the current LIR is closed or in the process of being closed.

The RIPE NCC will finalise the change after it receives a copy of the new End User Assignment Agreement and extract of the Trade Register. The new agreement will replace the old agreement.

3.2 Transfer from Sponsoring LIR to the RIPE NCC

If the contractual agreement between the End User of independent Internet number resources and the sponsoring LIR ceases and the End User wants to enter into a contractual relationship with the RIPE NCC, the End User will have to follow the application procedure to become a Direct Assignment User, signing the End User Assignment Agreement with the RIPE NCC and paying the Administration and first Maintenance Fee.

At this point, the RIPE NCC will need confirmation from both the End User and the sponsoring LIR before it can proceed with the transfer of the contractual relationship of independent Internet number resources, unless the LIR is closed or in the process of being closed.

4.0 De-registering of Independent Internet Number Resources

This section is replaced by the RIPE NCC organisational document “Closure of LIR and Deregistration of Internet Number Resources Link: http://www.ripe.net/publications/docs/closure ”.

4.1 Closure of Sponsoring LIR

This section is replaced by the RIPE NCC organisational document “Closure of LIR and Deregistration of Internet Number Resources Link: http://www.ripe.net/publications/docs/closure ”.

4.2 Violation of RIPE Policy, Law or Contract

This section is replaced by the RIPE NCC organisational document “Closure of LIR and Deregistration of Internet Number Resources Link: http://www.ripe.net/publications/docs/closure ”.

4.3 Contract Expired and Not Renewed / Ceased and Not Transferred

If the contract between the sponsoring LIR and the End User of independent Internet number resources has expired and has not been renewed, or has ceased

for any reason other than contractual relationship changes. For information on deregistration of independent resources for any other reason, the End User has a maximum of 90 days to sign a contract either with a new sponsoring LIR or with the RIPE NCC.

The timeframe for this case is described in Section 4.1.1 - Deregistration Timeframe.

please see the RIPE NCC procedural document, “Closure of Members, Deregistration of Internet Number Resources and Legacy Internet Resources Link: http://www.ripe.net/publications/docs/closure ”.

1. Change in End User's Official Legal Name

When the End User and the sponsoring LIR initially sign a contract, the sponsoring LIR must submit to the RIPE NCC an extract from the Commercial Trade Register or an equivalent document proving the registration of the End User's business with the relevant national authorities (see also the RIPE NCC procedural document, "Due Diligence for the Quality of the RIPE NCC Registration Data" Link: http://www.ripe.net/publications/docs/due-diligence ).

If the End User is a natural person, the sponsoring LIR must submit the identification papers of the End User. This can be a passport, driving license or other official document proving the identity of the individual (see also the RIPE NCC procedural document, "Due Diligence for the Quality of the RIPE NCC Registration Data Link: http://www.ripe.net/publications/docs/due-diligence ").

If the End User changes its name after signing the contract with the sponsoring LIR and, because of this change, the information held by the RIPE NCC on the End User is not up-to-date, then the sponsoring LIR has to inform the RIPE NCC accordingly and follow the procedure described below.

Procedure

The sponsoring LIR must inform the RIPE NCC of the End User’s name change and submit new registration papers from the national authority and the official legal documents supporting this change via the LIR Portal. If access to the LIR Portal is not possible, the sponsoring LIR needs to regain access by sending an email to [email protected] Link: mailto:[email protected] and then submit the request via the LIR Portal.

The RIPE NCC will update all RIPE Database objects maintained by the RIPE NCC that are affected by this change. End Users must update all RIPE Database objects that they maintain themselves that are affected by this change.

If the sponsoring LIR does not submit the aforementioned documents within 10 working days of the RIPE NCC requesting them, the RIPE NCC will send a reminder to the sponsoring LIR's contact email addresses and to the End User's contact email addresses as listed in the relevant RIPE Database object, asking the sponsoring LIR to submit the requested documents within 10 working days of the day of the reminder.

If the RIPE NCC has not received the requested documents 10 working days from the date of the reminder, the RIPE NCC will begin deregistering the independent Internet number resources according to the procedure described in section B.2.2 of the RIPE NCC procedural document, “Closure of Members, Deregistration of Internet Number Resources and Legacy Internet Resources Link: http://www.ripe.net/publications/docs/closure ”.

2. Termination of Contractual Relationship

An End User of independent Internet number resources must have a contractual relationship with a sponsoring LIR at all times. If the contractual relationship between the End User and the sponsoring LIR is terminated for any reason, the RIPE NCC must be notified. The End User must at this point enter into a contractual relationship with a different sponsoring LIR or with the RIPE NCC directly.

Procedure

Preferably, for registration purposes, the RIPE NCC must be notified before the contractual relationship terminates. It is the responsibility of the sponsoring LIR to submit this notification to the RIPE NCC prior to termination.

If the RIPE NCC has not been notified prior to the termination and the End User has already entered into a new contractual relationship with a different sponsoring LIR, this new sponsoring LIR must notify the RIPE NCC and submit the new contract they signed with the End User. The RIPE NCC will notify the previous sponsoring LIR of this change. Should the previous LIR object to the termination of their contract with the End User, the RIPE NCC will only accept the contract of the sponsoring LIR that submits a confirmation signed by the End User. This confirmation must clearly state that the End User has or has not terminated the contractual agreement with the previous sponsoring LIR.

The End User may also enter into a contractual relationship directly with the RIPE NCC. For more information, please see the notes on Requesting Independent Resources Link: http://www.ripe.net/participate/resource-management/independent-resources .

If the RIPE NCC is informed of the termination of the contractual relationship between the sponsoring LIR and the End User and, after 10 working days, no new contractual relationship has been established between the End User and a different sponsoring LIR or the RIPE NCC, the RIPE NCC will send a notification to the End User's contact email addresses, as listed in the relevant RIPE Database object, asking the End User to sign a new contractual agreement with another sponsoring LIR within 10 working days from the date of the notification or to sign an agreement directly with the RIPE NCC.

If the RIPE NCC has not received a new contractual agreement 10 working days from the date of the notification, the RIPE NCC will start deregistering the independent Internet number resources according to the procedure described in section B.2.2 of the RIPE NCC procedural document, “Closure of Members, Deregistration of Internet Number Resources and Legacy Internet Resources Link: http://www.ripe.net/publications/docs/closure ”.

3. Closure of Sponsoring LIR

If the sponsoring LIR has their RIPE NCC Standard Service Agreement terminated, the RIPE NCC will send a notification to the End User's contact email addresses, as listed in the relevant RIPE Database object, asking the End User to sign a new contractual agreement with another sponsoring LIR or with the RIPE NCC within 10 working days of the notification.

If the End User does not submit a new contractual agreement with another sponsoring LIR within 10 working days of the RIPE NCC requesting this, the RIPE NCC will send a reminder to the End User’s contact email addresses as listed in the relevant RIPE Database object, asking for the submission of the requested documents within 10 working days of the day of the reminder. 

If the RIPE NCC has not received a new contractual agreement 10 working days from the date of the reminder, the RIPE NCC will begin deregistering the independent resources according to the procedure described in section B.2.2 of the RIPE NCC procedural document, “Closure of Members, Deregistration of Internet Number Resources and Legacy Internet Resources Link: http://www.ripe.net/publications/docs/closure ”.

4. Transfer of the Assigned Independent Internet Number Resources

If an End User wants to transfer (parts of) the independent Internet number resources assigned to them by the RIPE NCC to a third party for any reason (e.g. the transfer is due to a change in the End User’s business structure or according to the RIPE Policy “RIPE Resource Transfer Policies Link: http://www.ripe.net/publications/docs/transfer-policies ”), this transfer must be declared to the RIPE NCC for approval.

Procedure

For the transfer to be processed, both parties must have a contractual relationship with either the RIPE NCC or a sponsoring LIR. The sponsoring LIR of the transferring End User must submit a request to the RIPE NCC via the LIR Portal. If access to the LIR Portal is not possible, the sponsoring LIR needs to regain access by sending an email to [email protected] Link: mailto:[email protected] and then submit the request via the LIR Portal.

The RIPE NCC will evaluate the request and process the transfer if it is supported sufficiently by the submitted information (see below under i-v).

The RIPE NCC will ask for the following information:

i. Information regarding the parties involved, including:

• The full official legal names of all parties involved
• Which party will transfer the independent Internet number resources and which party will receive them
• Recent registration papers from national authorities for all involved parties

If the current official legal name of the End User is different from the one the RIPE NCC has on record, the procedure described under Section 1 must be followed prior to the transfer of the assigned independent Internet number resources. If this update refers to a transferring End User who wants to transfer all of their assigned independent Internet number resources, then a relevant update of the RIPE Database object, as described under Section 1, may be disregarded.

ii. A description of the reason for the transfer (for example, due to merger, acquisition, transfer of Internet number resources according to the RIPE policies)

If the transfer is taking place due to a change in the structure of the organisation(s) involved (e.g., merger, acquisition), a description of the changes among these organisation(s) is necessary. This description must be accompanied by the official legal documents issued by the relevant national authorities proving/supporting the changes the request is based on.

If the change in the structure of the organisation(s) involved cannot be proven/supported by official documentation from national authorities describing this change (e.g., a network acquisition from one organisation to another), then these cases will fall within the scope of RIPE Policy “RIPE Resource Transfer Policies Link: http://www.ripe.net/publications/docs/transfer-policies ”.

iii. A list of the assigned independent Internet number resources for which a transfer is being requested

iv. The correct contact details of all parties involved

The RIPE NCC may ask the parties involved to confirm the correctness of their contact details or to update them.

v. A Transfer Agreement signed by both parties or by their legal successors

The RIPE NCC provides the template of the Transfer Agreement that either party may submit to the RIPE NCC.

The Transfer Agreement must be signed by authorised persons for both parties. For the transferring party, it is required that the Transfer Agreement is signed by an authorised representative having the general capacity to act on behalf of this party. The RIPE NCC reserves the right to request official documentation proving that the person signing on behalf of either party is authorised to do so.

The RIPE NCC may ask the other party/parties to confirm their agreement to the transfer. The confirmation must be authorised (signed or sent) by a registered contact person or authorised person.

If the transferring party no longer exists by the time the RIPE NCC has been informed, the receiving party must send both of the following:

• An official document (issued by a national authority) confirming the closure of the transferring party.
• A copy of an older signed agreement between the relevant parties mentioning the transfer of the assigned independent Internet number resources. If such an agreement is not available, the RIPE NCC may accept a confirmation of the transfer to the RIPE NCC signed by an authorised person (e.g. senior manager, legal successor) of the receiving party. The RIPE NCC reserves the right to reverse the transfer should another party object to this transfer and provide an agreement that proves that the Provider Independent address records should have been transferred to them.

The RIPE NCC will update all RIPE Database objects maintained by the RIPE NCC that are affected by this change. The parties involved must update all RIPE Database objects that they maintain themselves that are affected by this change.