1.0 Definitions

For the purposes of this document, Internet number resources refer to:

• The registered allocation and assignment records of a member
• In the case of a transfer of Internet number resources from the member to another party according to RIPE Policy "RIPE Resource Transfer Policies Link: http://www.ripe.net/publications/docs/transfer-policies ".

2.0 Introduction

In order for the RIPE NCC to maintain an accurate registry, it must hold accurate data concerning:

• The natural or legal persons holding the registration of Internet number resources
• The Internet number resources that are registered to these natural or legal persons

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.

A member must inform the RIPE NCC if one or bothof the following changes occurs:

1. Internet Number Resource are transferred. Such transfers may take place:
   1. 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.
   2. In the case of a transfer of Internet number resources from the member to another party according to RIPE Policy "RIPE Resource Transfer Policies Link: http://www.ripe.net/publications/docs/transfer-policies ".
2. The member changes its official legal name. Such a change may occur, for example, because of a merger or acquisition of the member's organisation.

This documents obsoletes ripe-65, version 0.6 of this document

Abstract

This document describes the procedures for such changes to be properly communicated and registered with the RIPE NCC.

Additionally, this document describes the procedure for requesting a voluntary transfer lock in accordance with the RIPE Policy “Voluntary Transfer Lock Link: ../../../resolveuid/074e7e56a0c8467db78c9c10b35feee0 ”.

Note:
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.

If a change in a member's business structure is notaccompanied 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.

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, "Independent Internet Number Resources - Contractual Relationship Changes Between Sponsoring LIR and End User Link: http://www.ripe.net/publications/docs/lir-end-user-contractual-changes ".

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, "Inter-RIR Transfer of Internet Number Resources Link: http://www.ripe.net/publications/docs/inter-rir-transfer-of-inr ".

3.0 Transfer of Internet Number Resources

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.

3.1 Submission of the Request for Transfer

For the transfer to be processed, a registered contact or an authorised person (e.g., senior manager, legal successor) of the involved parties must submit a request to the RIPE NCC. More specifically:

• 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), either of the parties involved must submit the request via the LIR Portal Link: https://my.ripe.net/#/update-registry . If the requesting party does not have access rights to the LIR portal, the request must be submitted via email to lir-help@ripe.net Link: mailto:lir-help@ripe.net
• If this is a transfer of Internet number resource from one member to another party according to RIPE Policy "RIPE Resource Transfer Policies Link: http://www.ripe.net/publications/docs/transfer-policies ", the transferring party must submit the request via the LIR Portal Link: https://my.ripe.net/ .

The RIPE NCC will evaluate the request and process the transfer if it is adequately supported by the submitted information (see below under i-v).

The RIPE NCC will ask for the following information:

i. Information regarding the parties involved, including:

• The full official legal names of all parties involved
• Which party will transfer the Internet number resources and which party will receive them
• Recent registration papers issued by the relevant national authorities for all involved parties

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 Section 4.0 Link: #memberchanges must be followed prior to the transfer of the Internet number resources.

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, "Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources Link: http://www.ripe.net/publications/docs/closure ".

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)

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.

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 acquisition from one member to another), then these cases will fall within the scope of RIPE Policy "RIPE Resource Transfer Policies Link: http://www.ripe.net/publications/docs/transfer-policies ".

iii. A list of the Internet number resources that are requested to be transferred.

If allof the transferring member's Internet number resources registered are being transferred, a confirmation of this is requested.

The member must also indicate any End User assignment agreements that are requested to be transferred.

If a member transfers all of their Internet number resources, their RIPE NCC Standard Service Agreement may be terminated upon request of the member or following the member's confirmation (see Section A.1.1. of the RIPE NCC Procedural Document, "Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources Link: http://www.ripe.net/publications/docs/closure ").

iv. The correct contact details of all parties involved

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.

v. A Transfer Agreement signed by both parties or by their legal successors

The RIPE NCC provides the template of the Transfer Agreement that either party may submit to the RIPE NCC.

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.

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 registered contact person or authorised person (e.g., senior manager, legal successor).

If the transferring party no longer exists by the time the RIPE NCC is being informed, the receiving party must send:

• An official document (issued by a national authority) confirming the closure of the transferring party
• 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.

vi. An overview of the utilisation of all allocations and of the status of all independent Internet number resource assignments

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.

3.2 If the Receiving Party is not a Member

Members may wish to transfer their Internet number resource to another member or to a third party that is not a member.

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 (more information on how to become a member is available Link: ../../../../../../../../../../../../../../../become-a-member ). If the receiving party refuses to do the above, the RIPE NCC will not transfer the Internet number resources to them.

If the Internet number resources to be transferred are Independent Resources (IPv4 PI, IPv6 PI and AS Numbers), the receiving party may either apply to become a member by signing the RIPE NCC Standard Service Agreement, or can enter into a contractual relationship with a sponsoring LIR. For more information, please see the notes on Requesting Independent Resources Link: ../../../../../../../../../../../../../../../participate/resource-management/independent-resources .

The request for the transfer can be submitted as described above (Section 3.1).

3.3 Financial Consequences

All outstanding invoices and 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. 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.

If the receiving party decides to sign the RIPE NCC Standard Service Agreement, then a sign-up fee must be paid (see RIPE NCC Charging Scheme Link: http://www.ripe.net/publications/docs/charging ).

3.4 Internet Number Resource Registration and RIPE Database Issues

the reassignment of IP network numbers from blocks obtained from the RIPE Network Coordination Centre. It deals with items as providing information for the RIPE database, as well as reassignment of IP addresses in light of the "Supernetting" proposal, as documented in RFC 1338, by Vince Fuller et al.

Introduction

Since May 1st 1992, the RIPE Network Coordination Centre (NCC) is acting as a delegated registry for IP networks numbers to NICs and NOCs in Europe. It is RIPE NCC policy not to give out network numbers to individual organisations, who should refer in turn, to their IP network service provider.

The mission of the RIPE NCC is to give network numbers to the various service providers and NICs. The NICs and NOCs can then reassign the actual IP network numbers to organisations requesting IP network numbers.

Class B Network Number Allocation Procedure

requests using the same standards as any other Internet Registry, particularly the US NIC.

Class C Allocation Procedures

NICs and NOCs accepting a block of class C numbers agree to adhere to the following procedures:

If the change in the member's official legal name occurred without a further change in the member's structure (e.g., merger with another legal entity, acquisition by/of another legal entity), the member will not have to sign a new RIPE NCC Standard Service Agreement.

5.0 Voluntary Transfer Lock of Internet Number Resources

5.1 The Scope of The Voluntary Transfer Lock

The RIPE NCC may approve a request for a voluntary transfer lock in accordance with the RIPE Policy “Voluntary Transfer Lock Link: ../../../resolveuid/074e7e56a0c8467db78c9c10b35feee0 ”.

If the RIPE NCC deems that a voluntary transfer lock request is not in line with RIPE policies, RIPE NCC procedural documents, or applicable law, the RIPE NCC reserves the right to reject the request. 

The RIPE NCC reserves the right not to enforce a voluntary transfer lock even if the relevant request has been approved by the RIPE NCC. The RIPE NCC may not enforce a voluntary transfer lock, for example, in case of Transfers of Internet Number Resources Due to a Change in the Member's Business Structure (see above Section 3.6) or Transfers Due to Seizure (see above Section 3.7). 

This document does not describe the procedure to be followed in the case of voluntary transfer locks for independent Internet number resources assigned to End Users. This procedure is described in the RIPE NCC Procedural Document, "Independent Internet Number Resources - Contractual Relationship Changes Between Sponsoring LIR and End User Link: http://www.ripe.net/publications/docs/lir-end-user-contractual-changes ".

5.2 Submission of the Request for Voluntary Transfer Lock

For the voluntary transfer lock to be approved, a registered contact or an authorised person (for e.g., a senior manager, the legal successor) of the requesting party must submit a request to the RIPE NCC.

The RIPE NCC will evaluate the request and approve the voluntary transfer lock if it is adequately supported by the information submitted and documentation as described below.

The RIPE NCC will ask for the following:

The Voluntary Transfer Lock Request Form

The requesting party must complete the Voluntary Transfer Lock Request Form. The template of the Voluntary Transfer Lock Request Form is provided by the RIPE NCC.

The Voluntary Transfer Lock Request Form must be submitted to the RIPE NCC via the LIR Portal by a registered contact or an authorised person of the requesting party.

The Voluntary Transfer Lock Request Form must be signed by the authorised person for the requesting party 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 the requesting party is authorised to do so.

To complete the Voluntary Transfer Lock Request Form, the requesting party will have to provide:

• The full official legal name
• Recent registration papers issued by the relevant national authority

If the current official legal name of the requesting party is different from the one in the relevant signed RIPE NCC Standard Service Agreement, then the procedure described in Section 4.0 Link: #memberchanges must be followed prior to requesting voluntary transfer lock.

The RIPE NCC may ask the requesting party 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.

In the Voluntary Transfer Lock Request Form the requesting party is required to indicate the duration of the voluntary transfer lock, which can be 6, 12 or 24 months. The voluntary transfer lock will be applied from the date on which the RIPE NCC approves the voluntary transfer lock request. 

The voluntary transfer lock will expire after 6, 12 or 24 months, depending on the duration requested. 

To continue with the voluntary transfer lock after the expiration of the requested lock duration, a member will have to submit a new voluntary transfer lock request to the RIPE NCC for approval.

Members cannot request the cancellation of the voluntary transfer lock once the lock has been applied until the voluntary transfer lock expires. 

5.3 The Publication of Internet Number Resources under the Voluntary Transfer Lock

The RIPE NCC will publish a list of Internet number resources under voluntary transfer lock on its website.

6.0 Temporary Transfers

As per Section 2.1 of RIPE Resource Transfer Policies Link: https://www.ripe.net/publications/docs/transfer-policies , transfers of Internet Number Resources in the RIPE NCC region are allowed on a permanent or temporary basis (“Temporary Transfers”). Temporary Transfers must be declared to the RIPE NCC for approval according to the procedure described in Section 3.0.

6.1 Term of a Temporary Transfer

In case of a Temporary Transfer, the Internet Number Resources are registered with the Receiving Party until a set date (as mutually agreed by the involved parties and specified in Article 1 of Transfer Agreement Link: https://www.ripe.net/media/documents/Transfer_Agreement_Template_v6.0_FINAL.pdf ) and on such date, the Internet Number Resources automatically return to the Offering Party. The Receiving Party may not further transfer these Internet Number Resources to a third party.

6.2 Earlier Termination of a Temporary Transfer

6.2.1 Standard Service Agreement termination

If the Offering Party is a member and its Standard Service Agreement is terminated (for any reason outlined in the Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources Link: https://www.ripe.net/publications/docs/closure/ ) before the date indicated in Article 1 of the Transfer Agreement, the Internet Number Resources that were temporarily transferred to the Receiving Party, shall not be returned to the Offering Party on the date indicated in Article 1 of the Transfer Agreement. Instead, the RIPE NCC shall deregister the relevant Internet Number Resources per such date.

If the Receiving Party is a member and its Standard Service Agreement is terminated (for any reason outlined in the Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources Link: https://www.ripe.net/publications/docs/closure/ ) before the date indicated in Article 1 of the Transfer Agreement, the Internet Number Resources that were temporarily transferred to the Receiving Party, shall be returned to the Offering Party as per the date that the Standard Service Agreement was terminated.

6.2.2 End User Assignment Agreement termination

As per Section 2 of Independent Internet Number Resources – Contractual Relationship Changes Between Sponsoring LIR and End User Link: http://ripe.net/publications/docs/lir-end-user-contractual-changes#2--termination-of-contractual-relationship , an End User of independent Internet number resources must have a contractual relationship with a sponsoring LIR at all times. If the contractual relationship between the End User and the sponsoring LIR is terminated for any reason, the RIPE NCC must be notified. The End User must at this point enter into a contractual relationship with a different sponsoring LIR or with the RIPE NCC directly.

If the Offering Party is an End User and its contractual relationship with its sponsoring LIR is terminated before the date indicated in Article 1 of the Transfer Agreement, and the Offering Party does not enter into a contractual relationship with a sponsoring LIR within the timeframe set by section 2 of the Independent Internet Number Resources – Contractual Relationship Changes Between Sponsoring LIR and End User Link: http://ripe.net/publications/docs/lir-end-user-contractual-changes#2--termination-of-contractual-relationship , the RIPE NCC shall deregister the relevant Internet Number Resources.

If the Receiving Party is an End User and its contractual relationship with its sponsoring LIR is terminated before the date indicated in Article 1 of the Transfer Agreement, and the Receiving Party does not enter into a contractual relationship with a sponsoring LIR within the timeframe set by section 2 of the Independent Internet Number Resources – Contractual Relationship Changes Between Sponsoring LIR and End User Link: http://ripe.net/publications/docs/lir-end-user-contractual-changes#2--termination-of-contractual-relationship , the Internet Number Resources shall be returned to the Offering Party.

6.2.3 Reasons for Deregistration of the temporarily transferred Internet Number Resources

If there is a reason to deregister temporarily transferred Internet Number Resources (for any reason outlined in the Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources Link: https://www.ripe.net/publications/docs/closure/ ) before the date indicated in Article 1 of the Transfer Agreement, the Internet Number Resources shall be returned to the Offering Party upon request by the RIPE NCC.

6.3 Sanctions on either party involved in the Temporary Transfer

As per Section 3.1 of the Due Diligence for the Quality of the RIPE NCC Registration Data Link: https://www.ripe.net/publications/docs/due-diligence , the RIPE NCC, as an association under Dutch Law, has to comply with sanctions imposed by the Netherlands and the EU.

In case the Offering Party becomes subject to sanctions, with which the RIPE NCC has to comply, before or on the date indicated in Article 1 of the Transfer Agreement, the Internet Number Resources it transferred to the Receiving Party, shall not be returned to the Offering Party on the date indicated in Article 1 of the Transfer Agreement, but shall be placed on such date under the RIPE NCC’s control. The Internet Number Resources will be returned to the Offering Party, when the Offering party ceases to be subject to sanctions applicable to the RIPE NCC.

In case the Receiving Party becomes subject to sanctions, with which the RIPE NCC has to comply, before the date indicated in Article 1 of the Transfer Agreement, the Internet Number Resources that were transferred to the Receiving Party, will be returned to the Offering Party on the date indicated in Article 1 of the Transfer Agreement.

B) In order to prevent implementation problems, network numbers ending with 0 or 255 should NOT be reassigned.

C) Full information about reassigned network numbers must be reported back to the RIPE NCC in full RIPE database format (ref ripe-13). The complete entries should be sent immediately after reassignment to <assign@ripe.net>. The RIPE NCC is ready to accept block entries for the RIPE database. For block syntax, please contact the RIPE NCC.

D) Reassignment of class C network numbers should be done in a manner that facilitates Supernetting (see next section).

E) Requests for network numbers should be reasonable. All NICs and NOCs should prevent stockpiling of network numbers.

F) On first request from the RIPE NCC, the class C network numbers not yet reassigned, must be returned to the RIPE NCC.

Supernetting

NICs and NOCs reassigning IP network numbers are urgently requested to read the Supernetting proposal by Vince Fuller et al. This document can be obtained from the rfc section of the RIPE document store or other RFC servers. It is called rfc1338.txt. The Supernetting proposal was made to reduce the increase of routing table size in the current Internet. It proposes to create a hierarchy of IP network numbers, which can then be aggregated resulting in less routing table entries in routing equipment. While this proposal has not been formally adopted we expect that something at least along the same principle will be implemented in the near future.

Here is how it works:

If an organisation A needs 8 class C network numbers, the numbers should be given out in such a way that the routing information for each of these 8 networks could appear as one entry with the correct mask in routers.

More concretely:

Service provider S hands out networks 192.24.8 through 192.24.15 to organisation A. These networks can then appear in routing equipment as a supernet route to 192.24.8 with mask 255.255.248.0. This way 8 class C network numbers appear as one routing table entry.

The guidelines that can be derived from the Supernetting proposal are:

A) Service providers should reserve blocks of class C network numbers from their allocation for each organisations requesting class C network numbers.

B) The size of these blocks should always be a power of 2.

C) The numbers in these blocks should be contiguous.

D) The blocks should start on bit boundaries. (ie powers of 2, AND multiples of the block size)

E) The blocks reserved for an organisation should be sufficient for a reasonable expected growth over the next few years.

F) Multi-homed organizations may obtain address space from one of their providers, the RIPE NCC, or the global NIC, as is appropriate to their network configuration. These organisations are strongly encouraged to contact the RIPE NCC for guidance.

If you have any questions concerning this, please do not hesitate to call or mail us at ncc@ripe.net.