You are here: Home > Publications > RIPE Document Store > RIPE NCC Internet Numbers Registration Procedures

Changes to RIPE NCC Internet Numbers Registration Procedures

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-065: RIPE NCC ripe-595: Transfer of Internet Numbers Registration Procedures Number Resource Records and Change of a Member’s Official Legal Name
delete: <p> insert: <h2>

Contents insert: </h2>

insert: <p>

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

insert: <p>

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

insert: <p>

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

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

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

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

insert: <a class="anchor-link" href="#receiving-organisation" target="_self" title=""> 3.2 If the Receiving Organisation is not yet a Member insert: </a> insert: </p>

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

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

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

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

insert: <p>

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

insert: <p>

insert: </p>

insert: <h3>

insert: <a name="definitions"> 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> assigned through the Member as a “sponsoring LIR” to an End User insert: </li>
  • insert: </ul>
insert: <h3>

insert: <a name="introduction"> 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 and legal persons insert: </li>
  • insert: </ul>
insert: <p>

This document is obsoleted by ripe-72, version 0.7 of this documen 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>

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: <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 title="" href="https://www.ripe.net/publications/docs/ipv4-policies#55" class="external-link" target="_self"> Section 5.5, IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region insert: </a> ). Such a transfer may also be facilitated through the insert: <a data-linktype="internal" target="_self" title="" href="resolveuid/8768823a7d79496c8bff938729212474" data-val="8768823a7d79496c8bff938729212474" class="internal-link"> RIPE NCC Listing Service. insert: </a> insert: </li>
    • insert: </ul>
    insert: </li>
  2. insert: <li>
  3. The Member changes its official legal name insert: <b> . t Such a change may occur, for example, because of a merger or acquisition of the Member's organisation. insert: </li>
  4. insert: </ol>
insert: <p>

This document describes the procedures for the reassignment of IP delete: <br /> network numbers 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: <b> Note: insert: </b> 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: <h3>

insert: <a name="transfer"> 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="submission"> 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>

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

insert: <p>

insert: </p>

insert: <p>

The RIPE NCC will ask for the following information: 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>

If the current official legal names of the involved Members are different from the RIPE Network Coordination delete: <br /> Centre. It deals with items as providing information for the RIPE and delete: <br /> US NIC databases, as well as reassignment of IP addresses ones in light of delete: <br /> the "Supernetting" proposal, as documented the relevant signed RIPE NCC Standard Service Agreement, then the procedure described under insert: <a class="anchor-link" href="#official-legal-name" target="_self" title=""> Section 4.0 insert: </a> 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 href="https://www.ripe.net/publications/docs/closure#11"> Section A.1.1. insert: </a> and insert: <a href="https://www.ripe.net/publications/docs/closure#12"> Section A.1.2. insert: </a> ). insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: <b> ii. A description of the reason for the transfer (for example, due to merger, acquisition, 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 RFC 1338, by Vince Fuller delete: <br /> et al. delete: <br /> delete: <br /> delete: <br /> Introduction delete: <br /> delete: <br /> Since May 1st 1992, the RIPE Network Coordination Centre (NCC) the structure of the organisation(s) involved, a description of the changes among the organisation(s) is delete: <br /> acting as a delegated registry for IP networks numbers to NICs and NOCs delete: <br /> in Europe. It necessary. The description must be accompanied by all official legal documents proving/supporting the changes the request is RIPE NCC policy 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 href="https://www.ripe.net/publications/docs/closure#11"> 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>

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 to give out network numbers to delete: <br /> individual organisations, who 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 refer in turn, to their IP network delete: <br /> service provider. delete: <br /> delete: <br /> The mission of the RIPE NCC is to give network numbers to the various delete: <br /> service providers and NICs. The NICs and NOCs can then reassign the delete: <br /> actual IP network numbers to organisations requesting IP network delete: <br /> numbers. delete: <br /> delete: <br /> delete: <br /> Class B Network Number Allocation Procedure delete: <br /> delete: <br /> Service providers can request Class B network numbers on a one-by-one delete: <br /> basis from the RIPE NCC. Because class B address space is a critical delete: <br /> resource, a request for a class B network number must be accompanied by delete: <br /> a justification in terms of the requesting organisation's size, current delete: <br /> network and expected network growth. The requestor another party object to this transfer and provide an agreement that proves that the Internet Number Resource records should also make delete: <br /> clear why they cannot use a block of class C network numbers to achieve delete: <br /> their goals. The RIPE NCC will review requests using the same standards delete: <br /> as any other Internet Registry, particularly the US NIC. delete: <br /> delete: <br /> delete: <br /> Class C Allocation Procedures delete: <br /> delete: <br /> delete: <br /> NICs and NOCs accepting a block of class C numbers agree to adhere to delete: <br /> the following procedures: delete: <br /> delete: <br /> A) The RIPE NCC will assign complete class C blocks to individual NICs delete: <br /> and NOCs. They can be requested from <hostmaster@ripe.net>. delete: <br /> delete: <br /> B) In order to prevent implementation problems, network numbers ending delete: <br /> with 0 or 255 should NOT be reassigned. delete: <br /> delete: <br /> C) Full information about reassigned network numbers must be reported delete: <br /> back to the RIPE NCC and the US NIC in full RIPE database format (ref delete: <br /> ripe-13). The complete entries should be sent immediately after delete: <br /> reassignment to <ripe-dbm@ripe.net> and <hostmaster@nic.ddn.mil> delete: <br /> Unfortunately, the RIPE NCC have been transferred to them. insert: </li>
  • insert: </ul>
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="receiving-organisation"> insert: </a> 3.2 If the Receiving Organisation is not yet ready to accept block entries for delete: <br /> the RIPE database, so you must send 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 must apply to be a Member by signing the RIPE NCC Standard Service Agreement before the transfer takes place ( insert: <a href="https://www.ripe.net/lir-services/member-support/become-a-member"> more information on how to become a Member is available insert: </a> ). insert: </p>

insert: <p>

If the receiving organisation refuses to do 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 above (Section 1). insert: </p>

insert: <p>

insert: </p>

insert: <p>

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

insert: <p>

All outstanding invoices and all outstanding financial obligations must be paid in each individual entry. delete: <br /> delete: <br /> D) Reassignment of class C network numbers should be done full. If the RIPE NCC Standard Service Agreement is terminated in a manner delete: <br /> 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 href="http://www.ripe.net/ripe/docs/ripe-499"> RIPE NCC Charging Scheme insert: </a> ). insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: <b> insert: <a name="db-issues"> insert: </a> insert: <a name="internet-number-resource-reg"> 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 facilitates Supernetting (see next section). delete: <br /> delete: <br /> E) Requests for network numbers should be reasonable. All NICs and NOCs delete: <br /> should prevent stockpiling of network numbers. delete: <br /> delete: <br /> F) On first request from the RIPE NCC, the class C network numbers not delete: <br /> yet reassigned, must be returned to the RIPE NCC. delete: <br /> delete: <br /> delete: <br /> Supernetting delete: <br /> delete: <br /> NICs and NOCs reassigning IP network numbers are urgently requested to delete: <br /> read the Supernetting proposal by Vince Fuller et al. This document can delete: <br /> be obtained from the rfc section of the RIPE document store or other RFC delete: <br /> servers. 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: <h3>

insert: <a name="official-legal-name"> insert: </a> 4.0 The Member Changes its Official Legal Name insert: <b> insert: </b> insert: </h3>

insert: <p>

It is called rfc1338.txt. delete: <br /> The Supernetting proposal was made to reduce the increase of routing delete: <br /> table size the obligation of the Member to inform the RIPE NCC immediately if any change in the current Internet. It proposes to create a hierarchy delete: <br /> of IP network numbers, which can then be aggregated resulting in less delete: <br /> routing table entries in routing equipment. While Member's official legal name occurs. insert: </p>

insert: <p>

The Member must send an email to insert: <a class="email-link" href="mailto:ncc@ripe.net" target="_self" title=""> 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 proposal has not delete: <br /> been formally adopted we expect 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/service-agreement" target="_self" title=""> 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 something at least along the same delete: <br /> principle will be implemented in the near future. delete: <br /> delete: <br /> Here is how it works: delete: <br /> delete: <br /> If an organisation A needs 8 class C network numbers, the numbers should delete: <br /> be given out in such a way are related to this change. The Member must update all RIPE Database objects maintained by them that the routing information for each of delete: <br /> these 8 networks could appear as one entry with the correct mask in delete: <br /> routers. delete: <br /> delete: <br /> More concretely: delete: <br /> delete: <br /> Service provider S hands out networks 192.24.8 through 192.24.15 to delete: <br /> organisation A. These networks can then appear in routing equipment as a delete: <br /> supernet route to 192.24.8 with mask 255.255.248.0. This way 8 class C delete: <br /> network numbers appear as one routing table entry. delete: <br /> delete: <br /> The guidelines that can be derived from the Supernetting proposal are: delete: <br /> delete: <br /> A) Service providers should reserve blocks of class C network numbers from delete: <br /> their allocation for each organisations requesting class C network numbers. delete: <br /> delete: <br /> B) The size of these blocks should always be a power of 2. delete: <br /> delete: <br /> C) The numbers in these blocks should be contiguous. delete: <br /> delete: <br /> D) The blocks should start on bit boundaries. delete: <br /> (ie powers of 2, AND multiples of the block size) delete: <br /> delete: <br /> E) The blocks reserved for an organisation should be sufficient for a delete: <br /> reasonable expected growth over the next few years. delete: <br /> delete: <br /> F) Multi-homed organizations may obtain address space from one of their delete: <br /> providers, the RIPE NCC, or the global NIC, as is appropriate to their delete: <br /> network configuration. These organisations are strongly encouraged to delete: <br /> contact the RIPE NCC for guidance. delete: <br /> delete: <br /> If you have any questions concerning this, please do not hesitate to delete: <br /> call or mail us at ncc@ripe.net. delete: </p> related to this change. insert: </p>

RIPE NCC Transfer of Internet Numbers Registration Procedures Number Resource Records and Change of a Member’s Official Legal Name