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

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

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-579: ripe-628: Transfer of Internet Number Resource Records and Change of a Member’s Official Legal Name
delete: <h3> insert: <h2 class="western">

Contents delete: </h3> delete: <p> insert: </h2>

insert: <p>

insert: <span> 1.0 delete: <a class="anchor-link" href="#1.0"> insert: <a href="#1"> Definitions delete: </p> delete: <p> insert: </span> insert: </p>

insert: <p>

insert: <span> 2.0 delete: <a class="anchor-link" href="#2.0"> insert: <a href="#2"> Introduction delete: </p> delete: <p> insert: </span> insert: </p>

insert: <p>

insert: <span> 3.0 delete: <a class="anchor-link" href="#3.0"> insert: <a href="#3"> Transfer of Internet Number Resource Records insert: </span>

insert: <span> 3.1 delete: <a class="anchor-link" href="#3.1"> insert: <a href="#31"> Submission of the Request delete: </a> for Transfer insert: </a> insert: </span>

insert: <span> 3.2 delete: <a class="anchor-link" href="#3.2"> insert: <a href="#32"> If the Receiving insert: </a> insert: <a href="#32"> Party insert: </a> insert: <a href="#32"> insert: </a> insert: <a href="#32"> is insert: </a> insert: <a href="#32"> not yet a Member delete: </a> insert: </a> insert: <a href="#32"> a insert: </a> insert: <span> insert: <a href="#32"> Member insert: </a> insert: </span> insert: </span>

insert: <span> 3.3 delete: <a class="anchor-link" href="#3.3"> Billing Issues delete: </a> insert: <a href="#33"> Financial Consequences insert: </a> insert: </span>

insert: <span> 3.4 delete: <a class="anchor-link" href="#3.4"> insert: <a href="#34"> Internet Number Resource Registration and RIPE Database Issues delete: </p> delete: <p> insert: </span> insert: </p>

insert: <p>

insert: <span> 4.0 delete: <a class="anchor-link" href="#4.0"> The Member insert: <a href="#4"> The insert: <span> Member insert: </span> Changes its Official Legal Name delete: </p> delete: <p> delete: </p> delete: <h3> delete: <a name="1.0"> delete: </a> insert: </span> insert: </p>

insert: <h3 class="western">

insert: <a name="1"> insert: </a> insert: <span> insert: <span> 1.0 Definitions insert: </span> insert: </span>

insert: <span> For the purposes of this document Internet Number Resource document: insert: </span> insert: </p>

insert: <p>

insert: <span> Internet number resource records refer to: to insert: </span>

  • insert: <p>

    insert: <span> The registered insert: <span> allocations and assignments of a Member insert: </span> insert: </span> insert: </p>

  • insert: <p>

    insert: <span> The independent Internet Number Resources delete: <b> delete: </b> number resources assigned through the Member as a “sponsoring LIR” to an End User insert: </span> insert: </p>

delete: <p> delete: </p> delete: <h3> delete: <a name="2.0"> delete: </a> insert: <h3 class="western">

insert: <a name="2"> insert: </a> insert: <span> insert: <span> 2.0 Introduction insert: </span> insert: </span>

insert: <span> In order for the RIPE NCC to maintain an accurate registry, it must hold accurate data concerning: insert: </span>

  • insert: <p>

    insert: <span> The natural or legal persons holding the registration of Internet Number Resources number resources insert: </span> insert: </p>

  • The Internet Number Resource insert: <p>

    insert: <span> The Internet number resource records that are registered to the natural or and legal persons insert: </span> insert: </p>

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

insert: <p>

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

  1. insert: <p>

    insert: <span> Internet Number Resource records are transferred. Such transfers may take place: insert: </span> insert: </p>

    • insert: <p>

      insert: <span> Because of a change in the business structure of the Member, for example in the case of a merger or acquisition of the Member's organisation; or insert: </span> insert: </p>

    • In insert: <p>

      insert: <span> I insert: </span> insert: <span> insert: <span> n the case of a pure transfer of an allocation IPv4 address records from a Member to another Member party according to RIPE Policies ( delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/ipv4-policies/#----transfers-of-allocations"> section 5.5, IPv4 insert: <a title="" href="https://www.ripe.net/publications/docs/ipv4-policies#55" class="external-link" target="_self"> Sections 5.5 and 6.4 , "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region ). ”). Such a transfer may also be facilitated through the delete: <a data-linktype="internal" target="_self" title="" href="./resolveuid/8768823a7d79496c8bff938729212474" data-val="8768823a7d79496c8bff938729212474" class="external-link"> insert: <a data-val="8768823a7d79496c8bff938729212474" href="./resolveuid/8768823a7d79496c8bff938729212474" data-linktype="internal"> RIPE NCC Listing Service delete: </a> Service. insert: </a> insert: </span> insert: </span> insert: </p>

  2. delete: </ol> delete: </ol> delete: <p> delete: </p> delete: <ol>
  3. insert: <p>

    insert: <span> The Member changes its official legal name . Such a change may occur, for example, because of a merger or acquisition of the Member's organisation. insert: </span> insert: </p>

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

Note:

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

insert: <p>

insert: <span> If a change in the Member's business structure is not accompanied by a transfer of Internet Number Resource number resource records or a change in the Member's official legal name, then the RIPE NCC does not need to be informed of this change. delete: </p> delete: <p> delete: </p> delete: <h3> delete: <a name="3.0"> delete: </a> insert: </span> insert: </p>

insert: <p>

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

insert: <h3 class="western">

insert: <a name="3"> insert: </a> insert: <span> insert: <span> 3.0 Transfer of Internet Number Resource Records insert: </span> insert: </span>

insert: <span> If a Member transfers their Internet Number Resource number resource records 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="3.1"> insert: </span> insert: </p>

insert: <h4>

insert: <a name="31"> 3.1 Submission of the Request for Transfer delete: </b> delete: </p> delete: <p> insert: </h4>

insert: <p>

insert: <span> One of the involved parties must submit a request by email to the RIPE NCC for the transfer to be executed: insert: </span>

  • insert: <p>

    insert: <span> If the transfer is due to a change in the business structure of the Member (e.g. (e.g., merger or acquisition), the request must be submitted to [email protected] insert: </span> insert: </p>

  • insert: <p>

    insert: <span> insert: <span> If the transfer is a transfer of allocation IPv4 address records from one Member to another Member according insert: </span> insert: </span> insert: <span> insert: <span> party ac insert: </span> insert: </span> insert: <span> insert: <span> cording to RIPE Policies ( delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/ipv4-policies/#----transfers-of-allocations"> section 5.5, IPv4 insert: <a title="" href="https://www.ripe.net/publications/docs/ipv4-policies#55" class="external-link" target="_self"> Sections 5.5 and 6.4, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region ), ”), the request must be submitted to [email protected] insert: </span> insert: </span> insert: </p>

delete: </p> delete: <p> insert: <span> A registered contact or an authorised person (e.g. (e.g., senior manager, legal successor) must send the request. delete: </p> delete: <p> insert: </span> insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: <span> The RIPE NCC will ask for the following information: delete: </p> delete: <p> delete: </p> delete: <p> insert: </span> insert: </p>

insert: <p>

insert: <span> i. Information regarding the parties involved, including: insert: </span>

  • insert: <p>

    insert: <span> The full official legal names of all parties involved insert: </span> insert: </p>

  • insert: <p>

    insert: <span> Which party will transfer the Internet Number Resource number resource records and which party will receive them insert: </span> insert: </p>

  • insert: <p>

    insert: <span> Recent registration papers issued by the relevant national authorities for all involved parties insert: </span> insert: </p>

delete: </p> delete: <p> If insert: <span> I insert: </span> insert: <span> insert: <span> f the current official legal names of the involved Members are different from the ones in the relevant signed RIPE NCC Standard Service Agreement, then the procedure described under section insert: <a href="#4"> Section insert: </a> insert: <a href="#4"> 4.0 insert: </a> must be followed prior to the transfer of the Internet Number Resource number resource records. insert: </span> insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <span> The procedure described under section Section 4.0 is not necessary for the transferring Member if the RIPE NCC Standard Service Agreement of the transferring Member is terminated (see Closure of LIR and Deregistration of Internet Number Resources, delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/closure/#a11"> section number resources, insert: <a title="" href="https://www.ripe.net/publications/docs/closure#11" class="external-link" target="_self"> Section A.1.1. and delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/closure/#a12"> section insert: <a title="" href="https://www.ripe.net/publications/docs/closure#12" class="external-link" target="_self"> Section A.1.2. ). delete: </p> delete: <p> delete: </p> delete: <p> insert: </span> insert: <span> insert: </span> insert: </b> insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <b> insert: <span> insert: <br />
insert: </span>
insert: </b>
insert: </span>
insert: </p>

insert: <p>

insert: <span> insert: <b> insert: <span> ii. A description of the reason for the transfer (for example, exa insert: </span> mple, due to merger, acquisition, or transfer of allocation according to the RIPE policies) delete: </p> delete: <p> insert: </span> insert: </p>

insert: <p>

insert: <span> If the transfer is taking place due to a change in the structure of the organisation(s) involved, a description of the changes among the organisation(s) is necessary. The description must be accompanied by all official legal documents proving/supporting the changes the request is based on. delete: </p> delete: <p> delete: </p> delete: <p> insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <b> insert: <br />
insert: </b>
insert: </span>
insert: </p>

insert: <p>

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

insert: <p>

insert: <span> The Member must also indicate any End User assignment agreements that are requested to be transferred. delete: </p> delete: <p> insert: </span> insert: </p>

insert: <p>

insert: <span> If a Member transfers all of their Internet Number Resource 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, delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/closure/#a12"> section number resources, insert: <a title="" href="https://www.ripe.net/publications/docs/closure#11" class="external-link" target="_self"> Section A.1.1. ). delete: </p> delete: <p> delete: </p> delete: <p> insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <b> insert: <br />
insert: </b>
insert: </span>
insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

insert: <span> insert: <b> insert: <br />
insert: </b>
insert: </span>
insert: </p>

insert: <p>

insert: <span> v. A Transfer Agreement signed by both parties or by their legal successors delete: </p> delete: <p> insert: </span> insert: </p>

insert: <p>

insert: <span> The RIPE NCC will make a template of the Transfer Agreement available. Either party may submit the Transfer Agreement to the RIPE NCC, signed by authorised persons for both parties. 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. (e.g., senior manager, legal successor). delete: </p> delete: <p> insert: </span> insert: </p>

insert: <p>

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

  • An insert: <p>

    insert: <span> an official document (issued by a national authority) confirming the closure of the transferring party; and insert: </span> insert: </p>

  • A insert: <p>

    insert: <span> a copy of an older signed agreement between the relevant parties mentioning the transfer of the Internet Number Resource number resource records. If such an agreement is not available, the receiving party must send confirmation of the transfer to the RIPE NCC signed by an authorised person (e.g. (e.g., senior manager, legal 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 them. insert: </span> insert: </p>

delete: </p> delete: <p> delete: </p> delete: <p> delete: </p> delete: <p> delete: </p> delete: <p> insert: <span> vi. insert: <span> insert: <span> insert: <br />
insert: </span>
insert: </span>
insert: </b>
insert: </span>
insert: </p>

insert: <p>

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

insert: <p>

insert: <span> insert: <span> The RIPE NCC may ask for an overview of the utilisation of all Internet Number Resources number resources registered to the 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="3.2"> insert: </span> insert: </span> insert: </p>

insert: <h4>

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

insert: <p>

insert: <span> insert: <span> Members may wish to transfer their Internet Number Resource number resource records to another Member or to an organisation a third party that is not yet a Member. delete: </p> delete: <p> insert: </span> insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <span> If the Internet Number Resource number resource records are transferred to a non-Member, the receiving organisation can: delete: </p> delete: <ul> delete: <li> Apply party must apply to be a Member by signing the RIPE NCC Standard Service Agreement before the transfer takes place ( delete: <a class="external-link" href="http://www.ripe.net/membership/new-members"> insert: <a href="https://www.ripe.net/lir-services/member-support/become-a-member"> more information on how to become a Member is available ); or delete: </li> delete: <li> Undertake all rights and obligations from ) If the receiving party refuses to do the above, the RIPE NCC will not transfer the Internet number resource records to them. insert: </span> insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <span> If the Internet number resource records to be transferred are Provider Independent (PI) addresses , the receiving party may either apply to be a Member by signing the RIPE NCC Standard Service Agreement signed by the transferring Member. This might happen if all Internet Number Resource records are transferred. The transferring party is then no longer considered to be a Member delete: </li> delete: </ul> delete: <p> delete: </p> delete: <p> If the receiving organisation refuses to do either of the above, the RIPE NCC will not transfer the Internet Number Resource records to them. delete: </p> delete: <p> or enter into a contractual relationship with a sponsoring LIR. insert: </span> insert: <span> insert: <span> For more information, please see: insert: </span> insert: </span> insert: </span> insert: </p>

insert: <p>

insert: <a href="https://www.ripe.net/lir-services/resource-management/independent-resources/"> insert: <span> insert: <span> insert: <span> insert: <span> https://www.ripe.net/lir-services/resource-management/independent-resources/ insert: </span> insert: </span> insert: </span> insert: </span> insert: </a> insert: </p>

insert: <p>

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

insert: <h4>

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

insert: <p>

insert: <span> insert: <span> 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 must be paid for the full year. The payment is the responsibility of the receiving Member.If the receiving party is not a Member, then the payment is the responsibility of the transferring Member. delete: </p> delete: <p> insert: </span> insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <span> If the receiving organisation party decides to sign the RIPE NCC Standard Service Agreement, then a sign-up fee must be paid (see delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/charging"> insert: <a href="http://www.ripe.net/ripe/docs/charging"> RIPE NCC Charging Scheme ). delete: </p> delete: <p> delete: </p> delete: <p> delete: <b> delete: <a name="3.4"> insert: </span> insert: </span> insert: </p>

insert: <h4>

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

insert: <p>

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

insert: <p>

insert: <span> The receiving Member must deregister from the RIPE Database any invalid or overlapping registrations or unused assignment approvals. delete: </p> delete: <p> insert: </span> insert: </p>

insert: <p>

insert: <span> 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 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="4.0"> delete: </a> insert: </span> insert: </p>

insert: <h3 class="western">

insert: <a name="4"> insert: </a> insert: <span> insert: <span> 4.0 The Member Changes its Official Legal Name insert: </span> insert: </span>

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

insert: <p>

insert: <span> The Member must send an email to [email protected] informing the RIPE NCC of the name change. This email must include: insert: </span>

  • insert: <p>

    insert: <span> New registration papers from the national authority; and insert: </span> insert: </p>

  • insert: <p>

    insert: <span> The official legal documents supporting this change insert: </span> insert: <br />
    insert: <br />
    insert: </p>

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