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-709: ripe-628: Transfer of Internet Number Resources Resource Records and Change of a Member’s Official Legal Name
delete: <h2> insert: <h2 class="western">

Contents

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

insert: <p>

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

insert: <p>

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

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

insert: <span> 3.1 delete: <a href="#transfer31"> insert: <a href="#31"> Submission of the Request for Transfer delete: </p> delete: <p style="padding-left: 30px;"> insert: </span> insert: </p>

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

insert: <span> 3.2 delete: <a href="#transfer32"> 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 a Member delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> insert: </a> insert: <a href="#32"> a insert: </a> insert: <span> insert: <a href="#32"> Member insert: </a> insert: </span> insert: </span> insert: </p>

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

insert: <span> 3.3 delete: <a href="#transfer33"> insert: <a href="#33"> Financial Consequences delete: </p> delete: <p style="padding-left: 30px;"> insert: </span> insert: </p>

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

insert: <span> 3.4 delete: <a href="#transfer34"> insert: <a href="#34"> Internet Number Resource Registration and RIPE Database Issues delete: </p> 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> delete: <p style="padding-left: 30px;"> 3.6 delete: <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 delete: </a> delete: </p> delete: <p> insert: </span> insert: </p>

insert: <p>

insert: <span> 4.0 delete: <a href="#memberchanges"> 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="definitions"> 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 resources document: insert: </span> insert: </p>

insert: <p>

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

  • insert: <p>

    insert: <span> The registered allocation insert: <span> allocations and assignment records of a member assignments of a Member insert: </span> insert: </span> insert: </p>

  • In the case of a transfer of insert: <p>

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

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

  • The Internet number resources insert: <p>

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

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

insert: <p>

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

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

    • In insert: <p>

      insert: <span> I insert: </span> insert: <span> insert: <span> n the case of a pure transfer of Internet number resources IPv4 address records from the member a 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> ". Transfers of IPv4 Internet number resources ( 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 insert: </a> ”). Such a transfer may also be facilitated through the delete: <a data-val="e222449049284bb1af45883cccde2da1" href="../../../resolveuid/e222449049284bb1af45883cccde2da1" data-linktype="internal"> IPv4 Transfer insert: <a data-val="8768823a7d79496c8bff938729212474" href="./resolveuid/8768823a7d79496c8bff938729212474" data-linktype="internal"> RIPE NCC Listing Service delete: </a> . delete: <br /> delete: <br /> Service. insert: </a> insert: </span> insert: </span> insert: </p>

  2. The member insert: <p>

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

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

insert: <p>

insert: </p>

insert: <p>

insert: <span> insert: <b> Note: delete: <br /> delete: </strong> insert: </b> insert: </span> insert: </p>

insert: <p>

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

insert: <p>

insert: <span> 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. delete: </p> delete: <p> 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 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/publications/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>   delete: </p> delete: <h3> delete: <a name="transfer"> delete: </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 Resources Resource Records insert: </span> insert: </span>

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

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

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

insert: <ul>
    insert: <li>
  • insert: <p>

    insert: <span> 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 insert: <a href="mailto:ncc@ripe.net"> ncc@ripe.net insert: </a> insert: </span> insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    insert: <span> insert: <span> If the transfer is a transfer of IPv4 address records from one Member to another insert: </span> insert: </span> insert: <span> insert: <span> party ac insert: </span> insert: </span> insert: <span> insert: <span> cording to RIPE Policies ( 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 insert: </a> ”), the request must be submitted to insert: <a href="mailto:lir-help@ripe.net"> lir-help@ripe.net insert: </a> insert: </span> insert: </span> insert: </p>

    insert: </li>
  • insert: </ul>
insert: <p>

insert: <span> A registered contact or an authorised person (e.g., senior manager, legal successor) of the involved parties must submit a request to the RIPE NCC. More specifically: delete: </p> delete: <ul> delete: <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 delete: <a href="https://my.ripe.net/#/update-registry"> LIR Portal delete: </a> . If the requesting party does not have access rights to the LIR portal, the request must be submitted via email to delete: <a href="mailto:ncc@ripe.net"> ncc@ripe.net delete: </a> delete: </li> delete: <li> If this is a transfer of Internet number resource from one 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> ", the transferring party must submit the request via the delete: <a href="https://my.ripe.net/"> LIR Portal delete: </a> . delete: </li> delete: </ul> delete: <p> 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). delete: </p> delete: <p> must send the request. 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: <strong> insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <b> i. Information regarding the parties involved, including: delete: </strong> insert: </b> 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 resources 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>

If insert: <span> I insert: </span> insert: <span> insert: <span> f 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 insert: </a> insert: <a href="#4"> 4.0 must be followed prior to the transfer of the Internet number resources. delete: </p> delete: <p> resource records. insert: </span> insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <span> 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 Closure of LIR 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 number resources, insert: <a title="" href="https://www.ripe.net/publications/docs/closure#11" class="external-link" target="_self"> Section A.1.1. insert: </a> and Legacy Internet Resources delete: </a> ". delete: </p> delete: <p> delete: <strong> insert: <a title="" href="https://www.ripe.net/publications/docs/closure#12" class="external-link" target="_self"> Section A.1.2. insert: </a> ). insert: </span> insert: <b> 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, transfer of Internet number resources allocation according to the RIPE policies) delete: </strong> delete: </p> delete: <p> insert: </b> 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 (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. delete: </p> delete: <p> 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: </span> insert: </p>

insert: <p>

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

insert: <p>

insert: <span> insert: <b> iii. A list of the Internet number resources resource records that are requested to be transferred. If delete: <em> insert: </b> insert: <i> insert: <b> all delete: </em> insert: </b> insert: </i> insert: <b> 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: </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 Member transfers all of their Internet number resources, their resource records, the 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, insert: <a title="" href="https://www.ripe.net/publications/docs/closure#11" class="external-link" target="_self"> 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: </span> insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

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

insert: <p>

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

insert: <p>

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

insert: <p>

insert: <span> 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 registered contact person or authorised person (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 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 resources. 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 records should have been transferred to them. insert: </span> insert: </p>

delete: <strong> vi. insert: <span> insert: <b> 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 assignments delete: </strong> delete: </p> delete: <p> insert: </span> insert: </span> insert: </span> insert: </b> 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 registered to the member Member and of all End User assignment agreements signed by the member. Member. insert: </span> insert: </span>

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

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

insert: <p>

insert: <span> insert: <span> 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 href="https://www.ripe.net/../../../become-a-member"> 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 ). ) If the receiving party refuses to do the above, the RIPE NCC will not transfer the Internet number resources resource records to them. delete: </p> delete: <p> insert: </span> insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <span> If the Internet number resources resource records to be transferred are Provider Independent Resources (IPv4 PI and AS Numbers), (PI) 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. insert: </span> insert: <span> insert: <span> For more information, please see the notes on delete: <a href="https://www.ripe.net/../../../participate/resource-management/independent-resources"> Requesting Independent Resources delete: </a> . delete: </p> delete: <p> 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 above (Section 3.1). 1). insert: </span> insert: </span>

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

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

insert: <p>

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

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

delete: <strong> insert: <span> insert: <b> insert: <span> 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> delete: </p> delete: <p> The transferring party or (if the transferring party does not exist anymore) the insert: </span> insert: </b> insert: </span> insert: </p>

insert: <p>

insert: <span> The receiving member Member must deregister from the RIPE Database any invalid or overlapping registrations. delete: </p> delete: <p> registrations or unused assignment approvals. 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 Member must update all RIPE Database objects maintained by them that are related to this transfer. delete: </p> 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> " 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: </h3>

insert: <p>

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

insert: <p>

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

insert: <ul>
    insert: <li>
  • insert: <p>

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

    insert: </li>
  • insert: <li>
  • insert: <p>

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

    insert: </li>
  • insert: </ul>
insert: <p>

insert: <span> insert: <span> T insert: </span> insert: </span> insert: <span> insert: <span> insert: <span> he RIPE NCC will be evaluated in accordance with them. delete: </p> delete: <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, send a new time restrictions will not be applied to these resources if they are further transferred between LIR accounts held insert: <a title="" href="https://www.ripe.net/publications/docs/service-agreement" class="external-link" target="_self"> RIPE NCC Standard Service Agreement insert: </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 same member. 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 for all LIR accounts 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 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: <h4> delete: <a id="transfer36"> delete: </a> 3.6 Transfers of Internet Number Resources under Policy Restrictions Due to a Change in the Member's Business Structure delete: </h4> delete: <p> Internet number resources that are subject to transfer restrictions imposed by 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 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. 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 in the member's official legal name occurs. delete: </p> delete: <p> The member must send a request for name change via the LIR Portal. The request 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> If the requesting party does not have access to the LIR Portal, the request must be submitted via email to delete: <a href="mailto:ncc@ripe.net"> ncc@ripe.net delete: </a> and the above-mentioned documents must be uploaded via a secure link provided by the RIPE NCC. delete: </p> 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 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. delete: </p> insert: </span> insert: </span> insert: </span> insert: </p>

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