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

Contents

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

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

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

insert: <a class="anchor-link" href="#submission" target="_self" title=""> 3.1 delete: <a href="#transfer31"> Submission of the Request for Transfer

insert: <a class="anchor-link" href="#receiving-organisation" target="_self" title=""> 3.2 delete: <a href="#transfer32"> If the Receiving Party Organisation is not a Member delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> yet a Member insert: </a> insert: </p>

insert: <a class="anchor-link" href="#financial" target="_self" title=""> 3.3 delete: <a href="#transfer33"> Financial Consequences

insert: <a class="anchor-link" href="#internet-number-resource-reg" target="_self" title=""> 3.4 delete: <a href="#transfer34"> Internet Number Resource Registration and RIPE Database Issues

insert: <a class="anchor-link" href="#official-legal-name" target="_self" title=""> 4.0 delete: <a href="#memberchanges"> The Member Changes its Official Legal Name

1.0 Definitions

For the purposes of this document, document Internet Number Resource records refer to: insert: </p>

insert: <li>
• The registered allocations and assignments of a Member insert: </li>
insert: <li>
• The independent Internet number resources refer to: delete: </p> delete: <ul> delete: <li> The registered allocation and assignment records of a member delete: </li> delete: <li> In the case of a transfer of Internet number resources from the member to another party according to RIPE Policy “ delete: <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> ”. Such a transfer may also be facilitated insert: <b> insert: </b> assigned through the RIPE NCC Listing Service. Member as a “sponsoring LIR” to an End User

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 resources Number Resource records that are registered to these the natural or and 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.

A member insert: </p>

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

1. Internet Number Resource records are transferred. Such transfers may take place: delete: </li>
   • Because of a change in the member's business structure (for of the Member, 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 transfer of Internet number resources pure transfer of an allocation from the member a Member to another party Member according to RIPE Policy “ delete: <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> ”. ( insert: <a title="" href="https://www.ripe.net/publications/docs/ipv4-policies#55" class="external-link" target="_self"> Section 5.5, IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region insert: </a> ). Such a transfer may also be facilitated through the delete: <a data-val="e222449049284bb1af45883cccde2da1" href="../../../resolveuid/e222449049284bb1af45883cccde2da1" data-linktype="internal"> insert: <a data-linktype="internal" target="_self" title="" href="resolveuid/8768823a7d79496c8bff938729212474" data-val="8768823a7d79496c8bff938729212474" class="internal-link"> RIPE NCC Listing Service delete: </a> . delete: <br /> delete: <br /> Service. insert: </a>
   insert: </li>
2. The member Member changes its official legal name delete: <strong> insert: <b> . delete: </strong> insert: </b> Such a change may occur, for example, because of a merger or acquisition of the member's Member's organisation.

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

insert: <b> Note: delete: </strong> insert: </b>

If a change in a member's the Member's official legal name is accompanied by a transfer of Internet number resources, the member Number Resource records, the Member must first inform the RIPE NCC of the name change and then of the transfer.

If a change in a member's the Member's business structure is delete: <em> insert: <i> not delete: </em> insert: </i> accompanied by a transfer of Internet number resources Number Resource records 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.

3.0 Transfer of Internet Number Resources Resource Records

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

insert: </p>

insert: <b> insert: <a name="submission"> 3.1 Submission of the Request for Transfer delete: </h4> delete: <p> For the transfer to be processed, one insert: </b> insert: </p>

One of the involved parties must submit a request to the RIPE NCC: by email to the RIPE NCC for the transfer to be executed:

• 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 of the Member (e.g., merger, acquisition, bankruptcy, liquidation), merger or acquisition), the request must be submitted via the LIR Portal. If the requesting party does not have access rights to the LIR portal, the request must be submitted via email to [email protected]
• If this the transfer is a transfer of Internet number resource allocation from one member Member to another party Member according to RIPE Policy “ delete: <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> ”, ( insert: <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 insert: </a> ), the request must be submitted via the delete: <a href="https://my.ripe.net" data-linktype="external" data-val="https://my.ripe.net"> LIR Portal delete: </a> . to insert: <a href="mailto:[email protected]"> [email protected] insert: </a>

A registered contact or an authorised person (e.g., senior manager, legal successor) must send the request.

insert: </p>

The RIPE NCC will ask for the following information:

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

• The full official legal names of all parties involved
• Which party will transfer the Internet number resources Number Resource records 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 those the ones in the relevant signed RIPE NCC Standard Service Agreement, then the procedure described in delete: <a href="#memberchanges"> under insert: <a class="anchor-link" href="#official-legal-name" target="_self" title=""> Section 4.0 must be followed prior to the transfer of the Internet number resources. delete: </p> delete: <p> Number Resource records. The procedure described under Section 4.0 is not necessary for the transferring member Member if the RIPE NCC Standard Service Agreement for that member of the transferring Member is terminated (see Sections A.1.1 and A.1.2 of the RIPE NCC Procedural Document, “ delete: <a href="http://www.ripe.net/publications/docs/closure" data-linktype="external" data-val="http://www.ripe.net/publications/docs/closure"> Closure of Members, LIR and Deregistration of Internet Resources and Legacy Internet Resources delete: </a> ”. delete: </p> delete: <p> delete: <strong> Number Resources, insert: <a href="https://www.ripe.net/publications/docs/closure#11"> Section A.1.1. insert: </a> and insert: <a href="https://www.ripe.net/publications/docs/closure#12"> Section A.1.2. insert: </a> ). insert: </p>

insert: </p>

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

If the transfer is taking place due to a change in the structure of the organisation(s) involved (e.g., merger, acquisition), involved, a description of the changes among these the organisation(s) is necessary. This The description must be accompanied by the all 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 member to another), then these cases will fall within the scope of RIPE Policy “ delete: <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> ”. delete: </p> delete: <p> delete: <strong> insert: </p>

insert: <b> iii. A list of the Internet number resources Number Resource records that are requested to be transferred. If delete: <em> insert: <i> all delete: </em> insert: </i> of the transferring member's Internet number resources Member's Internet Number Resource records registered are being transferred, a confirmation of this is requested. delete: </strong> delete: </p> delete: <p> The member insert: </b> 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 resources, their Number Resource records, the RIPE NCC Standard Service Agreement of the Member may be terminated (see Closure of LIR and Deregistration of Internet Number Resources, insert: <a href="https://www.ripe.net/publications/docs/closure#11"> Section A.1.1. of the RIPE NCC Procedural Document, “ delete: <a href="http://www.ripe.net/publications/docs/closure"> Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources delete: </a> ”). delete: </p> delete: <p> delete: <strong> insert: </a> ). insert: </p>

insert: </p>

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

The RIPE NCC may ask the parties organisations 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: <strong> insert: </p>

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

The RIPE NCC will make a template of the Transfer Agreement that either available. Either party may submit to the RIPE NCC. delete: </p> delete: <p> The the Transfer Agreement must be to the RIPE NCC, 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. delete: </p> delete: <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 contact person or authorised person (e.g., senior manager, legal successor).

insert: </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 party; and
• A a copy of an older signed agreement between the relevant parties mentioning the transfer of the Internet number resources. Number Resource records. If such an agreement is not available, the RIPE NCC may accept a receiving party must send confirmation of the transfer to the RIPE NCC signed by an authorised person (e.g., senior manager, legal successor) of the receiving party. successor). 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 Number Resource records should have been transferred to them.

delete: <strong> insert: </p>

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

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: <h4> delete: <a name="transfer32"> Member. insert: </p>

insert: </p>

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

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

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

If the receiving party organisation refuses to do the above, the RIPE NCC will not transfer the Internet number resources Number Resource records to them. delete: </p> delete: <p> If the Internet number resources to be transferred are Provider Independent (PI) addresses, 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 delete: <a data-val="9aaab7c7511208c0395fcc9d76608352" href="../../../resolveuid/9aaab7c7511208c0395fcc9d76608352" data-linktype="internal"> Requesting Independent Resources delete: </a> .

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

insert: </p>

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

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. This The payment is the responsibility of the receiving member. Member. insert: </p>

If the receiving party is not a member, then payment is the responsibility of the transferring member. delete: </p> delete: <p> If the receiving party organisation 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/publications/docs/charging"> insert: <a href="http://www.ripe.net/ripe/docs/ripe-499"> RIPE NCC Charging Scheme ).

insert: </p>

insert: <b> insert: <a name="db-issues"> insert: </a> insert: <a name="internet-number-resource-reg"> 3.4 Internet Number Resource Registration and RIPE Database Issues delete: </h4> delete: <p> delete: <strong> insert: </b> insert: </p>

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

The receiving member Member must deregister from the RIPE Database any invalid or overlapping registrations or unused assignment approvals.

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.

delete: <a name="memberchanges"> insert: <a name="official-legal-name"> 4.0 The Member Changes its Official Legal Name insert: <b> insert: </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 href="mailto:[email protected]"> [email protected] insert: <a class="email-link" href="mailto:[email protected]" target="_self" title=""> insert: <span class="email-link"> ncc [at] ripe [dot] insert: </span> insert: <span class="email-link"> net insert: </span> informing the RIPE NCC of the name change. This email must include:

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

insert: </p>

The RIPE NCC will send a new delete: <a href="http://www.ripe.net/publications/docs/service-agreement"> insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/service-agreement" target="_self" title=""> RIPE NCC Standard Service Agreement for the member 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.