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

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

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-619: ripe-517: Closure of Members, LIR and Deregistration of Internet Resources, and Legacy Number Resources

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

Section B describes the valid reasons for deregistration of Internet number resources and the procedure that applies in each circumstance.

delete: <p class="western"> delete: </p> delete: <h3 class="western"> insert: <p>

Please note that, for the purposes of this document, LIRs are referred to as “Contributors”. insert: </p>

insert: <h2>

insert: <b> Table of Contents delete: </h3> delete: <p class="western"> delete: <a href="#a"> insert: </b> insert: </h2>

insert: <p>

insert: <b> A. Closure of Member LIR – Termination of the RIPE NCC Standard Service Agreement delete: </a> delete: </p> delete: <p class="western"> delete: <a href="#1"> insert: </b> insert: </p>

insert: <p>

insert: <a class="anchor-link" href="#a1"> 1. Grounds for Termination, and the Procedure termination and procedure in Each Case delete: </a> delete: </p> delete: <p class="western"> delete: <a href="#11"> each case insert: </a> insert: </p>

insert: <p style="padding-left: 30px; ">

insert: <a class="anchor-link" href="#a11"> 1.1. Termination by the Member delete: </a> delete: </p> delete: <p class="western"> delete: <a href="#12"> Contributor insert: </a> insert: </p>

insert: <p style="padding-left: 30px; ">

insert: <a class="anchor-link" href="#a12"> 1.2. Termination by the RIPE NCC

delete: <p class="western" style="padding-left: 30px; "> delete: <a href="#121"> insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#a121"> 1.2.1. Termination with a Three-Month Notice Period delete: </a> delete: </p> delete: <p class="western" style="padding-left: 60px; "> delete: <a href="#1211"> three-month notice period insert: </a> insert: </p>

insert: <p style="padding-left: 90px; ">

insert: <a class="anchor-link" 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: 90px; "> delete: <a href="#1211a"> procedures insert: </a> insert: </p>

insert: <p style="padding-left: 120px; ">

insert: <a class="anchor-link" href="#a1211a"> a. Unresponsiveness

delete: <p class="western" style="padding-left: 90px; "> delete: <a href="#1211b"> insert: <p style="padding-left: 120px; ">

insert: <a class="anchor-link" href="#a1211b"> b. Allocations/assignments in contravention to RIPE policies delete: </a> delete: </p> delete: <p class="western" style="padding-left: 90px; "> delete: <a href="#1211c"> contravening RIPE Policies insert: </a> insert: </p>

insert: <p style="padding-left: 120px; ">

insert: <a class="anchor-link" href="#a1211c"> c. Incorrect registration in the RIPE Database

delete: <p class="western" style="padding-left: 90px; "> delete: <a href="#1211d"> insert: <p style="padding-left: 120px; ">

insert: <a class="anchor-link" href="#a1211d"> d. Non-compliance with RIPE NCC audits insert: </a> insert: </p>

insert: <p style="padding-left: 120px; ">

insert: <a class="anchor-link" href="#a1211e"> e. Non-compliance with an arbiter ruling

delete: <p class="western" style="padding-left: 60px; "> delete: <a class="anchor-link" href="#1212"> 1.2.1.2 insert: <p style="padding-left: 90px; ">

insert: <a class="anchor-link" href="#a1212"> 1.2.1.2. Provision of untruthful information insert: </a> insert: </p>

insert: <p style="padding-left: 120px; ">

insert: <a class="anchor-link" href="#a1212a"> a. Falsified/incorrect information insert: </a> insert: </p>

insert: <p style="padding-left: 120px; ">

insert: <a class="anchor-link" href="#a1212b"> b. Fraudulent requests insert: </a> insert: </p>

insert: <p style="padding-left: 90px; ">

insert: <a class="anchor-link" href="#a1213"> 1.2.1.3. Other Reasons delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px; "> delete: <a href="#122"> reasons insert: </a> insert: </p>

insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#a122"> 1.2.2. Termination with Immediate Effect delete: </a> delete: </p> delete: <p class="western" style="padding-left: 60px; "> delete: <a href="#122a"> immediate effect insert: </a> insert: </p>

insert: <p style="padding-left: 90px; ">

insert: <a class="anchor-link" href="#a122a"> a. Member Contributor files for bankruptcy, is liquidated, suspends its payments or becomes insolvent

delete: <p class="western" style="padding-left: 60px; "> delete: <a href="#122b"> insert: <p style="padding-left: 90px; ">

insert: <a class="anchor-link" href="#a122b"> b. Member Contributor damages the name, trademarks or intellectual property rights of the RIPE NCC

delete: <p class="western" style="padding-left: 60px; "> delete: <a href="#122c"> insert: <p style="padding-left: 90px; ">

insert: <a class="anchor-link" href="#a122c"> c. Member Contributor fails to submit to the RIPE NCC a valid extract from the Commercial Trade Register or equivalent register

delete: <p class="western" style="padding-left: 60px; "> delete: <a href="#122d"> insert: <p style="padding-left: 90px; ">

insert: <a class="anchor-link" href="#a122d"> d. The Member Contributor fails to observe any rule of applicable law

delete: <p class="western" style="padding-left: 60px; "> delete: <a href="#122e"> insert: <p style="padding-left: 90px; ">

insert: <a class="anchor-link" href="#a122e"> e. Non-payment

delete: <p class="western" style="padding-left: 60px; "> delete: <a href="#122f"> insert: <p style="padding-left: 90px; ">

insert: <a class="anchor-link" href="#a122f"> f. Termination of the Contributor's RIPE NCC member status

delete: <p class="western" style="padding-left: 60px; "> delete: <a href="#122g"> g. Untruthful information delete: </a> delete: </p> delete: <p class="western" style="padding-left: 60px; "> delete: <a href="#122h"> h. Non-compliance with RIPE NCC audits delete: </a> delete: </p> delete: <p class="western" style="padding-left: 60px; "> delete: <a href="#122i"> i. Discontinuation of RIPE NCC services delete: </a> delete: </p> delete: <p class="western"> delete: <a href="#2"> insert: <p>

insert: <a class="anchor-link" href="#a2"> 2. Consequences

delete: <p class="western"> delete: <a href="#21"> insert: <p style="padding-left: 30px; ">

insert: <a class="anchor-link" href="#a21"> 2.1. End of Provision of RIPE NCC Services delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px; "> delete: <a href="#211"> provision of RIPE NCC services insert: </a> insert: </p>

insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#a211"> 2.1.1. General Services delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px; "> delete: <a href="#212"> services insert: </a> insert: </p>

insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#a212"> 2.1.2. Registration of Distributed Internet Number Resources delete: </a> delete: </p> delete: <p class="western" style="padding-left: 30px; "> delete: <a href="#213"> distributed Internet number resources insert: </a> insert: </p>

insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#a213"> 2.1.3. Request for Independent Internet Number Resources independent Internet number resources as a “Sponsoring “sponsoring LIR”

delete: <p class="western"> delete: <a href="#22"> insert: <p style="padding-left: 30px; ">

insert: <a class="anchor-link" 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"> Contributor's RIPE NCC member status insert: </a> insert: </p>

insert: <p>

insert: </p>

insert: <p>

B. insert: <b> Deregistration of Internet Number Resources delete: </a> delete: </p> delete: <p class="western"> delete: <a href="#b1"> number resources insert: </b> insert: </p>

insert: <p>

insert: <a class="anchor-link" href="#b1"> 1. Reasons for Deregistration of Internet Number Resources - deregistration of Internet number resources insert: </a> insert: </p>

insert: <p style="padding-left: 30px; ">

insert: <a class="anchor-link" href="#b11"> 1.1. Allocations and Independent Internet Number Resources Assigned for the Member's Own Network number resources assigned for the Contributor's own network or Assigned Through a “Sponsoring assigned through a “sponsoring LIR”

delete: <p class="western" style="padding-left: 30px; "> delete: <a href="#b1a"> insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#b11a"> a. Termination of the SSA

delete: <p class="western" style="padding-left: 30px; "> delete: <a href="#b1b"> insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#b11b"> b. Invalidity of original allocation/assignment criteria

delete: <p class="western" style="padding-left: 30px; "> delete: <a href="#b1c"> insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#b11c"> c. Incorrect registration of the allocation/assignment in the RIPE Database

delete: <p class="western" style="padding-left: 30px; "> delete: <a href="#b1d"> insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#b11d"> d. Falsified/incorrect information

delete: <p class="western" style="padding-left: 30px; "> delete: <a href="#b1e"> insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#b11e"> e. Fraudulent request

delete: <p class="western" style="padding-left: 30px; "> delete: <a href="#b1f"> insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#b11f"> f. Non-compliance with a RIPE NCC audit

delete: <p class="western" style="padding-left: 30px; "> delete: <a href="#b1g"> insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#b11g"> g. Court order

delete: <p class="western" style="padding-left: 30px; "> delete: <a href="#b1h"> insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#b11h"> h. Independent Internet number resources assigned through a “sponsoring LIR” without a valid contractual relationship

delete: <p class="western"> delete: <a href="#b2"> 2. Procedures 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 insert: <p style="padding-left: 30px; ">

insert: <a class="anchor-link" href="#b12"> 1.2. Independent Internet Number number resources 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 Resources delete: </a> delete: </p> delete: <p> delete: <a href="#c1"> 1. assigned directly by the RIPE NCC for Direct Assignment Agreement insert: </a> insert: </p>

insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#b12a"> a. 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 RIPE NCC End User Assignment Agreement

delete: <a href="#c111"> 1.1.1. Termination by the Member insert: <a class="anchor-link" href="#b12b"> b. Unresponsive Direct Assignment User

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"> insert: <a class="anchor-link" href="#b12c"> c. Member has no rights to use the Legacy Internet Resources delete: </a> delete: </p> delete: <p style="padding-left: 120px; "> delete: <a href="#c1122d"> Invalidity of original criteria insert: </a> insert: </p>

insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#b12d"> 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 Holder Incorrect registration of the assignment in the RIPE Database

delete: <a href="#c121"> 1.2.1. Termination by the Legacy Holder insert: <a class="anchor-link" href="#b12e"> e. Falsified/incorrect information

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. Legacy Holder files for bankruptcy, is liquidated, suspends its payments or becomes insolvent delete: </a> delete: </p> delete: <p style="padding-left: 120px; "> delete: <a href="#c1222b"> b. Legacy 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. Member 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 Member 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"> insert: <a class="anchor-link" href="#b12f"> f. Untruthful information delete: </a> delete: </p> delete: <p style="padding-left: 120px; "> delete: <a href="#c1222g"> Fraudulent request insert: </a> insert: </p>

insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#b12g"> g. Non-compliance with RIPE NCC audits delete: </a> delete: </p> delete: <p style="padding-left: 120px; "> delete: <a href="#c1222h"> a RIPE NCC audit insert: </a> insert: </p>

insert: <p style="padding-left: 60px; ">

insert: <a class="anchor-link" href="#b12h"> 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 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 Holder has no rights to use the Legacy Internet Resources delete: </a> delete: </p> delete: <p> delete: <a href="#c2"> Court order insert: </a> insert: </p>

insert: <p>

insert: <a class="anchor-link" href="#b2"> 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: <p class="western"> delete: </p> delete: <h2 class="western"> delete: <a name="a"> delete: </a> Procedures for deregistration of different types of Internet number resources insert: </a> insert: </p>

insert: <p style="padding-left: 30px; ">

insert: <a class="anchor-link" href="#b21"> 2.1. Allocations and Independent Internet number resources for Contributor's own network insert: </a> insert: </p>

insert: <p style="padding-left: 30px; ">

insert: <a class="anchor-link" href="#b22"> 2.2. Independent Internet number resources assigned through a “sponsoring LIR” insert: </a> insert: </p>

insert: <p style="padding-left: 30px; ">

insert: <a class="anchor-link" href="#b23"> 2.3. Independent Internet number resources directly assigned by the RIPE NCC to Direct Assignment Users insert: </a> insert: </p>

insert: <h1>

insert: <b> A. Closure of Member LIR - Termination of the RIPE NCC Standard Service Agreement delete: </h2> delete: <p class="western"> insert: </b> insert: </h1>

insert: <p>

insert: </p>

insert: <p>

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

  • delete: <p class="western"> insert: <p>

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

  • delete: <p class="western"> insert: <p>

    Conform to the RIPE NCC Standard Terms and Conditions (STCs); and insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Conform to RIPE Policies.

delete: <p class="western"> insert: <p>

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

delete: <h2 class="western"> delete: <a name="1"> insert: <h3>

insert: <a name="a1"> 1. Grounds for Termination and Procedure termination and procedure in Each Case delete: </h2> delete: <p class="western"> each case insert: </h3>

insert: <p>

insert: <i> insert: <b> The SSA can be terminated by the Member Contributor (see section 1.1) or by the RIPE NCC. The termination by the RIPE NCC can either be with a notice period of three months (see section 1.2.1.) or, or for specific reasons, reasons with a shorter notice period and immediate effect (see section 1.2.2.). delete: </p> delete: <h3 class="western"> delete: <a name="11"> delete: </a> insert: </b> insert: </i> insert: </p>

insert: <h3>

insert: <a name="a11"> insert: </a> insert: <i> 1.1. Termination by the Member Contributor insert: </i>

delete: <p class="western"> insert: <p>

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

  • The Member Contributor decides to close or to change their business

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

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

delete: <p class="western"> insert: <p>

Procedure

delete: <p class="western"> insert: <p>

The notice will formally request the termination of the SSA.

delete: <p class="western"> insert: <p>

It must be:

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

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

delete: <p class="western"> insert: <p>

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

delete: <p class="western"> insert: <p>

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

delete: <p class="western"> insert: <p>

Billing Issues delete: </b> delete: </p> delete: <p class="western"> issues insert: </b> insert: </p>

insert: <p>

If the termination takes place in the course of a financial year, the annual contribution shall nevertheless remain due, due in full, full by the Member Contributor (see also paragraph 6.6 of the insert: <span> RIPE NCC Articles of Association (AoA) and the insert: </span> and the insert: <span> RIPE NCC Billing Procedure insert: </span> ).

delete: <h3 class="western"> delete: <a name="12"> insert: <h2>

insert: <i> insert: <a name="a12"> 1.2. Termination by the RIPE NCC delete: </h3> delete: <h4> delete: <a name="121"> insert: </i> insert: </h2>

insert: <h3>

insert: <a name="a121"> 1.2.1. Termination with a Three-Month Notice Period delete: </h4> delete: <p class="western"> three-month notice period insert: </h3>

insert: <p>

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

delete: <p class="western"> delete: </p> delete: <p> delete: <a name="1211"> delete: </a> delete: <b> 1.2.1.1 insert: <p>

insert: <b> insert: <a name="a1211"> insert: </a> 1.2.1.1. Violation of RIPE Policies and RIPE NCC Procedures delete: </b> delete: </p> delete: <p class="western"> The Member procedures insert: </b> insert: </p>

insert: <p>

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

delete: <ol class="listTypeLowerAlpha"> delete: <li> delete: <p class="western"> delete: <a name="1211a"> delete: </a> delete: <b> insert: <p>

insert: <b> insert: <a name="a1211a"> insert: </a> insert: </b> insert: <b> a. Unresponsiveness

delete: <p class="western"> The Member insert: <ol type="a">
    insert: </ol>
insert: <p>

The Contributor is unresponsive for a significant period of time.

delete: <p class="western"> Members insert: <p>

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

delete: </li> delete: <li> delete: <p class="western"> delete: <a name="1211b"> delete: </a> delete: <b> insert: <p>

insert: <b> insert: <a name="a1211b"> insert: </a> b. Allocations/assignments in contravention to contravening RIPE policies

delete: <p class="western"> insert: <p>

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

delete: </li> delete: <li> delete: <p class="western"> delete: <a name="1211c"> delete: </a> delete: <b> insert: <p>

insert: <b> insert: <a name="a1211c"> insert: </a> c. Incorrect registration in the RIPE Database

delete: <p class="western"> insert: <p>

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

delete: <p class="western"> insert: <p>

Proper registration must be as follows:

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

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

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

delete: </li> delete: <li> delete: <p class="western"> delete: <a name="1211d"> delete: </a> delete: <b> insert: <p>

insert: <b> insert: <a name="a1211d"> insert: </a> d. Non-compliance with RIPE NCC audits insert: </b> insert: </p>

insert: <p>

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

insert: <p>

insert: <b> insert: <a name="a1211e"> insert: </a> e. Non-compliance with an arbiter ruling

delete: <p class="western"> insert: <p>

For more information, please see delete: <span> RIPE NCC Conflict Arbitration Procedure delete: </span> .

delete: </li> delete: </ol> delete: <p class="western"> insert: <p>

Procedure

delete: <p class="western"> insert: <p>

If the RIPE NCC becomes aware of any of the aforementioned reasons for terminating the SSA, the RIPE NCC will s delete: <span> end will: insert: </p>

insert: <ul>
    insert: <li>
  • insert: <p>

    Send an email to the registered contact(s) indicating: delete: </span>

    • the violation

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

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

      delete: <p> delete: <span> The RIPE NCC will also terminate insert: </li>
    • insert: </ul>
    insert: </li>
  • insert: <li>
  • insert: <p>

    Terminate the progress of any open requests for RIPE NCC services delete: </span>

delete: <p class="western"> insert: <p>

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

  • The violation

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

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

delete: <p class="western"> insert: <p>

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

  • The violation

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

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

delete: <p class="western"> insert: <p>

After 90 days from the date of the first email, if the Member Contributor continues not to comply, the RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Member's Contributor's account) to all registered postal and email addresses of the Member. delete: </p> delete: <p class="western"> Contributor. insert: </p>

insert: <p>

insert: <b> insert: <a name="a1212"> insert: </a> 1.2.1.2 Provision of untruthful information insert: </b> insert: </p>

insert: <p>

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

delete: <a name="1212"> delete: </a> delete: <b> 1.2.1.2. Other Reasons delete: </b> delete: </p> delete: <p class="western"> Termination 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 class="western"> For example, such termination has taken place in the past in the case of the emergence of AfriNIC, the RIR for the African region, when, with the consent of the African Members, the SSAs with the RIPE NCC were terminated and new contracts with AfriNIC were signed. delete: </p> delete: <p class="western"> delete: <b> Procedure delete: </b> delete: </p> delete: <p class="western"> The notice will officially inform about the termination of the SSA, state the reasons for the termination and detail the planned arrangements regarding the Internet number resources that were distributed to the Member. delete: </p> delete: <p class="western"> Unless otherwise required by the circumstances: delete: </p> delete: <ul> delete: <li> delete: <p> The RIPE NCC will terminate the progress of any open requests for RIPE NCC services delete: </p> delete: </li> delete: <li> delete: <p> Section A.2. (Consequences of termination of the SSA) and section B (Deregistration of Internet number resources) of this document are applicable delete: </p> delete: </li> delete: </ul> delete: <p class="western"> The notice will be dated and signed by an authorised representative of the RIPE NCC. delete: </p> delete: <p class="western"> Notice will be sent to the registered contact(s) of the Member by electronic and postal mail. delete: </p> delete: <p class="western"> 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: <b> Billing Issues delete: </b> delete: </p> delete: <p class="western"> All outstanding amounts for the full year must be settled unless otherwise agreed. delete: </p> delete: <h3 class="western"> delete: <a name="122"> delete: </a> 1.2.2. Termination with Immediate Effect delete: </h3> 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: <ol class="listTypeLowerAlpha"> delete: <li> delete: <p> delete: <a name="122a"> delete: </a> delete: <b> Member files for bankruptcy, is liquidated, suspends its payments or becomes insolvent delete: </b> delete: </p> delete: <p> Upon receipt of the documents stating the bankruptcy, liquidation, suspension of payments or insolvency of the Member delete: <span> 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 delete: </span> fulfils delete: <span> the obligations coming from the SSA, the RIPE NCC will not terminate the SSA. delete: </span> delete: </p> delete: <p> delete: <b> Procedure delete: </b> delete: </p> delete: <p class="western"> 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 delete: </p> delete: </li> delete: </ul> delete: <p class="western"> The RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the member) to all registered contacts of the Member or to the legal successor, both by electronic and registered postal mail. delete: </p> delete: </li> delete: <li> delete: <p> delete: <a name="122b"> delete: </a> delete: <b> Member damages the name, trademarks or intellectual property rights of the RIPE NCC delete: </b> delete: </p> delete: <p> Examples: delete: </p> delete: <ul> delete: <li> delete: <p> The Member pretends to be, or to act on behalf of, the RIPE NCC through misuse of the RIPE NCC name or logo delete: </p> delete: </li> delete: <li> delete: <p> The 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: </p> delete: </li> delete: </ul> delete: <p> delete: <b> Procedure: delete: </b> delete: </p> delete: <p class="western"> 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/repair the violation delete: </p> delete: </li> delete: <li> delete: <p> The termination of the SSA if the violation continues delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> Terminate the progress of any open requests for RIPE NCC services delete: </p> delete: </li> delete: </ul> delete: <p class="western"> 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 class="western"> 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> delete: <p> Send a second reminder email to the registered contact(s) indicating the same as above delete: </p> delete: </li> delete: <li> delete: <p> Not approve any Internet number resource requests delete: </p> delete: </li> delete: </ul> delete: <p class="western"> After 90 days from the date of the first email, if the Member continues not to comply, the RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Send a third reminder email and a reminder by postal mail to the registered email and postal addresses indicating the same as above delete: </p> delete: </li> delete: <li> delete: <p class="western"> Stop providing any services to the Member delete: </p> delete: </li> delete: </ul> delete: <p class="western"> 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: </li> delete: <li> delete: <p> delete: <a name="122c"> delete: </a> delete: <b> Member fails to submit to the RIPE NCC a valid extract from the Commercial Trade Register or equivalent register delete: </b> delete: </p> delete: <p class="western"> 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 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 by the RIPE NCC, the RIPE NCC will terminate the SSA (see Article 9.4.d of the SSA). delete: </p> delete: <p> delete: <b> Procedure delete: </b> delete: </p> delete: <p class="western"> 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 delete: </p> delete: </li> delete: </ul> delete: <p class="western"> 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 class="western"> 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: </li> delete: <li> delete: <p> delete: <a name="122d"> delete: </a> delete: <b> The Member fails to observe any rule of applicable law delete: </b> delete: </p> delete: <p class="western"> 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: <b> Procedure delete: </b> delete: </p> delete: <p class="western"> 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 delete: </p> delete: </li> delete: </ul> delete: <p class="western"> 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: </li> delete: <li> delete: <p> delete: <a name="122e"> delete: </a> delete: <b> Non-payment delete: </b> . delete: </p> delete: <p> In case of non-payment, in accordance with the RIPE NCC Billing Procedure, the SSA is terminated after 120 days. For more information, please see the delete: <span> delete: <span> delete: <a href="https://www.ripe.net/lir-services/billing/procedure"> RIPE NCC Billing Procedure delete: </a> delete: </span> delete: </span> . delete: </p> delete: </li> delete: <li> delete: <p class="western"> delete: <a name="122f"> delete: </a> delete: <b> Termination of the RIPE NCC member status delete: </b> delete: </p> delete: <p class="western"> 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 AoA). delete: </p> delete: <p> delete: <b> Procedure delete: </b> delete: </p> delete: <p class="western"> 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 delete: </p> delete: </li> delete: </ul> delete: <p class="western"> 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: </li> delete: <li> delete: <a name="122g"> delete: </a> delete: <b> Untruthful information delete: </b> delete: <br /> delete: <p class="western"> 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: <ul> delete: <li> delete: <p class="western"> delete: <b> insert: <b> insert: <a name="a1212a"> insert: </a> a. Falsified/incorrect information

delete: </li> delete: </ul> delete: <p class="western"> insert: <p>

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

delete: <ul> delete: <li> delete: <p class="western"> delete: <b> insert: <p>

insert: <b> insert: <a name="a1212b"> insert: </a> b. Fraudulent requests

delete: </li> delete: </ul> delete: <p class="western"> insert: <p>

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

Procedure

delete: <p class="western"> The RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Send insert: <p>

If the RIPE NCC becomes aware of any of the aforementioned reasons for insert: </p>

insert: <p>

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

  • delete: <p> The reason for The Contributor's obligation to provide correct and true information insert: </li>
  • insert: <li>
  • The termination of the SSA delete: </p> delete: </li> delete: <li> delete: <p> The immediate if the Contributor does not comply with this obligation insert: </li>
  • insert: </ul>
insert: <p>

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

insert: <ul>
    insert: <li>
  • The Contributor's obligation to provide correct and true information insert: </li>
  • insert: <li>
  • The termination of the SSA delete: </p> the next time the Contributor sends falsified/incorrect information or fraudulent requests
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 class="western"> The insert: <p>

If the Contributor continues to send falsified/incorrect information or fraudulent requests, the RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Member's Contributor's account) to all registered postal and email addresses of the Member. delete: </p> delete: </li> delete: <li> delete: <a name="122h"> delete: </a> delete: <b> Non-compliance Contributor. insert: </p>

insert: <p>

insert: <b> insert: <a name="a1213"> insert: </a> 1.2.1.3 Other reasons insert: </b> insert: </p>

insert: <p>

Termination for any other reason by the RIPE NCC is only executed when the Contributor consents to the termination, unless the termination is for reasons above and beyond control of the RIPE NCC. insert: </p>

insert: <p>

For example, such termination has taken place in the past in the case of the emergence of AfriNIC, the RIR for the African region, when, with RIPE NCC audits delete: </b> delete: <br /> delete: <p class="western"> Non-compliance the consent of the African Contributors, the SSAs with RIPE NCC audits includes repeated unresponsiveness to the RIPE NCC were terminated and new contracts with AfriNIC were signed. insert: </p>

insert: <p>

insert: <b> Procedure insert: </b> insert: </p>

insert: <p>

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

insert: <p>

Unless otherwise required by the circumstances: insert: </p>

insert: <ul>
    insert: <li>
  • insert: <p>

    The RIPE NCC will terminate the progress of any open requests for RIPE NCC services insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Section A.2. (Consequences of termination of the SSA) and section B (Deregistration of Internet number resources) of this document are applicable insert: </p>

    insert: </li>
  • insert: </ul>
insert: <p>

The notice will be dated and signed by an authorised representative of the RIPE NCC. insert: </p>

insert: <p>

Notice will be sent to the registered contact(s) of the Contributor by electronic and postal mail. insert: </p>

insert: <p>

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

insert: <p>

insert: <b> Billing issues insert: </b> insert: </p>

insert: <p>

All outstanding amounts for the full year must be settled unless otherwise agreed. insert: </p>

insert: <h3>

insert: <a name="a122"> insert: </a> 1.2.2. Termination with immediate effect insert: </h3>

insert: <p>

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

insert: <p>

insert: <b> insert: <a name="a122a"> insert: </a> a. Contributor files for bankruptcy, is liquidated, suspends its payments 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 delete: <span> delete: <span> delete: <a href="http://www.ripe.net/ripe/docs/audit"> RIPE NCC audit activity delete: </a> delete: </span> delete: </span> . becomes insolvent insert: </b> insert: </p>

insert: <p>

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

Procedure

delete: <p class="western"> insert: <p>

The RIPE NCC will:

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

    insert: </li>
  • insert: </ul>
insert: <ul>
    • The reason for termination of the SSA

    • The immediate termination of the SSA

    delete: </li> insert: </ul>
insert: <ul>
  • Terminate the progress of any open requests for RIPE NCC services

delete: <p class="western"> insert: <p>

The RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Member's account) member) to all registered contacts of the Contributor or to the legal successor, both by electronic and registered postal and email addresses of the Member. delete: </p> delete: </li> delete: <li> delete: <a name="122i"> delete: </a> delete: <b> Discontinuation of RIPE NCC services delete: </b> delete: <br /> delete: <p class="western"> If 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 mail. insert: </p>

insert: <p>

insert: <b> insert: <a name="a122b"> insert: </a> b. Contributor damages the name, trademarks or intellectual property rights of the RIPE NCC insert: </b> insert: </p>

insert: <p>

Examples: insert: </p>

insert: <ul>
    insert: <li>
  • insert: <p>

    The Contributor pretends to be, or to act on behalf of, the RIPE NCC through misuse of the RIPE NCC name or generally accepted principles. delete: </p> delete: <p> delete: <b> Procedure delete: </b> delete: </p> delete: <p class="western"> The RIPE NCC will: logo insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    The Contributor unreasonably makes allegations against the RIPE NCC in order to damage the RIPE NCC's reputation and operations, resulting in irreversible damage to the RIPE NCC insert: </p>

    insert: </li>
  • insert: </ul>
insert: <p>

insert: <b> Procedure: insert: </b> insert: </p>

insert: <p>

The RIPE NCC will

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

    • The reason for the violation insert: </p>

      insert: </li>
    • insert: <li>
    • insert: <p>

      the Contributor's obligation to stop/repair the violation insert: </p>

      insert: </li>
    • insert: <li>
    • insert: <p>

      the termination of the SSA delete: </p> delete: </li> delete: <li> delete: <p> The immediate termination of the SSA if the violation continues

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

delete: <p class="western"> The insert: <p>

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

insert: <p>

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

insert: <ul>
    insert: <li>
  • insert: <p>

    Send a second reminder email to the registered contact(s) indicating the same as above insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Not approve any Internet number resource requests insert: </p>

    insert: </li>
  • insert: </ul>
insert: <p>

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

insert: <ul>
    insert: <li>
  • insert: <p>

    Send a third reminder email and a reminder by postal mail to the registered email and postal addresses indicating the same as above insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Stop providing any services to the Contributor insert: </p>

    insert: </li>
  • insert: </ul>
insert: <p>

After 120 days from the date of the first email, if the Contributor still does not comply, the RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Member's Contributor's account) to all registered postal and email addresses of the Member. delete: </p> delete: </li> delete: </ol> delete: <h2 class="western"> delete: <a name="2"> Contributor. insert: </p>

insert: <p>

insert: <b> insert: <a name="a122c"> insert: </a> c. Contributor fails to submit to the RIPE NCC a valid extract from the Commercial Trade Register or equivalent register insert: </b> insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

If the Contributor is a legal person, identification papers are also required for the authorised person signing the SSA on behalf of the legal person. insert: </p>

insert: <p>

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

insert: <p>

If the Contributor does not submit the aforementioned documents within one month of them being requested by the RIPE NCC, the RIPE NCC will terminate the SSA. insert: </p>

insert: <p>

insert: <b> Procedure insert: </b> insert: </p>

insert: <p>

The RIPE NCC will: insert: </p>

insert: <ul>
    insert: <li>
  • insert: <p>

    Send an email to the registered contact(s) indicating: insert: </p>

    insert: <ul>
      insert: <li>
    • insert: <p>

      the Contributor's obligation to submit the relevant documents insert: </p>

      insert: </li>
    • insert: <li>
    • insert: <p>

      the termination of the SSA if the documents are not submitted insert: </p>

      insert: </li>
    • insert: </ul>
    insert: </li>
  • insert: <li>
  • insert: <p>

    Terminate the progress of any open requests for RIPE NCC services insert: </p>

    insert: </li>
  • insert: </ul>
insert: <p>

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

insert: <p>

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

insert: <p>

insert: <b> insert: <a name="a122d"> insert: </a> d. The Contributor fails to observe any rule of applicable law insert: </b> insert: </p>

insert: <p>

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

insert: <p>

insert: <b> Procedure insert: </b> insert: </p>

insert: <p>

The RIPE NCC will: insert: </p>

insert: <ul>
    insert: <li>
  • insert: <p>

    Send an email to the registered contact(s) indicating: insert: </p>

    insert: </li>
  • insert: </ul>
insert: <ul>
    insert: <ul>
      insert: <li>
    • insert: <p>

      The reason for termination of the SSA insert: </p>

      insert: </li>
    • insert: <li>
    • insert: <p>

      The immediate termination of the SSA insert: </p>

      insert: </li>
    • insert: </ul>
    insert: </ul>
insert: <ul>
    insert: <li>
  • insert: <p>

    Terminate the progress of any open requests for RIPE NCC services insert: </p>

    insert: </li>
  • insert: </ul>
insert: <p>

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

insert: <p>

insert: <b> insert: <a name="a122e"> insert: </a> e. Non-payment insert: </b> . insert: </p>

insert: <p>

In case of non-payment, in accordance with the RIPE NCC Billing Procedure, the SSA is terminated after 120 days. For more information, please see the insert: <span> insert: <a href="http://www.ripe.net/lir-services/billing/procedure"> RIPE NCC Billing Procedure insert: </a> insert: </span> . insert: </p>

insert: <p>

insert: <b> insert: <a name="a122f"> insert: </a> f. Termination of the Contributor's member status insert: </b> insert: </p>

insert: <p>

By signing the SSA, Contributors become members of the RIPE NCC association. If Contributors cancel their member status with the RIPE NCC association, the SSA is automatically terminated. insert: </p>

insert: <p>

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

insert: <p>

insert: <b> Procedure insert: </b> insert: </p>

insert: <p>

The RIPE NCC will: insert: </p>

insert: <ul>
    insert: <li>
  • insert: <p>

    Send an email to the registered contact(s) indicating: insert: </p>

    insert: </li>
  • insert: </ul>
insert: <ul>
    insert: <ul>
      insert: <li>
    • insert: <p>

      The reason for termination of the SSA insert: </p>

      insert: </li>
    • insert: <li>
    • insert: <p>

      The immediate termination of the SSA insert: </p>

      insert: </li>
    • insert: </ul>
    insert: </ul>
insert: <ul>
    insert: <li>
  • insert: <p>

    Terminate the progress of any open requests for RIPE NCC services insert: </p>

    insert: </li>
  • insert: </ul>
insert: <p>

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

insert: <h2>

insert: <a name="a2"> 2. Consequences

delete: <p class="western"> insert: <p>

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

delete: <h3 class="western"> delete: <a name="21"> delete: </a> delete: <span> insert: <h3>

insert: <i> insert: <a name="a21"> insert: </a> 2.1. delete: </span> delete: <span> End of Provision of RIPE NCC Services delete: </span> provision of RIPE NCC services insert: </i>

delete: <h4> delete: <a name="211"> delete: </a> insert: <h3>

insert: <a name="a211"> insert: </a> insert: <b> 2.1.1. General Services delete: </h4> delete: <p class="western"> services insert: </b> insert: </h3>

insert: <p>

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

  • Distribution of Internet number resources

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

  • Access to the LIR Portal

  • Use of the RIPE NCC Certification Service

  • Participation in RIPE NCC Training Courses

delete: <h4> delete: <a name="212"> insert: <h3>

insert: <i> insert: <a name="a212"> 2.1.2. Registration of Distributed Internet Number Resources delete: </h4> delete: <p class="western"> distributed Internet number resources insert: </i> insert: </h3>

insert: <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: <h4> delete: <a name="213"> insert: <h3>

insert: <i> insert: <a name="a213"> 2.1.3. Request for Independent Internet Number Resources independent Internet number resources as a “Sponsoring “sponsoring LIR” delete: </h4> delete: <p class="western"> Members insert: </i> insert: </h3>

insert: <p>

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

delete: <h3 class="western"> delete: <a name="22"> insert: <h2>

insert: <b> insert: <a name="a22"> 2.2. End of RIPE NCC Member Status delete: </h3> delete: <p class="western"> Members Contributor's RIPE NCC member status insert: </b> insert: </h2>

insert: <p>

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

delete: <h2 class="western"> delete: <a name="b"> delete: </a> insert: <p>

insert: </p>

insert: <h1>

insert: <b> B. Deregistration of Internet Number Resources delete: </h2> delete: <h3 class="western"> insert: </b> insert: </h1>

insert: <p>

insert: <b> insert: <br />
insert: </b>
insert: </p>

insert: <h3>

1. Reasons for Deregistration of Internet Number Resources - deregistration of Internet number resources insert: </h3>

insert: <h3>

insert: <a name="b11"> insert: </a> insert: <i> 1.1 Allocations and Independent Internet Number Resources Assigned for the Member's Own Network number resources assigned for the Contributor's own network or Assigned Through a “Sponsoring assigned through a “sponsoring LIR” insert: </i>

delete: <ol class="listTypeLowerAlpha"> delete: <li> delete: <p> delete: <a name="b1a"> delete: </a> delete: <b> insert: <p>

insert: <b> insert: <a name="b11a"> insert: </a> a. Termination of the SSA

delete: <p class="western"> insert: <p>

For more information, see section A. For independent Independent Internet number resources through a “sponsoring LIR”, see delete: <span> delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/lir-end-user-contractual-changes" target="_self" title=""> insert: <a href="http://www.ripe.net/ripe/docs/lir-end-user-contractual-changes"> Independent Internet Number Resources – Contractual Relationship Changes between Sponsoring sponsoring LIR and End User delete: </span> .

delete: </li> delete: <li> delete: <p> delete: <a name="b1b"> delete: </a> delete: <b> insert: <p>

insert: </p>

insert: <p>

insert: <b> insert: <a name="b11b"> insert: </a> b. Invalidity of original allocation/assignment criteria

delete: <p class="western"> insert: <p>

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

delete: </li> delete: <li> delete: <p class="western"> delete: <a name="b1c"> delete: </a> delete: <b> Incorrect insert: <p>

insert: <b> insert: <a name="b11c"> insert: </a> c.Incorrect registration of the allocation/assignment in the RIPE Database

delete: <p class="western"> insert: <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 class="western"> insert: <p>

Proper registration must be as follows:

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

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

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

delete: </li> delete: <li> delete: <p> delete: <a name="b1d"> delete: </a> delete: <b> insert: <p>

insert: <b> insert: <a name="b11d"> insert: </a> d. Falsified/incorrect information

delete: <p class="western"> insert: <p>

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

delete: </li> delete: <li> delete: <p class="western"> delete: <a name="b1e"> delete: </a> delete: <b> insert: <p>

insert: <b> insert: <a name="b11e"> insert: </a> e. Fraudulent request

delete: <p class="western"> insert: <p>

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

delete: </li> delete: <li> delete: <p class="western"> delete: <a name="b1f"> delete: </a> delete: <b> insert: <p>

insert: <b> insert: <a name="b11f"> insert: </a> f. Non-compliance with a RIPE NCC audit

delete: <p class="western"> insert: <p>

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

delete: </li> delete: <li> delete: <p class="western"> delete: <a name="b1g"> delete: </a> delete: <b> insert: <p>

insert: <b> insert: <a name="b11g"> insert: </a> g. Court order

delete: <p class="western"> insert: <p>

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

delete: </li> delete: <li> delete: <p class="western"> delete: <a name="b1h"> delete: </a> delete: <b> insert: <p>

insert: <b> insert: <a name="b11h"> insert: </a> h. Independent Internet number resources assigned through a “sponsoring LIR” without an valid contractual relationship

delete: <p class="western"> insert: <p>

See delete: <span> delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/lir-end-user-contractual-changes" target="_self" title=""> insert: <a href="http://www.ripe.net/ripe/docs/lir-end-user-contractual-changes"> Independent Internet Number Resources – Contractual Relationship Changes between Sponsoring sponsoring LIR and End User . insert: </p>

insert: <h2>

insert: <i> insert: <a name="b12"> insert: </a> 1.2 Independent Internet number resources directly assigned by the RIPE NCC for Direct Assignment Users insert: </i> insert: </h2>

insert: <p>

insert: <b> insert: <a name="b12a"> insert: </a> a. Termination of the RIPE NCC End User Assignment Agreement insert: </b> insert: </p>

insert: <p>

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

insert: <p>

insert: <b> insert: <a name="b12b"> insert: </a> b. Unresponsive Direct Assignment User insert: </b> insert: </p>

insert: <p>

Direct Assignment Users are considered to be unresponsive if they do not react to a specific email/request made by the RIPE NCC relating to an incorrect/ambiguous registration of Internet number resources, regardless of whether they are at the same time responsive to a different email/request from the RIPE NCC or they continue paying the RIPE NCC fees (see also the RIPE Policy insert: <span> insert: <a href="http://www.ripe.net/ripe/docs/contract-req"> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region insert: </a> . delete: </p> delete: </li> delete: </ol> delete: <h2 class="western"> delete: <a name="b2"> delete: </a> 2. Procedures for Deregistration of Different Types of Internet Number Resources delete: </h2> delete: <h3 class="western"> delete: <a name="b21"> delete: </a> 2.1 Allocations and Independent Internet Number Resources for Member's Own Network delete: </h3> delete: <p class="western"> The RIPE NCC will send an official notification ). insert: </p>

insert: <p>

insert: <b> insert: <a name="b12c"> insert: </a> c. Invalidity of original criteria insert: </b> insert: </p>

insert: <p>

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

insert: <p>

insert: <b> insert: <a name="b12d"> insert: </a> d. Incorrect registration of the assignment in the RIPE Database insert: </b> insert: </p>

insert: <p>

If the Direct Assignment User does not properly register in the RIPE Database the assignment approved by email to all registered contacts stating that the allocation/independent Internet number resources will the RIPE NCC, the RIPE NCC is authorised to deregister the relevant Internet number resources. insert: </p>

insert: <p>

Proper registration must be deregistered, explaining the reasons for this deregistration and the procedure of the deregistration. The Member will as follows: insert: </p>

insert: <ul>
    insert: <li>
  • insert: <p>

    The insert: <b> inetnum insert: </b> and the insert: <b> inet6num insert: </b> object(s) for approved assignments must use the netname(s) approved by the RIPE NCC and not be able make any further assignments from the allocations. delete: </p> delete: <p class="western"> 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: </p> delete: <p class="western"> delete: <span> delete: <span> delete: <a href="http://www.ripe.net/membership/indices"> http://www.ripe.net/membership/indices delete: </a> delete: </span> delete: </span> delete: </p> delete: <p class="western"> During the three-month period: delete: </p> delete: <ul> delete: <li> delete: <p> The Member must stop announcing the allocation/independent Internet number resources delete: </p> delete: </li> delete: <li> delete: <p> The RIPE NCC will change the delete: <b> mnt-by delete: </b> larger than the size approved by the RIPE NCC insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    The date in the first “changed:” attribute on the Member's inetnum object to RIPE NCC maintainer and change the status attribute to “deregistered maintainer” delete: </p> delete: </li> delete: <li> delete: <p> A warning statement is added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources delete: </p> delete: </li> delete: <li> delete: <p> The RIPE NCC will revoke any certificates generated by the RIPE NCC Certification Service delete: </p> delete: </li> delete: </ul> delete: <p class="western"> After the three-month period, the allocation/assignment will be deregistered from the RIPE Database. delete: </p> delete: <p class="western"> Should the Member not react within four weeks, the RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Change the delete: <b> mnt-by delete: </b> attribute on the Member's inetnum object to RIPE NCC maintainer and change the status attribute to “deregistered maintainer”; and/or delete: </p> delete: </li> delete: <li> delete: <p> Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the Internet number resources; and/or delete: </p> delete: </li> delete: <li> delete: <p> Withdraw the reverse delegation; and/or delete: </p> delete: </li> delete: <li> delete: <p> Contact the upstream to investigate possible hijacking of Internet number resources; and/or delete: </p> delete: </li> delete: <li> delete: <p> Delete all relevant objects in the RIPE Database, including allocation/assignment and delete: <b> route delete: </b> objects delete: </p> delete: </li> delete: <li> delete: <p> Revoke any certificates generated by the RIPE NCC Certification Service. delete: </p> delete: </li> delete: </ul> delete: <p class="western"> The sole purpose of these actions by the RIPE NCC is for deregistration of the Internet number resources to reflect reality. As a result, if the Internet number resources are no longer announced after one of these actions, the RIPE NCC might not perform any other actions. delete: </p> delete: <p class="western"> Please note: delete: </p> delete: <p class="western"> 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 delete: <span> delete: <span> delete: <a href="http://www.ripe.net/ripe/docs/arbitration"> RIPE NCC Conflict Arbitration Procedure delete: </a> delete: </span> delete: </span> ). 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 change the delete: <b> mnt-by delete: </b> object on the relevant records to the status “maintainer in dispute” and a warning statement will be added to the relevant records of the RIPE Database until the communication of the arbiter's ruling. delete: </p> delete: <h3 class="western"> delete: <a name="b22"> delete: </a> 2.2 Independent Internet Number Resources Assigned Through a “Sponsoring LIR” delete: </h3> delete: <p class="western"> 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 class="western"> During this period: delete: </p> delete: <ul> delete: <li> delete: <p> The End User must stop announcing the Independent Internet number resources delete: </p> delete: </li> delete: <li> delete: <p> The RIPE NCC will change the delete: <b> mnt-by delete: </b> attribute on the relevant object to RIPE NCC maintainer and change the status attribute to “deregistered maintainer” delete: </p> delete: </li> delete: <li> delete: <p> A warning statement is added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources delete: </p> delete: </li> delete: </ul> delete: <p class="western"> After the three-month period, the independent Internet number resources will be deregistered from the RIPE Database. delete: </p> delete: <p class="western"> Should the Member not react within four weeks, the RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Change the delete: <b> mnt-by delete: </b> attribute on the relevant object to RIPE NCC maintainer and change the status attribute to “deregistered maintainer”; and/or delete: </p> delete: </li> delete: <li> delete: <p> Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the Internet number resources; and/or delete: </p> delete: </li> delete: <li> delete: <p> Withdraw the reverse delegation; and/or delete: </p> delete: </li> delete: <li> delete: <p> Contact the upstream to investigate possible hijacking of Internet number resources; and/or delete: </p> delete: </li> delete: <li> delete: <p> Delete all relevant objects in the RIPE Database, including allocation/assignment and delete: <b> route delete: </b> objects delete: </p> delete: </li> delete: </ul> delete: <p class="western"> The sole purpose of these actions by the RIPE NCC is for deregistration of the Internet number resources to reflect reality. As a result, if the Internet number resources are no longer announced after one of these actions, the RIPE NCC might not perform any other actions. delete: </p> delete: <p class="western"> Please note: delete: </p> delete: <p class="western"> 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 delete: <span> delete: <span> delete: <a href="http://www.ripe.net/ripe/docs/arbitration"> RIPE NCC Conflict Arbitration Procedure delete: </a> delete: </span> delete: </span> ). 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 change the delete: <b> mnt-by delete: </b> object on the relevant records to the status “maintainer in dispute” and a warning statement will be added to the relevant records of the RIPE Database until the communication of the arbiter's ruling. delete: </p> delete: <p class="western"> delete: </p> delete: <h2 class="western"> delete: <a name="c"> delete: </a> delete: <span> delete: <span> C. Legacy Internet Resources delete: </span> delete: </span> delete: </h2> delete: <h2> delete: <a name="c1"> delete: </a> delete: <span> delete: <span> 1. Termination of the Legacy Services delete: </span> delete: </span> delete: </h2> delete: <p> delete: <span> This Section describes the reasons for the termination of: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The Legacy Services the RIPE NCC provides to a Member pursuant to the Terms and Conditions Regarding Legacy Internet Resources for Members (section 1.1), delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The Legacy Agreement between the RIPE NCC and a Legacy Holder (section 1.2) delete: </span> delete: </p> delete: </li> delete: </ul> delete: <h3> delete: <a name="c11"> delete: </a> 1.1 Legacy Services by the RIPE NCC to a Member pursuant to the Terms and Conditions Regarding Legacy Internet Resources for Members delete: </h3> delete: <p> delete: <span> 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: </span> delete: </p> delete: <h4> delete: <a name="c111"> delete: </a> 1.1.1. Termination by the Member delete: </h4> delete: <p> delete: <span> 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 of three months. delete: </span> delete: </p> delete: <p> delete: <span> delete: <b> Procedure delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> The notice will formally request the termination of the Legacy Services. delete: </span> delete: </p> delete: <p> delete: <span> It must be delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> Dated and signed by an authorised representative of the Member. delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> Sent to the RIPE NCC by email to <…> or by postal mail to: [address] delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> 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: </span> delete: </p> delete: <p> delete: <span> The termination of the Legacy Services will take place three months after the receipt of the notice by the RIPE NCC. delete: </span> delete: </p> delete: <h4> delete: <a name="c112"> delete: </a> 1.1.2. Termination by the RIPE NCC delete: </h4> delete: <p> delete: <a name="c1121"> delete: </a> delete: <span> delete: <b> 1.1.2.1. Non compliance with contractual responsibilities delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> According to Article 5.3 of the Terms and Conditions Regarding Legacy Internet Resources for Members, the RIPE NCC can terminate the Legacy Services. Grounds for such termination may be the following: delete: </span> delete: </p> delete: <ol type="a"> delete: <li> delete: <p> delete: <span> The Member does no provide the RIPE NCC with complete, updated and accurate information necessary for the provision of the Legacy Services. delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The Member does not maintain accurate data in the RIPE Database regarding the Legacy Internet Resources. delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> 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 title="" href="https://www.ripe.net/publications/docs/due-diligence" class="external-link" target="_self"> Due Diligence for the Quality of the RIPE NCC Registration Data delete: </a> ”, “ delete: <a data-linktype="internal" target="_self" title="" href="./resolveuid/db489aea245ca2a1b81478bf121c58ab" data-val="db489aea245ca2a1b81478bf121c58ab" class="external-link"> RIPE NCC Audit Activity delete: </a> ”. delete: </span> delete: </p> delete: </li> delete: </ol> delete: <p> delete: <span> delete: <b> Procedure delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> If the RIPE NCC becomes aware of any of the aforementioned reasons for terminating the Legacy Services, the RIPE NCC will: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> Send an email to the registered contact(s) indicating delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The violation delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The Member's obligation to stop/repair the violation delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The termination of the Legacy Services in three months if the violation continues delete: </span> delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> delete: <span> Terminate the progress of any open requests related to Legacy Services delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> Add the remark "under review" in the RIPE Database resource object. delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> 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: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> Revoke any certificates generated by the RIPE NCC Certification Service Relating to Legacy Internet Resources. delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> 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: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The violation delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The Member's obligation to stop/repair the violation delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The termination of the Legacy Services in two months if the violation continues delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> 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: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The violation delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The Member's obligation to stop/repair the violation delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The termination of the Legacy Services in one month if the violation continues delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> After 90 days from the date of the first email, if the Member continues not to 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: </span> delete: <br /> delete: <br /> delete: </p> delete: <p> delete: <a name="c1122"> delete: </a> delete: <span> delete: <b> 1.1.2.2. Termination with immediate effect delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> 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: </span> delete: </p> delete: <ol class="listTypeLowerAlpha"> delete: <li> delete: <a name="c1122a"> delete: </a> delete: <strong> The Member's SSA is terminated for any reason. delete: </strong> delete: <br /> Upon termination of the Member's SSA (see section A of this document), the Legacy Services are also terminated without any further notification to be necessary. delete: </li> delete: <li> delete: <a name="c1122b"> delete: </a> delete: <strong> The Member transfers the Legacy Internet Resources to a third party. delete: </strong> delete: <br /> 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: </li> delete: <li> delete: <a name="c1122c"> delete: </a> delete: <strong> Member has no rights to use the Legacy Internet Resources delete: </strong> delete: <br /> 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: <br /> 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: </li> delete: <li> delete: <a name="c1122d"> delete: </a> delete: <strong> Reasons beyond control of the RIPE NCC delete: </strong> delete: <br /> 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 delete: <span> which the RIPE NCC cannot be held accountable by virtue of law, a juridical act or generally accepted principles. delete: </span> delete: </li> delete: </ol> delete: <p> delete: </p> delete: <p> delete: <span> delete: <b> Procedure delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> The RIPE NCC will: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> Send an email to the registered contact(s) indicating: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The reason for termination of the Legacy Services delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The immediate termination of the Legacy Services delete: </span> delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> delete: <span> Terminate the progress of any open requests related to Legacy Services delete: </span> delete: </p> delete: </li> delete: </ul> delete: <h3> delete: <a name="c12"> delete: </a> 1.2 Legacy Agreement between the RIPE NCC and a Legacy Holder delete: </h3> delete: <p> delete: <span> The Legacy Agreement can be terminated by the Legacy Holder (see section 1.2.1) or by the RIPE NCC. The Termination by the RIPE NCC can either be with a notice period of three months (see section 1.2.2.1) or for specific reasons with a shorter notice period and immediate effect (see section 1.2.2.2). delete: </span> delete: </p> delete: <h4> delete: <a name="c121"> delete: </a> 1.2.1. Termination by the Legacy Holder delete: </h4> delete: <p> delete: <span> According to Article 7.2 of the Legacy Agreement for Members, the Member shall be entitled to terminate the Legacy Agreement at any time with a written notice of three months. delete: </span> delete: </p> delete: <p> delete: <span> delete: <b> Procedure delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> The notice will formally request the termination of the Legacy Agreement. delete: </span> delete: </p> delete: <p> delete: <span> It earlier than the date of approval from the RIPE NCC insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    The data must be delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p align="LEFT"> delete: <span> Dated and signed by an authorised representative of the Legacy Holder. delete: </span> delete: </p> delete: </li> delete: <li> delete: <p align="LEFT"> delete: <span> Sent to the RIPE NCC by email to <…> valid and must allow the RIPE NCC to contact the natural person referenced directly in the insert: <b> inetnum insert: </b> or by postal mail to: [address] delete: </span> insert: <b> inet6num insert: </b> object(s) or via the maintainers of the insert: <b> inetnum insert: </b> or insert: <b> inet6num insert: </b> object(s) within a reasonable time without having to get information from another source

delete: <span> 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: </span> delete: </p> delete: <p> delete: <span> The termination of the Legacy Agreement will take place three months after the receipt of the notice by the RIPE NCC. delete: </span> delete: </p> delete: <p> delete: <span> delete: <b> Billing issues delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> All outstanding amounts for the full year must be settled unless otherwise agreed. delete: </span> delete: </p> delete: <h4> delete: <a name="c122"> delete: </a> 1.2.2. Termination by the RIPE NCC delete: </h4> delete: <p> delete: <a name="c1221"> delete: </a> delete: <span> delete: <b> 1.2.2.1. Non compliance with contractual responsibilities delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> 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: </span> delete: </p> delete: <ol type="a"> delete: <li> delete: <p> delete: <span> The Legacy Holder does no provide the RIPE NCC with complete, updated and accurate insert: <b> insert: <a name="b12e"> insert: </a> e. Falsified/ incorrect information necessary for the provision of the service under the Legacy Agreement. delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The Legacy Holder does not maintain accurate data in the RIPE Database regarding the Legacy Internet Resources. delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The Legacy 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 title="" href="https://www.ripe.net/publications/docs/due-diligence" class="external-link" target="_self"> Due Diligence for the Quality of the RIPE NCC Registration Data delete: </a> ”, “ delete: <a data-linktype="internal" target="_self" title="" href="./resolveuid/db489aea245ca2a1b81478bf121c58ab" data-val="db489aea245ca2a1b81478bf121c58ab" class="external-link"> RIPE NCC Audit Activity delete: </a> ”. delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The Legacy Holder does not comply with an arbiter ruling (see delete: <a data-linktype="internal" target="_self" title="" href="./resolveuid/b81490fe2c00243a37cb5c5ffaab8f6e" data-val="b81490fe2c00243a37cb5c5ffaab8f6e" class="external-link"> RIPE NCC Conflict Arbitration Procedure delete: </a> ). delete: </span> delete: </p> delete: </li> delete: </ol> delete: <p> delete: <span> delete: <b> Procedure delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> insert: </b> insert: </p>

insert: <p>

If the RIPE NCC becomes aware of any of the aforementioned reasons for terminating the Legacy Agreement, the RIPE NCC will: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> Send an email to the registered contact(s) of the Legacy Holder indicating: delete: </span> delete: </p> delete: </li> delete: </ul> delete: <ul> delete: <ul> delete: <li> delete: <p> delete: <span> The violation delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The Legacy Holder's obligation to stop/repair the violation delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The termination of the Legacy Agreement in three months if the violation continues delete: </span> delete: </p> delete: </li> delete: </ul> delete: <li> delete: <p> delete: <span> Terminate the progress of any open requests related to the Legacy Agreement delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> Add the remark "under review" in the RIPE Database resource object. delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> 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: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> Revoke any certificates generated by the RIPE NCC Certification Service relating to Legacy Internet Resources delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> If the Legacy 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: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The violation delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The Legacy Holder's obligation to stop/repair the violation delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The termination of the Legacy Agreement in two months if the violation continues delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> After 60 days from the date of the first email, if the Legacy 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: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The violation delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The Legacy Holder's obligation to stop/repair the violation delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The termination of the Legacy Agreement in one month if the violation continues delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> After 90 days from the date of the first email, if the Legacy Holder continues not to 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 Holder. delete: </span> delete: </p> delete: <p> delete: <span> delete: <b> Billing issues delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> All outstanding amounts for the full year must be settled unless otherwise agreed. delete: </span> delete: </p> delete: <p> delete: </p> delete: <p> delete: <a name="c1222"> delete: </a> delete: <span> delete: <b> 1.2.2.2. Termination with immediate effect delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> According to Article 7.4 of the Legacy Agreement, the RIPE NCC can terminate the Agreement with immediate effect for the following reasons: delete: </span> delete: </p> delete: <ol class="listTypeLowerAlpha"> delete: <li> delete: <p> delete: <a name="c1222a"> delete: </a> delete: <span> delete: </span> delete: <span> delete: <b> Legacy Holder files for bankruptcy, is liquidated, suspends its payments or becomes insolvent delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> delete: <span> Upon receipt of the documents stating the bankruptcy, liquidation, suspension of payments or insolvency of the Legacy Holder delete: </span> delete: <span> 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 delete: </span> delete: <span> delete: <span> Legacy Holder delete: </span> delete: </span> ' delete: <span> s operations can continue, and a Direct Assignment User has provided that the Legacy Holder fulfills the obligations coming from the Legacy Agreement, the RIPE NCC will not terminate the Legacy Agreement. delete: </span> delete: </span> delete: </p> delete: <p> delete: <span> delete: <span> delete: <b> Procedure delete: </b> delete: </span> delete: </span> delete: </p> delete: <p> delete: <span> The RIPE NCC will: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> Send an email to the registered contact(s) and/or to the legal successor indicating: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The reason for termination of the Legacy Agreement delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The immediate termination of the Legacy Agreement delete: </span> delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> delete: <span> Terminate the progress of any open requests related to the Legacy Agreement delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> The RIPE NCC Managing Director will send an official notification of termination of the Legacy Agreement to all registered contacts of the Legacy Holder or to the legal successor, both by electronic and registered postal mail. delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <a name="c1222b"> delete: </a> delete: <span> delete: <b> Legacy Holder damages the name, trademarks or intellectual property rights of the RIPE NCC delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> Examples: delete: </span> delete: </p> delete: <p> delete: <span> The Legacy Holder pretends to be, or to act on behalf of, the RIPE NCC through misuse of the RIPE NCC name or logo delete: </span> delete: </p> delete: <p> delete: <span> The Legacy 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: </span> delete: </p> delete: <p> delete: <span> delete: <b> Procedure: delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> The RIPE NCC will delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> Send an email to the registered contact(s) indicating: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The violation delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The delete: <span> Legacy Holder delete: </span> 's obligation to stop/repair the violation delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The termination of the SSA if the violation continues delete: </span> delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> delete: <span> Terminate the progress of any open requests related to the Legacy Agreement delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> delete: <span> If the Legacy 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: </span> delete: </span> delete: </p> delete: <p> delete: <span> delete: <span> After 60 days from the date of the first email, if the Legacy 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: </span> delete: </span> delete: </p> delete: <p> delete: <span> delete: <span> After 90 days from the date of the first email, if the Legacy Holder continues not to comply, the RIPE NCC will send a third reminder email and a reminder by postal mail to the registered email and postal addresses indicating the same as above. delete: </span> delete: </span> delete: </p> delete: <p> delete: <span> delete: <span> After 120 days from the date of the first email, if the Legacy Holder still does not comply, the delete: </span> RIPE NCC Managing Director will send an official notification of termination of the Legacy Agreement to all registered postal and email addresses of the delete: <span> Legacy Holder delete: </span> . delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <a name="c1222c"> delete: </a> delete: <span> delete: <b> Member fails to submit to the RIPE NCC a valid extract from the Commercial Trade Register or equivalent register delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> When initially signing the Legacy Agreement, the delete: <span> Legacy Holder delete: </span> must submit to the RIPE NCC an extract from the Commercial Trade Register or equivalent document providing the registration of the delete: <span> Legacy Holder delete: </span> 's business with the national authorities (see Article 2.2 of the Legacy Agreement). delete: </span> delete: </p> delete: <p> delete: <span> delete: <span> If the Legacy Holder is delete: </span> delete: <span> 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: </span> delete: </span> delete: </p> delete: <p> delete: <span> If the Legacy Holder is a legal person, identification papers are also required for the authorised person signing the Legacy Holder on behalf of the legal person. delete: </span> delete: </p> delete: <p> delete: <span> If there is any change in the Legacy Holder's business after signing the Legacy Agreement (for example, the Legacy Holder has merged with another company, has changed name, etc.) and, because of this change, the Legacy Holder's registration with the relevant register has been changed, then the Legacy Holder is obliged to submit the updated registration papers to the RIPE NCC. delete: </span> delete: </p> delete: <p> delete: <span> delete: <span> If the Legacy Holder delete: </span> delete: <span> does not submit the aforementioned documents within one month of them being requested by the RIPE NCC, the RIPE NCC will terminate the Legacy Holder (see delete: </span> delete: <span> Article 7.5.d of the Legacy Agreement). delete: </span> delete: </span> delete: </p> delete: <p> delete: <span> delete: <span> delete: <b> Procedure delete: </b> delete: </span> delete: </span> delete: </p> delete: <p> delete: <span> The RIPE NCC will: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> Send an email to the registered contact(s) indicating: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The Legacy Holder's obligation to submit the relevant documents delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The termination of the Legacy Agreement if the documents are not submitted delete: </span> delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> delete: <span> Terminate the progress of any open requests related to the Legacy Agreement delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> delete: <span> If the delete: </span> Legacy Holder delete: <span> 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: </span> delete: </span> delete: </p> delete: <p> delete: <span> delete: <span> After 30 days from the date of the first email, if the delete: </span> Legacy Holder delete: <span> continues not to comply, the delete: </span> 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 Holder. delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <a name="c1222d"> delete: </a> delete: <span> delete: <b> The Member fails to observe any rule of applicable law delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> 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 Holder with immediate effect, provided it receives a Dutch court order to do so. delete: </span> delete: </p> delete: <p> delete: <span> delete: <span> delete: <b> Procedure delete: </b> delete: </span> delete: </span> delete: </p> delete: <p> delete: <span> The RIPE NCC will: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> Send an email to the registered contact(s) indicating: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The reason for termination of the Legacy Agreement delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The immediate termination of the Legacy Agreement delete: </span> delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> delete: <span> Terminate the progress of any open requests related to the Legacy Agreement delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> 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 Holder. delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <a name="c1222e"> delete: </a> delete: <span> delete: <b> Non-payment. delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> delete: <span> In case of non-payment, in accordance with the RIPE NCC Billing Procedure, the Legacy Agreement is terminated after 120 days. For more information, please see the delete: <a title="" href="https://www.ripe.net/lir-services/billing/procedure" class="external-link" target="_self"> RIPE NCC Billing Procedure delete: </a> . delete: </span> delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <a name="c1222f"> delete: </a> delete: <span> delete: <b> Untruthful information delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> The RIPE NCC concludes the Legacy Agreement and provides services to Legacy Holder in good faith. The Legacy Holder is in breach of good faith, if the Legacy Holder repeatedly provides falsified data or information, or purposefully and/or repeatedly provides provided incorrect data or information (for example, falsified registration documents or IDs, incorrect/inaccurate contact details, etc.). etc.) regarding an allocation or an Independent resource, the RIPE NCC will deregister the relevant records. insert: </p>

insert: <p>

insert: <b> insert: <a name="b12f"> insert: </a> f. Fraudulent request insert: </b> insert: </p>

insert: <p>

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

insert: <p>

insert: <b> insert: <a name="b12g"> insert: </a> g. Non-compliance with a RIPE NCC audit insert: </b> insert: </p>

insert: <p>

If a Direct Assignment User does not comply with a RIPE NCC audit regarding an assignment of an Independent resource, the RIPE NCC will deregister the relevant records. Non-compliance includes, but is not limited to, unresponsiveness to or failure to cooperate with the RIPE NCC auditors' requests. For more information about the audit procedure, please see the insert: <span> insert: <a href="http://www.ripe.net/ripe/docs/audit"> RIPE NCC Audit Activity insert: </a> delete: </p> delete: <p> delete: <span> delete: <span> delete: <b> Procedure delete: </b> delete: </span> delete: </span> delete: </p> delete: <p> delete: <span> The RIPE NCC will: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> Send . insert: </p>

insert: <p>

insert: <b> insert: <a name="b12h"> insert: </a> h. Court order insert: </b> insert: </p>

insert: <p>

The RIPE NCC is an email to the registered contact(s) indicating: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The reason for termination of the Legacy Agreement delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The immediate termination of the Legacy Agreement delete: </span> delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> delete: <span> Terminate the progress of any open requests related to the Legacy Agreement delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> The RIPE NCC Managing Director association under Dutch law. In the event a Dutch court orders deregistration of specific Internet number resources, the RIPE NCC must and will comply. insert: </p>

insert: <h3>

insert: <a name="b2"> insert: </a> 2. Procedures for deregistration of different types of Internet number resources insert: </h3>

insert: <h3>

insert: <i> insert: <a name="b21"> insert: </a> 2.1 Allocations and independent Internet number resources for Contributor's own network insert: </i> insert: </h3>

insert: <p>

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

insert: <p>

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

insert: <p>

insert: <span> insert: <a href="https://www.ripe.net/membership/indices/index.html"> https://www.ripe.net/membership/indices/index.html insert: </a>

delete: </li> delete: <li> delete: <p> delete: <a name="c1222g"> delete: </a> insert: <p>

During the three-month period: insert: </p>

insert: <ul>
    insert: <li>
  • insert: <p>

    The Contributor must stop announcing the allocation/independent Internet number resources insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    The RIPE NCC will change the insert: <b> mnt-by insert: </b> object on the Contributor's records to the status “deregistered maintainer” insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    A warning statement is added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    The RIPE NCC will revoke any certificates generated by the RIPE NCC Certification Service insert: </p>

    insert: </li>
  • insert: </ul>
insert: <p>

After the three-month period, the allocation/assignment will be deregistered from the RIPE Database. insert: </p>

insert: <p>

Should the Contributor not react within four weeks, the RIPE NCC will: insert: </p>

insert: <ul>
    insert: <li>
  • insert: <p>

    Change the insert: <b> mnt-by insert: </b> object on the Contributor's records to the status “deregistered maintainer”; and/or insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the Internet number resources; and/or insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Withdraw the reverse delegation; and/or insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Contact the upstream to investigate possible hijacking of Internet number resources; and/or insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Delete all relevant objects in the RIPE Database, including allocation/assignment and insert: <b> route insert: </b> objects insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Revoke any certificates generated by the RIPE NCC Certification Service. insert: </p>

    insert: </li>
  • insert: </ul>
insert: <p>

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

insert: <p>

Please note: insert: </p>

insert: <p>

If the Contributor responds but with no intention to comply or objects at some point within the four-week period, the RIPE NCC will allow the time remaining in this four-week period for the Contributor to submit evidence that there is no reason for the deregistration of the Internet number resources or to request arbitration (see delete: <b> Non-compliance with RIPE NCC audits delete: </b> insert: <a data-val="b81490fe2c00243a37cb5c5ffaab8f6e" href="./resolveuid/b81490fe2c00243a37cb5c5ffaab8f6e" data-linktype="internal"> RIPE NCC Conflict Arbitration Procedure insert: </a> delete: </p> delete: <p> delete: <span> Non-compliance with RIPE NCC audits includes repeated unresponsiveness to ). However, if the four-week period expires without the submission of such evidence by the Contributor or failure to cooperate with the RIPE NCC auditors' without the submission of a request for arbitration, the RIPE NCC will proceed as if the Contributor had never reacted (see relevant procedure above). The Contributor may still request arbitration according to the timeframes of the RIPE NCC Conflict Arbitration Procedure. If the Contributor requests regarding registrations of arbitration, the RIPE NCC will change the insert: <b> mnt-by insert: </b> object on the relevant records to the status “maintainer in dispute” and a warning statement will be added to the relevant records of the RIPE Database until the communication of the arbiter's ruling. insert: </p>

insert: <h3>

insert: <a name="b22"> insert: </a> insert: <i> 2.2 Independent Internet number resources for the Member's own network. For more information about the audit procedure, please see the procedural document RIPE NCC Audit Activity. delete: </span> delete: </p> delete: <p> delete: <span> delete: <span> delete: <b> Procedure delete: </b> delete: </span> delete: </span> delete: </p> delete: <p> delete: <span> The RIPE NCC will: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> Send an email to the registered contact(s) indicating: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The reason for termination of the Legacy Agreement delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The immediate termination of the Legacy Agreement delete: </span> delete: </p> delete: </li> delete: </ul> delete: </li> delete: </ul> delete: <ul> delete: <li> delete: <p> delete: <span> Terminate the progress of any open requests related to the Legacy Agreement. delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> The RIPE NCC Managing Director assigned through a “sponsoring LIR” insert: </i> insert: </h3>

insert: <p>

The RIPE NCC will send an official notification of termination of the Legacy Agreement to all registered postal and email addresses of the Legacy Holder. contacts stating that the Independent Internet number resources will be deregistered, explaining the reasons for this deregistration and the procedure for the deregistration. The Contributor must immediately inform the End User about the imminent deregistration. insert: </p>

insert: <p>

During this period: insert: </p>

insert: <ul>
    insert: <li>
  • insert: <p>

    The End User must stop announcing the Independent Internet number resources insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    The RIPE NCC will change the insert: <b> mnt-by insert: </b> object on the relevant records to the status “deregistered maintainer” insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    A warning statement is added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources insert: </p>

    insert: </li>
  • insert: </ul>
insert: <p>

After the three-month period, the independent Internet number resources will be deregistered from the RIPE Database. insert: </p>

insert: <p>

Should the Contributor not react within four weeks, the RIPE NCC will: insert: </p>

insert: <ul>
    insert: <li>
  • insert: <p>

    Change the insert: <b> mnt-by insert: </b> object on the relevant records to the status “deregistered maintainer”; and/or insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the Internet number resources; and/or insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Withdraw the reverse delegation; and/or insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Contact the upstream to investigate possible hijacking of Internet number resources; and/or insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Delete all relevant objects in the RIPE Database, including allocation/assignment and insert: <b> route insert: </b> objects insert: </p>

    insert: </li>
  • insert: </ul>
insert: <p>

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

insert: <p>

Please note: insert: </p>

insert: <p>

If the Contributor responds but with no intention to comply or objects at some point within the four-week period, the RIPE NCC will allow the time remaining in this four-week period for the Contributor to submit evidence that there is no reason for deregistration of the Internet number resources or to request arbitration (see insert: <span> insert: <a data-val="b81490fe2c00243a37cb5c5ffaab8f6e" href="./resolveuid/b81490fe2c00243a37cb5c5ffaab8f6e" data-linktype="internal" class="external-link"> RIPE NCC Conflict Arbitration Procedure insert: </a> delete: </p> delete: </li> delete: <li> delete: <p> delete: <a name="c1222h"> delete: </a> delete: <span> delete: <b> Reasons beyond control of the RIPE NCC delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> ). However, if the four-week period expires without the submission of such evidence by the Contributor or without the submission of a request for arbitration, the RIPE NCC will proceed as if the Contributor had never reacted (see relevant procedure above). The Contributor may still request arbitration according to the timeframes of the RIPE NCC Conflict Arbitration Procedure. If the continuation of the Legacy Agreement is impossible for reasons above and beyond control Contributor requests arbitration, the RIPE NCC will change the insert: <b> mnt-by insert: </b> object on the relevant records to the status “maintainer in dispute” and a warning statement will be added to the relevant records of the RIPE Database until the communication of the arbiter's ruling. insert: </p>

insert: <h3>

insert: <b> insert: <a name="b23"> insert: </a> 2.3. Independent Internet number resources directly assigned 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: </span> delete: </p> delete: <p> delete: <span> delete: <span> delete: <b> Procedure delete: </b> delete: </span> delete: </span> delete: </p> delete: <p> delete: <span> The RIPE NCC will: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> Send an email to the registered contact(s) indicating: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The reason for termination of the Legacy Agreement delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The immediate termination of the Legacy Agreement delete: </span> delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> delete: <span> Terminate the progress of any open requests for RIPE NCC services delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> The RIPE NCC Managing Director to Direct Assignment Users insert: </b> insert: </h3>

insert: <p>

The RIPE NCC will send an official notification of termination of the Legacy Agreement by email to all registered postal and email addresses of the Legacy Holder. contacts stating that the Independent Internet number resources will be deregistered, explaining the reasons for this deregistration and the procedure for the deregistration. insert: </p>

insert: <p>

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

insert: <p>

During the three-month period: insert: </p>

insert: <ul>
    insert: <li>
  • insert: <p>

    The Direct Assignment User must stop announcing the Independent Internet number resources insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    The RIPE NCC will change the insert: <b> mnt-by insert: </b> object on the Direct Assignment User's records to the status “deregistered maintainer” insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    A warning statement is added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources insert: </p>

    insert: </li>
  • insert: </ul>
insert: <p>

After the three-month period, the Independent Internet number resources will be deregistered from the RIPE Database. insert: </p>

insert: <p>

Should the Direct Assignment User not react within four weeks, the RIPE NCC will: insert: </p>

insert: <ul>
    insert: <li>
  • insert: <p>

    Change the insert: <b> mnt-by insert: </b> object on the Contributor's records to the status “deregistered maintainer”; and/or insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the Internet number resources; and/or insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Withdraw the reverse delegation; and/or insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Contact the upstream to investigate possible hijacking of Internet number resources; and/or insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    Delete all relevant objects in the RIPE Database, including assignment and insert: <b> route insert: </b> objects insert: </p>

    insert: </li>
  • insert: </ul>
insert: <p>

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

insert: <p>

Please note: insert: </p>

insert: <p>

If the Direct Assignment User responds but with no intention to comply or objects at some point within the four-week period, the RIPE NCC will allow the time remaining in this four-week period for the Direct Assignment User to submit evidence that there is no reason for deregistration of the Internet number resources or to request arbitration (see insert: <span> insert: <a data-val="b81490fe2c00243a37cb5c5ffaab8f6e" href="./resolveuid/b81490fe2c00243a37cb5c5ffaab8f6e" data-linktype="internal" class="external-link"> RIPE NCC Conflict Arbitration Procedure insert: </a> delete: </p> delete: <p> delete: <span> delete: <b> Billing issues delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> All outstanding amounts for the full year must be settled unless otherwise agreed. delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <a name="c1222i"> delete: </a> delete: <span> delete: <span> delete: </span> delete: <b> The Legacy Holder transfers the Legacy Internet Resources to a third party delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> ). However, if the four-week period expires without the submission of such evidence by the Direct Assignment User or without the submission of a request for arbitration, the RIPE NCC will proceed as if the Direct Assignment User had never reacted (see relevant procedure above). insert: </p>

insert: <p>

The Direct Assignment User may still request arbitration according to the timeframes of the RIPE NCC Conflict Arbitration procedure. If the Legacy 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: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <a name="c1222j"> delete: </a> delete: <span> delete: <span> delete: </span> delete: <b> The Legacy Holder has no rights to use the Legacy Internet Resources delete: </b> delete: </span> delete: </p> delete: <p> delete: <span> If a third party provides sufficient evidence proving the Legacy Internet Resources must not be registered with the Legacy Holder, Contributor requests arbitration, the RIPE NCC will immediately terminate the Legacy Agreement. delete: </span> delete: </p> delete: <p> delete: <span> 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 Resource change the insert: <b> mnt-by insert: </b> object on the relevant records to the status “maintainer in doubt. delete: </span> delete: </p> delete: </li> delete: </ol> delete: <h2> delete: <a name="c2"> delete: </a> 2. Consequences delete: </h2> delete: <p> delete: <span> This Section describes the consequences of the termination of : delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The Legacy Services the RIPE NCC provides to a Member pursuant to the Terms and Conditions Regarding Legacy Internet Resources for Members, delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The Legacy Agreement between RIPE NCC and a Legacy Holder or delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The Legacy Agreement between a Legacy Holder and a sponsoring LIR. delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> Upon termination of the Legacy Service/Agreement for reasons of non-compliance with contractual responsibilities (see above Section 1.1.2.1): delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The RIPE NCC will add the remark “No-contract” in the RIPE Database resource object; and delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> A dispute” and a warning statement will be added to the relevant records in of the RIPE Database mentioning that the Legacy Internet Resources are not covered by a contractual relationship; delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> The RIPE NCC will withdraw the reverse delegation; and delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> 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 Terms and Conditions Regarding Legacy Internet Resources for Members or the signing of the Agreement. This does not include the reverse delegation. delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> Upon termination of the Legacy Service/Agreement for any other reason: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> The RIPE NCC will add the remark “No-contract” in the RIPE Database resource object; and delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> 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: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> 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 Terms and Conditions Regarding Legacy Internet Resources for Members or the signing of the Legacy Agreement. delete: </span> delete: </p> delete: </li> delete: </ul> delete: <h2> delete: <a name="c3"> delete: </a> 3. Change of status of Legacy Internet Resources delete: </h2> delete: <p> delete: <span> If a Legacy Holder (Member or not) wants to have particular Legacy Internet Resources registered as if they had been distributed by the RIPE NCC, the Legacy Holder must send an email to delete: <a href="mailto:legacy@ripe.net"> legacy@ripe.net delete: </a> . In the email the Legacy Holder must: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> Indicate the Legacy Internet Resources and delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> Acknowledge that the RIPE NCC will apply for these resources the RIPE policies concerning Internet number resources distributed by the RIPE NCC. delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> The RIPE NCC will send an acknowledgement of the receipt of the notice. Upon sent of such notice, the resources will be considered as distributed by the RIPE NCC. delete: </span> delete: </p> delete: <h2> delete: <a name="c4"> delete: </a> 4. Deregistration of Legacy Internet Resources delete: </h2> delete: <p> delete: <span> If a Legacy Holder (Member or not) wants to deregister particular Legacy Internet Resources, the Legacy Holder must send an email to delete: <a href="mailto:legacy@ripe.net"> legacy@ripe.net delete: </a> . In the email the Legacy Holder must: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> Indicate the Legacy Internet Resources and delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> Acknowledge that he/she resigns from any rights with regards to these resources. delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: <span> The RIPE NCC will send an acknowledgement of the receipt of the notice. Upon sent of such notice, the Legacy Holder must stop announcing the Legacy Internet Resources. The RIPE NCC will: delete: </span> delete: </p> delete: <ul> delete: <li> delete: <p> delete: <span> Change the mnt-by attribute on the relevant object to RIPE NCC maintainer and change the status attribute to “deregistered maintainer” delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> Withdraw the reverse delegation; delete: </span> delete: </p> delete: </li> delete: <li> delete: <p> delete: <span> Delete all relevant objects in the RIPE Database, including route objects delete: </span> delete: </p> delete: </li> delete: </ul> delete: <p> delete: </p> delete: <p class="callout"> until the communication of the arbiter's ruling. insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: <span class="discreet"> NOTE: This document might change due to future policy changes. If this happens, the RIPE NCC will send a notification to the RIPE NCC Services Working Group Mailing List. delete: </p> mailing list. insert: </span> insert: </p>

Closure of Members, LIR and Deregistration of Internet Resources, and Legacy Number Resources
RIPE Documents Search