Changes to RIPE NCC Internet Numbers Registration Procedures

Abstract delete: <br /> delete: <br /> delete: <br /> insert: </h2>

This document describes the 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: <a href="#1.0"> 1.0 Introduction insert: </a> insert: <br />
insert: <a href="#2.0"> 2.0 LIR Ownership Change insert: </a> insert: </p>

insert: <a href="#3.0"> 3.0 Closing an LIR insert: </a> insert: </p>

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

insert: </p>

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

When an organisation or company operating an LIR changes ownership status or stops serving as an LIR there are financial, IP address space 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: <a id="2.0" name="2.0"> insert: </a> 2.0 LIR Ownership Change insert: </h2>

In the case of an LIR ownership change, the LIR should contact the RIPE NCC at insert: <a href="mailto:[email protected]"> [email protected] insert: </a> . insert: </p>

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

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

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

insert: <li>
• A takeover of one LIR by another LIR, closing one of the LIRs. insert: </li>
insert: <li>
• A takeover of one LIR by another LIR, both remain open. insert: </li>
insert: <li>
• A takeover of an LIR by a non-LIR. insert: </li>
insert: </ul>

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

insert: <li>
• The reason for the change of organisation. insert: </li>
insert: <li>
• The name of the company/companies involved. insert: </li>
insert: <li>
• The number of LIRs affected by the change. insert: </li>
insert: <li>
• The RegID(s) of the LIR(s) affected by the change. insert: </li>
insert: </ul>

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

insert: <li>
• Confirmation from all parties agreeing to the change (See section insert: <a href="#2.3"> 2.3 insert: </a> ). insert: </li>
insert: <li>
• Updated list of contact person(s) (See section insert: <a href="#2.4"> 2.4 insert: </a> ). insert: </li>
insert: <li>
• Updated billing e-mail contact details, including any changes to VAT number. insert: </li>
insert: <li>
• A new service agreement, if applicable (See section insert: <a href="#2.2"> 2.2 insert: </a> ). insert: </li>
insert: <li>
• Legal documentation supporting the name change, if applicable (See section insert: <a href="#2.2"> 2.2 insert: </a> ). insert: </li>
insert: <li>
• Overview of utilisation in all allocations (See section insert: <a href="#2.6"> 2.6 insert: </a> ). insert: </li>
insert: </ul>

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

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: <a id="2.2" name="2.2"> insert: </a> 2.2 Service Agreement insert: </h3>

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: <li>
• The organisation operating the LIR changes name, or insert: </li>
insert: <li>
• The LIR wishes to change their RegID. insert: </li>
insert: </ul>

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>

The Standard RIPE NCC Service Agreement is available from the RIPE Document Store at: insert: <br />
insert: <br />
insert: <a title="" href="https://www.ripe.net/ripe/docs/service-agreement.html" class="external-link" target="_self"> http://www.ripe.net/ripe/docs/service-agreement.html insert: </a> 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: <a id="2.3" name="2.3"> insert: </a> 2.3 Change in Operating Organisation insert: </h3>

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: <a id="2.4" name="2.4"> insert: </a> 2.4 Contact Person(s) insert: </h3>

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: <br />
insert: <br />
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: <br />
insert: <br />
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 changes. These changes should include the new registered contact person(s) for the reassignment of LIR. insert: </p>

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

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>

If an LIR insists on changing their RegID, a fee corresponding to the sign-up fee for a new LIR will be 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: <br />
insert: <br />
insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/charging.html" target="_self" title=""> http://www.ripe.net/ripe/docs/charging.html insert: </a> insert: </p>

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

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 correct and up-to-date before the transfer occurs. Transferred allocations containing a 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: <br />
insert: <br />
insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/ipv4-policies.html" target="_self" title=""> http://www.ripe.net/ripe/docs/ipv4-policies.html insert: </a> insert: </p>

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

In cases where an organisation operating an LIR takes over one or more LIRs, a takeover fee is due for every LIR taken over (e.g. if three LIRs are taken over, the fee is paid three times). All current outstanding invoices for the LIRs being taken over will also have to be paid in full. insert: </p>

The transfer of address allocations also incurs a takeover fee and does not 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: <a id="3.0" name="3.0"> insert: </a> 3.0 Closing an LIR insert: </h2>

In the case of a closure of an LIR, the RIPE NCC should be contacted at least three months prior to the required closure date at insert: <a href="mailto:[email protected]"> [email protected] insert: </a> . insert: <br />
insert: <br />
Only registered LIR contact person(s) can discuss a closure of an LIR with the RIPE NCC. In case of bankruptcy, the court-appointed administrator may take over these responsibilities. insert: <br />
insert: <br />
To cease operations, an LIR is required to take the following four steps: insert: <br />
insert: <br />
1. Send the RIPE NCC a written request to officially close the LIR. State the reasons for closure of the LIR and state the intention to return the unassigned address space. insert: <br />
insert: <br />
2. Provide the RIPE NCC with documentation of all IP delete: <br /> network numbers assignments made from blocks obtained address space allocated by the RIPE NCC. insert: </p>

3. Provide a list of any End Users that have expressed a need to keep their assigned IP address space and/or Autonomous System Number (ASN). Contact information such as e-mail addresses of these End Users should be included. (See section insert: <a href="#3.7"> 3.7 insert: </a> ) insert: <br />
insert: <br />
4. Verify that the contents of the RIPE Database are up-to-date. A closing LIR is responsible for removing any objects entered by them in the RIPE Database that are no longer valid. Please send a confirmation to the RIPE NCC that all obsolete and invalid objects have been removed. (See section insert: <a href="#3.8"> 3.8 insert: </a> ) insert: </p>

insert: <a id="3.1" name="3.1"> insert: </a> 3.1 Further Assignments insert: </h3>

A closing LIR is not allowed to make any further assignments from the RIPE Network Coordination delete: <br /> Centre. It deals with items its address space allocations. insert: </p>

insert: <a id="3.2" name="3.2"> insert: </a> 3.2 Finance insert: </h3>

An LIR will continue to be billed for services until a formal request to be closed is sent by a registered contact person(s) of the LIR. insert: <br />
insert: <br />
In cases of mergers, the LIR whose allocation has been transferred to another LIR will continue to be billed until any inconsistencies are resolved. insert: </p>

insert: <a id="3.3" name="3.3"> insert: </a> 3.3 Transfers of Address Allocations from a Closing LIR insert: </h3>

If an LIR wishes to transfer its allocations to another existing LIR, it must provide the documentation about all assignments to the LIR receiving the transferred allocation. As outlined above, all transfers require approval by the RIPE NCC and all database objects must be valid and up-to-date. insert: </p>

insert: <a id="3.4" name="3.4"> insert: </a> 3.4 Open Address Space Requests insert: </h3>

As soon as providing information for the RIPE delete: <br /> database, 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 /> delete: <br /> Since May 1st 1992, the RIPE Network Coordination Centre (NCC) is delete: <br /> acting as a delegated registry the LIR decides to close, it should halt any open requests 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 and refer the End Users to the list of LIRs. This will prevent the customer from having to renumber at a later date. This list 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 available at: insert: </p>

insert: <a data-val="3628263b9a882491a5225984f80cc634" href="resolveuid/3628263b9a882491a5225984f80cc634" data-linktype="internal" class="internal-link"> http://www.ripe.net/lir/registries/indices/index.html insert: </a> insert: </p>

insert: <a id="3.5" name="3.5"> insert: </a> 3.5 End Users Keeping Address Assignments insert: </h3>

A closing LIR 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 /> 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 <[email protected]>. 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 in full RIPE database format (ref ripe-13). delete: <br /> The complete entries should be sent immediately after reassignment to delete: <br /> <[email protected]>. delete: <br /> The RIPE NCC is ready to accept block entries for the RIPE database. delete: <br /> For block syntax, please contact the RIPE NCC. 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. always encourage its End Users to renumber into an address allocation held by another LIR. 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 way, customer assignments can then be aggregated resulting routed as part of the other LIR's allocation. Organisations in less delete: <br /> routing table entries receipt of a Provider Aggregatable (PA) assignment should note that a new provider will not be able to announce an aggregate block. They may, therefore, have problems getting their addresses routed. insert: </p>

For more information, please see the RIPE documents "Smallest RIPE NCC Allocation / Assignment Sizes" and "Provider Independent versus Provider Aggregatable Address Space" available from the RIPE Document Store at: insert: </p>

http://www.ripe.net/ripe/docs/smallest-alloc-sizes.html insert: </p>

http://www.ripe.net/ripe/docs/pi-pa.html insert: </p>

The LIR should also supply the RIPE NCC with a list of Assignments kept by End Users in routing equipment. While the following format: insert: </p>

 Inetnum Range Size Date Netname  insert: <br /> 
 insert: <br /> 
 193.0.0.0 - 193.0.1.255 512 19950101 RIPE-NCC  insert: </pre> 

insert: <a id="3.6" name="3.6"> insert: </a> 3.6 Continued Internet Connectivity to End Users insert: </h3>

The End Users can continue to use the address space already assigned to them by the closing LIR. The LIR will continue to provide Internet connectivity to its End Users as an Internet Service Provider (ISP). Assignments made by an LIR that has closed are valid for as long as the original criteria under which they were assigned remain valid. (See section insert: <a href="#3.8"> 3.8 insert: </a> ) insert: </p>

insert: <a id="3.7" name="3.7"> insert: </a> 3.7 Discontinued Internet Connectivity to End Users insert: </h3>

If the LIR will no longer provide Internet connectivity to End Users with assigned address space, this proposal has not delete: <br /> been formally adopted we expect address space should be retrieved from the End Users by the LIR as they renumber. It is the LIR's responsibility to help its End Users with renumbering. insert: </p>

insert: <a id="3.8" name="3.8"> insert: </a> 3.8 Database Responsibilities insert: </h3>

LIRs are responsible for the accuracy of the data they enter into the RIPE Database. In the case of a closure of an LIR, the LIR should remove any objects in the RIPE Database that something at least along the same delete: <br /> principle are no longer valid. This includes insert: <b> inetnum insert: </b> , insert: <b> aut-num insert: </b> and insert: <b> domain insert: </b> objects with obsolete information. insert: </p>

In cases where End Users of an LIR keep the address space assigned to them after the LIR closes, the LIR maintainer in the database objects representing these assignments needs to be removed and replaced by the RIPE NCC maintainer. The LIR should provide the RIPE NCC with a list of relevant database objects agreeing to the RIPE NCC overwriting the current LIR maintainer. insert: </p>

insert: <a id="3.9" name="3.9"> insert: </a> 3.9 Unassigned Address Space insert: </h3>

Unassigned address space 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 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 returned to the RIPE NCC and will revert back to the public pool of IP address space. It 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 assigned by the RIPE NCC as necessary. Should an LIR decide to close and reopen at a later date, it must repeat all formal steps required to establish a new LIR. insert: </p>

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

The RIPE NCC may decide to close an LIR that stops paying its bills to the RIPE NCC and/or cannot be contacted by the RIPE NCC for each organisations requesting class C network numbers. delete: <br /> delete: <br /> B) a significant period of time. Moreover, if an LIR consistently violates the policies established by the Internet Assigned Numbers Authority (IANA) or the RIPE community, in spite of multiple warnings, it may be closed. insert: </p>

The size of these blocks should always be a power of 2. delete: <br /> delete: <br /> C) RIPE NCC will send the LIR a message to notify it of its closure. The numbers LIR must then provide documentation to the RIPE NCC regarding its allocated address space and follow the other procedures for closing an LIR as stated in these blocks section insert: <a href="#3.0"> 3.0 insert: </a> . insert: </p>

If the LIR does not provide the RIPE NCC with the proper Documentation, the RIPE NCC will determine which address space 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 returned to the public pool of IP 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 /> delete: <br /> delete: <br /> If you have any questions concerning this, please do not hesitate to delete: <br /> call or mail us at [email protected] delete: </p> space. insert: </p>