This documents obsoletes ripe-65, version 0.6 Contents
1.0 Definitions Link: #1.0
2.0 Introduction Link: #2.0
3.0 Transfer of Internet Number Resource Records Link: #3.0
3.1 Submission of the Request Link: #3.1
3.2 If the Receiving Party is not yet a Member Link: #3.2
3.3 Billing Issues Link: #3.3
3.4 Internet Number Resource Registration and RIPE Database Issues Link: #3.4
4.0 The Member Changes its Official Legal Name Link: #4.0
1.0 Definitions
For the purposes of this document
Abstract Internet Number Resource records refer to:The registered allocations and assignments of a Member The independent Internet Number Resourcesassigned through the Member as a “sponsoring LIR” to an End User
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 Resource records that are registered to the 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.
The Member must inform the RIPE NCC if one or both of the following changes occurs:
Internet Number Resource records are transferred. Such transfers may take place:
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 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
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
Service providers can request Class B network numbers on a one-by-one
basis from to be followed for such changes to be properly communicated to, 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 the Member's official legal name is accompanied by
a justification in terms of the requesting organisation's size, current
network and expected network growth. The requestor should also make
clear why they cannot use a block of class C network numbers to achieve
their goals. transfer of Internet Number Resource records, the Member must first inform the RIPE NCC of the name change and then of the transfer.If a change in the Member's business structure is not accompanied by a transfer of Internet Number Resource records or a change in the Member's official legal name, then the RIPE NCC does not need to be informed of this change.
3.0 Transfer of Internet Number Resource Records
If a Member transfers their Internet Number Resource records to a third party for any reason, this transfer must be declared to, and approved by, the RIPE NCC.
3.1 Submission of the Request for Transfer
One of the involved parties must submit a request by email to the RIPE NCC for the transfer to be executed:
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:
The full official legal names of all parties involved Which party will transfer the Internet Number Resource records 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 the ones in the relevant signed RIPE NCC Standard Service Agreement, then the procedure described under section 4.0 must be followed prior to the transfer of the Internet Number Resource records. The procedure described under section 4.0 is not necessary for the transferring Member if the RIPE NCC Standard Service Agreement of the transferring Member is terminated (see Closure of LIR and Deregistration of Internet Number Resources, section A.1.1. Link: http://www.ripe.net/ripe/docs/closure/#a11 and section A.1.2. Link: http://www.ripe.net/ripe/docs/closure/#a12 ).
ii. A description of the reason for the transfer (for example, due to merger, acquisition, or transfer of allocation 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 the organisation(s) is necessary. The 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 Resource records that are requested to be transferred. If all of the transferring Member's Internet Number Resource records 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 Resource records, the RIPE NCC Standard Service Agreement of the Member may be terminated (see Closure of LIR and Deregistration of Internet Number Resources, section A.1.1. Link: http://www.ripe.net/ripe/docs/closure/#a12 ).
iv. The correct contact details of all organisations involved
The RIPE NCC may ask the organisations 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:
An official document (issued by a national authority) confirming the closure of the transferring party; and A copy of an older signed agreement between the relevant parties mentioning the transfer of the Internet Number Resource records. If such an agreement is not available, the receiving party must send confirmation of the transfer to the RIPE NCC signed by an authorised person (e.g. senior manager, legal successor). The RIPE NCC reserves the right to reverse the transfer should another party object to this transfer and provide an agreement that proves that the Internet Number Resource records 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 The Receiving Organisation is not yet a Member
Members may wish to transfer their Internet Number Resource records to another Member or to an organisation that is not yet a Member.
If the Internet Number Resource records are transferred to a non-Member, the receiving organisation can:
If the receiving organisation refuses to do either of the above, the RIPE NCC will not transfer the Internet Number Resource records to them.
The request for the transfer can be submitted as described in 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. The payment is the responsibility of the receiving Member.
If the receiving organisation 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/ripe/docs/charging ).
3.4 Internet Number Resource Registration and RIPE Database Issues
The RIPE NCC will review 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:
A) the status of any IP address allocation or independent Internet Number Resource assignment maintained by the organisations involved in compliance with the RIPE Policies current at the time of the transfer.The receiving Member must deregister from the RIPE Database any invalid or overlapping registrations or unused assignment approvals.
The RIPE NCC will assign complete class C blocks to individual NICs
and NOCs. They can be requested from <[email protected]>.
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
<[email protected]>.
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 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.
4.0 The Member Changes its Official Legal Name
It is the obligation of the Member to inform the RIPE NCC for guidance.
If you have any questions concerning this, please do not hesitate to
call or mail us at [email protected]. immediately if any change in the Member's official legal name occurs.The Member must send an email to [email protected] Link: mailto:[email protected] informing the RIPE NCC of the name change. This email must include:
New registration papers from the national authority; and The official legal documents supporting this change
The RIPE NCC will send a new RIPE NCC Standard Service Agreement Link: http://www.ripe.net/ripe/docs/ssa 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.