You are here: Home > Publications > RIPE Document Store > Independent Internet Number Resources - Contractual Relationship Changes between Sponsoring LIR and End User

Changes to Independent Internet Number Resources - Contractual Relationship Changes between Sponsoring LIR and End User

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-475: This is a procedural document that describes the steps to be taken when there are changes in the contractual relationship between the End User ripe-541: Closure of independent LIR and Deregistration of Internet number resources and the sponsoring Local Internet Registry (LIR). Number Resources
delete: <h3> Abstract delete: </h3> delete: <p> This insert: <p>

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

insert: <p>

Section B describes the valid reasons for deregistration of Internet number resources and the procedure that applies in each circumstance. insert: </p>

insert: <p>

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

insert: <p>

  insert: </p>

insert: <p>

insert: <strong> Table of Contents insert: </strong> insert: </p>

insert: <p>

  insert: </p>

insert: <p>

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

insert: <p>

insert: <a href="#1"> 1. Grounds for termination and procedure in each case insert: </a> insert: </p>

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

insert: <a href="#11"> 1.1. Termination by the Member insert: </a> insert: </p>

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

insert: <a href="#12"> 1.2. Termination by the RIPE NCC insert: </a> insert: </p>

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

insert: <a href="#121"> 1.2.1. Termination with a three-month notice period insert: </a> insert: </p>

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

insert: <a class="anchor-link" href="#1211"> 1.2.1.1. Violation of RIPE Policies and RIPE NCC procedures insert: </a> insert: </p>

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

insert: <a href="#1211a"> a. Unresponsiveness insert: </a> insert: </p>

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

insert: <a href="#1211b"> b. Allocations/assignments contravening RIPE Policies insert: </a> insert: </p>

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

insert: <a href="#1211c"> c. Incorrect registration in the RIPE Database insert: </a> insert: </p>

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

insert: <a href="#1211d"> d. Non-compliance with an arbiter ruling insert: </a> insert: </p>

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

insert: <a class="anchor-link" href="#1212"> 1.2.1.2. Other reasons insert: </a> insert: </p>

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

insert: <a href="#122"> 1.2.2. Termination with immediate effect insert: </a> insert: </p>

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

insert: <a href="#122a"> a. Member files for bankruptcy, is a procedural document that describes the steps to be taken when there are changes liquidated, suspends its payments or becomes insolvent insert: </a> insert: </p>

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

insert: <a href="#122b"> b. Member damages the name, trademarks or intellectual property rights of the RIPE NCC insert: </a> insert: </p>

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

insert: <a href="#122c"> c. Member fails to submit to the RIPE NCC a valid extract from the Commercial Trade Register or equivalent register insert: </a> insert: </p>

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

insert: <a href="#122d"> d. The Member fails to observe any rule of applicable law insert: </a> insert: </p>

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

insert: <a href="#122e"> e. Non-payment insert: </a> insert: </p>

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

insert: <a href="#122f"> f. Termination of the RIPE NCC member status insert: </a> insert: </p>

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

insert: <a href="#122g"> g. Untruthful information insert: </a> insert: </p>

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

insert: <a href="#122h"> h. Non-compliance with RIPE NCC audit insert: </a> insert: </p>

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

insert: <a href="#122i"> i. Discontinuation of RIPE NCC services insert: </a> insert: </p>

insert: <p>

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

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

insert: <a href="#21"> 2.1. End of provision of RIPE NCC services insert: </a> insert: </p>

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

insert: <a href="#211"> 2.1.1. General services insert: </a> insert: </p>

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

insert: <a href="#212"> 2.1.2. Registration of distributed Internet number resources insert: </a> insert: </p>

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

insert: <a href="#213"> 2.1.3. Request for independent Internet number resources as a “sponsoring LIR” insert: </a> insert: </p>

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

insert: <a href="#22"> 2.2. End of RIPE NCC member status insert: </a> insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <a href="#B"> B. Deregistration of Internet number resources insert: </a> insert: </p>

insert: <p>

insert: <a href="#B1"> 1. Reasons for deregistration of Internet number resources insert: </a> insert: </p>

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

insert: <a href="#B11"> 1.1. Allocations and Independent Internet number resources assigned for the Member's own network or assigned through a “sponsoring LIR” insert: </a> insert: </p>

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

insert: <a href="#B11a"> a. Termination of the SSA insert: </a> insert: </p>

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

insert: <a href="#B11b"> b. Invalidity of original allocation/assignment criteria insert: </a> insert: </p>

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

insert: <a href="#B11c"> c. Incorrect registration of the allocation/assignment in the RIPE Database insert: </a> insert: </p>

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

insert: <a href="#B11d"> d. Falsified/incorrect information insert: </a> insert: </p>

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

insert: <a href="#B11e"> e. Fraudulent request insert: </a> insert: </p>

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

insert: <a href="#B11f"> f. Non-compliance with a RIPE NCC audit insert: </a> insert: </p>

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

insert: <a href="#B11g"> g. Court order insert: </a> insert: </p>

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

insert: <a href="#B11h"> h. Independent Internet number resources assigned through a “sponsoring LIR” without a valid contractual relationship between the End User of independent insert: </a> insert: </p>

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

insert: <a href="#B12"> 1.2. Independent Internet number resources and the sponsoring Local Internet Registry (LIR). The document also describes the scenarios in which the RIPE NCC may de-register independent Internet number resources. delete: </p> delete: <p> This document does not describe the procedure applicable to contractual relationship changes for independent Internet number resource users who have signed a contract with the RIPE NCC. delete: </p> delete: <h3> Table of Contents delete: </h3> delete: <p> delete: <a href="#10"> 1.0 Introduction delete: </a> delete: <br /> delete: <a href="#20"> 2.0 Ownership and Legal Name Changes delete: </a> delete: <br /> delete: <a href="#21"> 2.1 End User Organisation Changes Ownership delete: </a> delete: <br /> delete: <a href="#22"> 2.2 End User Organisation Changes Name delete: </a> delete: </p> delete: <p> delete: <a href="#30"> 3.0 Transfer of Contractual Relationship delete: </a> delete: <br /> delete: <a href="#31"> 3.1 Transfer between Sponsoring LIRs delete: </a> delete: <br /> delete: <a href="#32"> 3.2 Transfer from Sponsoring LIR to the RIPE NCC delete: </a> delete: </p> delete: <p> delete: <a href="#40"> 4.0 De-registering of Independent Internet Number Resources delete: </a> delete: <br /> delete: <a href="#41"> 4.1 Closure of Sponsoring LIR delete: </a> delete: <br /> delete: <a href="#411"> 4.1.1 De-registration Timeframe delete: </a> delete: <br /> delete: <a href="#42"> 4.2 Violation of RIPE Policy, Law or Contract delete: </a> delete: <br /> delete: <a href="#421"> 4.2.1 De-registration Timeframe delete: </a> delete: <br /> delete: <a href="#43"> 4.3 Contract Expired and Not Renewed / Ceased and Not Transferred delete: </a> delete: </p> delete: <p> delete: <a id="10" name="10"> delete: </a> delete: </p> delete: <h3> 1.0 Introduction delete: </h3> delete: <p> In October 2008, the RIPE community accepted a policy change which states that a contractual relationship must be established between an End User and a sponsoring LIR or the RIPE NCC before the End User can receive independent Internet number resources. delete: </p> delete: <p> In order to fulfil its mandate of manager of independent Internet number resources, the RIPE NCC requires End Users and LIRs to inform the RIPE NCC in case of changes to their contractual relationship. delete: </p> delete: <p> The procedures listed in this document are subject to RIPE policies. delete: </p> delete: <p> delete: <a id="20" name="20"> delete: </a> delete: </p> delete: <h3> 2.0 Ownership and Legal Name Changes delete: </h3> delete: <p> The RIPE NCC requires Sponsoring LIRs to maintain a proper registration of End User's legal organisation changes with the RIPE NCC. delete: </p> delete: <p> delete: <a id="21" name="21"> delete: </a> delete: </p> delete: <h3> 2.1 End User Organisation Changes Ownership delete: </h3> delete: <p> If the ownership of the organisation changes but the legal operating name is continued, the RIPE NCC does not have to be notified. delete: </p> delete: <p> delete: <a id="22" name="22"> delete: </a> delete: </p> delete: <h3> 2.2 End User Organisation Changes Name delete: </h3> delete: <p> When an End User that has been assigned independent Internet number resources changes its legal operating name, the RIPE NCC must be notified. delete: </p> delete: <p> In all cases, a new contract must be signed between the renamed End User organisation and the sponsoring LIR in order to guarantee a legitimate handover of the existing rights and obligations. delete: </p> delete: <p> A copy of this contract, a revised extract of the Trade Register and proof of change from an authorised person must be provided to the RIPE NCC. delete: </p> delete: <p> delete: <a id="30" name="30"> delete: </a> delete: </p> delete: <h3> 3.0 Transfer of Contractual Relationship delete: </h3> delete: <p> If the contractual agreement between the End User of independent Internet number resources and the sponsoring LIR ceases, for any reason, the contractual changes must be communicated to the RIPE NCC. delete: </p> delete: <p> delete: <a> delete: </a> delete: </p> delete: <h3> 3.1 Transfer between Sponsoring LIRs delete: </h3> delete: <p> If the End User decides to change sponsoring LIR, this change must be communicated to the RIPE NCC. delete: </p> delete: <p> The request must come from either the current or the new sponsoring LIR. The RIPE NCC will need confirmation from both LIRs before it can proceed with the transfer, unless the current LIR is closed or in the process of being closed. delete: </p> delete: <p> The RIPE NCC will finalise the change after it receives a copy of the new directly by the RIPE NCC for Direct Assignment Agreement insert: </a> insert: </p>

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

insert: <a href="#B12a"> a. Termination of the RIPE NCC End User Assignment Agreement and insert: </a> insert: </p>

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

insert: <a href="#B12b"> b. Unresponsive Direct Assignment User insert: </a> insert: </p>

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

insert: <a href="#B12c"> c. Invalidity of original criteria insert: </a> insert: </p>

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

insert: <a href="#B12d"> d. Incorrect registration of the assignment in the RIPE Database insert: </a> insert: </p>

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

insert: <a href="#B12e"> e. Falsified/incorrect information insert: </a> insert: </p>

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

insert: <a href="#B12f"> f. Fraudulent request insert: </a> insert: </p>

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

insert: <a href="#B12g"> g. Non-compliance with a RIPE NCC audit insert: </a> insert: </p>

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

insert: <a href="#B12h"> h. Court order insert: </a> insert: </p>

insert: <p>

insert: <a class="anchor-link" href="#---procedures-for-deregistration-of-different-types-of-internet-number-resources"> 2. 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="#----allocations-and-independent-internet-number-resources-for-member-s-own-network"> 2.1. Allocations and Independent Internet number resources for Member's own network insert: </a> insert: </p>

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

insert: <a class="anchor-link" href="#----independent-internet-number-resources-assigned-through-a--sponsoring-lir-"> 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="#-b------independent-internet-number-resources-directly-assigned-by-the-ripe-ncc-to-direct-assignment-users--b-"> 2.3. Independent Internet number resources directly assigned by the RIPE NCC to Direct Assignment Users insert: </a> insert: </p>

insert: <p>

insert: <a name="A"> insert: </a> insert: </p>

insert: <h2>

insert: <strong> A. Closure of LIR - Termination of the RIPE NCC Standard Service Agreement insert: </strong> insert: </h2>

insert: <p>

An organisation or an individual person can receive services from the RIPE NCC if they: insert: </p>

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

    Agree and sign the RIPE NCC Standard Service Agreement (SSA); and insert: </p>

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

    Conform to RIPE Policies. insert: </p>

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

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

insert: <p>

insert: <a name="1"> insert: </a> insert: </p>

insert: <h2>

1. Grounds for termination and procedure in each case insert: </h2>

insert: <p>

The SSA can be terminated by the Member (see section 1.1) or by the RIPE NCC. The termination by the RIPE NCC can either be with a notice period of three months (see section 1.2.1.) or for specific reasons with a shorter notice period and immediate effect (see section 1.2.2.). insert: </p>

insert: <p>

insert: <a name="11"> insert: </a> insert: </p>

insert: <h3>

1.1. Termination by the Member insert: </h3>

insert: <p>

According to Article 9.2 of the SSA, the Member can terminate the SSA with a notice period of three months. Possible reasons why Members might want to terminate their SSA include: insert: </p>

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

    The Member decides to close or to change their business insert: </p>

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

    The Member decides to merge with another Member and therefore they do not need to be Members themselves insert: </p>

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

    The Member decides to assign Internet number resources from another Member insert: </p>

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

insert: <strong> Procedure insert: </strong> insert: </p>

insert: <p>

The notice will formally request the termination of the SSA. insert: </p>

insert: <p>

It must be: insert: </p>

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

    Dated and signed by an authorised representative of the Member. A registered contact cannot give notice unless the registered contact is an authorised representative. insert: </p>

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

    Sent to the RIPE NCC by email to < insert: <a href="mailto:[email protected]"> [email protected] insert: </a> > or by postal mail to: RIPE NCC, Singel 258, 1016 AB Amsterdam, The Netherlands. insert: </p>

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

insert: <p>

insert: <a name="_GoBack"> insert: </a> The termination of the SSA will take place three months after the receipt of the notice by the RIPE NCC. insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

insert: <a name="12"> insert: </a> insert: </p>

insert: <h3>

1.2. Termination by the RIPE NCC insert: </h3>

insert: <p>

insert: <a name="121"> insert: </a> insert: </p>

insert: <h3>

1.2.1. Termination with a three-month notice period insert: </h3>

insert: <p>

According to Article 9.3 of the SSA, the RIPE NCC can terminate the SSA with a notice period of three months. Grounds for such termination may be the following: insert: </p>

insert: <p>

insert: <strong> insert: <a name="1211"> insert: </a> 1.2.1.1 Violation of RIPE Policies and RIPE NCC procedures insert: </strong> insert: </p>

insert: <p>

The Member must comply with RIPE Policies and RIPE NCC procedures (see Article 6 of the SSA). The RIPE NCC will terminate the SSA if the Member commits any of the following violations of RIPE Policies or RIPE NCC procedures: insert: </p>

insert: <ol class="listTypeLowerAlpha">
    insert: <li>
  1. insert: <a name="1211a"> insert: </a> insert: <strong> Unresponsiveness insert: </strong> insert: <p>

      insert: </p>

    insert: <p>

    The Member is unresponsive for a significant period of time. insert: </p>

    insert: <p>

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

    insert: </li>
  2. insert: <li>
  3. insert: <p>

    insert: <a name="1211b"> insert: </a> insert: <strong> Allocations/assignments contravening RIPE policies insert: </strong> insert: </p>

    insert: <p>

    Allocations or transfers of allocations and assignments are not made and used in accordance with the RIPE community's policies. insert: </p>

    insert: </li>
  4. insert: <li>
  5. insert: <p>

    insert: <a name="1211c"> insert: </a> insert: <strong> Incorrect registration in the RIPE Database insert: </strong> insert: </p>

    insert: <p>

    Registration data is repeatedly maintained incorrectly (allocations and assignments must be properly registered in the RIPE Database). insert: </p>

    insert: <p>

    Proper registration must be as follows: insert: </p>

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

      The insert: <strong> inetnum insert: </strong> and the insert: <strong> inet6num insert: </strong> object(s) for approved assignments must use the netname(s) approved by the RIPE NCC and not be larger than the size approved by the RIPE NCC insert: </p>

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

      The date in the first “changed:” attribute must not be earlier than the date of approval from the RIPE NCC insert: </p>

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

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

      insert: </li>
    • insert: </ul>
    insert: </li>
  6. insert: <li>
  7. insert: <p>

    insert: <a name="1211d"> insert: </a> insert: <strong> Non-compliance with an arbiter ruling insert: </strong> insert: </p>

    insert: <p>

    For more information, please see insert: <a href="http://www.ripe.net/ripe/docs/arbitration"> RIPE NCC Conflict Arbitration Procedure insert: </a> . insert: </p>

    insert: <p>

    insert: <strong> Procedure insert: </strong> insert: </p>

    insert: </li>
  8. insert: </ol>
insert: <p>

If the RIPE NCC becomes aware of any of the aforementioned reasons for terminating the SSA, 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 violation insert: </p>

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

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

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

      the termination of the SSA in three (3) months if the violation continues 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 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: insert: </p>

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

    The violation insert: </p>

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

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

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

    The termination of the SSA in two (2) months if the violation continues insert: </p>

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

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

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

    The violation insert: </p>

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

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

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

    The termination of the SSA in one (1) month if the violation continues insert: </p>

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

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 SSA (i.e., closure of the Member's account) to all registered postal and email addresses of the Member. insert: </p>

insert: <p>

The RIPE NCC concludes the SSA and provides services to Members in good faith. The Member is in breach of good faith in the following cases: insert: </p>

insert: <p>

insert: <strong> insert: <a name="1212"> insert: </a> 1.2.1.2 insert: </strong> insert: <strong> Other reasons insert: </strong> insert: </p>

insert: <p>

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. 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 the consent of the African Members, the SSAs with the RIPE NCC were terminated and new contracts with AfriNIC were signed. insert: </p>

insert: <p>

insert: <strong> Procedure insert: </strong> 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 Member. 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 Member 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 Member requests a longer period and this is agreed upon. insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

insert: <a name="122"> insert: </a> insert: </p>

insert: <h3>

1.2.2. Termination with immediate effect insert: </h3>

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

insert: <ol class="listTypeLowerAlpha">
    insert: <li>
  1. insert: <p>

    insert: <a name="122a"> insert: </a> insert: <strong> Member insert: </strong> insert: <strong> files for bankruptcy, is liquidated, suspends its payments or becomes insolvent insert: </strong> insert: </p>

    insert: <p>

    Upon receipt of the documents stating the bankruptcy, liquidation, suspension of payments or insolvency of the Member insert: </p>

    insert: <p>

    by the relevant authority or by public announcement of the fact, the RIPE NCC will terminate the SSA. If the relevant national authority decides that the Member's operations can continue, and provided that the Member fulfills the obligations coming from the SSA, the RIPE NCC will not terminate the SSA. insert: </p>

    insert: <p>

    insert: <strong> Procedure insert: </strong> insert: </p>

    insert: <p>

    The RIPE NCC will: insert: </p>

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

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

      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: </li>
    • 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 member) to all registered contacts of the Member or to the legal successor, both by electronic and registered postal mail. insert: </p>

    insert: </li>
  2. insert: <li>
  3. insert: <p>

    insert: <a name="122b"> insert: </a> insert: <strong> Member damages the name, trademarks or intellectual property rights of the RIPE NCC insert: </strong> insert: </p>

    insert: <p>

    Examples: insert: </p>

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

      The Member pretends to be, or to act on behalf of, the RIPE NCC through misuse of the RIPE NCC name or logo insert: </p>

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

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

    insert: <strong> Procedure: insert: </strong> 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 violation insert: </p>

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

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

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

        the termination of the SSA if the violation continues 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 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. insert: </p>

    insert: <p>

    After 60 days from the date of the first email, if the Member insert: </p>

    insert: <p>

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

    insert: <p>

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

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

    After 120 days from the date of the first email, if the Member insert: </p>

    insert: <p>

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

    insert: </li>
  4. insert: <li>
  5. insert: <p>

    insert: <a name="122c"> insert: </a> insert: <strong> Member fails to submit to the RIPE NCC a valid extract of the from the Commercial Trade Register. The new agreement Register or equivalent register insert: </strong> insert: </p>

    insert: <p>

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

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

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

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

    insert: <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 replace the old agreement. delete: </p> delete: <p> delete: <a id="32" name="32"> terminate the SSA (see Article 9.4.d of the SSA). insert: </p>

    insert: <p>

    insert: <strong> Procedure insert: </strong> 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 Member'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 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. insert: </p>

    insert: <p>

    After 30 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 SSA (i.e., closure of the Member's account) to all registered postal and email addresses of the Member. insert: </p>

    insert: </li>
  6. insert: <li>
  7. insert: <p>

    insert: <a name="122d"> insert: </a> insert: <strong> The Member fails to observe any rule of applicable law insert: </strong> 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 Member with immediate effect, provided it receives a Dutch court order to do so. insert: </p>

    insert: <p>

    insert: <strong> Procedure insert: </strong> 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 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: </li>
    • 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 Member's account) to all registered postal and email addresses of the Member. insert: </p>

    insert: </li>
  8. insert: <li>
  9. insert: <p>

    insert: <a name="122e"> insert: </a> insert: <strong> Non-payment insert: </strong> . 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: <a href="http://www.ripe.net/lir-services/billing/procedure"> RIPE NCC Billing Procedure insert: </a> . insert: </p>

    insert: </li>
  10. insert: <li>
  11. insert: <p>

    insert: <a name="122f"> insert: </a> insert: <strong> Termination of the RIPE NCC member status insert: </strong> insert: </p>

    insert: <p>

    By signing the SSA, Members become members of the RIPE NCC association. If Members terminate their member status with the RIPE NCC association, the SSA is automatically terminated (see also Article 6 of the AoA). insert: </p>

    insert: <p>

    insert: <strong> Procedure insert: </strong> 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 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: </li>
    • 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 Member's account) to all registered postal and email addresses of the Member. insert: </p>

    insert: </li>
  12. insert: <li>
  13. insert: <p>

    insert: <a name="122g"> insert: </a> insert: <strong> Untruthful information insert: </strong> insert: </p>

    insert: <p>

    The RIPE NCC concludes the SSA and provides services to Members in good faith. The Member is in breach of good faith in the following cases: insert: </p>

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

      insert: <strong> Falsified/incorrect information insert: </strong> insert: </p>

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

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

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

      insert: <strong> Fraudulent requests insert: </strong> insert: </p>

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

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

    insert: <p>

    insert: <strong> Procedure insert: </strong> 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 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: </li>
    • 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 Member's account) to all registered postal and email addresses of the Member. insert: </p>

    insert: </li>
  14. insert: <li>
  15. insert: <p>

    insert: <a name="122h"> insert: </a> insert: <strong> Non-compliance with RIPE NCC audits insert: </strong> 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 Member's own network. For more information about the audit procedure, please see insert: <a href="http://www.ripe.net/ripe/docs/audit"> RIPE NCC audit activity insert: </a> . insert: </p>

    insert: <p>

    insert: <strong> Procedure insert: </strong> 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 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: </li>
    • 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 Member's account) to all registered postal and email addresses of the Member. insert: </p>

    insert: </li>
  16. insert: <li>
  17. insert: <p>

    insert: <a name="122i"> insert: </a> insert: <strong> i. Discontinuation of RIPE NCC services insert: </strong> insert: </p>

    insert: <p>

    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 act or generally accepted principles. insert: </p>

    insert: <p>

    insert: <strong> Procedure insert: </strong> 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 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: </li>
    • 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 Member's account) to all registered postal and email addresses of the Member. insert: </p>

    insert: </li>
  18. insert: </ol>
insert: <p>

insert: <a name="2"> insert: </a> insert: </p>

insert: <h2>

2. Consequences insert: </h2>

insert: <p>

Upon termination of the SSA, Members lose all rights to RIPE NCC services and their RIPE NCC member status. insert: </p>

insert: <p>

insert: <a name="21">

3.2 Transfer from Sponsoring 2.1. End of provision of RIPE NCC services insert: </h3>

insert: <p>

insert: <a name="211"> insert: </a> insert: </p>

insert: <h3>

insert: <strong> 2.1.1. General services insert: </strong> insert: </h3>

insert: <p>

The RIPE NCC will stop providing RIPE NCC services, including: insert: </p>

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

    Distribution of Internet number resources insert: </p>

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

    Authority to maintain Internet number resource records in the RIPE Database insert: </p>

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

    Access to the LIR to the RIPE NCC Portal insert: </p>

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

    Use of the RIPE NCC Certification Service insert: </p>

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

    Participation in RIPE NCC Training Courses insert: </p>

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

insert: <a name="212"> insert: </a> insert: </p>

insert: <h3>

2.1.2. Registration of distributed Internet number resources

If the contractual agreement 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. insert: </p>

insert: <p>

insert: <a name="213"> insert: </a> insert: </p>

insert: <h3>

2.1.3. Request for independent Internet number resources as a “sponsoring LIR” insert: </h3>

insert: <p>

Members lose their right to request independent Internet number resources as a “sponsoring LIR”. For independent Internet number resources already assigned by them, see below at section B.2.2. insert: </p>

insert: <p>

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

insert: <h3>

insert: <strong> 2.2. End of RIPE NCC member status insert: </strong> insert: </h3>

insert: <p>

Members will also lose their RIPE NCC member status and all relevant rights, such as the right to attend and vote at RIPE NCC General Meetings. insert: </p>

insert: <p>

insert: <a name="B"> insert: </a> insert: </p>

insert: <h2>

insert: <strong> B. Deregistration of Internet Number Resources insert: </strong> insert: </h2>

insert: <p>

insert: <a name="B1"> insert: </a> insert: </p>

insert: <h2>

1. Reasons for deregistration of Internet number resources insert: </h2>

insert: <p>

insert: <a name="B11"> insert: </a> insert: </p>

insert: <h3>

1.1 Allocations and Independent Internet number resources assigned for the Member's own network or assigned through a “sponsoring LIR” insert: </h3>

insert: <ol class="listTypeLowerAlpha">
    insert: <li>
  1. insert: <p>

    insert: <a name="B11a"> insert: </a> insert: <strong> Termination of the SSA insert: </strong> insert: </p>

    insert: <p>

    For more information, see section A. For Independent Internet number resources through a “sponsoring LIR”, see insert: <a href="http://www.ripe.net/ripe/docs/lir-dau"> Independent Internet Number Resources – Contractual Relationship Changes between the sponsoring LIR and End User of independent insert: </a> . insert: </p>

    insert: </li>
  2. insert: <li>
  3. insert: <p>

    insert: <a name="B11b"> insert: </a> insert: <strong> Invalidity of original allocation/assignment criteria insert: </strong> insert: </p>

    insert: <p>

    Internet number resources and the 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. insert: </p>

    insert: </li>
  4. insert: <li>
  5. insert: <p>

    insert: <a name="B11c"> insert: </a> insert: <strong> Incorrect registration of the allocation/assignment in the RIPE Database insert: </strong> insert: </p>

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

    insert: <p>

    Proper registration must be as follows: insert: </p>

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

      The insert: <strong> inetnum insert: </strong> and the insert: <strong> inet6num insert: </strong> object(s) for approved assignments must use the netname(s) approved by the RIPE NCC and not be larger than the size approved by the RIPE NCC insert: </p>

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

      The date in the first “changed:” attribute must not be earlier than the date of approval from the RIPE NCC insert: </p>

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

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

      insert: </li>
    • insert: </ul>
    insert: </li>
  6. insert: <li>
  7. insert: <p>

    insert: <a name="B11d"> insert: </a> insert: <strong> Falsified/incorrect information insert: </strong> insert: </p>

    insert: <p>

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

    insert: </li>
  8. insert: <li>
  9. insert: <p>

    insert: <a name="B11e"> insert: </a> insert: <strong> Fraudulent request insert: </strong> insert: </p>

    insert: <p>

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

    insert: </li>
  10. insert: <li>
  11. insert: <p>

    insert: <a name="B11f"> insert: </a> insert: <strong> Non-compliance with a RIPE NCC audit insert: </strong> insert: </p>

    insert: <p>

    If a Member does not comply with a RIPE NCC audit regarding the registration of an Independent resource that the Member is responsible for as “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 insert: <a href="http://www.ripe.net/ripe/docs/audit"> RIPE NCC Audit Activity insert: </a> . insert: </p>

    insert: </li>
  12. insert: <li>
  13. insert: <p>

    insert: <a name="B11g"> insert: </a> insert: <strong> Court order insert: </strong> insert: </p>

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

    insert: </li>
  14. insert: <li>
  15. insert: <p>

    insert: <a name="B11h"> insert: </a> insert: <strong> Independent Internet number resources assigned through a “sponsoring LIR” without an valid contractual relationship insert: </strong> insert: </p>

    insert: <p>

    See insert: <a href="http://www.ripe.net/ripe/docs/lir-dau"> Independent Internet Number Resources – Contractual Relationship Changes between sponsoring LIR ceases and the and End User wants to enter into a contractual relationship with the RIPE NCC, the End User will have to follow the application procedure to become a insert: </a> . insert: </p>

    insert: </li>
  16. insert: </ol>
insert: <h3>

1.2 Independent Internet number resources directly assigned by the RIPE NCC for Direct Assignment User, signing the Users insert: </h3>

insert: <ol class="listTypeLowerAlpha">
    insert: <ol class="listTypeLowerAlpha">
      insert: <li>
    1. insert: <p>

      insert: <a name="B12a"> insert: </a> insert: <strong> Termination of the RIPE NCC End User Assignment Agreement with the RIPE NCC and paying the Administration and first Maintenance Fee. delete: </p> delete: <p> At this point, the RIPE NCC will need confirmation from both the insert: </strong> insert: </p>

      insert: <p>

      The RIPE NCC End User and the sponsoring LIR before it Assignment Agreement can proceed with the transfer of the contractual relationship of independent terminate according to Article 7 of that agreement. Sections A.1 and A.2.2 above, referring to the SSA and the Members, can apply accordingly for the RIPE NCC End User Assignment Agreement and the Direct Assignment Users. insert: </p>

      insert: </li>
    2. insert: <li>
    3. insert: <p>

      insert: <a name="B12b"> insert: </a> insert: <strong> Unresponsive Direct Assignment User insert: </strong> 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, unless the LIR 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: <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> ). insert: </p>

      insert: </li>
    4. insert: <li>
    5. insert: <p>

      insert: <a name="B12c"> insert: </a> insert: <strong> Invalidity of original criteria insert: </strong> 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 closed or in the process of being closed. delete: </p> delete: <p> delete: <a id="40" name="40"> delete: </a> delete: </p> delete: <h3> 4.0 De-registering of Independent Internet Number Resources delete: </h3> delete: <p> There are three possible scenarios in which the RIPE NCC will de-register independent authorised to deregister the relevant Internet number resources.

      delete: <p> delete: <a id="41" name="41"> delete: </a> delete: </p> insert: </li>
    6. insert: <li>
    7. insert: <p>

      insert: <a name="B12d"> insert: </a> insert: <strong> Incorrect registration of the assignment in the RIPE Database insert: </strong> insert: </p>

      insert: <p>

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

      insert: <p>

      Proper registration must be as follows: insert: </p>

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

        The insert: <strong> inetnum insert: </strong> and the insert: <strong> inet6num insert: </strong> object(s) for approved assignments must use the netname(s) approved by the RIPE NCC and not be larger than the size approved by the RIPE NCC insert: </p>

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

        The date in the first “changed:” attribute must not be earlier than the date of approval from the RIPE NCC insert: </p>

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

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

        insert: </li>
      • insert: </ul>
      insert: </li>
    8. insert: <li>
    9. insert: <p>

      insert: <a name="B12e"> insert: </a> insert: <strong> Falsified/ incorrect information insert: </strong> insert: </p>

      insert: <p>

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

      insert: </li>
    10. insert: <li>
    11. insert: <p>

      insert: <a name="B12f"> insert: </a> insert: <strong> Fraudulent request insert: </strong> 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: </li>
    12. insert: <li>
    13. insert: <a name="B12g"> insert: </a> insert: <strong> Non-compliance with a RIPE NCC audit insert: </strong> insert: </li>
    14. insert: </ol>
    insert: </ol>
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: <a href="http://www.ripe.net/ripe/docs/audit"> RIPE NCC Audit Activity insert: </a> . insert: </p>

insert: <ol class="listTypeLowerAlpha">
    insert: <li>
  1. insert: <p>

    insert: <a name="B12h"> insert: </a> insert: <strong> Court order insert: </strong> insert: </p>

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

    insert: </li>
  2. insert: </ol>
insert: <h2>

insert: <a name="---procedures-for-deregistration-of-different-types-of-internet-number-resources"> insert: </a> 2. Procedures for deregistration of different types of Internet number resources insert: </h2>

4.1 Closure of Sponsoring LIR insert: <a name="----allocations-and-independent-internet-number-resources-for-member-s-own-network"> insert: </a> 2.1 Allocations and independent Internet number resources for Member's own network

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

insert: <p>

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

insert: <p>

insert: <a href="http://www.ripe.net/membership/indices"> http://www.ripe.net/membership/indices insert: </a> insert: </p>

insert: <p>

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

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

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

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

    The RIPE NCC will change the insert: <strong> mnt-by insert: </strong> object on the Member'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 Member not react within four weeks, the RIPE NCC will: insert: </p>

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

    Change the insert: <strong> mnt-by insert: </strong> object on the Member'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: <strong> route insert: </strong> 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 sponsoring LIR 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 insert: <a href="http://www.ripe.net/ripe/docs/arbitration"> RIPE NCC Conflict Arbitration Procedure insert: </a> ). However, if the four-week period expires without the submission of such evidence by the Member or without the submission of a request for arbitration, the RIPE NCC will proceed as if the Member had never reacted (see relevant procedure above). The Member may still request arbitration according to the timeframes of the RIPE NCC Conflict Arbitration Procedure. If the Member requests arbitration, the RIPE NCC will change the insert: <strong> mnt-by insert: </strong> object on the relevant records to the status “maintainer in the process of being closed, 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="22"> insert: </a> insert: <a name="----independent-internet-number-resources-assigned-through-a--sponsoring-lir-"> insert: </a> 2.2 Independent Internet number resources assigned through a “sponsoring LIR” insert: </h3>

insert: <p>

The RIPE NCC will send an official notification to all registered contacts stating that the Independent Internet number resources will be deregistered, explaining the reasons for this deregistration and the procedure for the deregistration. The Member must immediately inform the End User that was assigned the independent 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 must sign a contract insert: </p>

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

    The RIPE NCC will change the insert: <strong> mnt-by insert: </strong> 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 Member not react within four weeks, the RIPE NCC will: insert: </p>

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

    Change the insert: <strong> mnt-by insert: </strong> 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: <strong> route insert: </strong> 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 Member responds but with a new sponsoring LIR no intention to comply or with the RIPE NCC. This must take place objects at some point within 90 days of the date of 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 insert: <a href="http://www.ripe.net/ripe/docs/arbitration"> RIPE NCC Conflict Arbitration Procedure insert: </a> ). However, if the four-week period expires without the submission of such evidence by the Member or without the submission of a request for arbitration, the RIPE NCC will proceed as if the Member had never reacted (see relevant procedure above). The Member may still request arbitration according to the timeframes of the RIPE NCC Conflict Arbitration Procedure. If the Member requests arbitration, the RIPE NCC will change the insert: <strong> mnt-by insert: </strong> 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="-b------independent-internet-number-resources-directly-assigned-by-the-ripe-ncc-to-direct-assignment-users--b-"> insert: </a> insert: <strong> 2.3. Independent Internet number resources directly assigned by the RIPE NCC to Direct Assignment Users insert: </strong> insert: </h3>

insert: <p>

The RIPE NCC will send an official notification by the RIPE NCC to the contact email addresses listed in the relevant RIPE Database object. delete: </p> delete: <p> delete: <a id="411" name="411"> delete: </a> delete: </p> delete: <p> delete: <b> 4.1.1 De-registration Timeframe delete: </b> delete: </p> delete: <p> delete: <b> Day one: delete: </b> The End 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. insert: </p>

insert: <p>

Should the Direct Assignment User contact email addresses listed in the RIPE Database 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: <strong> mnt-by insert: </strong> object are notified by the RIPE NCC about the need to sign a contract with a new sponsoring LIR or with the RIPE NCC. delete: </p> delete: <p> delete: <b> Day thirty: delete: </b> The End User contact email addresses listed in the RIPE Database object receive an email reminder and a "Remarks" line 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 resource relevant records of the RIPE Database object. delete: </p> delete: <p> delete: <b> Day sixty: delete: </b> The End User contact email addresses listed in the RIPE Database object receive a final email reminder; the resource RIPE Database object is locked with the RIPE NCC maintainer; and reverse delegation is removed for IP address ranges. delete: </p> delete: <p> delete: <b> Day ninety: delete: </b> The resource and related RIPE Database objects are deleted from the RIPE Database. The resource 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 de-registered and put 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: <strong> mnt-by insert: </strong> object on the Member'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 quarantine for future re-assignment. delete: </p> delete: <p> delete: <a id="42" name="42"> delete: </a> delete: </p> delete: <h3> 4.2 Violation of RIPE Policy, Law or Contract delete: </h3> delete: <p> The RIPE NCC will de-register the independent 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: <strong> route insert: </strong> 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 case of a fundamental breach of contract 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: <a href="http://www.ripe.net/ripe/docs/arbitration"> RIPE NCC Conflict Arbitration Procedure insert: </a> ). However, if the four-week period expires without the submission of such evidence by the End User, supported by a Dutch court order; Direct Assignment User or delete: </p> delete: <p> Violation of Law by the End User, supported by a Dutch court order; or violation of RIPE Policy by the End User. delete: </p> delete: <p> delete: <a id="421" name="421"> delete: </a> delete: </p> delete: <p> delete: <b> 4.2.1 De-registration Timeframe delete: </b> delete: </p> delete: <p> delete: <b> Day one: delete: </b> The sponsoring LIR and the End without the submission of a request for arbitration, the RIPE NCC will proceed as if the Direct Assignment User contact email addresses listed 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 Member requests arbitration, the RIPE NCC will change the insert: <strong> mnt-by insert: </strong> object on the relevant records to the status “maintainer in the RIPE Database object receive a notification from the RIPE NCC; the resource RIPE Database object is locked with the RIPE NCC maintainer. delete: </p> delete: <p> delete: <b> Day thirty: delete: </b> The sponsoring LIR and the End User contact email addresses listed in the RIPE Database object receive a notification from the RIPE NCC; the resource and related RIPE Database objects are deleted from the RIPE Database. The resource dispute” and a warning statement will be de-registered and put in quarantine for added to the relevant records of the RIPE Database until the communication of the arbiter's ruling. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <span class="discreet"> NOTE: This document might change due to future re-assignment. delete: </p> delete: <p> delete: <a id="43" name="43"> delete: </a> delete: </p> delete: <h3> 4.3 Contract Expired and Not Renewed / Ceased and Not Transferred delete: </h3> delete: <p> policy changes. If the contract between the sponsoring LIR and the End User of independent Internet number resources has expired and has not been renewed, or has ceased for any other reason, the End User has a maximum of 90 days to sign a contract either with a new sponsoring LIR or with the RIPE NCC. delete: </p> delete: <p> The timeframe for this case is described in Section 4.1.1 - De-registration Timeframe. delete: </p> happens, the RIPE NCC will send a notification to the RIPE NCC Services Working Group mailing list. insert: </span> insert: </p>

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