Skip to main content
  • Legend
  • Added
  • Deleted

Abstract

This is a procedural document that describes the steps to be taken when there are changes in the contractual relationship between the End User of independent Internet number resources and the sponsoring Local Internet Registry (LIR). The document also describes the scenarios in which the RIPE NCC may de-register independent Internet number resources.

This document does not describe the procedure applicable to contractual relationship changes for independent Internet number resource users who have signed a contract with the RIPE NCC.

Table of Contents

1.0 Introduction Link: #10
2.0 Ownership and Legal Name Changes Link: #20
2.1 End User Organisation Changes Ownership Link: #21
2.2 End User Organisation Changes Name Link: #22

3.0 Transfer of Contractual Relationship Link: #30
3.1 Transfer between Sponsoring LIRs Link: #31
3.2 Transfer from Sponsoring LIR to the RIPE NCC Link: #32

4.0 De-registering of Independent Internet Number Resources Link: #40
4.1 Closure of Sponsoring LIR Link: #41
4.1.1 De-registration Timeframe Link: #411
4.2 Violation of RIPE Policy, Law or Contract Link: #42
4.2.1 De-registration Timeframe Link: #421
4.3 Contract Expired and Not Renewed / Ceased and Not Transferred Link: #43

1.0 Introduction

In October 2008, the RIPE community accepted a policy change which states that a contractual relationship must be established between an End User and a sponsoring LIR or the RIPE NCC before the End User can receive independent Internet number resources.

In order to fulfil its mandate of manager of independent Internet number resources, the RIPE NCC requires End Users and LIRs to inform the RIPE NCC in case of changes to their contractual relationship.

The procedures listed in this document are subject to RIPE policies.

2.0 Ownership and Legal Name Changes

The RIPE NCC requires Sponsoring LIRs to maintain a proper registration of End User's legal organisation changes with the RIPE NCC.

2.1 End User Organisation Changes Ownership

If the ownership of the organisation changes but the legal operating name is continued, the RIPE NCC does not have to be notified.

2.2 End User Organisation Changes Name

When an End User that has been assigned independent

Section A of this document describes the valid reasons for terminating the RIPE NCC Standard Service Agreement that leads to the closure of an LIR account, the procedure that applies in each circumstance and the consequences.

Section B describes the valid reasons for deregistration of Internet number resources

changes its legal operating name, the RIPE NCC must be notified.

In all cases, a new contract must be signed between the renamed End User organisation and the sponsoring LIR in order to guarantee a legitimate handover of the existing rights and obligations.

A copy of this contract, a revised extract of the Trade Register and proof of change from an authorised person must be provided to the RIPE NCC.

3.0 Transfer of Contractual Relationship

If the contractual agreement between the End User of independent Internet number resources and the sponsoring LIR ceases, for any reason, the contractual changes must be communicated to the RIPE NCC.

3.1 Transfer between Sponsoring LIRs

If the End User decides to change sponsoring LIR, this change must be communicated to the RIPE NCC.

The request must come from either the current or the new sponsoring LIR. The RIPE NCC will need confirmation from both LIRs before it can proceed with the transfer, unless the current LIR is closed or in the process of being closed.

The RIPE NCC will finalise the change after it receives a copy of the new End User Assignment Agreement and extract of the Trade Register. The new agreement will replace the old agreement.

3.2 Transfer from Sponsoring LIR to the RIPE NCC

If the contractual agreement between the End User of independent and the procedure that applies in each circumstance.

Please note that, for the purposes of this document, LIRs are referred to as “Contributors”.

Table of Contents

A. Closure of LIR – Termination of the RIPE NCC Standard Service Agreement

1. Grounds for termination and procedure in each case Link: #a1

1.1. Termination by the Contributor Link: #a11

1.2. Termination by the RIPE NCC Link: #a12

1.2.1. Termination with a three-month notice period Link: #a121

1.2.1.1. Violation of RIPE Policies and RIPE NCC procedures Link: #a1211

a. Unresponsiveness Link: #a1211a

b. Allocations/assignments contravening RIPE Policies Link: #a1211b

c. Incorrect registration in the RIPE Database Link: #a1211c

d. Non-compliance with RIPE NCC audits Link: #a1211d

e. Non-compliance with an arbiter ruling Link: #a1211e

1.2.1.2. Provision of untruthful information Link: #a1212

a. Falsified/incorrect information Link: #a1212a

b. Fraudulent requests Link: #a1212b

1.2.1.3. Other reasons Link: #a1213

1.2.2. Termination with immediate effect Link: #a122

a. Contributor files for bankruptcy, is liquidated, suspends its payments or becomes insolvent Link: #a122a

b. Contributor damages the name, trademarks or intellectual property rights of the RIPE NCC Link: #a122b

c. Contributor fails to submit to the RIPE NCC a valid extract from the Commercial Trade Register or equivalent register Link: #a122c

d. The Contributor fails to observe any rule of applicable law Link: #a122d

e. Non-payment Link: #a122e

f. Termination of the Contributor's RIPE NCC member status Link: #a122f

2. Consequences Link: #a2

2.1. End of provision of RIPE NCC services Link: #a21

2.1.1. General services Link: #a211

2.1.2. Registration of distributed

Internet number resources and the sponsoring LIR ceases and the End User wants to enter into a contractual relationship with the RIPE NCC, the End User will have to follow the application procedure to become a Direct Assignment User, signing the Link: #a212

2.1.3. Request for independent Internet number resources as a “sponsoring LIR” Link: #a213

2.2. End of Contributor's RIPE NCC member status Link: #a22

B. Deregistration of Internet number resources

1. Reasons for deregistration of Internet number resources Link: #b1

1.1. Allocations and Independent Internet number resources assigned for the Contributor's own network or assigned through a “sponsoring LIR” Link: #b11

a. Termination of the SSA Link: #b11a

b. Invalidity of original allocation/assignment criteria Link: #b11b

c. Incorrect registration of the allocation/assignment in the RIPE Database Link: #b11c

d. Falsified/incorrect information Link: #b11d

e. Fraudulent request Link: #b11e

f. Non-compliance with a RIPE NCC audit Link: #b11f

g. Court order Link: #b11g

h. Independent Internet number resources assigned through a “sponsoring LIR” without a valid contractual relationship Link: #b11h

1.2. Independent Internet number resources assigned directly by the RIPE NCC for Direct Assignment Agreement Link: #b12

a. Termination of the RIPE NCC End User Assignment Agreement

with the RIPE NCC and paying the Administration and first Maintenance Fee.

At this point, the RIPE NCC will need confirmation from both the End User and the sponsoring LIR before it can proceed with the transfer of the contractual relationship of independent Internet number resources, unless the LIR is closed or in the process of being closed.

4.0 De-registering of Independent Internet Number Resources

There are three possible scenarios in which the RIPE NCC will de-register independent Internet number resources.

4.1 Closure of Sponsoring LIR

If the sponsoring LIR is in the process of being closed, the End User that was assigned the independent Link: #b12a

b. Unresponsive Direct Assignment User Link: #b12b

c. Invalidity of original criteria Link: #b12c

d. Incorrect registration of the assignment in the RIPE Database Link: #b12d

e. Falsified/incorrect information Link: #b12e

f. Fraudulent request Link: #b12f

g. Non-compliance with a RIPE NCC audit Link: #b12g

h. Court order Link: #b12h

2. Procedures for deregistration of different types of

Internet number resources must sign a contract with a new sponsoring LIR or with Link: #b2

2.1. Allocations and Independent Internet number resources for Contributor's own network Link: #b21

2.2. Independent Internet number resources assigned through a “sponsoring LIR” Link: #b22

2.3. Independent Internet number resources directly assigned by the RIPE NCC to Direct Assignment Users Link: #b23

A. Closure of LIR - Termination of the RIPE NCC Standard Service Agreement

An organisation or an individual person can receive services from the RIPE NCC if they:

  • Agree and sign the RIPE NCC Standard Service Agreement (SSA); and

  • Conform to the RIPE NCC Standard Terms and Conditions (STCs); and

  • Conform to RIPE Policies.

An organisation or an individual person signing the SSA is called a “Contributor”. The RIPE NCC SSA is entered into for an indefinite period of time, unless terminated by either party.

1. Grounds for termination and procedure in each case

The SSA can be terminated by the Contributor (see section 1.1) or by the RIPE NCC. This must take place within 90 days of the date of notification The termination by the RIPE NCC can either be with a notice period of three months (see section 1.2.1.) or for specific reasons with a shorter notice period and immediate effect (see section 1.2.2.).

1.1. Termination by the Contributor

According to Article 8.1 of the STCs, the Contributor can terminate the SSA with a notice period of three months. Possible reasons why Contributors might want to terminate their SSA include:

  • The Contributor decides to close or to change their business

  • The Contributor decides to merge with another Contributor and therefore they do not need to be Contributors themselves

  • The Contributor decides to assign Internet number resources from another Contributor

Procedure

The notice will formally request the termination of the SSA.

It must be:

  • Dated and signed by an authorised representative of the Contributor. A registered contact cannot give notice unless the registered contact is an authorised representative.

  • Sent to the RIPE NCC by email to <ncc@ripe.net Link: mailto:lir-help@ripe.net > or by postal mail to: RIPE NCC, Singel 258, 1016 AB Amsterdam, The Netherlands.

The RIPE NCC will send an acknowledgement of the receipt of the notice. Upon receipt of such notice, the progress of any open requests for RIPE NCC services is terminated.

The termination of the SSA will take place three months after the receipt of the notice by the RIPE

NCC to the contact email addresses listed in the relevant RIPE Database object.

4.1.1 De-registration Timeframe

Day one: The End User contact email addresses listed in the RIPE Database object are notified by the RIPE NCC about the need to sign a contract with a new sponsoring LIR or with the RIPE NCC.

Day thirty: The End User contact email addresses listed NCC.

Billing issues

If the termination takes place in the course of a financial year, the annual contribution shall nevertheless remain due in full by the Contributor (see also paragraph 6.6 of the RIPE NCC Articles of Association (AoA) Link: https://www.ripe.net/publications/docs/articles-association and the RIPE NCC Billing Procedure Link: http://www.ripe.net/lir-services/billing/procedure ).

1.2. Termination by the RIPE NCC

1.2.1. Termination with a three-month notice period

According to Article 8.1 of the STCs, the RIPE NCC can terminate the SSA with a notice period of three months. Grounds for such termination may be the following:

1.2.1.1. Violation of RIPE Policies and RIPE NCC procedures

The Contributor must comply with RIPE Policies and RIPE NCC procedures (see Articles 3.4 and 9 of the STCs). The RIPE NCC will terminate the SSA if the Contributor commits any of the following violations of RIPE Policies or RIPE NCC procedures:

a. Unresponsiveness

The Contributor is unresponsive for a significant period of time.

Contributors are considered to be unresponsive if they do not react to a specific email/request made by the RIPE NCC relating to an incorrect/ambiguous registration of Internet number resources, regardless of whether they are at the same time responsive to a different email/request from the RIPE NCC or they continue paying the RIPE NCC fees.

b. Allocations/assignments contravening RIPE policies

Allocations or transfers of allocations and assignments are not made and used in accordance with the RIPE community's policies.

c. Incorrect registration

in the RIPE Database

object receive an email reminder and a "Remarks" line is added to the resource RIPE Database object.

Day sixty: The End User contact email addresses listed in the RIPE Database object receive a final email reminder; the resource RIPE Database object is locked with the RIPE NCC maintainer; and reverse delegation is removed for IP address ranges.

Day ninety: The resource and related RIPE Database objects are deleted from the RIPE Database. The resource will be de-registered and put in quarantine for future re-assignment.

4.2 Violation of RIPE Policy, Law or Contract

The RIPE NCC will de-register the independent Internet number resources in case of a fundamental breach of contract by the End User, supported by a Dutch court order; or

Violation of Law by the End User, supported by a Dutch court order; or violation of RIPE Policy by the End User.

4.2.1 De-registration Timeframe

Day one: The sponsoring LIR and the End User contact email addresses listed in the RIPE Database object receive a notification from the RIPE NCC; the resource RIPE Database object is locked with the RIPE NCC maintainer.

Day thirty: The sponsoring LIR and the End User contact email addresses listed in the RIPE Database object receive a notification from the RIPE NCC; the resource and related RIPE Database objects are deleted from the RIPE Database. The resource will be de-registered and put in quarantine for future re-assignment.

4.3 Contract Expired and Not Renewed / Ceased and Not Transferred

If the contract between the sponsoring LIR and the End User of independent Internet number resources has expired and has not been renewed, or has ceased

Registration data is repeatedly maintained incorrectly (allocations and assignments must be properly registered in the RIPE Database).

Proper registration must be as follows:

  • The inetnum and the inet6num object(s) for approved assignments must use the netname(s) approved by the RIPE NCC and not be larger than the size approved by the RIPE NCC

  • The date in the first “changed:” attribute must not be earlier than the date of approval from the RIPE NCC

  • The data must be valid and must allow the RIPE NCC to contact the natural person referenced directly in the inetnum or inet6num object(s) or via the maintainers of the inetnum or inet6num object(s) within a reasonable time without having to get information from another source

d. Non-compliance with RIPE NCC audits

Non-compliance with RIPE NCC audits includes repeated unresponsiveness to or failure to cooperate with the RIPE NCC auditors' requests regarding registrations of Internet number resources for the Contributor's own network. For more information about the audit procedure, please see RIPE NCC audit activity Link: http://www.ripe.net/ripe/docs/audit .

e. Non-compliance with an arbiter ruling

For more information, please see RIPE NCC Conflict Arbitration Procedure Link: http://www.ripe.net/ripe/docs/arbitration .

Procedure

If the RIPE NCC becomes aware of any of the aforementioned reasons for terminating the SSA, the RIPE NCC will:

  • Send an email to the registered contact(s) indicating:

    • the violation

    • the Contributor's obligation to stop/repair the violation

    • the termination of the SSA in three (3) months if the violation continues

  • Terminate the progress of any open requests for RIPE NCC services

If the Contributor does not comply within 30 days of the date of the email, the RIPE NCC will send a reminder email to the registered contact(s) indicating:

  • The violation

  • The Contributor's obligation to stop/repair the violation

  • The termination of the SSA in two (2) months if the violation continues

After 60 days from the date of the first email, if the Contributor still does not comply, the RIPE NCC will send a second reminder email and a reminder by postal mail to the registered email and email addresses indicating:

  • The violation

  • The Contributor's obligation to stop/repair the violation

  • The termination of the SSA in one (1) month if the violation continues

After 90 days from the date of the first email, if the Contributor continues not to comply, the RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Contributor's account) to all registered postal and email addresses of the Contributor.

1.2.1.2 Provision of untruthful information

The RIPE NCC concludes the SSA and provides services to Contributors in good faith. The Contributor is in breach of good faith in the following cases:

a. Falsified/incorrect information

If the Contributor repeatedly provides falsified data or information, or purposefully and/or repeatedly provides incorrect data or information (for example, falsified registration documents or IDs, incorrect/inaccurate contact details, etc.)

b. Fraudulent requests

If the Contributor submits repeatedly fraudulent requests for Internet number resources (for example, providing incorrect purpose/need or falsified information about the network, etc.)

Procedure

If the RIPE NCC becomes aware of any of the aforementioned reasons for

terminating the SSA, the RIPE NCC will send an email to the registered contact(s) indicating:

  • The Contributor's obligation to provide correct and true information
  • The termination of the SSA if the Contributor does not comply with this obligation

If the Contributor continues to send falsified/incorrect information or fraudulent requests, the RIPE NCC will send a reminder email to the registered contact(s) indicating:

  • The Contributor's obligation to provide correct and true information
  • The termination of the SSA the next time the Contributor sends falsified/incorrect information or fraudulent requests

If the Contributor continues to send falsified/incorrect information or fraudulent requests, the RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Contributor's account) to all registered postal and email addresses of the Contributor.

1.2.1.3 Other reasons

Termination for any other

reason, the End User has a maximum of 90 days to sign a contract either with a new sponsoring LIR or with the RIPE NCC.The timeframe for this case reason by the RIPE NCC is only executed when the Contributor consents to the termination, unless the termination is for reasons above and beyond control of the RIPE NCC.

For example, such termination has taken place in the past in the case of the emergence of AfriNIC, the RIR for the African region, when, with the consent of the African Contributors, the SSAs with the RIPE NCC were terminated and new contracts with AfriNIC were signed.

Procedure

The notice will officially inform about the termination of the SSA, state the reasons for the termination and detail the planned arrangements regarding the Internet number resources that were distributed to the Contributor.

Unless otherwise required by the circumstances:

  • The RIPE NCC will terminate the progress of any open requests for RIPE NCC services

  • Section A.2. (Consequences of termination of the SSA) and section B (Deregistration of Internet number resources) of this document are applicable

The notice will be dated and signed by an authorised representative of the RIPE NCC.

Notice will be sent to the registered contact(s) of the Contributor by electronic and postal mail.

Upon receipt of such notice, the progress of any open requests for RIPE NCC services is terminated. The termination of the SSA will take place after three months from the date the RIPE NCC sends the notice, unless the Contributor requests a longer period and this is agreed upon.

Billing issues

All outstanding amounts for the full year must be settled unless otherwise agreed.

1.2.2. Termination with immediate effect

According to Article 8.2 of the STCs, the RIPE NCC is entitled to terminate the SSA with immediate effect in the following cases:

a. Contributor files for bankruptcy, is liquidated, suspends its payments or becomes insolvent

Upon receipt of the documents stating the bankruptcy, liquidation, suspension of payments or insolvency of the Contributor by the relevant authority or by public announcement of the fact, the RIPE NCC will terminate the SSA. If the relevant national authority decides that the Contributor's operations can continue, and provided that the Contributor fulfills the obligations coming from the SSA, the RIPE NCC will not terminate the SSA.

Procedure

The RIPE NCC will:

  • Send an email to the registered contact(s) and/or to the legal successor indicating:

    • The reason for termination of the SSA

    • The immediate termination of the SSA

  • Terminate the progress of any open requests for RIPE NCC services

The RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the member) to all registered contacts of the Contributor or to the legal successor, both by electronic and registered postal mail.

b. Contributor damages the name, trademarks or intellectual property rights of the RIPE NCC

Examples:

  • The Contributor pretends to be, or to act on behalf of, the RIPE NCC through misuse of the RIPE NCC name or logo

  • The Contributor unreasonably makes allegations against the RIPE NCC in order to damage the RIPE NCC's reputation and operations, resulting in irreversible damage to the RIPE NCC

Procedure:

The RIPE NCC will

  • Send an email to the registered contact(s) indicating:

    • the violation

    • the Contributor's obligation to stop/repair the violation

    • the termination of the SSA if the violation continues

  • Terminate the progress of any open requests for RIPE NCC services

If the Contributor does not comply within 30 days of the date of the email, the RIPE NCC will send a reminder email to the registered contact(s) indicating the same as above.

After 60 days from the date of the first email, if the Contributor still does not comply, the RIPE NCC will:

  • Send a second reminder email to the registered contact(s) indicating the same as above

  • Not approve any Internet number resource requests

After 90 days from the date of the first email, if the Contributor continues not to comply, the RIPE NCC will:

  • Send a third reminder email and a reminder by postal mail to the registered email and postal addresses indicating the same as above

  • Stop providing any services to the Contributor

After 120 days from the date of the first email, if the Contributor still does not comply, the RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Contributor's account) to all registered postal and email addresses of the Contributor.

c. Contributor fails to submit to the RIPE NCC a valid extract from the Commercial Trade Register or equivalent register

When initially signing the SSA, the Contributor must submit to the RIPE NCC an extract from the Commercial Trade Register or equivalent document providing the registration of the Contributor's business with the national authorities (see Article 2.2 of the STCs).

If the Contributor is a natural person, the RIPE NCC requires submission of any identification papers (passport, driving license or other official document proving the identity of the individual).

If the Contributor is a legal person, identification papers are also required for the authorised person signing the SSA on behalf of the legal person.

If there is any change in the Contributor's business after signing the SSA (for example, the Contributor has merged with another company, has changed name, etc.) and, because of this change, the Contributor's registration with the relevant register has been changed, then the Contributor is obliged to submit the updated registration papers to the RIPE NCC.

If the Contributor does not submit the aforementioned documents within one month of them being requested by the RIPE NCC, the RIPE NCC will terminate the SSA.

Procedure

The RIPE NCC will:

  • Send an email to the registered contact(s) indicating:

    • the Contributor's obligation to submit the relevant documents

    • the termination of the SSA if the documents are not submitted

  • Terminate the progress of any open requests for RIPE NCC services

If the Contributor does not comply within 15 days of the date of the email, the RIPE NCC will send a reminder email and a notification by postal mail to the registered email and postal addresses indicating the same as above.

After 30 days from the date of the first email, if the Contributor continues not to comply, the RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Contributor's account) to all registered postal and email addresses of the Contributor.

d. The Contributor fails to observe any rule of applicable law

The SSA is exclusively governed by the laws of the Netherlands because the RIPE NCC is an association under Dutch law. The RIPE NCC is allowed to terminate the SSA of a Contributor with immediate effect, provided it receives a Dutch court order to do so.

Procedure

The RIPE NCC will:

  • Send an email to the registered contact(s) indicating:

    • The reason for termination of the SSA

    • The immediate termination of the SSA

  • Terminate the progress of any open requests for RIPE NCC services

The RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Contributor's account) to all registered postal and email addresses of the Contributor.

e. Non-payment.

In case of non-payment, in accordance with the RIPE NCC Billing Procedure, the SSA is terminated after 120 days. For more information, please see the RIPE NCC Billing Procedure Link: http://www.ripe.net/lir-services/billing/procedure .

f. Termination of the Contributor's member status

By signing the SSA, Contributors become members of the RIPE NCC association. If Contributors cancel their member status with the RIPE NCC association, the SSA is automatically terminated.

Please note that if this cancellation takes place due to restrictions in the local law or due to specific restrictions in the structure of the organisation that prevent the Contributor from being a member, the SSA is not terminated (see also Article 6 of the AoA).

Procedure

The RIPE NCC will:

  • Send an email to the registered contact(s) indicating:

    • The reason for termination of the SSA

    • The immediate termination of the SSA

  • Terminate the progress of any open requests for RIPE NCC services

The RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Contributor's account) to all registered postal and email addresses of the Contributor.

2. Consequences

Upon termination of the SSA, Contributors lose all rights to RIPE NCC services and their RIPE NCC member status.

2.1. End of provision of RIPE NCC services

2.1.1. General services

The RIPE NCC will stop providing RIPE NCC services, including:

  • Distribution of Internet number resources

  • Authority to maintain Internet number resource records in the RIPE Database

  • Access to the LIR Portal

  • Use of the RIPE NCC Certification Service

  • Participation in RIPE NCC Training Courses

2.1.2. Registration of distributed Internet number resources

The RIPE NCC will deregister the relevant Internet number resource records. The procedure for deregistration

is described in Section 4.1.1 - De-registration Timeframe. section B.2. The RIPE NCC will also revoke any certificates generated by the RIPE NCC Certification Service.

2.1.3. Request for independent Internet number resources as a “sponsoring LIR”

Contributors lose their right to request independent Internet number resources as a “sponsoring LIR”. For independent Internet number resources already assigned by them, see below at section B.2.2.

2.2. End of Contributor's RIPE NCC member status

Contributors will also lose their RIPE NCC member status and all relevant rights, such as the right to attend and vote at RIPE NCC General Meetings.

B. Deregistration of Internet Number Resources


1. Reasons for deregistration of Internet number resources

1.1 Allocations and Independent Internet number resources assigned for the Contributor's own network or assigned through a “sponsoring LIR”

a. Termination of the SSA

For more information, see section A. For Independent Internet number resources through a “sponsoring LIR”, see Independent Internet Number Resources – Contractual Relationship Changes between sponsoring LIR and End User Link: http://www.ripe.net/ripe/docs/lir-end-user-contractual-changes .

b. Invalidity of original allocation/assignment criteria

Internet number resources are allocated/assigned based on a specific need. When the original technical requirements or the business purpose for the use of the Internet number resources change, the allocation/assignment becomes invalid. If the RIPE NCC notices any change in the original technical criteria or the original business purposes for using the Internet number resources, the RIPE NCC is authorised to deregister the relevant Internet number resources.

c.Incorrect registration of the allocation/assignment in the RIPE Database

If the allocation/assignment approved by the RIPE NCC is not properly registered in the RIPE Database, the RIPE NCC is authorised to deregister the relevant Internet number resources.

Proper registration must be as follows:

  • The inetnum and the inet6num object(s) for approved assignments must use the netname(s) approved by the RIPE NCC and not be larger than the size approved by the RIPE NCC

  • The date in the first “changed:” attribute must not be earlier than the date of approval from the RIPE NCC

  • The data must be valid and must allow the RIPE NCC to contact the natural person mentioned directly in the inetnum or inet6num object(s) or via the maintainers of the inetnum or inet6num object(s) object within a reasonable time without having to get information from another source

d. Falsified/incorrect information

If a Contributor has provided falsified data or information, or purposefully provided incorrect data or information (for example, falsified registration documents or IDs, incorrect/inaccurate contact details, etc.) regarding an allocation or an Independent resource, the RIPE NCC will deregister the relevant records.

e. Fraudulent request

If a Contributor has submitted a fraudulent request for an allocation or an Independent resource (for example, by providing incorrect purpose/need or falsified information about the network, etc.), the RIPE NCC will deregister the relevant records.

f. Non-compliance with a RIPE NCC audit

If a Contributor does not comply with a RIPE NCC audit regarding the registration of an Independent resource that the Contributor is responsible for as “sponsoring LIR”, the RIPE NCC will deregister the relevant records. Non-compliance includes, but is not limited to, unresponsiveness to or failure to cooperate with the RIPE NCC auditors' requests. For more information about the audit procedure, please see RIPE NCC Audit Activity Link: http://www.ripe.net/ripe/docs/audit .

g. Court order

The RIPE NCC is an association under Dutch law. In the event a Dutch court orders deregistration of specific Internet number resources, the RIPE NCC must and will comply.

h. Independent Internet number resources assigned through a “sponsoring LIR” without an valid contractual relationship

See Independent Internet Number Resources – Contractual Relationship Changes between sponsoring LIR and End User Link: http://www.ripe.net/ripe/docs/lir-end-user-contractual-changes .

1.2 Independent Internet number resources directly assigned by the RIPE NCC for Direct Assignment Users

a. Termination of the RIPE NCC End User Assignment Agreement

The RIPE NCC End User Assignment Agreement can terminate according to Article 7 of that agreement. Sections A.1 and A.2.2 above, referring to the SSA and the Contributors, can apply accordingly for the RIPE NCC End User Assignment Agreement and the Direct Assignment Users.

b. Unresponsive Direct Assignment User

Direct Assignment Users are considered to be unresponsive if they do not react to a specific email/request made by the RIPE NCC relating to an incorrect/ambiguous registration of Internet number resources, regardless of whether they are at the same time responsive to a different email/request from the RIPE NCC or they continue paying the RIPE NCC fees (see also the RIPE Policy Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region Link: http://www.ripe.net/ripe/docs/contract-req ).

c. Invalidity of original criteria

If the Direct Assignment User does not inform the RIPE NCC of any change in the original technical criteria or the original business purposes for using the resources when the change takes place, the RIPE NCC is authorised to deregister the relevant Internet number resources.

d. Incorrect registration of the assignment in the RIPE Database

If the Direct Assignment User does not properly register in the RIPE Database the assignment approved by the RIPE NCC, the RIPE NCC is authorised to deregister the relevant Internet number resources.

Proper registration must be as follows:

  • The inetnum and the inet6num object(s) for approved assignments must use the netname(s) approved by the RIPE NCC and not be larger than the size approved by the RIPE NCC

  • The date in the first “changed:” attribute must not be earlier than the date of approval from the RIPE NCC

  • The data must be valid and must allow the RIPE NCC to contact the natural person referenced directly in the inetnum or inet6num object(s) or via the maintainers of the inetnum or inet6num object(s) within a reasonable time without having to get information from another source

e. Falsified/ incorrect information

If a Direct Assignment User has provided falsified data or information, or purposefully and/or repeatedly provided incorrect data or information (for example, falsified registration documents or IDs, incorrect/inaccurate contact details, etc.) regarding an allocation or an Independent resource, the RIPE NCC will deregister the relevant records.

f. Fraudulent request

If a Direct Assignment User has submitted a fraudulent request for assignment of an Independent resource (for example, providing incorrect purpose/need or falsified information about the network, etc.), the RIPE NCC will deregister the relevant records.

g. Non-compliance with a RIPE NCC audit

If a Direct Assignment User does not comply with a RIPE NCC audit regarding an assignment of an Independent resource, the RIPE NCC will deregister the relevant records. Non-compliance includes, but is not limited to, unresponsiveness to or failure to cooperate with the RIPE NCC auditors' requests. For more information about the audit procedure, please see the RIPE NCC Audit Activity Link: http://www.ripe.net/ripe/docs/audit .

h. Court order

The RIPE NCC is an association under Dutch law. In the event a Dutch court orders deregistration of specific Internet number resources, the RIPE NCC must and will comply.

2. Procedures for deregistration of different types of Internet number resources

2.1 Allocations and independent Internet number resources for Contributor's own network

The RIPE NCC will send an official notification by email to all registered contacts stating that the allocation/independent Internet number resources will be deregistered, explaining the reasons for this deregistration and the procedure of the deregistration. The Contributor will not be able make any further assignments from the allocations.

Should the Contributor respond within four weeks, the RIPE NCC will provide a timeframe of three months for the Contributors to take care of any actions necessary for the deregistration of the Internet number resources. In the case of allocations, Contributors are responsible for requesting that their customers renumber immediately and for providing them with all available options. In particular, Contributors must refer their customers to the list of other Contributors. This list is available at:

https://www.ripe.net/membership/indices/index.html Link: https://www.ripe.net/membership/indices/index.html

During the three-month period:

  • The Contributor must stop announcing the allocation/independent Internet number resources

  • The RIPE NCC will change the mnt-by object on the Contributor's records to the status “deregistered maintainer”

  • A warning statement is added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources

  • The RIPE NCC will revoke any certificates generated by the RIPE NCC Certification Service

After the three-month period, the allocation/assignment will be deregistered from the RIPE Database.

Should the Contributor not react within four weeks, the RIPE NCC will:

  • Change the mnt-by object on the Contributor's records to the status “deregistered maintainer”; and/or

  • Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the Internet number resources; and/or

  • Withdraw the reverse delegation; and/or

  • Contact the upstream to investigate possible hijacking of Internet number resources; and/or

  • Delete all relevant objects in the RIPE Database, including allocation/assignment and route objects

  • Revoke any certificates generated by the RIPE NCC Certification Service.

The sole purpose of these actions by the RIPE NCC is for deregistration of the Internet number resources to reflect reality. As a result, if the Internet number resources are no longer announced after one of these actions, the RIPE NCC might not perform any other actions.

Please note:

If the Contributor responds but with no intention to comply or objects at some point within the four-week period, the RIPE NCC will allow the time remaining in this four-week period for the Contributor to submit evidence that there is no reason for the deregistration of the Internet number resources or to request arbitration (see RIPE NCC Conflict Arbitration Procedure Link: /about-us/legal/arbitration/ ). However, if the four-week period expires without the submission of such evidence by the Contributor or without the submission of a request for arbitration, the RIPE NCC will proceed as if the Contributor had never reacted (see relevant procedure above). The Contributor may still request arbitration according to the timeframes of the RIPE NCC Conflict Arbitration Procedure. If the Contributor requests arbitration, the RIPE NCC will change the mnt-by object on the relevant records to the status “maintainer in dispute” and a warning statement will be added to the relevant records of the RIPE Database until the communication of the arbiter's ruling.

2.2 Independent Internet number resources assigned through a “sponsoring LIR”

The RIPE NCC will send an official notification to all registered contacts stating that the Independent Internet number resources will be deregistered, explaining the reasons for this deregistration and the procedure for the deregistration. The Contributor must immediately inform the End User about the imminent deregistration.

During this period:

  • The End User must stop announcing the Independent Internet number resources

  • The RIPE NCC will change the mnt-by object on the relevant records to the status “deregistered maintainer”

  • A warning statement is added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources

After the three-month period, the independent Internet number resources will be deregistered from the RIPE Database.

Should the Contributor not react within four weeks, the RIPE NCC will:

  • Change the mnt-by object on the relevant records to the status “deregistered maintainer”; and/or

  • Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the Internet number resources; and/or

  • Withdraw the reverse delegation; and/or

  • Contact the upstream to investigate possible hijacking of Internet number resources; and/or

  • Delete all relevant objects in the RIPE Database, including allocation/assignment and route objects

The sole purpose of these actions by the RIPE NCC is for deregistration of the Internet number resources to reflect reality. As a result, if the Internet number resources are no longer announced after one of these actions, the RIPE NCC might not perform any other actions.

Please note:

If the Contributor responds but with no intention to comply or objects at some point within the four-week period, the RIPE NCC will allow the time remaining in this four-week period for the Contributor to submit evidence that there is no reason for deregistration of the Internet number resources or to request arbitration (see RIPE NCC Conflict Arbitration Procedure Link: /about-us/legal/arbitration/ ). However, if the four-week period expires without the submission of such evidence by the Contributor or without the submission of a request for arbitration, the RIPE NCC will proceed as if the Contributor had never reacted (see relevant procedure above). The Contributor may still request arbitration according to the timeframes of the RIPE NCC Conflict Arbitration Procedure. If the Contributor requests arbitration, the RIPE NCC will change the mnt-by object on the relevant records to the status “maintainer in dispute” and a warning statement will be added to the relevant records of the RIPE Database until the communication of the arbiter's ruling.

2.3. Independent Internet number resources directly assigned by the RIPE NCC to Direct Assignment Users

The RIPE NCC will send an official notification by email to all registered contacts stating that the Independent Internet number resources will be deregistered, explaining the reasons for this deregistration and the procedure for the deregistration.

Should the Direct Assignment User respond within four weeks, the RIPE NCC will provide a timeframe of three months for the Direct Assignment User to take care of any actions necessary for the deregistration of the Internet number resources.

During the three-month period:

  • The Direct Assignment User must stop announcing the Independent Internet number resources

  • The RIPE NCC will change the mnt-by object on the Direct Assignment User's records to the status “deregistered maintainer”

  • A warning statement is added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources

After the three-month period, the Independent Internet number resources will be deregistered from the RIPE Database.

Should the Direct Assignment User not react within four weeks, the RIPE NCC will:

  • Change the mnt-by object on the Contributor's records to the status “deregistered maintainer”; and/or

  • Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the Internet number resources; and/or

  • Withdraw the reverse delegation; and/or

  • Contact the upstream to investigate possible hijacking of Internet number resources; and/or

  • Delete all relevant objects in the RIPE Database, including assignment and route objects

The sole purpose of these actions by the RIPE NCC is for deregistration of the Internet number resources to reflect reality. As a result, if the Internet number resources are no longer announced after one of these actions, the RIPE NCC might not perform any other actions.

Please note:

If the Direct Assignment User responds but with no intention to comply or objects at some point within the four-week period, the RIPE NCC will allow the time remaining in this four-week period for the Direct Assignment User to submit evidence that there is no reason for deregistration of the Internet number resources or to request arbitration (see RIPE NCC Conflict Arbitration Procedure Link: /about-us/legal/arbitration/ ). However, if the four-week period expires without the submission of such evidence by the Direct Assignment User or without the submission of a request for arbitration, the RIPE NCC will proceed as if the Direct Assignment User had never reacted (see relevant procedure above).

The Direct Assignment User may still request arbitration according to the timeframes of the RIPE NCC Conflict Arbitration procedure. If the Contributor requests arbitration, the RIPE NCC will change the mnt-by object on the relevant records to the status “maintainer in dispute” and a warning statement will be added to the relevant records of the RIPE Database until the communication of the arbiter's ruling.

NOTE: This document might change due to future policy changes. If this happens, the RIPE NCC will send a notification to the RIPE NCC Services Working Group mailing list.