You are here: Home > Publications > RIPE Document Store > Transfer of Internet Number Resources and Change of a Member’s Official Legal Name

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

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-689: ripe-648: Transfer of Internet Number Resources Resource Records and Change of a Member’s Official Legal Name
delete: <h2> insert: <h4>

Contents delete: </h2> insert: </h4>

1.0 delete: <a href="#definitions"> insert: <a href="#1"> Definitions

2.0 delete: <a href="#introduction"> insert: <a href="#2"> Introduction

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

insert: <p style="padding-left: 30px; ">

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

delete: <p style="padding-left: 30px;"> insert: <p style="padding-left: 30px; ">

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

delete: <p style="padding-left: 30px;"> insert: <p style="padding-left: 30px; ">

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

delete: <p style="padding-left: 30px;"> insert: <p style="padding-left: 30px; ">

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

delete: <p style="padding-left: 30px;"> 3.5 delete: <a href="#transfer35"> Transfers Between LIR Accounts Belonging to the Same Member delete: </a> delete: </p>

4.0 delete: <a href="#memberchanges"> Member insert: <a href="#4"> The insert: <span> Member insert: </span> Changes its Official Legal Name

  insert: </p>

insert: <p>

insert: <a name="1"> insert: </a>

delete: <a name="definitions"> delete: </a> 1.0 Definitions

For the purposes of this document, Internet number resources document: insert: </p>

insert: <p>

Internet number resource records refer to: to

  • The registered allocation and assignment records of a member allocations and assignments of a Member
  • In the case of a transfer of The independent 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 assigned through the RIPE NCC Listing Service. Member as a “sponsoring LIR” to an End User

  insert: <a name="2"> insert: </a>

delete: <a name="introduction"> delete: </a> 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
  • The Internet number resources resource records that are registered to these the natural or and legal persons

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

A member 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:
  2. The member Member changes its official legal name delete: <strong> . delete: </strong> name. Such a change may occur, for example, because of a merger or acquisition of the member's Member's organisation.

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

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 User's business structure. This procedure is described in the RIPE NCC Procedural Document, delete: <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"> insert: <a href="https://www.ripe.net/ripe/docs/lir-end-user-contractual-changes"> Independent Internet Number Resources Contractual Relationship Changes Between Sponsoring LIR and End User ”. delete: </p> delete: <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, “ delete: <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 delete: </a> ”. delete: </p> delete: <p>   ”. insert: </p>

insert: <p>

insert: <a name="3"> insert: </a>

delete: <a name="transfer"> delete: </a> 3.0 Transfer of Internet Number Resources Resource Records

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

insert: <p>

insert: <a name="31"> insert: </a>

delete: <a name="transfer31"> delete: </a> 3.1 Submission of the Request for Transfer

For the transfer to be processed, one 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:

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

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 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 href="#4"> Section 4.0 must be followed prior to the transfer of the Internet number resources. 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, Deregistration of Internet Resources and Legacy Internet Resources delete: </a> ”. delete: </p> delete: <p> delete: <strong> Resources, insert: <a href="https://www.ripe.net/ripe/docs/closure#11"> Section A.1.1. insert: </a> and insert: <a href="https://www.ripe.net/ripe/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 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: <b> iii. A list of the Internet number resources 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>

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 resource records, the RIPE NCC Standard Service Agreement of the Member may be terminated (see Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources, insert: <a href="https://www.ripe.net/ripe/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 involved delete: </strong> insert: </b>

The RIPE NCC may ask the 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: <strong> 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>

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

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. resource records. 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 Internet number resource records should have been transferred to them.

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

The RIPE NCC may ask for an overview of the utilisation of all Internet number resources registered to the member Member and of all End User assignment agreements signed by the member. Member. insert: </p>

insert: <p>

insert: <a name="32"> insert: </a>

delete: <a name="transfer32"> delete: </a> 3.2 If the Receiving Party is not a Member

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

If the Internet number resources resource records are transferred to a non-member, non-Member, the receiving party 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 data-linktype="internal" target="_self" title="" href="resolveuid/e292d712e8380f2d2507f0a15e4b66a4" data-val="e292d712e8380f2d2507f0a15e4b66a4" class="internal-link"> more information on how to become a member Member is available ). ) If the receiving party refuses to do the above, the RIPE NCC will not transfer the Internet number resources resource records to them.

If the Internet number resources resource records to be transferred are Provider Independent (PI) addresses, addresses , the receiving party may either apply to become a member be a Member by signing the RIPE NCC Standard Service Agreement, 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"> insert: <a data-linktype="internal" target="_self" title="" href="resolveuid/19535eb1d3f320e6aaec89eec3a8ba6d" data-val="19535eb1d3f320e6aaec89eec3a8ba6d" class="internal-link"> Requesting Independent Resources .

The request for the transfer can be submitted as described above (Section 3.1). 1). insert: </p>

insert: <p>

insert: <a name="33"> insert: </a>

delete: <a name="transfer33"> delete: </a> 3.3 Financial Consequences

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. If Member.If the receiving party is not a member, Member, then the payment is the responsibility of the transferring member. Member.

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/publications/docs/charging"> insert: <a href="http://www.ripe.net/ripe/docs/charging"> RIPE NCC Charging Scheme ).

insert: <p>

insert: <a name="34"> insert: </a> insert: </p>

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

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

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: <h4> delete: <a name="transfer35"> delete: </a> 3.5 Transfers Between LIR Accounts Belonging to the Same Member delete: </h4> delete: <p> Transfers of Internet number resources between LIR accounts belonging to the same member fall within the scope of the 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> ” and insert: <p>

insert: <a name="4"> insert: </a> insert: </p>

insert: <h3>

insert: <b> 4.0 The Member Changes its Official Legal Name insert: </b> insert: </h3>

insert: <p>

It is the obligation of the Member to inform the RIPE NCC immediately if any change in the Member's official legal name occurs. insert: </p>

insert: <p>

The Member must send an email to insert: <a href="mailto:ncc@ripe.net"> ncc@ripe.net insert: </a> informing the RIPE NCC of the name change. This email must include: insert: </p>

insert: <ul>
    insert: <li>
  • New registration papers from the national authority; and insert: </li>
  • insert: <li>
  • The official legal documents supporting this change insert: </li>
  • insert: </ul>
insert: <p>

The RIPE NCC will be evaluated in accordance with them. delete: </p> delete: <p> The procedure described above in Section 3.1 is applicable except from paragraphs 3.1.ii and 3.1.v. delete: </p> delete: <p> If after the transfer the member decides to close an LIR account, all outstanding invoices and all outstanding financial obligations send a new insert: <a href="http://www.ripe.net/ripe/docs/service-agreement"> RIPE NCC Standard Service Agreement insert: </a> for this LIR account must be paid in full. delete: </p> delete: <p> The RIPE NCC will review the status of any IP address allocation or independent Internet number resource assignment maintained 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, in compliance with the RIPE Policies current at the time of the transfer. delete: </p> delete: <p> The member must deregister from the RIPE Database any invalid or overlapping registrations. delete: </p> delete: <p> The RIPE NCC Member, it will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this transfer. The member change. The Member must update all RIPE Database objects maintained by them that are related to this transfer. delete: </p> delete: <p>   delete: </p> delete: <h3> delete: <a name="memberchanges"> delete: </a> 4.0 Member Changes Official Legal Name delete: </h3> delete: <p> It is the obligation of the member to inform the RIPE NCC immediately if any change. insert: </p>

insert: <p>

insert: <span> If the change in the member's official legal name occurs. delete: </p> delete: <p> The member must send an email to delete: <a href="mailto:ncc@ripe.net"> ncc@ripe.net delete: </a> informing the RIPE NCC of the name change. This email must include: delete: </p> delete: <ul> delete: <li> New registration papers from the national authority; and delete: </li> delete: <li> The official legal documents supporting this change delete: </li> delete: </ul> delete: <p> The RIPE NCC will send a new delete: <a href="http://www.ripe.net/publications/docs/service-agreement"> RIPE NCC Standard Service Agreement delete: </a> 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, it will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this change. The member must update all RIPE Database objects maintained by them that are related to this change. delete: </p> delete: <p> If the change in the member's Member's official legal name occurred without a further change in the member's Member's structure (e.g., (e.g. merger with another legal entity, acquisition by/of another legal entity), the member Member will not have to sign a new RIPE NCC Standard Service Agreement. delete: </p> insert: </span> insert: </p>

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