Changes to RIPE NCC Internet Numbers Registration Procedures

Contents insert: </h2>

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

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

3.0 insert: <a href="#transfer"> Transfer of Internet Number Resources insert: </a> insert: </p>

3.1 insert: <a href="#transfer31"> Submission of the Request for Transfer insert: </a> insert: </p>

3.2 insert: <a href="#transfer32"> If the Receiving Party is not a Member insert: </a> insert: </p>

3.3 insert: <a href="#transfer33"> Financial Consequences insert: </a> insert: </p>

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

3.5 insert: <a href="#transfer35"> Transfers between LIR accounts belonging to the same member insert: </a> insert: </p>

4.0 insert: <a href="#memberchanges"> Member Changes Official Legal Name insert: </a> insert: </p>

insert: </p>

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

For the purposes of this document, Internet number resources refer to: insert: </p>

insert: <li>
• The registered allocation and assignment records of a member insert: </li>
insert: <li>
• The independent Internet number resource records assigned to an End User through a member acting as a sponsoring LIR insert: </li>
insert: </ul>

insert: </p>

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

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

insert: <li>
• The natural or legal persons holding the registration of Internet number resources insert: </li>
insert: <li>
• The Internet number resources that are registered to these natural or legal persons insert: </li>
insert: </ul>

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

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

insert: <li>
1. Internet Number Resource are transferred. Such transfers may take place: insert: </li>
insert: <ul>
insert: <li>
• Because of a change in the member's business structure (for example in the case of a merger or acquisition of the 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: </li>
insert: <li>
• In the case of a transfer of Internet number resources from the member to another party according to RIPE Policies (Section 5.5 and 6.4 of “ insert: <a href="https://www.ripe.net/publications/docs/ipv4-policies#55"> IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region insert: </a> ”, Section 8 of “ insert: <a href="https://www.ripe.net/publications/docs/ipv6-policy#8--transfer-of-ipv6-resources"> IPv6 Address Allocation and Assignment Policy insert: </a> ” and Section 4.0 of “ insert: <a href="https://www.ripe.net/publications/docs/asn-assignment-policies#Transferring"> Autonomous System (AS) Number Assignment Policies insert: </a> ”). Such a transfer may also be facilitated through the insert: <a data-val="e222449049284bb1af45883cccde2da1" href="./resolveuid/e222449049284bb1af45883cccde2da1" data-linktype="internal"> RIPE NCC Listing Service insert: </a> . insert: </li>
insert: </ul>
insert: <li>
2. The member changes its official legal name This document is obsoleted by ripe-72, version 0.7 of this documen . t delete: </p> Such a change may occur, for example, because of a merger or acquisition of the member's organisation. insert: </li>
insert: </ol>

This document describes the procedures for the reassignment of IP delete: <br /> such changes to be properly communicated and registered with the RIPE NCC. insert: </p>

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

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

If a change in a member's business structure is insert: <i> not insert: </i> accompanied by a transfer of Internet number resources 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>

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 business structure. This procedure is described in the RIPE NCC Procedural Document, “ 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 insert: </a> ”. insert: </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, “ insert: <a title="" href="https://www.ripe.net/publications/docs/inter-rir-transfer-of-inr" class="external-link" target="_self"> Inter-RIR Transfer of Internet Number Resources insert: </a> ”. insert: </p>

insert: </p>

insert: <a name="transfer"> insert: </a> 3.0 Transfer of Internet Number Resources insert: </h3>

If a member transfers their Internet number resources to a third party for any reason, this transfer must be declared to the RIPE NCC for approval. insert: </p>

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

For the transfer to be processed, one of the involved parties must submit a request to the RIPE NCC: insert: </p>

insert: <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), the request must be submitted via the LIR Portal. If the requesting party does not have access rights to the LIR portal, the request must be submitted via email to insert: <a href="mailto:[email protected]"> [email protected] insert: </a> insert: </li>
insert: <li>
• If this is a transfer of Internet number resource from one member to another party according to RIPE Policies (Sections 5.5 and 6.4 of “ insert: <a href="https://www.ripe.net/publications/docs/ipv4-policies#55"> IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region insert: </a> ”, Section 8 of “ insert: <a href="https://www.ripe.net/publications/docs/ipv6-policy#8--transfer-of-ipv6-resources"> IPv6 Address Allocation and Assignment Policy insert: </a> ” and Section 4.0 of “ insert: <a href="https://www.ripe.net/publications/docs/asn-assignment-policies#Transferring"> Autonomous System (AS) Number Assignment Policies insert: </a> ”, the request must be submitted to insert: <a href="mailto:[email protected]"> [email protected] insert: </a> insert: </li>
insert: </ul>

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

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

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

insert: <li>
• The full official legal names of all parties involved insert: </li>
insert: <li>
• Which party will transfer the Internet number resources 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>

If the current official legal names of the involved members are different from those in the relevant signed RIPE NCC Standard Service Agreement, then the procedure described in insert: <a href="#memberchanges"> Section 4.0 insert: </a> must be followed prior to the transfer of the Internet number resources. insert: </p>

The procedure described under Section 4.0 is not necessary for the transferring member if the RIPE NCC Standard Service Agreement for that member is terminated (see Sections A.1.1 and A.1.2 of the RIPE NCC Procedural Document, “ insert: <a href="https://www.ripe.net/publications/docs/closure"> Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources insert: </a> ”. insert: </p>

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

If the transfer is taking place due to a change in the structure of the organisation(s) involved (e.g., merger, acquisition), a description of the changes among these organisation(s) is necessary. This description must be accompanied by the official legal documents issued by the relevant national authorities proving/supporting the changes the request is based on. insert: </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 numbers acquisition from blocks obtained from the RIPE Network Coordination delete: <br /> Centre. It deals one member to another), then these cases will fall within the scope of the relevant RIPE Policies (Section 5.5 and 6.4 of “ insert: <a href="https://www.ripe.net/publications/docs/ipv4-policies"> IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region insert: </a> ”, Section 8 of “ insert: <a href="https://www.ripe.net/publications/docs/ipv6-policy"> IPv6 Address Allocation and Assignment Policy insert: </a> ” and Section 4.0 of “ insert: <a href="https://www.ripe.net/publications/docs/asn-assignment-policies"> Autonomous System (AS) Number Assignment Policies insert: </a> ”) and will be evaluated in accordance with items as providing them. insert: </p>

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

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

If a member transfers all of their Internet number resources, their RIPE NCC Standard Service Agreement may be terminated (see Section A.1.1. of the RIPE NCC Procedural Document, “ insert: <a href="http://www.ripe.net/publications/docs/closure"> Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources insert: </a> ”). insert: </p>

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

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

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

The RIPE NCC provides the template of the Transfer Agreement that either party may submit to the RIPE NCC. insert: </p>

The Transfer Agreement must be 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. insert: </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 contact person or authorised person (e.g., senior manager, legal successor). 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: <li>
• An official document (issued by a national authority) confirming the closure of the transferring party insert: </li>
insert: <li>
• A copy of an older signed agreement between the relevant parties mentioning the transfer of the Internet number resources. If such an agreement is not available, the RIPE NCC may accept a confirmation of the transfer to the RIPE NCC signed by an authorised person (e.g., senior manager, legal successor) of the receiving party. The RIPE NCC reserves the right to reverse the transfer should another party object and provide an agreement that proves that the Internet number resource should have been transferred to them. insert: </li>
insert: </ul>

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>

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: <a name="transfer32"> insert: </a> 3.2 If the Receiving Party is not a Member insert: </h4>

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

If the Internet number resources are transferred to a non-member, the receiving party must apply to be a member by signing a RIPE NCC Standard Service Agreement before the transfer takes place ( insert: <a href="https://www.ripe.net/become-a-member"> more 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 on how to become a member is available insert: </a> ). If the receiving party refuses to do the above, the RIPE NCC will 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 transfer the Internet number resources to them. insert: </p>

If the Internet number resources to be transferred are Provider Independent (PI) addresses, the receiving party may either apply to become a member by signing the RIPE NCC Standard Service Agreement, or 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 enter into a contractual relationship with a sponsoring LIR. For more information, please see the notes on a one-by-one delete: <br /> basis from the RIPE NCC. Because class B address space is a critical delete: <br /> resource, a insert: <a href="https://www.ripe.net/participate/resource-management/independent-resources"> Requesting Independent Resources insert: </a> . insert: </p>

The request for a class B network number must be accompanied by delete: <br /> a justification the transfer can be submitted as described above (Section 3.1). insert: </p>

insert: <a name="transfer33"> insert: </a> 3.3 Financial Consequences insert: </h4>

All outstanding invoices and all outstanding financial obligations must be paid 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. 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. This payment is the responsibility of the receiving member. If the receiving party is not a member, then payment is the responsibility of the transferring member. insert: </p>

If the receiving party 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/publications/docs/charging"> RIPE NCC Charging Scheme insert: </a> ). insert: </p>

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

insert: <b> The RIPE NCC will review requests using the status of any IP address allocation or independent Internet number resource assignment maintained by the party involved, in compliance with the RIPE Policies current at the time of the transfer. insert: </b> insert: </p>

The receiving member must deregister from the RIPE Database any invalid or overlapping registrations or unused assignment approvals. 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: <a name="transfer35"> insert: </a> 3.5 Transfers between LIR accounts belonging to the same standards delete: <br /> as member insert: </h4>

Transfers of Internet number resources between LIR accounts belonging to the same member fall within the scope of the relevant RIPE Policies (Section 5.5 and 6.4 of “ insert: <a href="https://www.ripe.net/publications/docs/ipv4-policies"> IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region insert: </a> ”, Section 8 of “ insert: <a href="https://www.ripe.net/publications/docs/ipv6-policy"> IPv6 Address Allocation and Assignment Policy insert: </a> ” and Section 4.0 of “ insert: <a href="https://www.ripe.net/publications/docs/asn-assignment-policies"> Autonomous System (AS) Number Assignment Policies insert: </a> ”) and will be evaluated in accordance with them. insert: </p>

The procedure described above in Section 3.1 is applicable except from paragraphs 3.1.ii and 3.1.v. insert: </p>

If after the transfer the member decides to close an LIR account, all outstanding invoices and all outstanding financial obligations for this LIR account must be paid in full. insert: </p>

The RIPE NCC will review the status of 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) 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. insert: </p>

The member must deregister from the RIPE Database any invalid or overlapping registrations. insert: </p>

The RIPE NCC will assign complete class C blocks to individual NICs delete: <br /> and NOCs. They can be requested update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this transfer. The member must update all RIPE Database objects maintained by them that are related to this transfer. insert: </p>

insert: </p>

insert: <a name="memberchanges"> insert: </a> 4.0 Member Changes Official Legal Name insert: </h3>

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>

The member must send an email to insert: <a href="mailto:[email protected]"> [email protected] insert: </a> informing the RIPE NCC of the name change. This email must include: insert: </p>

insert: <li>
• New registration papers from <[email protected]>. delete: <br /> delete: <br /> B) In order to prevent implementation problems, network numbers ending delete: <br /> the national authority; and insert: </li>
insert: <li>
• The official legal documents supporting this change insert: </li>
insert: </ul>

The RIPE NCC will send a new insert: <a href="http://www.ripe.net/publications/docs/service-agreement"> 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>

If the change in the member's official legal name occurred without a further change in the member's structure (e.g., merger 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 <[email protected]> and <[email protected]> delete: <br /> Unfortunately, the RIPE NCC is another legal entity, acquisition by/of another legal entity), the member will 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 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 /> have to sign a new RIPE NCC Standard 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 [email protected]. delete: </p> Agreement. insert: </p>