You are here: Home > Publications > RIPE Document Store > European Internet Registry Policies And Procedures

Changes to European Internet Registry Policies And Procedures

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-185: European ripe-579: Transfer of Internet Registry Policies And Procedures Number Resource Records and Change of a Member’s Official Legal Name
delete: <p> delete: <br /> insert: <h3>

Contents insert: </h3>

insert: <p>

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

insert: <p>

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

insert: <p>

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

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

3.1 insert: <a class="anchor-link" href="#3.1"> Submission of the Request insert: </a> insert: </p>

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

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

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

3.3 insert: <a class="anchor-link" href="#3.3"> Billing Issues insert: </a> insert: </p>

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

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

insert: <p>

4.0 insert: <a class="anchor-link" href="#4.0"> The Member Changes its Official Legal Name insert: </a> insert: </p>

insert: <p>

insert: </p>

insert: <h3>

insert: <a name="1.0"> insert: </a> 1.0 Definitions insert: </h3>

insert: <p>

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

insert: <ul>
    insert: <li>
  • The registered allocations and assignments of a Member insert: </li>
  • insert: <li>
  • The independent Internet Number Resources insert: <b> insert: </b> assigned through the Member as a “sponsoring LIR” to an End User insert: </li>
  • insert: </ul>
insert: <p>

insert: </p>

insert: <h3>

insert: <a name="2.0"> insert: </a> 2.0 Introduction insert: </h3>

insert: <p>

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

insert: <ul>
    insert: <li>
  • The natural or legal persons holding the registration of Internet Number Resources insert: </li>
  • insert: <li>
  • The Internet Number Resource records that are registered to the natural or legal persons insert: </li>
  • insert: </ul>
insert: <p>

insert: </p>

insert: <p>

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

insert: <p>

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

insert: <ol>
    insert: <ol>
      insert: <li>
    1. Internet Number Resource records are transferred. Such transfers may take place: insert: <ul>
        insert: <li>
      • 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: </li>
      • insert: <li>
      • In the case of a pure transfer of an allocation from a Member to another Member according to RIPE Policies ( insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/ipv4-policies/#----transfers-of-allocations"> 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 insert: <a data-linktype="internal" target="_self" title="" href="./resolveuid/8768823a7d79496c8bff938729212474" data-val="8768823a7d79496c8bff938729212474" class="external-link"> RIPE NCC Listing Service insert: </a> insert: </li>
      • insert: </ul>
      insert: </li>
    2. insert: </ol>
    insert: </ol>
insert: <p>

insert: </p>

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

insert: </p>

insert: <p>

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

insert: <p>

insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

If a change in the Member's business structure is insert: <i> not insert: </i> accompanied by a transfer of Internet 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. insert: </p>

insert: <p>

insert: </p>

insert: <h3>

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

insert: <p>

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

insert: <p>

insert: </p>

insert: <p>

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

insert: <p>

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

insert: <ul> insert: <p>

insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

insert: </p>

insert: <p>

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

insert: <ul>
    insert: <li>
  • The full official legal names of all parties involved insert: </li>
  • insert: <li>
  • Which party will transfer the Internet Number Resource records and which party will receive them insert: </li>
  • insert: <li>
  • Recent registration papers issued by the relevant national authorities for all involved parties insert: </li>
  • insert: </ul>
insert: <p>

insert: </p>

insert: <p>

If 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 4.0 must be followed prior to the transfer of the Internet Number Resource records. The procedure described under 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, insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/closure/#a11"> section A.1.1. insert: </a> and insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/closure/#a12"> section A.1.2. insert: </a> ). insert: </p>

insert: <p>

insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

If a Member transfers all of their Internet 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 class="external-link" href="http://www.ripe.net/ripe/docs/closure/#a12"> section A.1.1. insert: </a> ). insert: </p>

insert: <p>

insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

insert: </p>

insert: <p>

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

insert: <p>

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. senior manager, legal successor). insert: </p>

insert: <p>

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

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

insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

insert: </p>

insert: <p>

insert: <b> insert: <a name="3.2"> insert: </a> 3.2 The Receiving Organisation is not yet a Member insert: </b> insert: </p>

insert: <p>

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

insert: <p>

If the Internet Number Resource records are transferred to a non-Member, the receiving organisation can: insert: </p>

insert: <ul>
    insert: <li>
  • Apply to be a Member by signing the RIPE NCC Standard Service Agreement before the transfer takes place ( insert: <a class="external-link" href="http://www.ripe.net/membership/new-members"> more information on how to become a Member is available insert: </a> ); or insert: </li>
  • insert: <li>
  • Undertake all rights and obligations from 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 insert: </li>
  • insert: </ul>
insert: <p>

insert: </p>

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

insert: <p>

The request for the transfer can be submitted as described in a ASCII section 3.1. insert: </p>

insert: <p>

insert: </p>

insert: <p>

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

insert: <p>

All outstanding invoices and PDF delete: </p> 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. insert: </p>

insert: <p>

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

insert: <p>

insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

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

insert: <p>

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

insert: <p>

insert: </p>

insert: <h3>

insert: <a name="4.0"> insert: </a> 4.0 The Member Changes its Official Legal Name 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>

insert: </p>

insert: <p>

The RIPE NCC will send a new insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/ssa"> 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 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. insert: </p>

European Transfer of Internet Registry Policies And Procedures Number Resource Records and Change of a Member’s Official Legal Name