You are here: Home > Publications > RIPE Document Store > Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources

Changes to Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-697: 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 Members, Deregistration of independent Internet Resources number resources and Legacy the sponsoring Local Internet 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 (SSA) 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 a Member, the procedure that applies in each circumstance, and the consequences of termination. 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> Section C describes the valid reasons for terminating a Legacy Services Agreement, the procedure that applies in each circumstance, and the consequences and procedures that apply if the Legacy Internet Resource Holder wants to change the status of their Legacy Internet Resources or have them deregistered. delete: </p> delete: <p>   delete: </p> delete: <h2> Table of Contents delete: </h2> delete: <div class="page" title="Page 1"> delete: <div class="layoutArea"> delete: <div class="column"> delete: <p class="western"> delete: <a href="#a"> A. Closure of Member – Termination of the RIPE NCC Standard Service Agreement delete: </a> delete: </p> delete: <p class="western"> delete: <a href="#a1"> 1. Grounds for Termination, and the Procedure in Each Case delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px;"> delete: <a href="#a11"> 1.1. Termination by the Member delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px;"> delete: <a href="#a12"> 1.2. Termination by the RIPE NCC delete: </a> delete: </p> delete: <p class="western" style="padding-left: 60px;"> delete: <a href="#a121"> 1.2.1. Termination with a Three-Month Notice Period delete: </a> delete: </p> delete: <p class="western" style="padding-left: 90px;"> delete: <a href="#a1211"> 1.2.1.1. Violation of RIPE Policies and RIPE NCC Procedures delete: </a> delete: </p> delete: <p class="western" style="padding-left: 120px;"> delete: <a href="#a1211a"> a. Unresponsiveness delete: </a> delete: </p> delete: <p class="western" style="padding-left: 120px;"> delete: <a href="#a1211b"> b. Allocations/assignments in contravention of RIPE Policies delete: </a> delete: </p> delete: <p class="western" style="padding-left: 120px;"> delete: <a href="#a1211c"> c. Incorrect registration in the RIPE Database delete: </a> delete: </p> delete: <p class="western" style="padding-left: 120px;"> delete: <a href="#a1211d"> d. Non-compliance with an arbiter ruling delete: </a> delete: </p> delete: <p class="western" style="padding-left: 90px;"> delete: <a class="anchor-link" href="#a1212"> 1.2.1.2 Other Reasons delete: </a> delete: </p> delete: <p class="western" style="padding-left: 60px;"> delete: <a href="#a122"> 1.2.2. Termination with Immediate Effect delete: </a> delete: </p> delete: <p class="western" style="padding-left: 90px;"> delete: <a href="#a122a"> a. The Member files for bankruptcy, is liquidated, suspends changes its payments or becomes insolvent delete: </a> delete: </p> delete: <p class="western" style="padding-left: 90px;"> delete: <a href="#a122b"> b. The Member damages the legal operating name, trademarks or intellectual property 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 of the RIPE NCC delete: </a> delete: </p> delete: <p class="western" style="padding-left: 90px;"> delete: <a href="#a122c"> c. The Member fails to submit to the RIPE NCC a valid and obligations. insert: </p>

insert: <p>

A copy of this contract, a revised extract from the Commercial of the Trade Register 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 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 equivalent register delete: </a> delete: </p> delete: <p class="western" style="padding-left: 90px;"> delete: <a href="#a122d"> d. The Member fails to observe any rule of applicable law delete: </a> delete: </p> delete: <p class="western" style="padding-left: 90px;"> delete: <a href="#a122e"> e. Non-payment delete: </a> delete: </p> delete: <p class="western" style="padding-left: 90px;"> delete: <a href="#a122f"> f. Termination of RIPE NCC member status delete: </a> delete: </p> delete: <p class="western" style="padding-left: 90px;"> delete: <a href="#a122g"> g. Untruthful information delete: </a> delete: </p> delete: <p class="western" style="padding-left: 90px;"> delete: <a href="#a122h"> h. Non-compliance the new sponsoring LIR. The RIPE NCC will need confirmation from both LIRs before it can proceed with RIPE NCC audits delete: </a> delete: </p> delete: <p class="western" style="padding-left: 90px;"> delete: <a href="#a122i"> i. Discontinuation of RIPE NCC services delete: </a> delete: </p> delete: <p class="western"> delete: <a href="#a2"> 2. Consequences delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px;"> delete: <a href="#a21"> 2.1. End of Provision of RIPE NCC Services delete: </a> delete: </p> delete: <p class="western" style="padding-left: 60px;"> delete: <a href="#a211"> 2.1.1. General Services delete: </a> delete: </p> delete: <p class="western" style="padding-left: 60px;"> delete: <a href="#a212"> 2.1.2. Registration of Distributed 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 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 delete: </a> delete: </p> delete: <p class="western" style="padding-left: 60px;"> delete: <a href="#a213"> 2.1.3. Request for Independent Internet Number Resources as a “Sponsoring LIR” delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px;"> delete: <a href="#a22"> 2.2. End of RIPE NCC Member Status delete: </a> delete: </p> delete: <p class="western">   delete: </p> delete: <p class="western"> delete: <a href="#b"> B. Deregistration of Internet Number Resources delete: </a> delete: </p> delete: <p class="western"> delete: <a href="#b1"> 1. Reasons for Deregistration of Internet Number Resources - Allocations and Independent Internet Number Resources Assigned for the Member's Own Network or Assigned Through a “Sponsoring LIR” delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px;"> delete: <a href="#b1a"> a. Termination of the SSA delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px;"> delete: <a href="#b1b"> b. Invalidity of original allocation/assignment criteria delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px;"> delete: <a href="#b1c"> c. Incorrect registration of the allocation/assignment in the RIPE Database delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px;"> delete: <a href="#b1d"> d. Falsified/incorrect information delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px;"> delete: <a href="#b1e"> e. Fraudulent request delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px;"> delete: <a href="#b1f"> f. Non-compliance with a RIPE NCC audit delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px;"> delete: <a href="#b1g"> g. Court order delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px;"> delete: <a href="#b1h"> h. Independent 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 assigned through a “sponsoring LIR” without a valid contractual relationship delete: </a> delete: </p> delete: <p class="western"> delete: <a href="#b2"> 2. Procedures 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 insert: </b> insert: </p>

insert: <p>

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 Different Types of Internet Number Resources delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px;"> delete: <a href="#b21"> 2.1. Allocations and Independent Internet Number Resources 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 Member's Own Network delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px;"> delete: <a href="#b22"> 2.2. Independent Internet Number Resources Assigned Through a “Sponsoring LIR” delete: </a> delete: </p> delete: <p class="western">   delete: </p> delete: <p> delete: <a class="anchor-link" href="#c"> C. Legacy Internet Resources delete: </a> delete: </p> delete: <p> delete: <a href="#c1"> 1. Termination of the Legacy Services delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> delete: <a href="#c11"> 1.1 Legacy Services by the RIPE NCC to a Member Pursuant to the Terms and Conditions Regarding Legacy Internet Resources for Members delete: </a> delete: </p> delete: <p style="padding-left: 60px;"> delete: <a href="#c111"> 1.1.1. Termination by the Member delete: </a> delete: </p> delete: <p style="padding-left: 60px;"> delete: <a href="#c112"> 1.1.2. Termination by the RIPE NCC delete: </a> delete: </p> delete: <p style="padding-left: 90px;"> delete: <a href="#c1121"> 1.1.2.1. Non compliance with contractual responsibilities delete: </a> delete: </p> delete: <p style="padding-left: 90px;"> delete: <a href="#c1122"> 1.1.2.2. Termination with immediate effect delete: </a> delete: </p> delete: <p style="padding-left: 120px;"> delete: <a href="#c1122a"> a. The Member's SSA is terminated for any reason delete: </a> delete: </p> delete: <p style="padding-left: 120px;"> delete: <a href="#c1122b"> b. The Member transfers the Legacy Internet Resources to a third party delete: </a> delete: </p> delete: <p style="padding-left: 120px;"> delete: <a href="#c1122c"> c. The member has no rights to use the Legacy Internet Resources delete: </a> delete: </p> delete: <p style="padding-left: 120px;"> delete: <a href="#c1122d"> d. Reasons beyond control of the RIPE NCC delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> delete: <a href="#c12"> 1.2 Legacy Agreement Between the RIPE NCC and a Legacy Internet Resource Holder delete: </a> delete: </p> delete: <p style="padding-left: 60px;"> delete: <a href="#c121"> 1.2.1. Termination by the Legacy Internet Resource Holder delete: </a> delete: </p> delete: <p style="padding-left: 60px;"> delete: <a href="#c122"> 1.2.2. Termination by the RIPE NCC delete: </a> delete: </p> delete: <p style="padding-left: 90px;"> delete: <a href="#c1221"> 1.2.2.1. Non-compliance with Contractual Responsibilities delete: </a> delete: </p> delete: <p style="padding-left: 90px;"> delete: <a href="#c1222"> 1.2.2.2. Termination with Immediate Effect delete: </a> delete: </p> delete: <p style="padding-left: 120px;"> delete: <a href="#c1222a"> a. The Legacy Internet Resource Holder files for bankruptcy, is liquidated, suspends their payments 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 becomes insolvent delete: </a> delete: </p> delete: <p style="padding-left: 120px;"> delete: <a href="#c1222b"> b. The Legacy Internet Resource Holder damages the name, trademarks or intellectual property rights of the RIPE NCC delete: </a> delete: </p> delete: <p style="padding-left: 120px;"> delete: <a href="#c1222c"> c. The Legacy Internet Resource Holder fails to submit to the RIPE NCC a valid extract from the Commercial Trade Register or equivalent register delete: </a> delete: </p> delete: <p style="padding-left: 120px;"> delete: <a href="#c1222d"> d. The Legacy Internet Resource Holder fails to observe any rule of applicable law delete: </a> delete: </p> delete: <p style="padding-left: 120px;"> delete: <a href="#c1222e"> e. Non-payment delete: </a> delete: </p> delete: <p style="padding-left: 120px;"> delete: <a href="#c1222f"> f. Untruthful information delete: </a> delete: </p> delete: <p style="padding-left: 120px;"> delete: <a href="#c1222g"> g. Non-compliance with RIPE NCC audits delete: </a> delete: </p> delete: <p style="padding-left: 120px;"> delete: <a href="#c1222h"> h. Reasons beyond control of the RIPE NCC delete: </a> delete: </p> delete: <p style="padding-left: 120px;"> delete: <a href="#c1222i"> i. The Legacy Internet Resource Holder transfers the Legacy Internet Resources to a third party delete: </a> delete: </p> delete: <p style="padding-left: 120px;"> delete: <a href="#c1222j"> j. The Legacy Internet Resource Holder has no rights to use the Legacy Internet Resources delete: </a> delete: </p> delete: <p> delete: <a href="#c2"> 2. Consequences delete: </a> delete: </p> delete: <p> delete: <a href="#c3"> 3. Change of Status of Legacy Internet Resources delete: </a> delete: </p> delete: <p> delete: <a href="#c4"> 4. Deregistration of Legacy Internet Resources delete: </a> delete: </p> delete: </div> delete: </div> delete: </div> delete: <p>   delete: </p> delete: <p> delete: <a name="a"> delete: </a> delete: </p> delete: <h2> A. Closure of Member - Termination of the RIPE NCC Standard Service Agreement delete: </h2> 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 RIPE Policies. delete: </p> delete: </li> delete: </ul> delete: <p> An organisation or an individual person signing the SSA is called a “Member”. 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> delete: <strong> 1. Grounds for Termination and Procedure in Each Case delete: </strong> Contract

The SSA can be terminated by the Member (see section 1.1) or by the RIPE NCC. Termination by the RIPE NCC can either occur with a three-month notice period (see section 1.2.1.) or, due to specific reasons, with immediate effect (see section 1.2.2.). delete: </p> delete: <h4> delete: <a name="a11"> delete: </a> delete: <strong> 1.1. Termination by the Member delete: </strong> delete: </h4> delete: <p> According to Article 9.2 of the SSA, the Member can terminate the SSA with a notice period of three months. Possible reasons why Members might want to terminate their SSA include: delete: </p> delete: <ul> delete: <li> delete: <p> The Member decides to close or to change their business delete: </p> delete: </li> delete: <li> delete: <p> The Member decides to merge with another Member and therefore does not need to be a Member themselves delete: </p> delete: </li> delete: <li> delete: <p> The Member decides to assign 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 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 another Member delete: </p> delete: </li> delete: </ul> delete: <p> delete: <strong> Procedure delete: </strong> delete: </p> delete: <p> The Member must formally request the termination of the SSA the RIPE NCC; the resource RIPE Database object is locked with a written notice. delete: </p> delete: <p> The notice must be: delete: </p> delete: <ul> delete: <li> delete: <p> Dated and signed by an authorised representative of the Member. A registered the RIPE NCC maintainer. insert: </p>

insert: <p>

insert: <b> Day thirty: insert: </b> The sponsoring LIR and the End User 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 at < delete: <a href="mailto:ncc@ripe.net" data-linktype="email" data-val="ncc@ripe.net"> ncc@ripe.net delete: </a> > or by postal mail to: RIPE NCC, Stationsplein 11, 1012 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 and the Member 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 suspended 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: <strong> Billing Issues delete: </strong> delete: </p> delete: <p> Regardless of when the termination takes place in the course of the financial year, the annual contribution shall nevertheless remain due, in full, by the Member (see also paragraph 6.6 of the  delete: <a href="http://www.ripe.net/publications/docs/articles-association"> RIPE NCC Articles of Association (AoA) delete: </a>  and the  delete: <a href="http://www.ripe.net/participate/billing/procedure"> RIPE NCC Billing Procedure delete: </a> ). de-registered and put in quarantine for future re-assignment. insert: </p>

insert: <p>

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

delete: <a name="a12"> delete: </a> delete: <br /> delete: <strong> 1.2. Termination by the RIPE NCC delete: </strong> 4.3 Contract Expired and Not Renewed / Ceased and Not Transferred

delete: <h4> delete: <a name="a121"> delete: </a> delete: <strong> 1.2.1. Termination with a Three-Month Notice Period delete: </strong> delete: </h4> delete: <p> According to Article 9.3 of the SSA, 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: <h4> delete: <a name="a1211"> delete: </a> delete: <strong> 1.2.1.1 Violation of RIPE Policies and RIPE NCC Procedures delete: </strong> delete: </h4> delete: <p> The Member must comply with RIPE Policies and RIPE NCC procedures (see Article 6 of the SSA). The RIPE NCC will terminate the SSA if the Member commits any of the following violations of RIPE Policies insert: <p>

If the contract between the sponsoring LIR and the End User of independent Internet number resources has expired and has not been renewed, or RIPE NCC procedures: delete: </p> delete: <p> delete: <strong> delete: <a name="a1211a"> delete: </a> a. Unresponsiveness delete: </strong> delete: </p> delete: <p> The Member is unresponsive for a significant period of time. delete: </p> delete: <p> Members 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 continue paying the RIPE NCC fees. delete: </p> delete: <p> delete: <strong> delete: <a name="a1211b"> delete: </a> b. Allocations/assignments in contravention of RIPE Policies delete: </strong> 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: <strong> delete: <a name="a1211c"> delete: </a> c. Incorrect registration in the RIPE Database delete: </strong> 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: <strong> inetnum delete: </strong>  and the  delete: <strong> inet6num delete: </strong>  object(s) for approved assignments must use the netname(s) approved by the RIPE NCC and must 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: <strong> inetnum delete: </strong>  or  delete: <strong> inet6num delete: </strong>  object(s) or via the maintainers of the  delete: <strong> inetnum delete: </strong>  or  delete: <strong> inet6num delete: </strong>  object(s) within a reasonable time without having to get information from another source delete: </p> delete: </li> delete: </ul> delete: <p> delete: <strong> delete: <a name="a1211d"> delete: </a> d. Non-compliance with an arbiter ruling delete: </strong> delete: </p> delete: <p> For more information, please see the  delete: <a href="http://www.ripe.net/ripe/docs/arbitration"> RIPE NCC Conflict Arbitration Procedure delete: </a> . delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> delete: </p> delete: <p> 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: delete: </p> delete: <ul> delete: <li> delete: <p> The violation delete: </p> delete: </li> delete: <li> delete: <p> The Member's obligation to stop or rectify 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: <p> The RIPE NCC will also terminate the progress of any open requests for RIPE NCC services and the Member will be suspended. delete: </p> delete: <p> If the Member 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 Member's obligation to stop or rectify 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 Member 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 Member's obligation to stop or rectify 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 Member continues to not comply, the RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Member's account) to all registered postal and email addresses of the Member. delete: </p> delete: <h4> delete: <a name="a1212"> delete: </a> delete: <strong> 1.2.1.2. Other Reasons delete: </strong> delete: </h4> delete: <p> Termination has ceased for any other reason by the RIPE NCC is only executed when the Member 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 Members, the SSAs with the RIPE NCC were terminated and new contracts with AFRINIC were signed. delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> delete: </p> delete: <p> The termination 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 Member. 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 and the Member will be suspended. 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 Member 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 Member requests a longer period and this is agreed upon. delete: </p> delete: <p> delete: <strong> Billing Issues delete: </strong> delete: </p> delete: <p> All outstanding amounts for the full year must be settled unless otherwise agreed. delete: </p> delete: <h4> delete: <a name="a122"> delete: </a> delete: <strong> 1.2.2. Termination with Immediate Effect delete: </strong> delete: </h4> delete: <p> According to Article 9.4 of the SSA, the RIPE NCC is entitled to terminate the SSA with immediate effect in the following cases: delete: </p> delete: <p>   delete: </p> delete: <p> delete: <strong> delete: <a name="a122a"> delete: </a> a. The Member files for bankruptcy, is liquidated, suspends their payments or becomes insolvent delete: </strong> delete: </p> delete: <p> Upon receipt of the documents stating the bankruptcy, liquidation, suspension of payments or insolvency of the Member 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 Member's operations can continue, and provided that the Member fulfills the obligations imposed by the SSA, the RIPE NCC will not terminate the SSA. delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> 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: <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: </li> delete: <li> delete: <p> Terminate the progress of any open requests for RIPE NCC services and the Member will be suspended 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's account(s)) to all registered contacts of the Member or to the legal successor, both by electronic and registered postal mail. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <strong> delete: <a name="a122b"> delete: </a> b. The Member damages the name, trademarks or intellectual property rights of the RIPE NCC delete: </strong> delete: </p> delete: <p> Examples: delete: </p> delete: <ul> delete: <li> The Member pretends to be, or to act on behalf of, the RIPE NCC through misuse of the RIPE NCC name or logo delete: </li> delete: <li> The Member 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: </li> delete: </ul> delete: <p> delete: <strong> Procedure: delete: </strong> 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 Member's obligation to stop or rectify 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 and the Member will be suspended delete: </p> delete: </li> delete: </ul> delete: <p> If the Member 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 Member still does not comply, the RIPE NCC will: delete: </p> delete: <ul> delete: <li> Send a second reminder email to the registered contact(s) indicating the same as above delete: </li> delete: <li> Not approve any Internet number resource requests delete: </li> delete: </ul> delete: <p> After a maximum of 90 days from the date of the first email, if the Member continues to not comply, the RIPE NCC will: delete: </p> delete: <ol type="a"> delete: <li> Send a third reminder email and a reminder by postal mail to the registered email and postal addresses indicating the same as above delete: </li> delete: <li> Stop providing any services to the Member delete: </li> delete: </ol> delete: <p> After 120 days from the date of the first email, if the Member still does not comply, the RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Member's account) to all registered postal and email addresses of the Member. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <strong> delete: <a name="a122c"> delete: </a> c. The Member 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: </strong> delete: </p> delete: <p> When initially signing the SSA, the Member must submit to the RIPE NCC an extract from the Commercial Trade Register or equivalent document providing the registration of the Member's business with the national authorities (see Article 2.2 of the SSA). delete: </p> delete: <p> If the Member 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 Member 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 Member's business after signing the SSA (for example, the Member has merged with another company, has changed name, etc.) and, because of this change, the Member's registration with the relevant register has been changed, then the Member is obliged to submit the updated registration papers to the RIPE NCC. delete: </p> delete: <p> If the Member does not submit the aforementioned documents within one month of them being requested to do so by the RIPE NCC, the RIPE NCC will terminate the SSA (see Article 9.4.d of the SSA). delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> 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 Member'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 and the Member will be suspended delete: </p> delete: </li> delete: </ul> delete: <p> If the Member 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 Member continues to not comply, the RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Member's account) to all registered postal and email addresses of the Member. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <strong> delete: <a name="a122d"> delete: </a> d. The Member fails to observe any rule of applicable law delete: </strong> 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 Member with immediate effect, provided it receives a Dutch court order to do so. delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> 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 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: </li> delete: <li> delete: <p> Terminate the progress of any open requests for RIPE NCC services and the Member will be suspended 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's account) to all registered postal and email addresses of the Member. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <strong> delete: <a name="a122e"> delete: </a> e. Non-payment delete: </strong> delete: </p> delete: <p> In case of non-payment, in accordance with the RIPE NCC Billing Procedure, the SSA will be terminated after 120 days. For more information, please see the  delete: <a href="http://www.ripe.net/participate/billing/procedure"> RIPE NCC Billing Procedure delete: </a> . delete: </p> delete: <p>   delete: </p> delete: <p> delete: <strong> delete: <a name="a122f"> delete: </a> f. Termination of RIPE NCC member status delete: </strong> delete: </p> delete: <p> By signing the SSA, Members become members of the RIPE NCC association. If Members terminate their member status with the RIPE NCC association, the SSA is automatically terminated (see also Article 6 of the RIPE NCC Articles of Association). delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> 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 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: </li> delete: <li> delete: <p> Terminate the progress of any open requests for RIPE NCC services and the Member will be suspended 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's account) to all registered postal and email addresses of the Member. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <strong> delete: <a name="a122g"> delete: </a> g. Untruthful information delete: </strong> delete: </p> delete: <p> The RIPE NCC concludes the SSA and provides services to Members in good faith. The Member is in breach of good faith in the following cases: delete: </p> delete: <ol type="a"> delete: <ul> delete: <li> delete: <p> delete: <strong> Falsified/incorrect information delete: </strong> delete: </p> delete: </li> delete: </ul> delete: </ol> delete: <p> The Member 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: <ol type="a"> delete: <ul> delete: <li> delete: <p> delete: <strong> Fraudulent requests delete: </strong> delete: </p> delete: </li> delete: </ul> delete: </ol> delete: <p> The Member 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: <strong> Procedure delete: </strong> 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 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: </li> delete: <li> delete: <p> Terminate the progress of any open requests for RIPE NCC services and the Member will be suspended 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's account) to all registered postal and email addresses of the Member. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <strong> delete: <a name="a122h"> delete: </a> h. Non-compliance with RIPE NCC audits delete: </strong> 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 Member's own network. For more information about the audit procedure, please see the  delete: <a href="http://www.ripe.net/ripe/docs/audit"> RIPE NCC Audit Activity delete: </a> . delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> 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 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: </li> delete: <li> delete: <p> Terminate the progress of any open requests for RIPE NCC services and the Member will be suspended 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's account) to all registered postal and email addresses of the Member. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <strong> delete: <a name="a122i"> delete: </a> i. Discontinuation of RIPE NCC services delete: </strong> delete: </p> delete: <p> The RIPE NCC cannot reasonably be required to continue the SSA for reasons that can not be attributed to the RIPE NCC and for which the RIPE NCC cannot be held accountable by virtue of law, a juridical act or generally accepted principles. delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> delete: </p> delete: <p> The RIPE NCC will: delete: </p> delete: <ol type="a"> delete: <ul> delete: <li> delete: <p> Send an email to the registered contact(s) indicating: delete: </p> 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: </li> delete: <li> delete: <p> Terminate the progress of any open requests for RIPE NCC services and the Member will be suspended delete: </p> delete: </li> delete: </ul> delete: </ol> delete: <p> The RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Member's account) to all registered postal and email addresses of the Member. delete: </p> delete: <p>   delete: </p> delete: <h2> delete: <a name="a2"> delete: </a> delete: <strong> 2. Consequences delete: </strong> delete: </h2> delete: <p> Upon termination of the SSA, Members lose all rights to RIPE NCC services and their RIPE NCC member status. delete: </p> delete: <h3> delete: <a name="a21"> delete: </a> delete: <strong> 2.1. End of Provision of RIPE NCC Services delete: </strong> delete: </h3> delete: <h4> delete: <a name="a211"> delete: </a> delete: <strong> 2.1.1. General Services delete: </strong> delete: </h4> 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 Resource Certification (RPKI) service delete: </p> delete: </li> delete: <li> delete: <p> Participation in RIPE NCC training courses delete: </p> delete: </li> delete: </ul> delete: <h4> delete: <a name="a212"> delete: </a> delete: <strong> 2.1.2. Registration of Distributed Internet Number Resources delete: </strong> delete: </h4> 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: <h4> delete: <a name="a213"> delete: </a> delete: <strong> 2.1.3. Request for Independent Internet Number Resources as a “Sponsoring LIR” delete: </strong> delete: </h4> delete: <p> Members lose their right to request independent Internet number resources as a “sponsoring LIR”. For independent Internet number resources already assigned by them, see section B.2.2 below. delete: </p> delete: <h4> delete: <a name="a22"> delete: </a> delete: <strong> 2.2. End of RIPE NCC Member Status delete: </strong> delete: </h4> delete: <p> Members 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: <h2> delete: <a name="b"> delete: </a> delete: <strong> B. Deregistration of Internet Number Resources delete: </strong> delete: </h2> delete: <h3> delete: <a name="b1"> delete: </a> delete: <strong> 1. Reasons for Deregistration of Internet Number Resources Section 4.1.1 - Allocations and Independent Internet Number Resources Assigned for the Member's Own Network or Assigned Through a “Sponsoring LIR” delete: </strong> delete: </h3> delete: <p> delete: <a name="b1a"> delete: </a> delete: <strong> a. Termination of the SSA delete: </strong> delete: </p> delete: <p> For more information, see section A. For independent Internet number resources through a “sponsoring LIR”, see  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: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="b1b"> delete: </a> delete: <strong> b. Invalidity of original allocation/assignment criteria delete: </strong> 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 changes, 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: </p> delete: <p> delete: <a name="b1c"> delete: </a> delete: <strong> c. Incorrect registration of the allocation/assignment in the RIPE Database delete: </strong> 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: <ol> delete: <ul> delete: <li> The  delete: <strong> inetnum delete: </strong>  and the  delete: <strong> inet6num delete: </strong>  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: </li> delete: <li> The date in the first “changed:” attribute must not be earlier than the date of approval from the RIPE NCC delete: </li> delete: <li> The data must be valid and must allow the RIPE NCC to contact the natural person mentioned directly in the  delete: <strong> inetnum delete: </strong>  or  delete: <strong> inet6num delete: </strong>  object(s) or via the maintainers of the  delete: <strong> inetnum delete: </strong>  or  delete: <strong> inet6num delete: </strong>  object(s) object within a reasonable time without having to get information from another source delete: </li> delete: </ul> delete: </ol> delete: <div class="column">   delete: </div> delete: <div class="column"> delete: <strong> delete: <a name="b1d"> delete: </a> d. Falsified/incorrect information delete: </strong> delete: </div> delete: <p> If a Member 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: </p> delete: <p> delete: <strong> delete: <a name="b1e"> delete: </a> e. Fraudulent request delete: </strong> delete: </p> delete: <p> If a Member 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: </p> delete: <p> delete: <strong> delete: <a name="b1f"> delete: </a> f. Non-compliance with a RIPE NCC audit delete: </strong> delete: </p> delete: <p> If a Member does not comply with a RIPE NCC audit regarding the registration of an independent resource that the Member is responsible for as a “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 the  delete: <a href="http://www.ripe.net/ripe/docs/audit"> RIPE NCC Audit Activity delete: </a> . delete: </p> delete: <p>   delete: </p> delete: <p> delete: <strong> delete: <a name="g"> delete: </a> delete: <a name="b1g"> delete: </a> g. Court order delete: </strong> delete: </p> delete: <p> The RIPE NCC is an association under Dutch law. In the event that a Dutch court orders the deregistration of specific Internet number resources, the RIPE NCC must and will comply. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <strong> delete: <a name="h"> delete: </a> delete: <a name="b1h"> delete: </a> h. Independent Internet number resources assigned through a “sponsoring LIR” without a valid contractual relationship delete: </strong> delete: </p> delete: <p> See  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: </p> delete: <p>   delete: </p> delete: <h2> delete: <a name="b2"> delete: </a> delete: <strong> 2. Procedures for Deregistration of Different Types of Internet Number Resources delete: </strong> delete: </h2> delete: <h3> delete: <a name="b21"> delete: </a> delete: <strong> 2.1 Allocations and Independent Internet Number Resources for Member's Own Network delete: </strong> 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 Member will not be able make any further assignments from the allocations. delete: </p> delete: <p> Should the Member respond within four weeks, the RIPE NCC will provide a timeframe of three months for the Members to take care of any actions necessary for the deregistration of the Internet number resources. In the case of allocations, Members are responsible for requesting that their customers renumber immediately and for providing them with all available options. In particular, Members must refer their customers to the list of other Members. This list is available at:  delete: <a href="http://www.ripe.net/membership/indices"> http://www.ripe.net/membership/indices delete: </a> delete: </p> delete: <p> During the three-month period: delete: </p> delete: <ul> delete: <li> The Member must stop announcing the allocation/independent Internet number resources delete: </li> delete: <li> The RIPE NCC will change the “mnt-by” attribute on the Member's  delete: <strong> inetnum delete: </strong>  object to a RIPE NCC maintainer delete: </li> delete: <li> A warning statement will be added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources delete: </li> delete: <li> The RIPE NCC will revoke any certificates generated by the RIPE NCC Resource Certification (RPKI) service 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 Member not react within four weeks, the RIPE NCC will: delete: </p> delete: <ul> delete: <li> Change the “mnt-by delete: <strong> :” delete: </strong>  attribute on the Member's  delete: <strong> inetnum delete: </strong>  object to a RIPE NCC maintainer; and/or 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 provider 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: <strong> route delete: </strong>  objects delete: </p> delete: </li> delete: <li> delete: <p> Revoke any certificates generated by the RIPE NCC Resource Certification (RPKI) Service delete: </p> delete: </li> delete: </ul> delete: <p> The sole purpose of these actions by the RIPE NCC is for the 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 Member 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 Member to submit evidence that there is no reason for the deregistration of the Internet number resources or to request arbitration (see the  delete: <a href="http://www.ripe.net/ripe/docs/arbitration"> RIPE NCC Conflict Arbitration Procedure delete: </a> ). However, if the four-week period expires without the submission of such evidence by the Member or without the submission of a request for arbitration, the RIPE NCC will proceed as if the Member had never reacted (see relevant procedure above). The Member may still request arbitration according to the timeframes of the RIPE NCC Conflict Arbitration Procedure. If the Member requests arbitration, the RIPE NCC will lock the relevant records in the RIPE Database and add a warning statement to them, until the communication of the arbiter's ruling. delete: </p> delete: <p>   delete: </p> delete: <h3> delete: <a name="b22"> delete: </a> delete: <strong> 2.2 Independent Internet Number Resources Assigned Through a “Sponsoring LIR” delete: </strong> 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 Member must immediately inform the End User about the imminent deregistration. delete: </p> delete: <p> During this period: delete: </p> delete: <ul> delete: <li> The End User must stop announcing the independent Internet number resources delete: </li> delete: <li> delete: <p> The RIPE NCC will change the “mnt-by:” attribute on the relevant object to RIPE NCC maintainer delete: </p> delete: </li> delete: <li> delete: <p> A warning statement will be 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 Member not react within four weeks, the RIPE NCC will: delete: </p> delete: <ul> delete: <li> Change the “mnt-by:” attribute on the relevant object to RIPE NCC maintainer; and/or 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 provider 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: <strong> route delete: </strong>  objects delete: </p> delete: </li> delete: </ul> delete: <p> The sole purpose of these actions by the RIPE NCC is for the 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 Member 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 Member to submit evidence that there is no reason for deregistration of the Internet number resources or to request arbitration (see the  delete: <a href="http://www.ripe.net/ripe/docs/arbitration"> RIPE NCC Conflict Arbitration Procedure delete: </a> ). However, if the four-week period expires without the submission of such evidence by the Member or without the submission of a request for arbitration, the RIPE NCC will proceed as if the Member had never reacted (see relevant procedure above). The Member may still request arbitration according to the timeframes of the RIPE NCC Conflict Arbitration Procedure. If the Member requests arbitration, the RIPE NCC will lock the relevant records in the RIPE Database and add a warning statement to them until the communication of the arbiter's ruling. delete: </p> delete: <p>   delete: </p> delete: <h2> delete: <a name="c"> delete: </a> delete: <strong> C. Legacy Internet Resources delete: </strong> delete: </h2> delete: <h3> delete: <a name="c1"> delete: </a> delete: <strong> 1. Termination of the Legacy Services delete: </strong> delete: </h3> delete: <p> This section describes the reasons for the termination of: delete: </p> delete: <ul> delete: <li> The Legacy Services the RIPE NCC provides to a Member pursuant to the  delete: <a href="http://www.ripe.net/publications/docs/legacy-internet-resources-terms-conditions" data-val="https://www.ripe.net/publications/docs/legacy-internet-resources-terms-conditions" data-linktype="external"> RIPE NCC Services for Legacy Internet Resources of RIPE NCC Members Terms and Conditions delete: </a>  (section 1.1) delete: </li> delete: <li> delete: <p> The  delete: <a href="http://www.ripe.net/publications/docs/legacy-internet-resources-agreement" data-val="https://www.ripe.net/publications/docs/legacy-internet-resources-agreement" data-linktype="external"> RIPE NCC Services for Legacy Internet Resource Holders (Legacy Agreement) delete: </a>  between the RIPE NCC and a Legacy Internet Resource Holder (section 1.2) delete: </p> delete: </li> delete: </ul> delete: <h3> delete: <a name="c11"> delete: </a> delete: <strong> 1.1 Legacy Services by the RIPE NCC to a Member Pursuant to the Terms and Conditions Regarding Legacy Internet Resources for Members delete: </strong> delete: </h3> delete: <p> The Legacy Services can be terminated by the Member (see section 1.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.1.2.1) or for specific reasons with a shorter notice period and immediate effect (see section 1.1.2.2). delete: </p> delete: <h4> delete: <a name="c111"> delete: </a> delete: <strong> 1.1.1. Termination by the Member delete: </strong> delete: </h4> delete: <p> According to Article 5.2 of the Terms and Conditions Regarding Legacy Internet Resources for Members, the Member shall be entitled to terminate the Legacy Services at any time with a written notice period of three months. delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> delete: </p> delete: <p> The notice will formally request the termination of the Legacy Services. delete: </p> delete: <p> The notice must be: delete: </p> delete: <ul> delete: <li> Dated and signed by an authorised representative of the Member delete: </li> delete: <li> delete: <p> Sent to the RIPE NCC by email at  delete: <a class="email-link" title="" href="mailto:legacy@ripe.net" target="_self"> legacy@ripe.net delete: </a>  or by postal mail to: Stationsplein 11, 1012 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 regarding Legacy Services is terminated. delete: </p> delete: <p> The termination of the Legacy Services will take place three months after the receipt of the notice by the RIPE NCC. delete: </p> delete: <h4> delete: <a name="c112"> delete: </a> delete: <strong> 1.1.2. Termination by the RIPE NCC delete: </strong> delete: </h4> delete: <p> delete: <a name="c1121"> delete: </a> delete: <strong> 1.1.2.1. Non-compliance with Contractual Responsibilities delete: </strong> delete: </p> delete: <p> According to Article 5.3 of the  delete: <a href="http://www.ripe.net/publications/docs/legacy-internet-resources-terms-conditions" data-val="https://www.ripe.net/publications/docs/legacy-internet-resources-terms-conditions" data-linktype="external"> RIPE NCC Services for Legacy Internet Resources of RIPE NCC Members Terms and Conditions, delete: </a>  the RIPE NCC can terminate the Legacy Services. Grounds for such termination may be the following: delete: </p> delete: <div class="column"> delete: <p> a. The Member does not provide the RIPE NCC with complete, updated and accurate information necessary for the provision of the Legacy Services delete: </p> delete: <p> b. The Member does not maintain accurate data in the RIPE Database regarding the Legacy Internet Resources delete: </p> delete: <p> c. The Member does not assist the RIPE NCC with data accuracy checks in accordance with the procedure described in RIPE NCC procedural documents, including the documents  delete: <a href="http://www.ripe.net/publications/docs/due-diligence"> Due Diligence for the Quality of the RIPE NCC Registration Data delete: </a>  and  delete: <a href="http://www.ripe.net/publications/docs/audit" data-val="http://www.ripe.net/publications/docs/audit" data-linktype="internal"> RIPE NCC Audit Activity delete: </a> delete: </p> delete: </div> delete: <div class="column">   delete: </div> delete: <p> delete: <strong> Procedure delete: </strong> delete: </p> delete: <p> If the RIPE NCC becomes aware of any of the aforementioned reasons for terminating the Legacy Services, 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 Member's obligation to stop or rectify the violation delete: </p> delete: </li> delete: <li> delete: <p> The termination of the Legacy Services in three months if the violation continues delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> Terminate the progress of any open requests related to Legacy Services delete: </p> delete: </li> delete: <li> delete: <p> Add the remark "under review" in the RIPE Database resource object delete: </p> delete: </li> delete: <li> delete: <p> Add a warning statement to the relevant records of the RIPE Database mentioning that the Legacy Internet Resources are not in compliance with data accuracy obligations delete: </p> delete: </li> delete: <li> delete: <p> Revoke any certificates generated by the RIPE NCC Resource Certification (RPKI) service relating to Legacy Internet Resources delete: </p> delete: </li> delete: </ul> delete: <p>   delete: </p> delete: <p> If the Member 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> The violation delete: </li> delete: <li> delete: <p> The Member's obligation to stop or rectify the violation delete: </p> delete: </li> delete: <li> delete: <p> The termination of the Legacy Services in two months if the violation continues delete: </p> delete: </li> delete: </ul> delete: <p>   delete: </p> delete: <p> After 60 days from the date of the first email, if the Member 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> The violation delete: </li> delete: <li> delete: <p> The Member's obligation to stop or rectify the violation delete: </p> delete: </li> delete: <li> delete: <p> The termination of the Legacy Services in one month if the violation continues delete: </p> delete: </li> delete: </ul> delete: <p>   delete: </p> delete: <p> After 90 days from the date of the first email, if the Member continues to not comply, the RIPE NCC Managing Director will send an official notification of termination of the Legacy Services to all registered postal and email addresses of the Member. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="c1122"> delete: </a> delete: <strong> 1.1.2.2. Termination with Immediate Effect delete: </strong> delete: </p> delete: <p> According to Article 5.4 of the Legacy Agreement, the RIPE NCC can terminate the Legacy Services with immediate effect for the following reasons: delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="c1122a"> delete: </a> delete: <strong> a. The Member's SSA is terminated for any reason delete: </strong> delete: </p> delete: <p> Upon termination of the Member's SSA (see section A of this document), the Legacy Services are also terminated without any further notification being necessary. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="c1122b"> delete: </a> delete: <strong> b. The Member transfers the Legacy Internet Resources to a third party delete: </strong> delete: </p> delete: <p> If the Member transfers the Legacy Internet Resources to a third party, the Legacy Services provided by the RIPE NCC regarding these Legacy Internet Resources are not transferred to the third party. The third party has to sign a contractual agreement with either the RIPE NCC or a sponsoring LIR. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="c1122c"> delete: </a> delete: <strong> c. The Member has no rights to use the Legacy Internet Resources delete: </strong> delete: </p> delete: <p> If a third party provides sufficient evidence proving the Legacy Internet Resources must not be registered with the Member, the RIPE NCC will immediately terminate the Legacy Services. delete: </p> delete: <p> If the sufficient evidence refers to some of the Legacy Internet Resources, the RIPE NCC may decide not to terminate all Legacy Services but only those related to the Legacy Internet Resource in doubt. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="c1122d"> delete: </a> delete: <strong> d. Reasons beyond control of the RIPE NCC delete: </strong> delete: </p> delete: <p> The RIPE NCC may terminate the Legacy Services if the continuation of the Legacy Services is impossible for reasons above and beyond control by the RIPE NCC or if the RIPE NCC cannot reasonably be required to continue the Legacy Services for reasons that cannot be attributed to the RIPE NCC and for which the RIPE NCC cannot be held accountable by virtue of law, a juridical act or generally accepted principles. delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> 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 reason for termination of the Legacy Services delete: </p> delete: </li> delete: <li> delete: <p> The immediate termination of the Legacy Services delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> Terminate the progress of any open requests related to Legacy Services delete: </p> delete: </li> delete: </ul> delete: <div>   delete: </div> delete: <h3> delete: <a name="c12"> delete: </a> delete: <strong> 1.2 Legacy Agreement Between the RIPE NCC and a Legacy Internet Resource Holder delete: </strong> delete: </h3> delete: <p> The Legacy Agreement can be terminated by the Legacy Internet Resource Holder (see section 1.2.1) or by the RIPE NCC. Termination by the RIPE NCC can either occur with a three-month notice period(see section 1.2.2.1), or, for specific reasons, with immediate effect (see section 1.2.2.2). delete: </p> delete: <h4> delete: <a name="c121"> delete: </a> delete: <strong> 1.2.1. Termination by the Legacy Internet Resource Holder delete: </strong> delete: </h4> delete: <p> According to Article 7.2 of the  delete: <a href="http://www.ripe.net/publications/docs/legacy-internet-resources-agreement" data-val="https://www.ripe.net/publications/docs/legacy-internet-resources-agreement" data-linktype="external"> Legacy Agreement delete: </a> , the Legacy Internet Resource Holder shall be entitled to terminate the Legacy Agreement at any time with a written notice of three months. delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> delete: </p> delete: <p> The termination notice will formally request the termination of the Legacy Agreement. delete: </p> delete: <p> It must be: delete: </p> delete: <ul> delete: <li> Dated and signed by an authorised representative of the Legacy Internet Resource Holder. delete: </li> delete: <li> Sent to the RIPE NCC by email to  delete: <a class="email-link" title="" href="mailto:legacy@ripe.net" target="_self"> legacy@ripe.net delete: </a>  or by postal mail to: Stationsplein 11, 1012 AB Amsterdam, the Netherlands delete: </li> delete: </ul> delete: <p>   delete: </p> 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 regarding Legacy Services under the Legacy Agreement is terminated. delete: </p> delete: <p> The termination of the Legacy Agreement will take place three months after the receipt of the notice by the RIPE NCC. delete: </p> delete: <p> delete: <strong> Billing issues delete: </strong> delete: </p> delete: <p> All outstanding amounts for the full year must be settled unless otherwise agreed. delete: </p> delete: <p>   delete: </p> delete: <h4> delete: <a name="c122"> delete: </a> delete: <strong> 1.2.2. Termination by the RIPE NCC delete: </strong> delete: </h4> delete: <p> delete: <a name="c1221"> delete: </a> delete: <strong> 1.2.2.1. Non-compliance with Contractual Responsibilities delete: </strong> delete: </p> delete: <p> According to Article 7.3 of the Legacy Agreement, the RIPE NCC can terminate the Legacy Agreement. Grounds for such termination may be the following: delete: </p> delete: <p> a. The Legacy Internet Resource Holder does not provide the RIPE NCC with complete, updated and accurate information necessary for the provision of the service under the Legacy Agreement delete: </p> delete: <p> b. The Legacy Internet Resource Holder does not maintain accurate data in the RIPE Database regarding the Legacy Internet Resources delete: </p> delete: <p> c. The Legacy Internet Resource Holder does not assist the RIPE NCC with data accuracy checks in accordance with the procedure described in RIPE NCC procedural documents, including the documents  delete: <a href="http://www.ripe.net/publications/docs/due-diligence"> Due Diligence for the Quality of the RIPE NCC Registration Data delete: </a>  and  delete: <a href="http://www.ripe.net/ripe/docs/audit" data-val="http://www.ripe.net/ripe/docs/audit" data-linktype="external"> RIPE NCC Audit Activity delete: </a> delete: </p> delete: <p> d. The Legacy Internet Resource Holder does not comply with an arbiter's ruling (see  delete: <a href="http://www.ripe.net/publications/docs/arbitration" data-val="http://www.ripe.net/publications/docs/arbitration" data-linktype="internal"> RIPE NCC Conflict Arbitration Procedure delete: </a> ) delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> delete: </p> delete: <p> If the RIPE NCC becomes aware of any of the aforementioned reasons for terminating the Legacy Agreement, the RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Send an email to the registered contact(s) of the Legacy Internet Resource Holder indicating: delete: </p> delete: <ul> delete: <li> delete: <p> The violation delete: </p> delete: </li> delete: <li> delete: <p> The Legacy Internet Resource Holder's obligation to stop or rectify the violation delete: </p> delete: </li> delete: <li> delete: <p> The termination of the Legacy Agreement in three months if the violation continues delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> Terminate the progress of any open requests related to the Legacy Agreement delete: </li> delete: <li> delete: <p> Add the remark "under review" in the RIPE Database resource object delete: </p> delete: </li> delete: <li> delete: <p> Add a warning statement to the relevant records of the RIPE Database mentioning that the Legacy Internet Resources are not in compliance with data accuracy obligations delete: </p> delete: </li> delete: <li> delete: <p> Revoke any certificates generated by the RIPE NCC Resource Certification (RPKI) service relating to Legacy Internet Resources delete: </p> delete: </li> delete: </ul> delete: <p> If the Legacy Internet Resource Holder 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> The violation delete: </li> delete: <li> delete: <p> The Legacy Internet Resource Holder's obligation to stop or rectify the violation delete: </p> delete: </li> delete: <li> delete: <p> The termination of the Legacy Agreement in two 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 Legacy Internet Resource Holder 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> The violation delete: </li> delete: <li> delete: <p> The Legacy Internet Resource Holder's obligation to stop or rectify the violation delete: </p> delete: </li> delete: <li> delete: <p> The termination of the Legacy Agreement in one 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 Legacy Internet Resource Holder continues to not comply, the RIPE NCC Managing Director will send an official notification of termination of the Legacy Agreement to all registered postal and email addresses of the Legacy Internet Resource Holder. delete: </p> delete: <p> delete: <strong> Billing issues delete: </strong> delete: </p> delete: <p> All outstanding amounts for the full year must be settled unless otherwise agreed. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="c1222"> delete: </a> delete: <strong> 1.2.2.2. Termination with Immediate Effect delete: </strong> delete: </p> delete: <p> According to Article 7.4 of the Legacy Agreement, the RIPE NCC can terminate the Agreement with immediate effect for the following reasons: delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="c1222a"> delete: </a> delete: <strong> a. The Legacy Internet Resource Holder files for bankruptcy, is liquidated, suspends their payments or becomes insolvent delete: </strong> delete: </p> delete: <p> Upon receipt of the documents stating the bankruptcy, liquidation, suspension of payments or insolvency of the Legacy Internet Resource Holder by the relevant authority or by public announcement of the fact, the RIPE NCC will terminate the Legacy Agreement. If the relevant national authority decides that the Legacy Internet Resource Holder's operations can continue, and provided that the Legacy Internet Resource Holder fulfils the obligations imposed by the Legacy Agreement, the RIPE NCC will not terminate the Legacy Agreement. delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> 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: <ul> delete: <li> delete: <p> The reason for termination of the Legacy Agreement delete: </p> delete: </li> delete: <li> delete: <p> The immediate termination of the Legacy Agreement delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> Terminate the progress of any open requests related to the Legacy Agreement delete: </p> delete: </li> delete: </ul> delete: <p>   delete: </p> delete: <p> The RIPE NCC Managing Director will send an official notification of termination of the Legacy Agreement to all registered contacts of the Legacy Internet Resource Holder or to the legal successor, both by electronic and registered postal mail. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="c1222b"> delete: </a> delete: <strong> b. The Legacy Internet Resource Holder damages the name, trademarks or intellectual property rights of the RIPE NCC delete: </strong> delete: </p> delete: <p> Examples: delete: </p> delete: <p> The Legacy Internet Resource Holder pretends to be, or to act on behalf of, the RIPE NCC through misuse of the RIPE NCC name or logo delete: </p> delete: <p> The Legacy Internet Resource Holder 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: <p> delete: <strong> Procedure: delete: </strong> 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> The violation delete: </li> delete: <li> The Legacy Internet Resource Holder's obligation to stop or rectify the violation delete: </li> delete: <li> The termination of the SSA if the violation continues delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> Terminate the progress of any open requests related to the Legacy Agreement delete: </p> delete: </li> delete: </ul> delete: <p>   delete: </p> delete: <p> If the Legacy Internet Resource Holder 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 Legacy Internet Resource Holder still does not comply, the RIPE NCC will send a second reminder email to the registered contact(s) indicating the same as above. delete: </p> delete: <p> After 90 days from the date of the first email, if the Legacy Internet Resource Holder continues to not 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. delete: </p> delete: <p> After 120 days from the date of the first email, if the Legacy Internet Resource Holder still does not comply, the RIPE NCC Managing Director will send an official notification of termination of the Legacy Agreement to all registered postal and email addresses of the Legacy Internet Resource Holder. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="c1222c"> delete: </a> delete: <strong> c. The Legacy Internet Resource Holder fails to submit to the RIPE NCC a valid extract from the Commercial Trade Register or equivalent register delete: </strong> delete: </p> delete: <p> When initially signing the Legacy Agreement, the Legacy Internet Resource Holder must submit to the RIPE NCC an extract from the Commercial Trade Register or equivalent document providing the registration of the Legacy Internet Resource Holder's business with the national authorities (see Article 2.2 of the Legacy Agreement). delete: </p> delete: <p> If the Legacy Internet Resource Holder 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 Legacy Internet Resource Holder is a legal person, identification papers are also required for the authorised person signing the Legacy Internet Resource Holder on behalf of the legal person. delete: </p> delete: <p> If there is any change in the Legacy Internet Resource Holder's business after signing the Legacy Agreement (for example, the Legacy Internet Resource Holder has merged with another company, has changed name, etc.) and, because of this change, the Legacy Internet Resource Holder's registration with the relevant register has been changed, then the Legacy Internet Resource Holder is obliged to submit the updated registration papers to the RIPE NCC. delete: </p> delete: <p> If the Legacy Internet Resource Holder does not submit the aforementioned documents within one month of them being requested by the RIPE NCC, the RIPE NCC will terminate the Legacy Agreement (see Article 7.5.d of the Legacy Agreement). delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> 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 Legacy Internet Resource Holder's obligation to submit the relevant documents delete: </p> delete: </li> delete: <li> delete: <p> The termination of the Legacy Agreement 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 related to the Legacy Agreement delete: </p> delete: </li> delete: </ul> delete: <p>   delete: </p> delete: <p> If the Legacy Internet Resource Holder 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 Legacy Internet Resource Holder continues to not comply, the RIPE NCC Managing Director will send an official notification of termination of the Legacy Agreement to all registered postal and email addresses of the Legacy Internet Resource Holder. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="c1222d"> delete: </a> delete: <strong> d. The Legacy Internet Resource Holder fails to observe any rule of applicable law delete: </strong> delete: </p> delete: <p> The Legacy Agreement 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 Legacy Agreement of a Legacy Internet Resource Holder with immediate effect, provided it receives a Dutch court order to do so. delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> 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 reason for termination of the Legacy Agreement delete: </p> delete: </li> delete: <li> delete: <p> The immediate termination of the Legacy Agreement delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> Terminate the progress of any open requests related to the Legacy Agreement delete: </p> delete: </li> delete: </ul> delete: <p> The RIPE NCC Managing Director will send an official notification of termination of the Legacy Agreement. to all registered postal and email addresses of the Legacy Internet Resource Holder. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="c1222e"> delete: </a> delete: <strong> e. Non-payment delete: </strong> delete: </p> delete: <p> In case of non-payment, in accordance with the RIPE NCC Billing Procedure, the Legacy Agreement will be terminated after 120 days. For more information, please see the  delete: <a href="http://www.ripe.net/participate/billing/procedure"> RIPE NCC Billing Procedure delete: </a> . delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="c1222f"> delete: </a> delete: <strong> f. Untruthful information delete: </strong> delete: </p> delete: <p> The RIPE NCC concludes the Legacy Agreement and provides services to Legacy Internet Resource Holder in good faith. The Legacy Internet Resource Holder is in breach of good faith, if the Legacy Internet Resource Holder 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: <strong> Procedure delete: </strong> 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 reason for termination of the Legacy Agreement delete: </p> delete: </li> delete: <li> delete: <p> The immediate termination of the Legacy Agreement delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> Terminate the progress of any open requests related to the Legacy Agreement delete: </p> delete: </li> delete: </ul> delete: <p> The RIPE NCC Managing Director will send an official notification of termination of the Legacy Agreement to all registered postal and email addresses of the Legacy Internet Resource Holder. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="c1222g"> delete: </a> delete: <strong> g. Non-compliance with RIPE NCC audits delete: </strong> 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 Legacy Internet Resource Holder's own network. For more information about the audit procedure, please see the  delete: <a href="http://www.ripe.net/ripe/docs/audit"> RIPE NCC Audit Activity delete: </a> . delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> 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 reason for termination of the Legacy Agreement delete: </p> delete: </li> delete: <li> delete: <p> The immediate termination of the Legacy Agreement delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> Terminate the progress of any open requests related to the Legacy Agreement. delete: </p> delete: </li> delete: </ul> delete: <p> The RIPE NCC Managing Director will send an official notification of termination of the Legacy Agreement to all registered postal and email addresses of the Legacy Internet Resource Holder. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="c1222h"> delete: </a> delete: <strong> h. Reasons beyond control of the RIPE NCC delete: </strong> delete: </p> delete: <p> If the continuation of the Legacy Agreement is impossible for reasons above and beyond control by the RIPE NCC or if the RIPE NCC cannot reasonably be required to continue the Legacy Agreement for reasons that can not be attributed to the RIPE NCC and for which the RIPE NCC cannot be held accountable by virtue of law, a juridical act or generally accepted principles, the RIPE NCC may terminate the Legacy Agreement. delete: </p> delete: <p> delete: <strong> Procedure delete: </strong> 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 reason for termination of the Legacy Agreement delete: </p> delete: </li> delete: <li> delete: <p> The immediate termination of the Legacy Agreement 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> The RIPE NCC Managing Director will send an official notification of termination of the Legacy Agreement to all registered postal and email addresses of the Legacy Internet Resource Holder. delete: </p> delete: <p> delete: <strong> Billing issues delete: </strong> delete: </p> delete: <p> All outstanding amounts for the full year must be settled unless otherwise agreed. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="c1222i"> delete: </a> delete: <strong> i. The Legacy Internet Resource Holder transfers the Legacy Internet Resources to a third party delete: </strong> delete: </p> delete: <p> If the Legacy Internet Resource Holder transfers the Legacy Internet Resources to a third party, the Legacy Services provided by the RIPE NCC regarding these Legacy Internet Resources are not transferred to the third party. The third party has to sign a contractual agreement with either the RIPE NCC or a sponsoring LIR. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a name="c1222j"> delete: </a> delete: <strong> j. The Legacy Internet Resource Holder has no rights to use the Legacy Internet Resources delete: </strong> delete: </p> delete: <p> If a third party provides sufficient evidence proving the Legacy Internet Resources must not be registered with the Legacy Internet Resource Holder, the RIPE NCC will immediately terminate the Legacy Agreement. delete: </p> delete: <p> If the sufficient evidence refers to some of the Legacy Internet Resources, the RIPE NCC may decide not to terminate the Legacy Agreement but to update it by removing the Legacy Internet Resources in doubt. delete: </p> delete: <p>   delete: </p> delete: <h2> delete: <a name="c2"> delete: </a> delete: <strong> 2. Consequences delete: </strong> delete: </h2> delete: <p> This section describes the consequences of the termination of: delete: </p> delete: <ul> delete: <li> The Legacy Services the RIPE NCC provides to a Member pursuant to the  delete: <a href="http://www.ripe.net/publications/docs/legacy-internet-resources-terms-conditions" data-val="https://www.ripe.net/publications/docs/legacy-internet-resources-terms-conditions" data-linktype="external"> RIPE NCC Services for Legacy Internet Resources of RIPE NCC Members Terms and Conditions delete: </a> ; delete: </li> delete: <li> The  delete: <a href="http://www.ripe.net/publications/docs/legacy-internet-resources-agreement" data-val="https://www.ripe.net/publications/docs/legacy-internet-resources-agreement" data-linktype="external"> RIPE NCC Services for Legacy Internet Resources Agreement delete: </a> ; or delete: </li> delete: <li> The Legacy Agreement between a Legacy Internet Resource Holder and a sponsoring LIR delete: </li> delete: </ul> delete: <p>   delete: </p> delete: <p> Upon termination of the Legacy Services/Agreement for reasons of non-compliance with contractual responsibilities: delete: </p> delete: <ul> delete: <li> delete: <p> The RIPE NCC will add the remark “No-contract” in the RIPE Database resource object; and delete: </p> delete: </li> delete: <li> delete: <p> A warning statement will be added to the relevant records in the RIPE Database mentioning that the Legacy Internet Resources are not covered by a contractual relationship; and delete: </p> delete: </li> delete: <li> delete: <p> The RIPE NCC will withdraw the reverse delegation; and delete: </p> delete: </li> delete: <li> delete: <p> The RIPE NCC will not be obliged to keep providing the holder with services other than those provided, with regards to each Legacy Internet Resources immediately before the agreement to the  delete: <a href="http://www.ripe.net/publications/docs/legacy-internet-resources-terms-conditions" data-val="https://www.ripe.net/publications/docs/legacy-internet-resources-terms-conditions" data-linktype="external"> RIPE NCC Services for Legacy Internet Resources of RIPE NCC Members Terms and Condition delete: </a> s or the signing of the Legacy Agreement (this does not include the reverse delegation) delete: </p> delete: </li> delete: </ul> delete: <p>   delete: </p> delete: <p> Upon termination of the Legacy Service/Agreement for any other reason: delete: </p> delete: <ul> delete: <li> delete: <p> The RIPE NCC will add the remark “No-contract” in the RIPE Database resource object; and delete: </p> delete: </li> delete: <li> delete: <p> A warning statement will be added to the relevant records in the RIPE Database mentioning that the Legacy Internet Resources are not covered by a contractual relationship; and delete: </p> delete: </li> delete: <li> delete: <p> The RIPE NCC will not be obliged to keep providing the holder with services other than those provided, with regards to each Legacy Internet Resources immediately before the agreement to the  delete: <a href="http://www.ripe.net/publications/docs/legacy-internet-resources-terms-conditions" data-val="https://www.ripe.net/publications/docs/legacy-internet-resources-terms-conditions" data-linktype="external"> RIPE NCC Services for Legacy Internet Resources of RIPE NCC Members Terms and Conditions delete: </a>  or the signing of the Legacy Agreement delete: </p> delete: </li> delete: </ul> delete: <p> Please note that if the termination of the Legacy Agreement takes place because of contractual relationship changes between the Legacy Internet Resource Holder and the sponsoring LIR, the RIPE NCC procedural document  delete: <a href="http://www.ripe.net/publications/docs/sponsoring-lir-legacy-contractual-relationship" data-val="https://www.ripe.net/publications/docs/sponsoring-lir-legacy-contractual-relationship" data-linktype="external"> Legacy Internet Resources – Contractual Relationship Changes Between Sponsoring LIR and Legacy Internet Resource Holder delete: </a>  is applicable. delete: </p> delete: <p>   delete: </p> delete: <h2> delete: <a name="c3"> delete: </a> delete: <strong> 3. Change of Status of Legacy Internet Resources delete: </strong> delete: </h2> delete: <p> If a Legacy Internet Resource Holder (Member or not) wants to have particular Legacy Internet Resources registered as if they had been distributed by the RIPE NCC, the Legacy Internet Resource Holder must send an email to  delete: <a href="mailto:legacy@ripe.net"> legacy@ripe.net delete: </a> . In the email, the Legacy Internet Resource Holder must: delete: </p> delete: <ul> delete: <li> delete: <p> Indicate the Legacy Internet Resources; and delete: </p> delete: </li> delete: <li> delete: <p> Acknowledge that the RIPE NCC will apply for these resources the RIPE Policies concerning Internet number resources distributed by the RIPE NCC delete: </p> delete: </li> delete: </ul> delete: <p> The RIPE NCC will send an acknowledgement of the receipt of the notice. Upon the sending of such notice, the resources will be considered as distributed by the RIPE NCC. delete: </p> delete: <h2> delete: <a name="c4"> delete: </a> delete: <strong> 4. Deregistration of Legacy Internet Resources delete: </strong> delete: </h2> delete: <p> If a Legacy Internet Resource Holder (Member or not) wants to deregister particular Legacy Internet Resources, the Legacy Internet Resource Holder must send an email to  delete: <a href="mailto:legacy@ripe.net"> legacy@ripe.net delete: </a> . In the email, the Legacy Internet Resource Holder must: delete: </p> delete: <ul> delete: <li> delete: <p> Indicate the Legacy Internet Resources; and delete: </p> delete: </li> delete: <li> delete: <p> Acknowledge that they resign from any rights with regards to these resources delete: </p> delete: </li> delete: </ul> delete: <p> The RIPE NCC will send an acknowledgement of the receipt of the notice. Upon the sending of such notice, the Legacy Internet Resource Holder must stop announcing the Legacy Internet Resources. The RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Withdraw the reverse delegation; and delete: </p> delete: </li> delete: <li> delete: <p> Delete all relevant objects in the RIPE Database, including  delete: <strong> route delete: </strong>  objects delete: </p> delete: </li> delete: </ul> delete: <p>   delete: </p> delete: <p class="callout"> 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: </p> De-registration Timeframe. insert: </p>

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