This document is obsoleted by ripe-72, version 0.7 of this document
1.0 Definitions Link: #definitions
2.0 Introduction Link: #introduction
3.0 Transfer of Internet Number Resources Link: #transfer
3.1 Submission of the Request for Transfer Link: #transfer31
3.2 If the Receiving Party is not a Member Link: #transfer32
3.3 Financial Consequences Link: #transfer33
3.4 Internet Number Resource Registration and RIPE Database Issues Link: #transfer34
4.0 Member Changes Official Legal Name Link: #memberchanges
For the purposes of this document, Internet number resources refer to:
In order for the RIPE NCC to maintain an accurate registry, it must hold accurate data concerning:
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 both of the following changes occurs:
This document describes the procedures for 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 and
US NIC databases, 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
Service providers can request Class B network numbers on a one-by-one
basis from such changes to be properly communicated and registered with the RIPE NCC. Because class B address space is a critical
resource, a request for a class B network number must be
Note:
If a change in a member's business structure is not 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.
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 User's 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: https://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: https://www.ripe.net/publications/docs/inter-rir-transfer-of-inr ”.
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.
For the transfer to be processed, one of the involved parties must submit a request by email to the RIPE NCC:
A registered contact or an authorised person (e.g., senior manager, legal successor) must send the request.
The RIPE NCC will ask for the following information:
i. Information regarding the parties involved, including:
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: https://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, a description of the changes among these organisation(s) is necessary. This description must be accompanied by all official legal documents proving/supporting the changes the request is based on.
iii. A list of the Internet number resources that are requested to be transferred. If all of 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 (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 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).
If the transferring party no longer exists by the time the RIPE NCC is being informed, the receiving party must send:
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.
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: https://www.ripe.net/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 Provider Independent (PI) addresses, 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: https://www.ripe.net/participate/resource-management/independent-resources .
The request for the transfer can be submitted as described above (Section 3.1).
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 ).
The receiving member must deregister from the RIPE Database any invalid or overlapping registrations or unused assignment approvals.
The RIPE NCC will send a new RIPE NCC Standard Service Agreement Link: http://www.ripe.net/publications/docs/service-agreement 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.
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.