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 Internet Numbers Registration Procedures ripe-515: Mergers, Acquisitions, Takeovers and Closures of Organisations Operating an LIR
delete: <p> delete: <b> insert: <h2 class="western">

Abstract insert: </h2>

insert: <p>

This document is obsoleted by ripe-72, version 0.7 of this documen delete: </b> t provides guidelines to Local Internet Registries (LIRs) on the steps to take when the organisation operating an LIR changes ownership (due to a merger, sale or takeover) or stops serving entirely as an LIR. insert: </p>

insert: <p>

_________________________________________________________________ insert: </p>

insert: <h2 class="western">

Table of Contents insert: </h2>

insert: <p>

insert: </p>

insert: <p>

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

insert: <p>

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

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

insert: <a class="anchor-link" href="#2.1"> 2.1 IP Address Space insert: </a> insert: </p>

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

insert: <a class="anchor-link" href="#2.2"> 2.2 Service Agreement insert: </a> insert: </p>

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

insert: <a class="anchor-link" href="#2.3"> 2.3 Change in Operating Organisation insert: </a> insert: </p>

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

insert: <a class="anchor-link" href="#2.4"> 2.4 Contact Person(s) insert: </a> insert: </p>

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

insert: <a class="anchor-link" href="#2.5"> 2.5 RegID insert: </a> insert: </p>

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

insert: <a class="anchor-link" href="#2.6"> 2.6 Transfers of Address Allocations insert: </a> insert: </p>

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

insert: <a class="anchor-link" href="#2.7"> 2.7 Takeover fee insert: </a> insert: </p>

insert: <p>

insert: <a class="anchor-link" href="#3.0"> 3.0 Closing an LIR insert: </a>

This section is replaced by the RIPE NCC organisational document describes the procedures for the reassignment of " insert: <a href="https://www.ripe.net/publications/docs/closure"> Closure of LIR and Deregistration of Internet Number Resources insert: </a> ". insert: </p>

insert: <p>

insert: <a class="anchor-link" href="#4.0"> 4.0 When an LIR is Closed by the RIPE NCC insert: </a> insert: </p>

insert: <p>

This section is replaced by the RIPE NCC organisational document " insert: <a href="https://www.ripe.net/publications/docs/closure"> Closure of LIR and Deregistration of Internet Number Resources insert: </a> ". insert: </p>

insert: <h2 class="western">

insert: <a name="1.0"> insert: </a> 1.0 Introduction insert: </h2>

insert: <p>

When an organisation or company operating an LIR changes ownership status or stops serving as an LIR there are financial, IP delete: <br /> network numbers from blocks obtained 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 in light of delete: <br /> the "Supernetting" proposal, as documented 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) is delete: <br /> acting as a delegated registry for IP networks numbers to NICs and NOCs delete: <br /> in Europe. It is RIPE NCC policy not to give out network numbers to delete: <br /> individual organisations, who 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 and RIPE Database issues that need resolving. Therefore, the RIPE NCC must always be contacted when an LIR changes ownership or closes. insert: </p>

insert: <h2 class="western">

insert: <a name="2.0"> insert: </a> 2.0 LIR Ownership Change insert: </h2>

insert: <p>

In the case of an LIR ownership change, the LIR should contact the RIPE NCC at insert: <a href="mailto:lir-help@ripe.net"> lir-help@ripe.net insert: </a> . insert: </p>

insert: <p>

Only registered LIR contact person(s) can discuss the change of an LIR ownership with the RIPE NCC. insert: </p>

insert: <p>

The following steps are required to change the organisation operating an LIR: insert: </p>

insert: <p>

insert: </p>

insert: <p>

1. Clarify the type of change: insert: </p>

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

    A takeover of one LIR by another LIR, closing one of the LIRs. insert: </p>

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

    A takeover of one LIR by another LIR, both remain open. insert: </p>

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

    A takeover of an LIR by a critical delete: <br /> resource, non-LIR. insert: </p>

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

insert: </p>

insert: <p>

2. Outline the details of the change, stating: insert: </p>

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

    The reason for the change of organisation. insert: </p>

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

    The name of the company/companies involved. insert: </p>

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

    The number of LIRs affected by the change. insert: </p>

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

    The RegID(s) of the LIR(s) affected by the change. insert: </p>

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

insert: </p>

insert: <p>

3. Present the following documents to the RIPE NCC: insert: </p>

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

    Confirmation from all parties agreeing to the change (See section 2.3). insert: </p>

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

    Updated list of contact person(s) (See section 2.4). insert: </p>

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

    Updated billing e-mail contact details, including any changes to VAT number. insert: </p>

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

    A new service agreement, if applicable (See section 2.2). insert: </p>

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

    Legal documentation supporting the name change, if applicable (See section 2.2). insert: </p>

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

    Overview of utilisation in all allocations (See section 2.6). insert: </p>

    insert: </li>
  • insert: </ul>
insert: <h3 class="western">

insert: <a name="2.1"> insert: </a> 2.1 IP Address Space insert: </h3>

insert: <p>

Following any type of change (such as mergers, acquisitions or takeovers) of an organisation operating an LIR, the RIPE NCC will review the status of any IP address allocations that are held by the new organisation. insert: </p>

insert: <h3 class="western">

insert: <a name="2.2"> insert: </a> 2.2 Service Agreement insert: </h3>

insert: <p>

When an organisation operating an LIR changes ownership, a new service agreement may need to be signed. The RIPE NCC will need to request a new service agreement from the new owners if: insert: </p>

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

    The organisation operating the LIR changes name, or insert: </p>

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

    The LIR wishes to change their RegID. insert: </p>

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

The registration documentation from the relevant Chamber of Commerce, or its country equivalent, supporting the name change must be submitted to the RIPE NCC. insert: </p>

insert: <p>

The Standard RIPE NCC Service Agreement is available from the RIPE Document Store at: insert: <a href="http://www.ripe.net/ripe/docs/service-agreement"> http://www.ripe.net/ripe/docs/service-agreement insert: </a> insert: </p>

insert: <p>

insert: </p>

insert: <p>

If the organisation operating the LIR does not change its name and keeps the original RegID, the LIR can continue operating under the same service agreement. insert: </p>

insert: <h3 class="western">

insert: <a name="2.3"> insert: </a> 2.3 Change in Operating Organisation insert: </h3>

insert: <p>

In cases where an organisation operating an LIR takes over one or more LIRs, confirmation of the takeover from all parties involved or their legal successors must be included. insert: </p>

insert: <h3 class="western">

insert: <a name="2.4"> insert: </a> 2.4 Contact Person(s) insert: </h3>

insert: <p>

It is very important to notify the RIPE NCC, if there is a change of contact person(s). This is essential, as only registered contact person(s) can submit Internet resource requests to the RIPE NCC and provide updates to our internal registry files. insert: </p>

insert: <p>

insert: </p>

insert: <p>

If the contact person(s) of the affected LIR has changed, the RIPE NCC may adjust the Assignment Window of the LIR until the contact person(s) is up-to-date with RIPE NCC procedures and RIPE community policies. insert: </p>

insert: <p>

insert: </p>

insert: <p>

If there are no current registered contacts remaining with the LIR, a fax signed by the Managing Director of the LIR on organisation letterhead is required to implement these insert: </p>

insert: <p>

changes. These changes should include the new registered contact person(s) for the LIR. insert: </p>

insert: <h3 class="western">

insert: <a name="2.5"> insert: </a> 2.5 RegID insert: </h3>

insert: <p>

It is not necessary to obtain a new Registry Identifier (RegID) if the name of the organisation that operates the LIR changes. The RegID is merely an internal identifier used by the RIPE NCC to distinguish the various LIRs. It does not have to correspond to the legal name of the organisation operating the LIR. insert: </p>

insert: <p>

insert: </p>

insert: <p>

If an LIR insists on changing their RegID, a fee corresponding to the sign-up fee 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 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 is not yet ready to accept block entries for delete: <br /> the RIPE database, so you must send in each individual entry. delete: <br /> delete: <br /> D) Reassignment of class C network numbers should be done in a manner delete: <br /> 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. It is called rfc1338.txt. delete: <br /> The Supernetting proposal was made to reduce the increase of routing delete: <br /> table size 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 this proposal has not delete: <br /> been formally adopted we expect that something at least along the same delete: <br /> principle new LIR 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 /> charged to cover additional administrative work generated. Please see the current version of the RIPE NCC Charging Scheme available from the RIPE Document Store at: insert: <a href="http://www.ripe.net/ripe/docs/charging"> http://www.ripe.net/ripe/docs/charging insert: </a> insert: </p>

insert: <h3 class="western">

insert: <a name="2.6"> insert: </a> 2.6 Transfers of Address Allocations insert: </h3>

insert: <p>

All transfers of address allocations from one LIR to another LIR (or to a non-LIR) require approval by the RIPE NCC. It is expected that all database objects relating to this allocation be given out in such correct and up-to-date before the transfer occurs. Transferred allocations containing a way 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 large amount of unassigned address space may be set aside and kept by the RIPE NCC until the other allocations held by the LIR are considered fully used (about 80%). Once the LIR has reached full utilisation in its other allocations, the reserved allocations will be made available to the LIR. For further details on allocation policy, please refer to the document "IPv4 Address Allocation and Assignment Policies in the RIPE NCC Service Region" available from the RIPE Document Store at: insert: </p>

insert: <p>

insert: <a href="http://www.ripe.net/ripe/docs/ipv4-policies"> http://www.ripe.net/ripe/docs/ipv4-policies insert: </a> insert: </p>

insert: <h3 class="western">

insert: <a name="2.7"> insert: </a> 2.7 Takeover Fee insert: </h3>

insert: <p>

In cases where an organisation operating an LIR takes over one of their delete: <br /> providers, the RIPE NCC, or the global NIC, as is appropriate to their delete: <br /> network configuration. These organisations more LIRs, a takeover fee is due for every LIR taken over (e.g. if three LIRs are strongly encouraged to delete: <br /> contact the RIPE NCC taken over, the fee is paid three times). All current outstanding invoices for guidance. delete: <br /> delete: <br /> If you the LIRs being taken over will also have any questions concerning this, please do to be paid in full. insert: </p>

insert: <p>

insert: </p>

insert: <p>

The transfer of address allocations also incurs a takeover fee and does not hesitate to delete: <br /> call or mail us at ncc@ripe.net. delete: </p> vary according to the amount of address space being transferred (e.g. if three allocations are being transferred from LIR A to LIR B, the fee is only paid once). insert: </p>

insert: <h2 class="western">

insert: <a name="3.0"> insert: </a> 3.0 Closing an LIR insert: </h2>

insert: <p>

This section is replaced by the RIPE NCC organisational document "Closure of LIR and Deregistration of Internet Number Resources" available from the RIPE Document Store at: insert: <a href="http://www.ripe.net/ripe/docs/closure"> http://www.ripe.net/ripe/docs/closure insert: </a> . insert: </p>

insert: <h2 class="western">

insert: <a name="4.0"> insert: </a> 4.0 When an LIR is Closed by the RIPE NCC insert: </h2>

insert: <p>

This section is replaced by the RIPE NCC organisational document "Closure of LIR and Deregistration of Internet Number Resources"available from the RIPE Document Store at: insert: <a href="http://www.ripe.net/ripe/docs/closure"> http://www.ripe.net/ripe/docs/closure insert: </a> . insert: </p>

RIPE NCC Internet Numbers Registration Procedures Mergers, Acquisitions, Takeovers and Closures of Organisations Operating an LIR