You are here: Home > Publications > RIPE Document Store > Closure of LIR and Deregistration of Internet Number Resources

Changes to Closure of LIR and Deregistration of Internet Number Resources

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-517: Closure ripe-475: 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 LIR independent Internet number resources and Deregistration of the sponsoring Local Internet Number Resources Registry (LIR).
delete: <p> Section A of insert: <h3>

Abstract insert: </h3>

insert: <p>

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. insert: </p>

insert: <p>

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. insert: </p>

insert: <h3>

Table of Contents insert: </h3>

insert: <p>

insert: <a href="#10"> 1.0 Introduction insert: </a> insert: <br />
insert: <a href="#20"> 2.0 Ownership and Legal Name Changes insert: </a> insert: <br />
insert: <a href="#21"> 2.1 End User Organisation Changes Ownership insert: </a> insert: <br />
insert: <a href="#22"> 2.2 End User Organisation Changes Name insert: </a> insert: </p>

insert: <p>

insert: <a href="#30"> 3.0 Transfer of Contractual Relationship insert: </a> insert: <br />
insert: <a href="#31"> 3.1 Transfer between Sponsoring LIRs insert: </a> insert: <br />
insert: <a href="#32"> 3.2 Transfer from Sponsoring LIR to the RIPE NCC insert: </a> insert: </p>

insert: <p>

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

insert: <p>

insert: <a id="10" name="10"> insert: </a> insert: </p>

insert: <h3>

1.0 Introduction insert: </h3>

insert: <p>

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. insert: </p>

insert: <p>

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. insert: </p>

insert: <p>

The procedures listed in this document describes the valid reasons for terminating the RIPE NCC Standard Service Agreement are subject to RIPE policies. insert: </p>

insert: <p>

insert: <a id="20" name="20"> insert: </a> insert: </p>

insert: <h3>

2.0 Ownership and Legal Name Changes insert: </h3>

insert: <p>

The RIPE NCC requires Sponsoring LIRs to maintain a proper registration of End User's legal organisation changes with the RIPE NCC. insert: </p>

insert: <p>

insert: <a id="21" name="21"> insert: </a> insert: </p>

insert: <h3>

2.1 End User Organisation Changes Ownership insert: </h3>

insert: <p>

If the ownership of the organisation changes but the legal operating name is continued, the RIPE NCC does not have to be notified. insert: </p>

insert: <p>

insert: <a id="22" name="22"> insert: </a> insert: </p>

insert: <h3>

2.2 End User Organisation Changes Name insert: </h3>

insert: <p>

When an End User that leads to the closure of an LIR account, the procedure that applies in each circumstance and the consequences. delete: </p> delete: <p> Section B describes the valid reasons for deregistration of has been assigned independent Internet number resources and the procedure that applies in each circumstance. delete: </p> delete: <p> Please note that, for the purposes changes its legal operating name, the RIPE NCC must be notified. insert: </p>

insert: <p>

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. insert: </p>

insert: <p>

A copy of this document, LIRs are referred to as “Contributors”. delete: </p> delete: <h2> delete: <b> Table of Contents delete: </b> delete: </h2> delete: <p> delete: <b> A. Closure of LIR – Termination of the RIPE NCC Standard Service Agreement delete: </b> delete: </p> delete: <p> delete: <a class="anchor-link" href="#a1"> 1. Grounds for termination and procedure in each case delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#a11"> 1.1. Termination by the Contributor delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#a12"> 1.2. Termination by the RIPE NCC delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#a121"> 1.2.1. Termination with a three-month notice period delete: </a> delete: </p> delete: <p style="padding-left: 90px; "> delete: <a class="anchor-link" href="#a1211"> 1.2.1.1. Violation of RIPE Policies and RIPE NCC procedures delete: </a> delete: </p> delete: <p style="padding-left: 120px; "> delete: <a class="anchor-link" href="#a1211a"> a. Unresponsiveness delete: </a> delete: </p> delete: <p style="padding-left: 120px; "> delete: <a class="anchor-link" href="#a1211b"> b. Allocations/assignments contravening RIPE Policies delete: </a> delete: </p> delete: <p style="padding-left: 120px; "> delete: <a class="anchor-link" href="#a1211c"> c. Incorrect registration in the RIPE Database delete: </a> delete: </p> delete: <p style="padding-left: 120px; "> delete: <a class="anchor-link" href="#a1211d"> d. Non-compliance with RIPE NCC audits delete: </a> delete: </p> delete: <p style="padding-left: 120px; "> delete: <a class="anchor-link" href="#a1211e"> e. Non-compliance with an arbiter ruling delete: </a> delete: </p> delete: <p style="padding-left: 90px; "> delete: <a class="anchor-link" href="#a1212"> 1.2.1.2. Provision of untruthful information delete: </a> delete: </p> delete: <p style="padding-left: 120px; "> delete: <a class="anchor-link" href="#a1212a"> a. Falsified/incorrect information delete: </a> delete: </p> delete: <p style="padding-left: 120px; "> delete: <a class="anchor-link" href="#a1212b"> b. Fraudulent requests delete: </a> delete: </p> delete: <p style="padding-left: 90px; "> delete: <a class="anchor-link" href="#a1213"> 1.2.1.3. Other reasons delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#a122"> 1.2.2. Termination with immediate effect delete: </a> delete: </p> delete: <p style="padding-left: 90px; "> delete: <a class="anchor-link" href="#a122a"> a. Contributor files for bankruptcy, is liquidated, suspends its payments or becomes insolvent delete: </a> delete: </p> delete: <p style="padding-left: 90px; "> delete: <a class="anchor-link" href="#a122b"> b. Contributor damages the name, trademarks or intellectual property rights of the RIPE NCC delete: </a> delete: </p> delete: <p style="padding-left: 90px; "> delete: <a class="anchor-link" href="#a122c"> c. Contributor fails to submit to the RIPE NCC a valid contract, a revised extract from the Commercial of the Trade Register or equivalent register delete: </a> delete: </p> delete: <p style="padding-left: 90px; "> delete: <a class="anchor-link" href="#a122d"> d. The Contributor fails to observe any rule of applicable law delete: </a> delete: </p> delete: <p style="padding-left: 90px; "> delete: <a class="anchor-link" href="#a122e"> e. Non-payment delete: </a> delete: </p> delete: <p style="padding-left: 90px; "> delete: <a class="anchor-link" href="#a122f"> f. Termination of the Contributor's RIPE NCC member status delete: </a> delete: </p> delete: <p> delete: <a class="anchor-link" href="#a2"> 2. Consequences delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#a21"> 2.1. End of provision of RIPE NCC services delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#a211"> 2.1.1. General services delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#a212"> 2.1.2. Registration of distributed and proof of change from an authorised person must be provided to the RIPE NCC. insert: </p>

insert: <p>

insert: <a id="30" name="30"> insert: </a> insert: </p>

insert: <h3>

3.0 Transfer of Contractual Relationship insert: </h3>

insert: <p>

If the contractual agreement between the End User of independent Internet number resources delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#a213"> 2.1.3. Request and the sponsoring LIR ceases, for any reason, the contractual changes must be communicated to the RIPE NCC. insert: </p>

insert: <p>

insert: <a> insert: </a> insert: </p>

insert: <h3>

3.1 Transfer between Sponsoring LIRs insert: </h3>

insert: <p>

If the End User decides to change sponsoring LIR, this change must be communicated to the RIPE NCC. insert: </p>

insert: <p>

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. insert: </p>

insert: <p>

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. insert: </p>

insert: <p>

insert: <a id="32" name="32"> insert: </a> insert: </p>

insert: <h3>

3.2 Transfer from Sponsoring LIR to the RIPE NCC insert: </h3>

insert: <p>

If the contractual agreement between the End User of independent Internet number resources as a “sponsoring LIR” delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#a22"> 2.2. End of Contributor's RIPE NCC member status delete: </a> delete: </p> delete: <p> delete: </p> delete: <p> B. delete: <b> Deregistration of 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 End User Assignment Agreement with the RIPE NCC and paying the Administration and first Maintenance Fee. insert: </p>

insert: <p>

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. insert: </p>

insert: <p>

insert: <a id="40" name="40"> insert: </a> insert: </p>

insert: <h3>

4.0 De-registering of Independent Internet Number Resources insert: </h3>

insert: <p>

There are three possible scenarios in which the RIPE NCC will de-register independent Internet number resources. insert: </p>

insert: <p>

insert: <a id="41" name="41"> insert: </a> insert: </p>

insert: <h3>

4.1 Closure of Sponsoring LIR insert: </h3>

insert: <p>

If the sponsoring LIR is in the process of being closed, the End User that was assigned the independent Internet number resources must sign a contract with a new sponsoring LIR or with the RIPE NCC. This must take place within 90 days of the date of notification by the RIPE NCC to the contact email addresses listed in the relevant RIPE Database object. insert: </p>

insert: <p>

insert: <a id="411" name="411"> insert: </a> insert: </p>

insert: <p>

insert: <b> 4.1.1 De-registration Timeframe

delete: <a class="anchor-link" href="#b1"> 1. Reasons insert: <b> Day one: insert: </b> 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. insert: </p>

insert: <p>

insert: <b> Day thirty: insert: </b> The End User contact email addresses listed in the RIPE Database object receive an email reminder and a "Remarks" line is added to the resource RIPE Database object. insert: </p>

insert: <p>

insert: <b> Day sixty: insert: </b> 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 deregistration of IP address ranges. insert: </p>

insert: <p>

insert: <b> Day ninety: insert: </b> 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. insert: </p>

insert: <p>

insert: <a id="42" name="42"> insert: </a> insert: </p>

insert: <h3>

4.2 Violation of RIPE Policy, Law or Contract insert: </h3>

insert: <p>

The RIPE NCC will de-register the independent Internet number resources delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#b11"> 1.1. Allocations and Independent in case of a fundamental breach of contract by the End User, supported by a Dutch court order; or insert: </p>

insert: <p>

Violation of Law by the End User, supported by a Dutch court order; or violation of RIPE Policy by the End User. insert: </p>

insert: <p>

insert: <a id="421" name="421"> insert: </a> insert: </p>

insert: <p>

insert: <b> 4.2.1 De-registration Timeframe insert: </b> insert: </p>

insert: <p>

insert: <b> Day one: insert: </b> 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. insert: </p>

insert: <p>

insert: <b> Day thirty: insert: </b> 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. insert: </p>

insert: <p>

insert: <a id="43" name="43"> insert: </a> insert: </p>

insert: <h3>

4.3 Contract Expired and Not Renewed / Ceased and Not Transferred insert: </h3>

insert: <p>

If the contract between the sponsoring LIR and the End User of independent Internet number resources assigned for the Contributor's own network has expired and has not been renewed, or assigned through a “sponsoring LIR” delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#b11a"> a. Termination of the SSA delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#b11b"> b. Invalidity of original allocation/assignment criteria delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#b11c"> c. Incorrect registration of the allocation/assignment in the RIPE Database delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#b11d"> d. Falsified/incorrect information delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#b11e"> e. Fraudulent request delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#b11f"> f. Non-compliance with a RIPE NCC audit delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#b11g"> g. Court order delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#b11h"> h. Independent Internet number resources assigned through a “sponsoring LIR” without a valid contractual relationship delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#b12"> 1.2. Independent Internet number resources assigned directly by the RIPE NCC for Direct Assignment Agreement delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#b12a"> a. Termination of the RIPE NCC End User Assignment Agreement delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#b12b"> b. Unresponsive Direct Assignment User delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#b12c"> c. Invalidity of original criteria delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#b12d"> d. Incorrect registration of the assignment in the RIPE Database delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#b12e"> e. Falsified/incorrect information delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#b12f"> f. Fraudulent request delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#b12g"> g. Non-compliance with a RIPE NCC audit delete: </a> delete: </p> delete: <p style="padding-left: 60px; "> delete: <a class="anchor-link" href="#b12h"> h. Court order delete: </a> delete: </p> delete: <p> delete: <a class="anchor-link" href="#b2"> 2. Procedures for deregistration of different types of Internet number resources delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#b21"> 2.1. Allocations and Independent Internet number resources for Contributor's own network delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#b22"> 2.2. Independent Internet number resources assigned through a “sponsoring LIR” delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#b23"> 2.3. Independent Internet number resources directly assigned by the RIPE NCC to Direct Assignment Users delete: </a> delete: </p> delete: <h1> delete: <b> A. Closure of LIR - Termination of the RIPE NCC Standard Service Agreement delete: </b> delete: </h1> delete: <p> delete: </p> delete: <p> An organisation or an individual person can receive services from the RIPE NCC if they: delete: </p> delete: <ul> delete: <li> delete: <p> Agree and sign the RIPE NCC Standard Service Agreement (SSA); and delete: </p> delete: </li> delete: <li> delete: <p> Conform to the RIPE NCC Standard Terms and Conditions (STCs); and delete: </p> delete: </li> delete: <li> delete: <p> Conform to RIPE Policies. delete: </p> delete: </li> delete: </ul> delete: <p> 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. delete: </p> delete: <h3> delete: <a name="a1"> delete: </a> 1. Grounds for termination and procedure in each case delete: </h3> delete: <p> delete: <i> delete: <b> The SSA can be terminated by the Contributor (see section 1.1) or by the RIPE NCC. 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.). delete: </b> delete: </i> delete: </p> delete: <h3> delete: <a name="a11"> delete: </a> delete: <i> 1.1. Termination by the Contributor delete: </i> delete: </h3> delete: <p> 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: delete: </p> delete: <ul> delete: <li> delete: <p> The Contributor decides to close or to change their business delete: </p> delete: </li> delete: <li> delete: <p> The Contributor decides to merge with another Contributor and therefore they do not need to be Contributors themselves delete: </p> delete: </li> delete: <li> delete: <p> The Contributor decides to assign Internet number resources from another Contributor delete: </p> delete: </li> delete: </ul> delete: <p> delete: <b> Procedure delete: </b> delete: </p> delete: <p> The notice will formally request the termination of the SSA. delete: </p> delete: <p> It must be: delete: </p> delete: <ul> delete: <li> delete: <p> Dated and signed by an authorised representative of the Contributor. A registered contact cannot give notice unless the registered contact is an authorised representative. delete: </p> delete: </li> delete: <li> delete: <p> Sent to the RIPE NCC by email to < delete: <a href="mailto:lir-help@ripe.net"> ncc@ripe.net delete: </a> > or by postal mail to: RIPE NCC, Singel 258, 1016 AB Amsterdam, The Netherlands. delete: </p> delete: </li> delete: </ul> delete: <p> 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. delete: </p> delete: <p> The termination of the SSA will take place three months after the receipt of the notice by the RIPE NCC. delete: </p> delete: <p> delete: <b> Billing issues delete: </b> delete: </p> delete: <p> 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 delete: <span> delete: <a href="https://www.ripe.net/publications/docs/articles-association"> RIPE NCC Articles of Association (AoA) delete: </a> delete: </span> and the delete: <span> delete: <a href="http://www.ripe.net/lir-services/billing/procedure"> RIPE NCC Billing Procedure delete: </a> delete: </span> ). delete: </p> delete: <h2> delete: <i> delete: <a name="a12"> delete: </a> 1.2. Termination by the RIPE NCC delete: </i> delete: </h2> delete: <h3> delete: <a name="a121"> delete: </a> 1.2.1. Termination with a three-month notice period delete: </h3> delete: <p> 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: delete: </p> delete: <p> delete: <b> delete: <a name="a1211"> delete: </a> 1.2.1.1. Violation of RIPE Policies and RIPE NCC procedures delete: </b> delete: </p> delete: <p> 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: delete: </p> delete: <p> delete: <b> delete: <a name="a1211a"> delete: </a> delete: </b> delete: <b> a. Unresponsiveness delete: </b> delete: </p> delete: <ol type="a"> delete: </ol> delete: <p> The Contributor is unresponsive for a significant period of time. delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: <b> delete: <a name="a1211b"> delete: </a> b. Allocations/assignments contravening RIPE policies delete: </b> delete: </p> delete: <p> Allocations or transfers of allocations and assignments are not made and used in accordance with the RIPE community's policies. delete: </p> delete: <p> delete: <b> delete: <a name="a1211c"> delete: </a> c. Incorrect registration in the RIPE Database delete: </b> delete: </p> delete: <p> Registration data is repeatedly maintained incorrectly (allocations and assignments must be properly registered in the RIPE Database). delete: </p> delete: <p> Proper registration must be as follows: delete: </p> delete: <ul> delete: <li> delete: <p> The delete: <b> inetnum delete: </b> and the delete: <b> inet6num delete: </b> 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 delete: </p> delete: </li> delete: <li> delete: <p> The date in the first “changed:” attribute must not be earlier than the date of approval from the RIPE NCC delete: </p> delete: </li> delete: <li> delete: <p> The data must be valid and must allow the RIPE NCC to contact the natural person referenced directly in the delete: <b> inetnum delete: </b> or delete: <b> inet6num delete: </b> object(s) or via the maintainers of the delete: <b> inetnum delete: </b> or delete: <b> inet6num delete: </b> object(s) within a reasonable time without having to get information from another source delete: </p> delete: </li> delete: </ul> delete: <p> delete: <b> delete: <a name="a1211d"> delete: </a> d. Non-compliance with RIPE NCC audits delete: </b> delete: </p> delete: <p> 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 delete: <span> delete: <a href="http://www.ripe.net/ripe/docs/audit"> RIPE NCC audit activity delete: </a> delete: </span> . delete: </p> delete: <p> delete: <b> delete: <a name="a1211e"> delete: </a> e. Non-compliance with an arbiter ruling delete: </b> delete: </p> delete: <p> For more information, please see delete: <span> delete: <a href="http://www.ripe.net/ripe/docs/arbitration"> RIPE NCC Conflict Arbitration Procedure delete: </a> delete: </span> . delete: </p> delete: <p> delete: <b> Procedure delete: </b> delete: </p> delete: <p> If the RIPE NCC becomes aware of any of the aforementioned reasons for terminating the SSA, the RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Send an email to the registered contact(s) indicating: delete: </p> delete: <ul> delete: <li> delete: <p> the violation delete: </p> delete: </li> delete: <li> delete: <p> the Contributor's obligation to stop/repair the violation delete: </p> delete: </li> delete: <li> delete: <p> the termination of the SSA in three (3) months if the violation continues delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> Terminate the progress of any open requests for RIPE NCC services delete: </p> delete: </li> delete: </ul> delete: <p> 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: delete: </p> delete: <ul> delete: <li> delete: <p> The violation delete: </p> delete: </li> delete: <li> delete: <p> The Contributor's obligation to stop/repair the violation delete: </p> delete: </li> delete: <li> delete: <p> The termination of the SSA in two (2) months if the violation continues delete: </p> delete: </li> delete: </ul> delete: <p> 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: delete: </p> delete: <ul> delete: <li> delete: <p> The violation delete: </p> delete: </li> delete: <li> delete: <p> The Contributor's obligation to stop/repair the violation delete: </p> delete: </li> delete: <li> delete: <p> The termination of the SSA in one (1) month if the violation continues delete: </p> delete: </li> delete: </ul> delete: <p> 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. delete: </p> delete: <p> delete: <b> delete: <a name="a1212"> delete: </a> 1.2.1.2 Provision of untruthful information delete: </b> delete: </p> delete: <p> 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: delete: </p> delete: <p> delete: <b> delete: <a name="a1212a"> delete: </a> a. Falsified/incorrect information delete: </b> delete: </p> delete: <p> 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.) delete: </p> delete: <p> delete: <b> delete: <a name="a1212b"> delete: </a> b. Fraudulent requests delete: </b> delete: </p> delete: <p> If the Contributor submits repeatedly fraudulent requests for Internet number resources (for example, providing incorrect purpose/need or falsified information about the network, etc.) delete: </p> delete: <p> delete: <b> Procedure delete: </b> delete: </p> delete: <p> If the RIPE NCC becomes aware of any of the aforementioned reasons for delete: </p> delete: <p> terminating the SSA, the RIPE NCC will send an email to the registered contact(s) indicating: delete: </p> delete: <ul> delete: <li> The Contributor's obligation to provide correct and true information delete: </li> delete: <li> The termination of the SSA if the Contributor does not comply with this obligation delete: </li> delete: </ul> delete: <p> 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: delete: </p> delete: <ul> delete: <li> The Contributor's obligation to provide correct and true information delete: </li> delete: <li> The termination of the SSA the next time the Contributor sends falsified/incorrect information or fraudulent requests delete: </li> delete: </ul> delete: <p> 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. delete: </p> delete: <p> delete: <b> delete: <a name="a1213"> delete: </a> 1.2.1.3 Other reasons delete: </b> delete: </p> delete: <p> Termination has ceased for any other 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. delete: </p> delete: <p> For example, such termination reason, the End User 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. delete: </p> delete: <p> delete: <b> Procedure delete: </b> delete: </p> delete: <p> 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. delete: </p> delete: <p> Unless otherwise required by the circumstances: delete: </p> delete: <ul> delete: <li> delete: <p> The RIPE NCC will terminate the progress of any open requests for RIPE NCC services delete: </p> delete: </li> delete: <li> delete: <p> Section A.2. (Consequences of termination of the SSA) and section B (Deregistration of Internet number resources) of this document are applicable delete: </p> delete: </li> delete: </ul> delete: <p> The notice will be dated and signed by an authorised representative of the RIPE NCC. delete: </p> delete: <p> Notice will be sent to the registered contact(s) of the Contributor by electronic and postal mail. delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: <b> Billing issues delete: </b> delete: </p> delete: <p> All outstanding amounts for the full year must be settled unless otherwise agreed. delete: </p> delete: <h3> delete: <a name="a122"> delete: </a> 1.2.2. Termination with immediate effect delete: </h3> delete: <p> According to Article 8.2 of the STCs, the RIPE NCC is entitled to terminate the SSA with immediate effect in the following cases: delete: </p> delete: <p> delete: <b> delete: <a name="a122a"> delete: </a> a. Contributor files for bankruptcy, is liquidated, suspends its payments or becomes insolvent delete: </b> delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: <b> Procedure delete: </b> delete: </p> delete: <p> The RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Send an email to the registered contact(s) and/or to the legal successor indicating: delete: </p> delete: </li> delete: </ul> delete: <ul> delete: <ul> delete: <li> delete: <p> The reason for termination of the SSA delete: </p> delete: </li> delete: <li> delete: <p> The immediate termination of the SSA delete: </p> delete: </li> delete: </ul> delete: </ul> delete: <ul> delete: <li> delete: <p> Terminate the progress of any open requests for RIPE NCC services delete: </p> delete: </li> delete: </ul> delete: <p> 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. delete: </p> delete: <p> delete: <b> delete: <a name="a122b"> delete: </a> b. Contributor damages the name, trademarks or intellectual property rights of the RIPE NCC delete: </b> delete: </p> delete: <p> Examples: delete: </p> delete: <ul> delete: <li> delete: <p> The Contributor pretends to be, or to act on behalf of, the RIPE NCC through misuse of the RIPE NCC name or logo delete: </p> delete: </li> delete: <li> delete: <p> 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 delete: </p> delete: </li> delete: </ul> delete: <p> delete: <b> Procedure: delete: </b> delete: </p> delete: <p> The RIPE NCC will delete: </p> delete: <ul> delete: <li> delete: <p> Send an email to the registered contact(s) indicating: delete: </p> delete: <ul> delete: <li> delete: <p> the violation delete: </p> delete: </li> delete: <li> delete: <p> the Contributor's obligation to stop/repair the violation delete: </p> delete: </li> delete: <li> delete: <p> the termination of the SSA if the violation continues delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> Terminate the progress of any open requests for RIPE NCC services delete: </p> delete: </li> delete: </ul> delete: <p> 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. delete: </p> delete: <p> After 60 days from the date of the first email, if the Contributor still does not comply, the RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Send a second reminder email to the registered contact(s) indicating the same as above delete: </p> delete: </li> delete: <li> delete: <p> Not approve any Internet number resource requests delete: </p> delete: </li> delete: </ul> delete: <p> After a maximum of 90 days from the date of the first email, if the Contributor continues not to comply, the RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Send a third reminder email and a reminder by postal mail to the registered email and postal addresses indicating the same as above delete: </p> delete: </li> delete: <li> delete: <p> Stop providing any services to the Contributor delete: </p> delete: </li> delete: </ul> delete: <p> 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. delete: </p> delete: <p> delete: <b> delete: <a name="a122c"> delete: </a> c. Contributor fails to submit to the RIPE NCC a valid extract from the Commercial Trade Register to sign a contract either with a new sponsoring LIR or equivalent register delete: </b> delete: </p> delete: <p> 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). delete: </p> delete: <p> 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). delete: </p> delete: <p> If the Contributor is a legal person, identification papers are also required RIPE NCC. insert: </p>

insert: <p>

The timeframe for the authorised person signing the SSA on behalf of the legal person. delete: </p> delete: <p> 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. delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: <b> Procedure delete: </b> delete: </p> delete: <p> The RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Send an email to the registered contact(s) indicating: delete: </p> delete: <ul> delete: <li> delete: <p> the Contributor's obligation to submit the relevant documents delete: </p> delete: </li> delete: <li> delete: <p> the termination of the SSA if the documents are not submitted delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> Terminate the progress of any open requests for RIPE NCC services delete: </p> delete: </li> delete: </ul> delete: <p> 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. delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: <b> delete: <a name="a122d"> delete: </a> d. The Contributor fails to observe any rule of applicable law delete: </b> delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: <b> Procedure delete: </b> delete: </p> delete: <p> The RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Send an email to the registered contact(s) indicating: delete: </p> delete: </li> delete: </ul> delete: <ul> delete: <ul> delete: <li> delete: <p> The reason for termination of the SSA delete: </p> delete: </li> delete: <li> delete: <p> The immediate termination of the SSA delete: </p> delete: </li> delete: </ul> delete: </ul> delete: <ul> delete: <li> delete: <p> Terminate the progress of any open requests for RIPE NCC services delete: </p> delete: </li> delete: </ul> delete: <p> 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. delete: </p> delete: <p> delete: <b> delete: <a name="a122e"> delete: </a> e. Non-payment delete: </b> . delete: </p> delete: <p> 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 delete: <span> delete: <a href="http://www.ripe.net/lir-services/billing/procedure"> RIPE NCC Billing Procedure delete: </a> delete: </span> . delete: </p> delete: <p> delete: <b> delete: <a name="a122f"> delete: </a> f. Termination of the Contributor's member status delete: </b> delete: </p> delete: <p> 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. delete: </p> delete: <p> 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). delete: </p> delete: <p> delete: <b> Procedure delete: </b> delete: </p> delete: <p> The RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Send an email to the registered contact(s) indicating: delete: </p> delete: </li> delete: </ul> delete: <ul> delete: <ul> delete: <li> delete: <p> The reason for termination of the SSA delete: </p> delete: </li> delete: <li> delete: <p> The immediate termination of the SSA delete: </p> delete: </li> delete: </ul> delete: </ul> delete: <ul> delete: <li> delete: <p> Terminate the progress of any open requests for RIPE NCC services delete: </p> delete: </li> delete: </ul> delete: <p> 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. delete: </p> delete: <h2> delete: <a name="a2"> delete: </a> 2. Consequences delete: </h2> delete: <p> Upon termination of the SSA, Contributors lose all rights to RIPE NCC services and their RIPE NCC member status. delete: </p> delete: <h3> delete: <i> delete: <a name="a21"> delete: </a> 2.1. End of provision of RIPE NCC services delete: </i> delete: </h3> delete: <h3> delete: <a name="a211"> delete: </a> delete: <b> 2.1.1. General services delete: </b> delete: </h3> delete: <p> The RIPE NCC will stop providing RIPE NCC services, including: delete: </p> delete: <ul> delete: <li> delete: <p> Distribution of Internet number resources delete: </p> delete: </li> delete: <li> delete: <p> Authority to maintain Internet number resource records in the RIPE Database delete: </p> delete: </li> delete: <li> delete: <p> Access to the LIR Portal delete: </p> delete: </li> delete: <li> delete: <p> Use of the RIPE NCC Certification Service delete: </p> delete: </li> delete: <li> delete: <p> Participation in RIPE NCC Training Courses delete: </p> delete: </li> delete: </ul> delete: <h3> delete: <i> delete: <a name="a212"> delete: </a> 2.1.2. Registration of distributed Internet number resources delete: </i> delete: </h3> delete: <p> The RIPE NCC will deregister the relevant Internet number resource records. The procedure for deregistration is described in section B.2. The RIPE NCC will also revoke any certificates generated by the RIPE NCC Certification Service. delete: </p> delete: <h3> delete: <i> delete: <a name="a213"> delete: </a> 2.1.3. Request for independent Internet number resources as a “sponsoring LIR” delete: </i> delete: </h3> delete: <p> 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. delete: </p> delete: <h2> delete: <b> delete: <a name="a22"> delete: </a> 2.2. End of Contributor's RIPE NCC member status delete: </b> delete: </h2> delete: <p> 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. delete: </p> delete: <p> delete: </p> delete: <h1> delete: <b> B. Deregistration of Internet Number Resources delete: </b> delete: </h1> delete: <p> delete: <b> delete: <br /> delete: </b> delete: </p> delete: <h3> delete: <a name="b1"> delete: </a> 1. Reasons for deregistration of Internet number resources delete: </h3> delete: <h3> delete: <a name="b11"> delete: </a> delete: <i> 1.1 Allocations and Independent Internet number resources assigned for the Contributor's own network or assigned through a “sponsoring LIR” delete: </i> delete: </h3> delete: <p> delete: <b> delete: <a name="b11a"> delete: </a> a. Termination of the SSA delete: </b> delete: </p> delete: <p> For more information, see section A. For Independent Internet number resources through a “sponsoring LIR”, see delete: <span> delete: <a href="http://www.ripe.net/ripe/docs/lir-end-user-contractual-changes"> Independent Internet Number Resources – Contractual Relationship Changes between sponsoring LIR and End User delete: </a> delete: </span> . delete: </p> delete: <p> delete: </p> delete: <p> delete: <b> delete: <a name="b11b"> delete: </a> b. Invalidity of original allocation/assignment criteria delete: </b> delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: <b> delete: <a name="b11c"> delete: </a> c.Incorrect registration of the allocation/assignment in the RIPE Database delete: </b> delete: </p> delete: <p> 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. delete: </p> delete: <p> Proper registration must be as follows: delete: </p> delete: <ul> delete: <li> delete: <p> The delete: <b> inetnum delete: </b> and the delete: <b> inet6num delete: </b> 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 delete: </p> delete: </li> delete: <li> delete: <p> The date in the first “changed:” attribute must not be earlier than the date of approval from the RIPE NCC delete: </p> delete: </li> delete: <li> delete: <p> The data must be valid and must allow the RIPE NCC to contact the natural person mentioned directly in the delete: <b> inetnum delete: </b> or delete: <b> inet6num delete: </b> object(s) or via the maintainers of the delete: <b> inetnum delete: </b> or delete: <b> inet6num delete: </b> object(s) object within a reasonable time without having to get information from another source delete: </p> delete: </li> delete: </ul> delete: <p> delete: <b> delete: <a name="b11d"> delete: </a> d. Falsified/incorrect information delete: </b> delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: <b> delete: <a name="b11e"> delete: </a> e. Fraudulent request delete: </b> delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: <b> delete: <a name="b11f"> delete: </a> f. Non-compliance with a RIPE NCC audit delete: </b> delete: </p> delete: <p> 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 delete: <span> delete: <a href="http://www.ripe.net/ripe/docs/audit"> RIPE NCC Audit Activity delete: </a> delete: </span> . delete: </p> delete: <p> delete: <b> delete: <a name="b11g"> delete: </a> g. Court order delete: </b> delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: <b> delete: <a name="b11h"> delete: </a> h. Independent Internet number resources assigned through a “sponsoring LIR” without an valid contractual relationship delete: </b> delete: </p> delete: <p> See delete: <span> delete: <a href="http://www.ripe.net/ripe/docs/lir-end-user-contractual-changes"> Independent Internet Number Resources – Contractual Relationship Changes between sponsoring LIR and End User delete: </a> delete: </span> . delete: </p> delete: <h2> delete: <i> delete: <a name="b12"> delete: </a> 1.2 Independent Internet number resources directly assigned by the RIPE NCC for Direct Assignment Users delete: </i> delete: </h2> delete: <p> delete: <b> delete: <a name="b12a"> delete: </a> a. Termination of the RIPE NCC End User Assignment Agreement delete: </b> delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: <b> delete: <a name="b12b"> delete: </a> b. Unresponsive Direct Assignment User delete: </b> delete: </p> delete: <p> 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 delete: <span> delete: <a href="http://www.ripe.net/ripe/docs/contract-req"> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region delete: </a> delete: </span> ). delete: </p> delete: <p> delete: <b> delete: <a name="b12c"> delete: </a> c. Invalidity of original criteria delete: </b> delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: <b> delete: <a name="b12d"> delete: </a> d. Incorrect registration of the assignment in the RIPE Database delete: </b> delete: </p> delete: <p> 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. delete: </p> delete: <p> Proper registration must be as follows: delete: </p> delete: <ul> delete: <li> delete: <p> The delete: <b> inetnum delete: </b> and the delete: <b> inet6num delete: </b> 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 delete: </p> delete: </li> delete: <li> delete: <p> The date in the first “changed:” attribute must not be earlier than the date of approval from the RIPE NCC delete: </p> delete: </li> delete: <li> delete: <p> The data must be valid and must allow the RIPE NCC to contact the natural person referenced directly in the delete: <b> inetnum delete: </b> or delete: <b> inet6num delete: </b> object(s) or via the maintainers of the delete: <b> inetnum delete: </b> or delete: <b> inet6num delete: </b> object(s) within a reasonable time without having to get information from another source delete: </p> delete: </li> delete: </ul> delete: <p> delete: <b> delete: <a name="b12e"> delete: </a> e. Falsified/ incorrect information delete: </b> delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: <b> delete: <a name="b12f"> delete: </a> f. Fraudulent request delete: </b> delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: <b> delete: <a name="b12g"> delete: </a> g. Non-compliance with a RIPE NCC audit delete: </b> delete: </p> delete: <p> 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 delete: <span> delete: <a href="http://www.ripe.net/ripe/docs/audit"> RIPE NCC Audit Activity delete: </a> delete: </span> . delete: </p> delete: <p> delete: <b> delete: <a name="b12h"> delete: </a> h. Court order delete: </b> delete: </p> delete: <p> 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. delete: </p> delete: <h3> delete: <a name="b2"> delete: </a> 2. Procedures for deregistration of different types of Internet number resources delete: </h3> delete: <h3> delete: <i> delete: <a name="b21"> delete: </a> 2.1 Allocations and independent Internet number resources for Contributor's own network delete: </i> delete: </h3> delete: <p> 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. delete: </p> delete: <p> 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: delete: </p> delete: <p> delete: <span> delete: <a href="https://www.ripe.net/membership/indices/index.html"> https://www.ripe.net/membership/indices/index.html delete: </a> delete: </span> delete: </p> delete: <p> During the three-month period: delete: </p> delete: <ul> delete: <li> delete: <p> The Contributor must stop announcing the allocation/independent Internet number resources delete: </p> delete: </li> delete: <li> delete: <p> The RIPE NCC will change the delete: <b> mnt-by delete: </b> object on the Contributor's records to the status “deregistered maintainer” delete: </p> delete: </li> delete: <li> delete: <p> A warning statement is added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources delete: </p> delete: </li> delete: <li> delete: <p> The RIPE NCC will revoke any certificates generated by the RIPE NCC Certification Service delete: </p> delete: </li> delete: </ul> delete: <p> After the three-month period, the allocation/assignment will be deregistered from the RIPE Database. delete: </p> delete: <p> Should the Contributor not react within four weeks, the RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Change the delete: <b> mnt-by delete: </b> object on the Contributor's records to the status “deregistered maintainer”; and/or delete: </p> delete: </li> delete: <li> delete: <p> Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the Internet number resources; and/or delete: </p> delete: </li> delete: <li> delete: <p> Withdraw the reverse delegation; and/or delete: </p> delete: </li> delete: <li> delete: <p> Contact the upstream to investigate possible hijacking of Internet number resources; and/or delete: </p> delete: </li> delete: <li> delete: <p> Delete all relevant objects in the RIPE Database, including allocation/assignment and delete: <b> route delete: </b> objects delete: </p> delete: </li> delete: <li> delete: <p> Revoke any certificates generated by the RIPE NCC Certification Service. delete: </p> delete: </li> delete: </ul> delete: <p> 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. delete: </p> delete: <p> Please note: delete: </p> delete: <p> 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 delete: <span> delete: <a data-val="b81490fe2c00243a37cb5c5ffaab8f6e" href="./resolveuid/b81490fe2c00243a37cb5c5ffaab8f6e" data-linktype="internal"> RIPE NCC Conflict Arbitration Procedure delete: </a> delete: </span> ). 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 delete: <b> mnt-by delete: </b> 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. delete: </p> delete: <h3> delete: <a name="b22"> delete: </a> delete: <i> 2.2 Independent Internet number resources assigned through a “sponsoring LIR” delete: </i> delete: </h3> delete: <p> 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. delete: </p> delete: <p> During this period: delete: </p> delete: <ul> delete: <li> delete: <p> The End User must stop announcing the Independent Internet number resources delete: </p> delete: </li> delete: <li> delete: <p> The RIPE NCC will change the delete: <b> mnt-by delete: </b> object on the relevant records to the status “deregistered maintainer” delete: </p> delete: </li> delete: <li> delete: <p> A warning statement is added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources delete: </p> delete: </li> delete: </ul> delete: <p> After the three-month period, the independent Internet number resources will be deregistered from the RIPE Database. delete: </p> delete: <p> Should the Contributor not react within four weeks, the RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Change the delete: <b> mnt-by delete: </b> object on the relevant records to the status “deregistered maintainer”; and/or delete: </p> delete: </li> delete: <li> delete: <p> Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the Internet number resources; and/or delete: </p> delete: </li> delete: <li> delete: <p> Withdraw the reverse delegation; and/or delete: </p> delete: </li> delete: <li> delete: <p> Contact the upstream to investigate possible hijacking of Internet number resources; and/or delete: </p> delete: </li> delete: <li> delete: <p> Delete all relevant objects in the RIPE Database, including allocation/assignment and delete: <b> route delete: </b> objects delete: </p> delete: </li> delete: </ul> delete: <p> 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. delete: </p> delete: <p> Please note: delete: </p> delete: <p> 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 delete: <span> delete: <a data-val="b81490fe2c00243a37cb5c5ffaab8f6e" href="./resolveuid/b81490fe2c00243a37cb5c5ffaab8f6e" data-linktype="internal" class="external-link"> RIPE NCC Conflict Arbitration Procedure delete: </a> delete: </span> ). 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 delete: <b> mnt-by delete: </b> 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. delete: </p> delete: <h3> delete: <b> delete: <a name="b23"> delete: </a> 2.3. Independent Internet number resources directly assigned by the RIPE NCC to Direct Assignment Users delete: </b> delete: </h3> delete: <p> 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. delete: </p> delete: <p> 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. delete: </p> delete: <p> During the three-month period: delete: </p> delete: <ul> delete: <li> delete: <p> The Direct Assignment User must stop announcing the Independent Internet number resources delete: </p> delete: </li> delete: <li> delete: <p> The RIPE NCC will change the delete: <b> mnt-by delete: </b> object on the Direct Assignment User's records to the status “deregistered maintainer” delete: </p> delete: </li> delete: <li> delete: <p> A warning statement is added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources delete: </p> delete: </li> delete: </ul> delete: <p> After the three-month period, the Independent Internet number resources will be deregistered from the RIPE Database. delete: </p> delete: <p> Should the Direct Assignment User not react within four weeks, the RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Change the delete: <b> mnt-by delete: </b> object on the Contributor's records to the status “deregistered maintainer”; and/or delete: </p> delete: </li> delete: <li> delete: <p> Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the Internet number resources; and/or delete: </p> delete: </li> delete: <li> delete: <p> Withdraw the reverse delegation; and/or delete: </p> delete: </li> delete: <li> delete: <p> Contact the upstream to investigate possible hijacking of Internet number resources; and/or delete: </p> delete: </li> delete: <li> delete: <p> Delete all relevant objects in the RIPE Database, including assignment and delete: <b> route delete: </b> objects delete: </p> delete: </li> delete: </ul> delete: <p> 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. delete: </p> delete: <p> Please note: delete: </p> delete: <p> 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 delete: <span> delete: <a data-val="b81490fe2c00243a37cb5c5ffaab8f6e" href="./resolveuid/b81490fe2c00243a37cb5c5ffaab8f6e" data-linktype="internal" class="external-link"> RIPE NCC Conflict Arbitration Procedure delete: </a> delete: </span> ). 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). delete: </p> delete: <p> 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 delete: <b> mnt-by delete: </b> 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. delete: </p> delete: <p> delete: </p> delete: <p> delete: </p> delete: <p> delete: <span class="discreet"> 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. delete: </span> delete: </p> Section 4.1.1 - De-registration Timeframe. insert: </p>

Closure of LIR and Deregistration of Independent Internet Number Resources - Contractual Relationship Changes between Sponsoring LIR and End User
RIPE Documents Search