Contents

1.0 Definitions Link: #1

2.0 Introduction Link: #2

3.0 Transfer of Internet Number Resource Records Link: #3

3.1 Submission of the Request for Transfer Link: #31

3.2 If the Receiving Link: #32 Party Link: #32 Link: #32 is Link: #32 not Link: #32 a Link: #32 Member Link: #32

3.3 Financial Consequences Link: #33

3.4 Internet Number Resource Registration and RIPE Database Issues Link: #34

4.0 The Member Changes its Official Legal Name Link: #4

1.0 Definitions

For the purposes of this document:

Internet number resource records refer to

• The registeredallocations and assignments of a Member

• The independent Internet number resources assigned 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 and 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:

1. Internet Number Resource records are transferred. Such transfers may take place:

   • Because of a change in the business structure of the Member, for example in the case of a merger or acquisition of the Member's organisation; or

   • In the case of a pure transfer of IPv4 address records from a Member to another party according to RIPE Policies (Sections 5.5 and 6.4 , "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region Link: https://www.ripe.net/publications/docs/ipv4-policies#55 ”). Such a transfer may also be facilitated through the RIPE NCC Listing Service. Link: /manage-ips-and-asns/resource-transfers-and-mergers/listing/

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.

Introduction

This document describes the procedures

to be followed for such changes to be properly communicated to, and registered with, the RIPE NCC.

Note:

If a change in the Member's official legal name is accompanied by a 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.

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 ”.

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:

• If the transfer is due to a change in the business structure of the Member (e.g., merger or acquisition), the request must be submitted to [email protected] Link: mailto:[email protected]

• If the transfer is a transfer of IPv4 address records from one Member to another party according to RIPE Policies (Sections 5.5 and 6.4, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region Link: https://www.ripe.net/publications/docs/ipv4-policies#55 ”), the request must be submitted to [email protected] Link: mailto:[email protected]

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 Link: #4 4.0 Link: #4 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: https://www.ripe.net/publications/docs/closure#11 and Section A.1.2. Link: https://www.ripe.net/publications/docs/closure#12 ).

ii. A description of the reason for the transfer (for example, due to merger, acquisition, 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 allof 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: https://www.ripe.net/publications/docs/closure#11 ).

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

A bit more explained

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 If the Receiving Party is not a Member

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

If the Internet number resource records are transferred to a non-Member, the receiving party must apply to be a Member by signing the 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/lir-services/member-support/become-a-member ) If the receiving party refuses to do the above, the RIPE NCC will not transfer the Internet number resource records to them.

If the Internet number resource records to be transferred are Provider Independent (PI) addresses , the receiving party may either apply to be a Member by signing the RIPE NCC Standard Service Agreement or enter into a contractual relationship with a sponsoring LIR. For more information, please see:

https://www.ripe.net/lir-services/resource-management/independent-resources/ Link: https://www.ripe.net/lir-services/resource-management/independent-resources/

The request for the transfer can be submitted as described above (Section 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 party is not a Member, then the 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/ripe/docs/charging ).

3.4 Internet Number Resource Registration and RIPE Database Issues

The RIPE NCC will review 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.

The receiving Member must deregister from the RIPE Database any invalid or overlapping registrations or unused assignment approvals.

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.

4.0 The Member Changes its Official Legal Name

It is the obligation of the Member to inform the RIPE NCC 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: https://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.

Procedures for the delegation of direct subdomains of 193.in-addr.arpa

1. A secondary nameserver at ns.ripe.net is mandatory for all blocks of class C network numbers delegated in the 193.in-addr.arpa domain.

2. Because of the increasing importance of correct reverse address mapping, for all delegated blocks a good set of secondaries must be defined. There should be at least 2 nameservers for all blocks delegated, excluding the RIPE NCC secondary.

3. The delegation of a class C block in the 193.in-addr.arpa domain can be requested by sending in a domain object for the RIPE database to <[email protected]> with all necessary contact and nameserver information. The RIPE NCC will then forward all
current reverse zones inside this block to the registry, and after addition of these by the registry, the NCC will check the working of the reverse server. Once everything is setup properly, the NCC will delegate the block, and submit the database object for inclusion in the database. An example domain object can be found at the end of this document.

4. All reverse servers for blocks must be reachable from the whole of the Internet. In short, all servers must meet similar connectivity requirements as top-level domain servers.

5. Running the reverse server for class C blocks does not imply that one controls that part of the reverse domain, it only implies that one administers that part of the reverse domain.

6. Before adding individual nets, the administrator of a reverse domain must check wether all servers to be added for these nets are indeed setup properly.

7. There are some serious implications when a customer of a service provider that uses address space out of the service provider class C blocks, moves to another service provider. The previous service provider cannot force its ex-customer to change network
addresses, and will have to continue to provide the appropriate delegation records for reverse mapping of these addresses, even though it they are no longer belonging to a customer.

8. The registration of the reverse zones for individual class C networks will usually be done by the registry administering the class C block this network has been assigned from. The registry will make the necessary changes to the zone, and update the network objects in the RIPE database for these networks, to reflect the correct "rev-srv" fields. In case the RIPE NCC receives a request for the reverse zone of an individual class C network out
of a block that has been delegated, the request will be forwarded to the zone contact for this reverse block.

9. The NCC advises the following timers and counters for direct subdomains of 193.in-addr.arpa: 8 hours refresh (28800 seconds), 2 hours retry (7200 seconds), 7 days expire (604800 seconds) and 1 day Time To Live (86400 seconds). The retry counter should be
lowered where connectivity is unstable.

Above procedures are defined to ensure the necessary high availability for the 193 reverse domains, and to minimize confusion. The NCC will ensure fast repsonse times for addition requests, and will in principle update the 193.in-addr.arpa domain at least once per working day.

Example domain object to request a block delegation

domain: 202.193.in-addr.arpa
descr: Pan European Organisations class C block
admin-c: Daniel Karrenberg
tech-c: Marten Terpstra
zone-c: Marten Terpstra
nserver: ns.eu.net
nserver: sunic.sunet.se
nserver: ns.ripe.net
changed: [email protected] 930319
source: RIPE

Procedures for the delegation of individual network zones by the RIPE NCC.

The registration of the reverse zones for individual class C networks will usually be done by the registry administering the class C block this network has been assigned from. In case the zone corresponding to the class C block has not been delegated, the RIPE NCC will automatically add the reverse nameserver as specified in the "rev-srv" attribute of the RIPE database object for this network, using the following procedures:

1. Because of the increasing importance of correct reverse address mapping, for all delegated networks a good set of secondaries must be defined. There should be at least two nameservers for all networks delegated.

2. The "rev-srv" field should ONLY contain one fully qualified domain name of a nameserver which is authoritative for the reverse zone for this network.

3. If a network has or is going to have any external connectivity, it is strongly recommended that it has at least one reverse nameserver that can be reached from all of the Internet.

4. The checking and addition of the reverse zones for single networks is completely automated at the RIPE NCC. Although we do our best to check the setup of the nameservers, these does not receive the same level of scrutiny as nameservers for blocks of class C network numbers. It is the responsibility of the network contacts to ensure proper operation.

5. Any problems regarding the reverse zones in 193.in-addr.arpa should be directed to <[email protected]>.

The NCC also suggests that similar procedures are set up for the delegation of reverse zones for individual class C networks from the registries to individual organisations.