Contents

1. Change in End User's Official Legal Name Link: #1--change-in-end-user-s-official-legal-name
2. Termination of Contractual Relationship Link: #2--termination-of-contractual-relationship
3. Closure of Sponsoring LIR Link: #3--closure-of-sponsoring-lir
4. Transfer of the Assigned Independent Internet Number Resources Link: #4--transfer-of-the-assigned-independent-internet-number-resources
5. Voluntary Transfer Lock of the Assigned Independent Internet Number Resources Link: #5--voluntary-transfer-lock-of-the-assigned-independent-internet-number-resources

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 a sponsoring LIR and an End User of 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 users of independent Internet number resources who have a contractual relationship directly with the RIPE NCC. Nor does it describe the deregistration of independent Internet number resources for any reason other than contractual relationship changes. For information on deregistration of independent resources for any other reason, please see the RIPE NCC procedural document, Closure of LIR and “Closure of Members, Deregistration of Internet Number Resources Link: http://www.ripe.net/publications/docs/closure . and Legacy Internet Resources Link: http://www.ripe.net/publications/docs/closure ”.

1. Change in End User's Business Structure

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/ripe/docs/due-diligence 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 "Due Diligence for the Quality of the RIPE NCC Registration Data

Link: http://www.ripe.net/ripe/docs/due-diligence ).If there is any change in the End User's business structure Link: http://www.ripe.net/publications/docs/due-diligence ").If the End User changes its name

after signing the contract with the sponsoring LIR (for example, the End User has merged with another company or has changed name), 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 is obliged to submit the updated/new registration papers of the End User to the RIPE NCC, as well as any documents verifying this change. has to inform the RIPE NCC accordingly and follow the procedure described below.

Procedure

The sponsoring LIR must send an email to [email protected] Link: mailto:[email protected] informing the RIPE NCC of the End User's business change. This email must include 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. 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 independent Internet number resources according to the procedure described in section B.2.2 of the RIPE NCC procedural document Closure of LIR and document, “Closure of Members, Deregistration of Internet Number Resources (section B.2.2) Link: http://www.ripe.net/publications/docs/closure#b22 . and Legacy Internet Resources Link: http://www.ripe.net/publications/docs/closure ”.

2. Termination of Contractual Relationship

An End User of Independent 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 that 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:

https://www.ripe.net/lir-services/resource-management/direct-assignments Link: http://www.ripe.net/lir-services/resource-management/direct-assignments

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 of the day 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 LIR and “Closure of Members, Deregistration of Internet Number Resources (section B.2.2) Link: http://www.ripe.net/publications/docs/closure#b22 . 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 sponsorship sponsoring LIR within 10 working days of the RIPE NCC requesting them, this, the RIPE NCC will send a reminder to the End User's User’s contact email addresses as listed in the relevant RIPE Database object, asking the sponsoring LIR to submit 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 LIR and “Closure of Members, Deregistration of Internet Number Resources (section B.2.2) Link: http://www.ripe.net/publications/docs/closure#b22 . and Legacy Internet Resources Link: http://www.ripe.net/publications/docs/closure ”.

4. Transfer of the Assigned Provider Independent (PI) Address Records

Independent Internet Number Resources

If an End User wants to transfer (parts of) the PI address records independent Internet number resources assigned to them by the RIPE NCC to a third party in accordance with 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 “

IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region Link: http://www.ripe.net/publications/docs/ipv4-policies ” (Section 6.4), this must be communicated to the RIPE NCC.

Procedure

Both 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. One of the parties involved 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] via their sponsoring LIR, if they have one. 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 PI address records 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 PI address records. the assigned independent Internet number resources. If this update refers to a transferring End User who wants to transfer all of their assigned PI address records, 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 PI address records assigned independent Internet number resources for which a transfer is being requested

iii. 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.

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

The RIPE NCC will make a provides the template of the Transfer Agreement available. Either that either party may submit the Transfer Agreement to the RIPE NCC, 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 PI address records. assigned independent Internet number resources. If such an agreement is not available, the receiving party must send RIPE NCC may accept a confirmation of the transfer to the RIPE NCC signed by an authorised person (e.g. senior manager, legal successor). 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 PI 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.

4.1 Transfer due to Seizure

If the RIPE NCC is delivered a court order for the seizure of the right to registration of Internet number resources for the recovery of money, in accordance with Dutch legal procedures, the RIPE NCC will comply with its obligations. This order may create obligations for the RIPE NCC, such as the restriction of the transfer of Internet number resources from the member’s account, the issuance of a statement outlining the Internet number resources registered to a member’s account, and the transfer of the Internet number resources away from the member’s account.

The RIPE NCC will comply on the condition that the court order:

• Has entered into force and is recognised by the Dutch courts.
• Is served by a bailiff in advance to the RIPE NCC in the form of an authentic enforceable document (e.g., a court order).
• Specifically mentions the RIPE NCC and creates an obligation for the RIPE NCC to perform the transfer. (i.e., the enforceable title must apply specifically to the RIPE NCC). This does not mean the RIPE NCC needs to be named as a defendant.
• States the specific Internet number resources at issue.

Each order will be reviewed on a case-by-case basis. If the RIPE NCC believes that an order or the third party seeking to enforce the order does not comply with RIPE policies or RIPE NCC procedures, the RIPE NCC reserves the right to dispute it.

5. Voluntary Transfer Lock of the Assigned Independent Internet Number Resources

5.1 The Scope of The Voluntary Transfer Lock

The RIPE NCC may approve a request for a voluntary transfer lock in accordance with the RIPE Policy “Voluntary Transfer Lock Link: /publications/docs/ripe-806/ ”.

If the RIPE NCC deems that a voluntary transfer lock request is not in line with RIPE policies, RIPE NCC procedural documents, or applicable law, the RIPE NCC reserves the right to reject the request.

The RIPE NCC reserves the right not to enforce a voluntary transfer lock, even if the relevant request has been approved by the RIPE NCC. The RIPE NCC may not enforce a voluntary transfer lock, for example, in case of Transfers of Internet Number Resources due to a change in the structure of the organisation involved such as mergers or acquisitions (see above Section 4) or Transfers Due to Seizure (see above Section 4.1).

This document does not describe the procedure to be followed in the case of voluntary transfer locks for users of independent Internet number resources who have a contractual relationship directly with the RIPE NCC. This procedure is described in the RIPE NCC Procedural Document, "Transfer of Internet Number Resources and Change of a Member’s Official Legal Name Link: http://www.ripe.net/publications/docs/mergers ".

5.2 Submission of the Request for Voluntary Transfer Lock 

If an End User wants to request the voluntary transfer lock on independent Internet number resources assigned to them by the RIPE NCC, this must be declared to the RIPE NCC for approval.

The RIPE NCC will evaluate the request and approve the voluntary transfer lock if it is adequately supported by information submitted and documentation as described below.

The RIPE NCC will ask for the following:

The Voluntary Transfer Lock Request Form

The requesting party must complete the Voluntary Transfer Lock Request Form. The template of the Voluntary Transfer Lock Request Form is provided by the RIPE NCC.

The sponsoring LIR of the requesting End User must submit the Voluntary Transfer Lock Request Form 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] and then submit the request via the LIR Portal.

The Voluntary Transfer Lock Request Form must be signed by the authorised person for the requesting party 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 the requesting party is authorised to do so.

To complete the Voluntary Transfer Lock Request Form, the following should be provided:

i. Information regarding the party requesting the voluntary transfer lock, including:

• The full official legal name
• Recent registration papers issued by the relevant national authority

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 requesting the voluntary transfer lock. 

ii. Thelist of Internet number resources for which thevoluntary transfer lock is being requested

iii. The correct contact details of the requesting party

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

iv. The duration of the voluntary transfer lock

In the Voluntary Transfer Lock Request Form, the requesting party is required to indicate the duration of the voluntary transfer lock, which can be 6, 12 or 24 months. The voluntary transfer lock will be applied from the date on which the RIPE NCC approves the voluntary transfer lock request.

The voluntary transfer lock will expire after 6, 12 or 24 months, depending on the duration requested. 

To continue with the voluntary transfer lock after the expiration of the requested lock duration, the requesting party will have to submit a new voluntary transfer lock request to the RIPE NCC for approval.

The requesting party cannot request the cancellation of the voluntary transfer lock once the lock has been applied until the voluntary transfer lock expires. 

5.3 The Publication of Internet Number Resources under the Voluntary Transfer Lock

The RIPE NCC will publish a list of Internet number resources under voluntary transfer lock on its website.