Changes to Transfer of Internet Number Resource Records and Change of a Member’s Official Legal Name

Contents

delete: <a class="anchor-link" href="#definitions" target="_self" title=""> 1.0 1.0  insert: <a href="#definitions"> Definitions

delete: <a class="anchor-link" href="#introduction" target="_self" title=""> 2.0 2.0  insert: <a href="#introduction"> Introduction

delete: <a class="anchor-link" href="#transfer" target="_self" title=""> 3.0 3.0  insert: <a href="#transfer"> Transfer of Internet Number Resource Records delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#submission" target="_self" title=""> 3.1 Resources insert: </a> insert: </p>

3.1  insert: <a href="#transfer31"> Submission of the Request for Transfer

3.2  insert: <a href="#transfer32"> If the Receiving Organisation Party is not yet a Member

3.3  insert: <a href="#transfer33"> Financial Consequences

3.4  insert: <a href="#transfer34"> Internet Number Resource Registration and RIPE Database Issues

3.5  insert: <a href="#transfer35"> Transfers Between LIR Accounts Belonging to the Same Member insert: </a> insert: </p>

3.6  insert: <a href="#transfer36" data-linktype="anchor" data-val="8"> Transfer of Internet Number Resources under Policy Restrictions due to a Change in the Member's Business Structure insert: </a> insert: </p>

3.7 insert: <a href="#transfer37" data-linktype="anchor" data-val="9"> Transfers due to Seizure insert: </a> insert: </p>

4.0  insert: <a href="#memberchanges"> Member Changes its Official Legal Name

1.0 Definitions

For the purposes of this document Internet Number Resource records document, Internet number resources refer to:

• The registered allocations allocation and assignments of a Member assignment records of a member
• The independent In the case of a transfer of Internet number resources delete: <b> delete: </b> assigned from the member to another party according to RIPE Policy " insert: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies insert: </a> ". Such a transfer may also be facilitated through the Member as a “sponsoring LIR” to an End User RIPE NCC Listing Service.

  insert: </p>

2.0 Introduction

In order for the RIPE NCC to maintain an accurate registry, it must hold accurate data concerning:

• The natural or legal persons holding the registration of Internet Number Resources number resources
• The Internet Number Resource records number resources that are registered to the these natural and or legal persons

This means that any transfer of Internet Number Resources number resources from one party to another, or any change to the legal status of a party holding the registration of Internet Number Resources, number resources, must be communicated to the RIPE NCC.

delete: </p> delete: <p> The Member A member must inform the RIPE NCC if delete: <i> if  insert: <em> one or both delete: </i> of insert: </em>  of the following changes occurs:

1. Internet Number Resource records are transferred. Such transfers may take place:
   • Because of a change in the member's business structure of the Member, for (for example in the case of a merger or acquisition of the Member's organisation; member's organisation, or if the member is undergoing bankruptcy, liquidation, suspension of payments or insolvency proceedings) that can be proved/supported by official documentation from national authorities.
   • In the case of a pure transfer of an allocation Internet number resources from a Member the member to another Member party according to RIPE Policy " insert: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies ( delete: <a title="" href="https://www.ripe.net/publications/docs/ipv4-policies#55" class="external-link" target="_self"> Section 5.5, insert: </a> ". Transfers of IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region delete: </a> ). Such a transfer Internet number resources may also be facilitated through the delete: <a data-linktype="internal" target="_self" title="" href="resolveuid/8768823a7d79496c8bff938729212474" data-val="8768823a7d79496c8bff938729212474" class="internal-link"> RIPE NCC the  insert: <a data-val="e222449049284bb1af45883cccde2da1" href="../../../resolveuid/e222449049284bb1af45883cccde2da1" data-linktype="internal"> IPv4 Transfer Listing Service. delete: </a> Service insert: </a> . insert: <br />
     insert: <br />
     
2. The Member member changes its official legal name delete: <b> . delete: </b> insert: <strong> .  insert: </strong> Such a change may occur, for example, because of a merger or acquisition of the Member's member's organisation.

delete: </p> delete: <p> This document describes the procedures to be followed for such changes to be properly communicated to, and registered with, with the RIPE NCC.

delete: </p> delete: <p> delete: <b> insert: <strong> Note: delete: </b> delete: </p> delete: <p> insert: <br />
insert: </strong> If a change in the Member's a member's official legal name is accompanied by a transfer of Internet Number Resource records, the Member number resources, the member must first inform the RIPE NCC of the name change and then of the transfer.

If a change in the Member's a member's business structure is delete: <i> is  insert: <em> not delete: </i> accompanied insert: </em>  accompanied by a transfer of Internet Number Resource records number resources or a change in the Member's member's official legal name, then the RIPE NCC does not need to be informed of this change.

This document does not describe the procedure to be followed in the case of changes with regards to independent Internet number resources assigned to End Users or any changes to the End Users business structure. This procedure is described in the RIPE NCC Procedural Document, " insert: <a href="http://www.ripe.net/publications/docs/lir-end-user-contractual-changes" data-val="http://www.ripe.net/publications/docs/lir-end-user-contractual-changes" data-linktype="external"> Independent Internet Number Resources - Contractual Relationship Changes Between Sponsoring LIR and End User insert: </a> ". insert: </p>

This document does not describe the procedure to be followed in case of a transfer of Internet number resources from the RIPE NCC service region to the service region of another RIR and vice versa. This procedure is described in the RIPE NCC procedural document, " insert: <a class="external-link" href="http://www.ripe.net/publications/docs/inter-rir-transfer-of-inr" data-linktype="external" data-val="http://www.ripe.net/publications/docs/inter-rir-transfer-of-inr"> Inter-RIR Transfer of Internet Number Resources insert: </a> ". insert: </p>

  insert: </p>

3.0 Transfer of Internet Number Resource Records Resources

If a Member member transfers their Internet Number Resource records number resources to a third party for any reason, this transfer must be declared to, and approved by, the RIPE NCC. delete: </p> delete: <p> delete: </p> delete: <p> delete: <b> delete: <a name="submission"> to the RIPE NCC for approval. insert: </p>

insert: <a name="transfer31"> 3.1 Submission of the Request for Transfer delete: </b> delete: </p> delete: <p> One of the involved parties must submit a request by email to the RIPE NCC for insert: </h4>

For the transfer to be executed: delete: </p> delete: <ul> delete: <li> If the transfer is due to a change in the business structure of the Member (e.g., merger or acquisition), the request must be submitted to delete: <a href="mailto:[email protected]"> [email protected] delete: </a> delete: </li> delete: <li> If the transfer is a transfer of allocation from one Member to another Member according to RIPE Policies ( delete: <a title="" href="https://www.ripe.net/ripe/docs/ipv4-policies#55" class="external-link" target="_self"> Section 5.5, IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region delete: </a> ), the request must be submitted to delete: <a href="mailto:[email protected]"> [email protected] delete: </a> delete: </li> delete: </ul> delete: <p> A processed, a registered contact or an authorised person (e.g., senior manager, legal successor) must send the request. delete: </p> delete: <p> of the involved parties must submit a request to the RIPE NCC. More specifically: insert: </p>

insert: <li>
• If the transfer is due to a change in the member's business structure that can be proved/supported by official documentation by national authorities (e.g., merger, acquisition, bankruptcy, liquidation), either of the parties involved must submit the request via the  insert: <a href="https://my.ripe.net/#/update-registry"> LIR Portal insert: </a> . If the requesting party does not have access rights to the LIR portal, the request must be submitted via email to  insert: <a href="mailto:[email protected]"> [email protected] insert: </a> insert: </li>
insert: <li>
• If this is a transfer of Internet number resource from one member to another party according to RIPE Policy " insert: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies insert: </a> ", the transferring party must submit the request via the  insert: <a href="https://my.ripe.net/"> LIR Portal insert: </a> . insert: </li>
insert: </ul>

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

The RIPE NCC will ask for the following information:

delete: <b> insert: <strong> i. Information regarding the parties involved, including: delete: </b> insert: </strong>

• The full official legal names of all parties involved
• Which party will transfer the Internet Number Resource records number resources and which party will receive them
• Recent registration papers issued by the relevant national authorities for all involved parties

If the current official legal names of the involved Members members are different from the ones those in the relevant signed RIPE NCC Standard Service Agreement, then the procedure described under delete: <a class="anchor-link" href="#official-legal-name" target="_self" title=""> in  insert: <a href="#memberchanges"> Section 4.0 must  must be followed prior to the transfer of the Internet Number Resource records. number resources. insert: </p>

The procedure described under Section 4.0 is not necessary for the transferring Member member if the RIPE NCC Standard Service Agreement of the transferring Member for that member is terminated (see Sections A.1.1 and A.1.2 of the RIPE NCC Procedural Document, " insert: <a href="http://www.ripe.net/publications/docs/closure" data-linktype="external" data-val="http://www.ripe.net/publications/docs/closure"> Closure of LIR Members, Deregistration of Internet Resources and Deregistration of Internet Number Resources, delete: <a href="https://www.ripe.net/publications/docs/closure#11"> Section A.1.1. delete: </a> and delete: <a href="https://www.ripe.net/publications/docs/closure#12"> Section A.1.2. delete: </a> ). delete: </p> delete: <p> delete: </p> delete: <p> delete: <b> Legacy Internet Resources insert: </a> ". insert: </p>

insert: <strong> ii. A description of the reason for the transfer (for example, due to merger, acquisition, transfer of allocation Internet number resources according to the RIPE policies) delete: </b> insert: </strong>

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

delete: </p> delete: <p> delete: <b> 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 member to another), then these cases will fall within the scope of RIPE Policy " insert: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies insert: </a> ". insert: </p>

insert: <strong> iii. A list of the Internet Number Resource records number resources that are requested to be transferred. If delete: <i> If  insert: <em> all delete: </i> of insert: </em>  of the transferring Member's Internet Number Resource records member's Internet number resources registered are being transferred, a confirmation of this is requested. delete: </b> delete: </p> delete: <p> The Member insert: </strong> insert: </p>

The member must also indicate any End User assignment agreements that are requested to be transferred.

If a Member member transfers all of their Internet Number Resource records, the number resources, their RIPE NCC Standard Service Agreement of the Member may be terminated upon request of the member or following the member's confirmation (see Closure of LIR and Deregistration of Internet Number Resources, delete: <a href="https://www.ripe.net/publications/docs/closure#11"> Section A.1.1. delete: </a> ). delete: </p> delete: <p> delete: </p> delete: <p> delete: <b> of the RIPE NCC Procedural Document, " insert: <a href="http://www.ripe.net/publications/docs/closure"> Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources insert: </a> "). insert: </p>

insert: <strong> iv. The correct contact details of all organisations parties involved delete: </b> insert: </strong>

The RIPE NCC may ask the organisations parties involved to confirm the correctness of their contact details or to update them. The contact details include the billing contact details and the VAT number details.

delete: </p> delete: <p> delete: <b> insert: <strong> v. A Transfer Agreement signed by both parties or by their legal successors delete: </b> delete: </p> delete: <p> The RIPE NCC will make a insert: </strong> insert: </p>

The RIPE NCC provides the template of the Transfer Agreement available. Either that either party may submit the to the RIPE NCC. insert: </p>

The Transfer Agreement to the RIPE NCC, 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. insert: </p>

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 (e.g., senior manager, legal successor).

delete: </p> delete: <p> If the transferring party no longer exists by the time the RIPE NCC is being informed, the receiving party must send:

• an An official document (issued by a national authority) confirming the closure of the transferring party; and party
• a A copy of an older signed agreement between the relevant parties mentioning the transfer of the Internet Number Resource records. 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 Internet Number Resource records number resource should have been transferred to them.

delete: </p> delete: <p> delete: <b> insert: <strong> vi. An overview of the utilisation of all allocations and of the status of all independent Internet Number Resource number resource assignments delete: </b> insert: </strong>

The RIPE NCC may ask for an overview of the utilisation of all Internet Number Resources number resources registered to the Member member and of all End User assignment agreements signed by the Member. delete: </p> delete: <p> delete: </p> delete: <p> delete: <b> delete: <a name="receiving-organisation"> member. insert: </p>

insert: <a name="transfer32"> 3.2 If the Receiving Organisation Party is not yet a Member delete: </b> delete: </p> insert: </h4>

Members may wish to transfer their Internet Number Resource records number resource to another Member member or to an organisation a third party that is not yet a Member. a member.

If the Internet Number Resource records number resources are transferred to a non-Member, non-member, the receiving organisation party must apply to be a Member member by signing the a RIPE NCC Standard Service Agreement before the transfer takes place ( delete: <a href="https://www.ripe.net/lir-services/member-support/become-a-member"> insert: <a href="https://www.ripe.net/../../../../../../become-a-member"> more information on how to become a Member member is available ). delete: </p> delete: <p> If the receiving organisation party refuses to do the above, the RIPE NCC will not transfer the Internet Number Resource records number resources to them. insert: </p>

If the Internet number resources to be transferred are Independent Resources (IPv4 PI and AS Numbers), the receiving party may either apply to become a member by signing the RIPE NCC Standard Service Agreement, or can enter into a contractual relationship with a sponsoring LIR. For more information, please see the notes on  insert: <a href="https://www.ripe.net/../../../../../../participate/resource-management/independent-resources"> Requesting Independent Resources insert: </a> .

The request for the transfer can be submitted as described above (Section 1). delete: </p> delete: <p> delete: </p> delete: <p> delete: <b> delete: <a name="financial"> 3.1). insert: </p>

insert: <a name="transfer33"> 3.3 Financial Consequences delete: </b> delete: </p> insert: </h4>

All outstanding invoices and all outstanding financial obligations must be paid in full. If the RIPE NCC Standard Service Agreement is terminated in the course of the RIPE NCC financial year, the service fee for this Member member must be paid for the full year. The This payment is the responsibility of the receiving Member. delete: </p> delete: <p> member. If the receiving organisation party is not a member, then payment is the responsibility of the transferring member. insert: </p>

If the receiving party decides to sign the RIPE NCC Standard Service Agreement, then a sign-up fee must be paid (see delete: <a href="http://www.ripe.net/ripe/docs/ripe-499"> (see  insert: <a href="http://www.ripe.net/publications/docs/charging"> RIPE NCC Charging Scheme ).

insert: <a name="transfer34"> 3.4 Internet Number Resource Registration and RIPE Database Issues delete: </b> delete: </p> delete: <p> insert: </h4>

insert: <strong> The RIPE NCC will review the status of any IP address allocation or independent Internet Number Resource number resource assignment maintained by the organisations party involved, in compliance with the RIPE Policies current at the time of the transfer. delete: </p> delete: <p> The insert: </strong> insert: </p>

The transferring party or (if the transferring party does not exist anymore) the receiving Member member must deregister from the RIPE Database any invalid or overlapping registrations or unused assignment approvals. registrations.

The RIPE NCC will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this transfer. The transferring Member member must update all RIPE Database objects maintained by them that are related to this transfer.

insert: <a name="transfer35"> insert: </a> 3.5 Transfers Between LIR Accounts Belonging to the Same Member insert: </h4>

Transfers of Internet number resources between LIR accounts belonging to the same member fall within the scope of the RIPE Policy " insert: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies insert: </a> " and will be evaluated in accordance with them. insert: </p>

Any time restriction that is applied to Internet number resources when they are received must expire before they can be transferred. However, once this restriction has expired, new time restrictions will not be applied to these resources if they are further transferred between LIR accounts held by the same member. insert: </p>

The procedure described above in Section 3.1 is applicable except from paragraphs 3.1.ii and 3.1.v. insert: </p>

If after the transfer the member decides to close an LIR account, all outstanding invoices and all outstanding financial obligations for all LIR accounts must be paid in full. insert: </p>

The RIPE NCC will review the status of any IP address allocation or independent Internet number resource assignment maintained by the member, in compliance with the RIPE Policies current at the time of the transfer. insert: </p>

The member must deregister from the RIPE Database any invalid or overlapping registrations. insert: </p>

The RIPE NCC will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this transfer. The member must update all RIPE Database objects maintained by them that are related to this transfer. insert: </p>

insert: <a id="transfer36"> insert: </a> 3.6 Transfers of Internet Number Resources under Policy Restrictions Due to a Change in the Member's Business Structure insert: </h4>

Internet number resources that are subject to transfer restrictions imposed by the RIPE Policy " insert: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies insert: </a> ", and that are transferred due to a change in a member's business structure, must either remain registered with the original LIR account or be registered with a new LIR account. The receiving party will be provided with RIPE NCC services for these Internet number resources via either the original LIR account or the new LIR account until the policy restrictions are lifted. insert: </p>

insert: <a id="transfer37"> insert: </a> 3.7 Transfers due to Seizure insert: </h4>

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. insert: </p>

The RIPE NCC will comply on the condition that the court order: insert: </p>

insert: <li>
• Has entered into force and is recognised by the Dutch courts. insert: </li>
insert: <li>
• Is served by a bailiff in advance to the RIPE NCC in the form of an authentic enforceable document (e.g., a court order). insert: </li>
insert: <li>
• 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. insert: </li>
insert: <li>
• States the specific Internet number resources at issue. insert: </li>
insert: </ul>

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. insert: </p>

  insert: </p>

delete: <a name="official-legal-name"> insert: <a name="memberchanges"> 4.0 The Member Changes its Official Legal Name delete: <b> delete: </b>

It is the obligation of the Member member to inform the RIPE NCC immediately if any change in the Member's member's official legal name occurs.

The Member member must send an email to delete: <a class="email-link" href="mailto:nc[email protected]" target="_self" title=""> delete: <span class="email-link"> ncc [at] ripe [dot] delete: </span> delete: <span class="email-link"> net delete: </span> delete: </a> informing the RIPE NCC of the a request for name change. This email change via the LIR Portal. The request must include:

• New registration papers from the national authority; and
• The official legal documents supporting this change

If the requesting party does not have access to the LIR Portal, the request must be submitted via email to  insert: <a href="mailto:[email protected]"> [email protected] insert: </a>  and the above-mentioned documents must be uploaded via a secure link provided by the RIPE NCC.

The RIPE NCC will send a new delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/service-agreement" target="_self" title=""> new  insert: <a href="http://www.ripe.net/publications/docs/service-agreement"> RIPE NCC Standard Service Agreement for the Member  for the member to sign under the new official legal name. When the RIPE NCC receives the new RIPE NCC Standard Service Agreement properly signed by the Member, member, it will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this change. The Member member must update all RIPE Database objects maintained by them that are related to this change.

If the change in the member's official legal name occurred without a further change in the member's structure (e.g., merger with another legal entity, acquisition by/of another legal entity), the member will not have to sign a new RIPE NCC Standard Service Agreement. insert: </p>