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

Changes to Closure of LIR and Deregistration of Internet Number Resources

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

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

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

Please note that, for the purposes of this document, LIRs are referred to as “Members”. Section C describes the valid reasons for terminating a Legacy Services Agreement, the procedure that applies in each circumstance, and the consequences and procedures that apply if the Legacy Internet Resource Holder wants to change the status of their Legacy Internet Resources or have them deregistered.

 

delete: <p> delete: <strong> insert: <h2>

Table of Contents delete: </strong> delete: </p> delete: <p>   delete: </p> delete: <p> delete: <a href="#A"> insert: </h2>

insert: <div class="page" title="Page 1">
insert: <div class="layoutArea">
insert: <div class="column">
insert: <p class="western">

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

delete: <p> delete: <a href="#1"> insert: <p class="western">

insert: <a href="#a1"> 1. Grounds for termination and procedure Termination, and the Procedure in each case delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> delete: <a href="#11"> Each Case insert: </a> insert: </p>

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

insert: <a href="#a11"> 1.1. Termination by the Member

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

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

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

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

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

insert: <a href="#a1211"> 1.2.1.1. Violation of RIPE Policies and RIPE NCC procedures delete: </a> delete: </p> delete: <p style="padding-left: 120px;"> delete: <a href="#1211a"> Procedures insert: </a> insert: </p>

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

insert: <a href="#a1211a"> a. Unresponsiveness

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

insert: <a href="#a1211b"> b. Allocations/assignments contravening in contravention of RIPE Policies

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

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

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

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

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

insert: <a class="anchor-link" href="#a1212"> 1.2.1.2 Other reasons delete: </a> delete: </p> delete: <p style="padding-left: 60px;"> delete: <a href="#122"> Reasons insert: </a> insert: </p>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

insert: <a href="#a122g"> g. Untruthful information

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

insert: <a href="#a122h"> h. Non-compliance with RIPE NCC audit delete: </a> delete: </p> delete: <p style="padding-left: 90px;"> delete: <a href="#122i"> audits insert: </a> insert: </p>

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

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

delete: <p> delete: <a class="anchor-link" href="#2"> insert: <p class="western">

insert: <a href="#a2"> 2. Consequences

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

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

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

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

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

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

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

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

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

insert: <a href="#a22"> 2.2. End of RIPE NCC member status delete: </a> delete: </p> delete: <p> Member Status insert: </a> insert: </p>

insert: <p class="western">

 

delete: <p> delete: <a href="#B"> insert: <p class="western">

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

insert: <p class="western">

insert: <a href="#b1"> 1. Reasons for deregistration of Internet number resources delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> delete: <a href="#B11"> 1.1. Deregistration of Internet Number Resources - Allocations and Independent Internet number resources assigned Number Resources Assigned for the Member's own network Own Network or assigned through a “sponsoring Assigned Through a “Sponsoring LIR”

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

insert: <a href="#b1a"> a. Termination of the SSA

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

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

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

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

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

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

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

insert: <a href="#b1e"> e. Fraudulent request

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

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

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

insert: <a href="#b1g"> g. Court order

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

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

insert: <p class="western">

insert: <a href="#b2"> 2. Procedures for Deregistration of Different Types of Internet Number Resources insert: </a> insert: </p>

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

insert: <a href="#b21"> 2.1. Allocations and Independent Internet Number Resources for Member's Own Network insert: </a> insert: </p>

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

insert: <a href="#b22"> 2.2. Independent Internet Number Resources Assigned Through a “Sponsoring LIR” insert: </a> insert: </p>

insert: <p class="western">

  insert: </p>

insert: <p>

insert: <a class="anchor-link" href="#c"> C. Legacy Internet Resources insert: </a> insert: </p>

insert: <p>

insert: <a href="#c1"> 1. Termination of the Legacy Services insert: </a> insert: </p>

delete: <a href="#B12"> 1.2. Independent Internet number resources assigned directly insert: <a href="#c11"> 1.1 Legacy Services by the RIPE NCC for Direct Assignment to a Member Pursuant to the Terms and Conditions Regarding Legacy Internet Resources for Members insert: </a> insert: </p>

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

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

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

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

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

insert: <a href="#c1121"> 1.1.2.1. Non compliance with contractual responsibilities insert: </a> insert: </p>

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

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

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

insert: <a href="#c1122a"> a. The Member's SSA is terminated for any reason insert: </a> insert: </p>

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

insert: <a href="#c1122b"> b. The Member transfers the Legacy Internet Resources to a third party insert: </a> insert: </p>

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

insert: <a href="#c1122c"> c. The member has no rights to use the Legacy Internet Resources insert: </a> insert: </p>

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

insert: <a href="#c1122d"> d. Reasons beyond control of the RIPE NCC insert: </a> insert: </p>

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

insert: <a href="#c12"> 1.2 Legacy Agreement Between the RIPE NCC and a Legacy Internet Resource Holder

delete: <a href="#B12a"> insert: <a href="#c121"> 1.2.1. Termination by the Legacy Internet Resource Holder insert: </a> insert: </p>

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

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

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

insert: <a href="#c1221"> 1.2.2.1. Non-compliance with Contractual Responsibilities insert: </a> insert: </p>

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

insert: <a href="#c1222"> 1.2.2.2. Termination with Immediate Effect insert: </a> insert: </p>

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

insert: <a href="#c1222a"> a. Termination of the RIPE NCC End User Assignment Agreement delete: </a> delete: </p> delete: <p style="padding-left: 60px;"> delete: <a href="#B12b"> The Legacy Internet Resource Holder files for bankruptcy, is liquidated, suspends their payments or becomes insolvent insert: </a> insert: </p>

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

insert: <a href="#c1222b"> b. Unresponsive Direct Assignment User delete: </a> delete: </p> delete: <p style="padding-left: 60px;"> delete: <a href="#B12c"> The Legacy Internet Resource Holder damages the name, trademarks or intellectual property rights of the RIPE NCC insert: </a> insert: </p>

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

insert: <a href="#c1222c"> c. Invalidity of original criteria delete: </a> delete: </p> delete: <p style="padding-left: 60px;"> delete: <a href="#B12d"> The Legacy Internet Resource Holder 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: 120px;">

insert: <a href="#c1222d"> d. Incorrect registration of the assignment in the RIPE Database delete: </a> delete: </p> delete: <p style="padding-left: 60px;"> delete: <a href="#B12e"> The Legacy Internet Resource Holder fails to observe any rule of applicable law insert: </a> insert: </p>

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

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

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

insert: <a href="#c1222f"> f. Untruthful information

delete: <p style="padding-left: 60px;"> delete: <a href="#B12f"> f. Fraudulent request delete: </a> delete: </p> delete: <p style="padding-left: 60px;"> delete: <a href="#B12g"> insert: <p style="padding-left: 120px;">

insert: <a href="#c1222g"> g. Non-compliance with a RIPE NCC audit delete: </a> delete: </p> delete: <p style="padding-left: 60px;"> delete: <a href="#B12h"> RIPE NCC audits insert: </a> insert: </p>

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

insert: <a href="#c1222h"> h. Court order delete: </a> delete: </p> delete: <p> delete: <a class="anchor-link" href="#---procedures-for-deregistration-of-different-types-of-internet-number-resources"> Reasons beyond control of the RIPE NCC insert: </a> insert: </p>

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

insert: <a href="#c1222i"> i. The Legacy Internet Resource Holder transfers the Legacy Internet Resources to a third party insert: </a> insert: </p>

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

insert: <a href="#c1222j"> j. The Legacy Internet Resource Holder has no rights to use the Legacy Internet Resources insert: </a> insert: </p>

insert: <p>

insert: <a href="#c2"> 2. Procedures for deregistration of different types of Internet number resources delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> delete: <a class="anchor-link" href="#----allocations-and-independent-internet-number-resources-for-member-s-own-network"> 2.1. Allocations and Independent Internet number resources for Member's own network delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> delete: <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” delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> delete: <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 delete: </a> delete: </p> delete: <p> delete: <a name="A"> Consequences insert: </a> insert: </p>

insert: <p>

insert: <a href="#c3"> 3. Change of Status of Legacy Internet Resources insert: </a> insert: </p>

insert: <p>

insert: <a href="#c4"> 4. Deregistration of Legacy Internet Resources insert: </a> insert: </p>

insert: </div>
insert: </div>
insert: </div>
insert: <p>

  insert: </p>

insert: <p>

insert: <a name="a">

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

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

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

  • Conform to RIPE Policies.

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

delete: <p> delete: <a name="1"> delete: </a> delete: </p> delete: <h2> insert: <h3>

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

The SSA can be terminated by the Member (see section 1.1) or by the RIPE NCC. The termination Termination by the RIPE NCC can either be occur with a three-month notice period of three months (see section 1.2.1.) or for or, due to specific reasons reasons, with a shorter notice period and immediate effect (see section 1.2.2.).

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

insert: <a name="a11"> insert: </a> insert: <strong> 1.1. Termination by the Member delete: </h3> insert: </strong> insert: </h4>

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:

  • The Member decides to close or to change their business

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

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

Procedure

The notice will Member must formally request the termination of the SSA. delete: </p> delete: <p> It SSA with a written notice. insert: </p>

insert: <p>

The notice must be:

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

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

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

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

Billing issues delete: </strong> delete: </p> delete: <p> If Issues insert: </strong> insert: </p>

insert: <p>

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

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

insert: <a name="a12"> insert: </a> insert: <br />
insert: <strong> 1.2. Termination by the RIPE NCC insert: </strong>

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

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

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

delete: <p> delete: <strong> delete: <a name="1211"> delete: </a> insert: <h4>

insert: <a name="a1211"> insert: </a> insert: <strong> 1.2.1.1 Violation of RIPE Policies and RIPE NCC procedures delete: </strong> delete: </p> Procedures insert: </strong> insert: </h4>

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:

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

insert: <strong> insert: <a name="a1211a"> insert: </a> a. Unresponsiveness delete: <p>  

The Member is unresponsive for a significant period of time.

Member Members are considered to be unresponsive if they do not react to a specific email/request made by the RIPE NCC relating to an incorrect/ambiguous registration of Internet number resources, regardless of whether they are 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> delete: <a name="1211b"> delete: </a> delete: <strong> insert: <p>

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

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> delete: <a name="1211c"> delete: </a> delete: <strong> insert: <p>

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

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

Proper registration must be as follows:

  • The inetnum and the inet6num object(s) for approved assignments must use the netname(s) approved by the RIPE NCC and 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> delete: <a name="1211d"> delete: </a> delete: <strong> insert: <p>

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

For more information, please see the RIPE NCC Conflict Arbitration Procedure .

Procedure

delete: </li> delete: </ol>

If the RIPE NCC becomes aware of any of the aforementioned reasons for terminating the SSA, the RIPE NCC will: delete: </p> delete: <ul> delete: <li> delete: <p> Send will send an email to the registered contact(s) indicating:

  • the The violation

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

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

delete: </li> delete: <li> delete: <p> Terminate insert: <p>

The RIPE NCC will also terminate the progress of any open requests for RIPE NCC services delete: </p> delete: </li> delete: </ul> services. 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 violation

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

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

After 60 days from the date of the first email, if the 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:

  • The violation

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

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

After 90 days from the date of the first email, if the Member continues to 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.

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: <strong> delete: <a name="1212"> delete: </a> 1.2.1.2 delete: </strong> delete: <strong> insert: <h4>

insert: <a name="a1212"> insert: </a> insert: <strong> 1.2.1.2. Other reasons delete: </strong> delete: </p> Reasons insert: </strong> insert: </h4>

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.

For example, such termination has taken place in the past in the case of the emergence of AfriNIC, 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 AFRINIC were signed.

Procedure

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

Unless otherwise required by the circumstances:

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

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

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

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

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

Billing issues Issues

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

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

insert: <a name="a122"> insert: </a> insert: <strong> 1.2.2. Termination with immediate effect delete: </h3> Immediate Effect insert: </strong> insert: </h4>

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: <ol class="listTypeLowerAlpha"> delete: <li> delete: <p> delete: <a name="122a"> delete: </a> delete: <strong> insert: <p>

  insert: </p>

insert: <p>

insert: <strong> insert: <a name="a122a"> insert: </a> a. The Member delete: </strong> delete: <strong> files for bankruptcy, is liquidated, suspends its their payments or becomes insolvent

Upon receipt of the documents stating the bankruptcy, liquidation, suspension of payments or insolvency of the Member delete: </p> delete: <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 fulfils the obligations coming from imposed by the SSA, the RIPE NCC will not terminate the SSA.

Procedure

The RIPE NCC will:

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

    • The reason for termination of the SSA

    • The immediate termination of the SSA

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

insert: <p>

  insert: </p>

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

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

  insert: </p>

insert: <p>

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

Examples:

  • 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> insert: </li>
  • insert: <li>
  • The Member unreasonably makes allegations against the RIPE NCC in order to damage the RIPE NCC's reputation and operations, resulting in irreversible damage to the RIPE NCC delete: </p>

Procedure:

The RIPE NCC will

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

    • the The violation

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

    • the The termination of the SSA if the violation continues

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

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.

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

  • 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> insert: </li>
  • insert: <li>
  • Not approve any Internet number resource requests delete: </p>

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

delete: <ul> delete: <li> delete: <p> insert: <ol type="a">
    insert: <li>
  1. 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> insert: </li>
  2. insert: <li>
  3. Stop providing any services to the Member delete: </p> delete: </li> delete: </ul> insert: </li>
  4. insert: </ol>

After 120 days from the date of the first email, if the Member delete: </p> delete: <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.

delete: </li> delete: <li> delete: <p> delete: <a name="122c"> delete: </a> delete: <strong> insert: <p>

  insert: </p>

insert: <p>

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

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).

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).

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.

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.

If the Member does not submit the aforementioned documents within one month of them being requested to do so by the RIPE NCC, the RIPE NCC will terminate the SSA (see Article 9.4.d of the SSA).

Procedure

The RIPE NCC will:

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

    • the The Member's obligation to submit the relevant documents

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

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

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.

After 30 days from the date of the first email, if the Member continues to 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.

delete: </li> delete: <li> delete: <p> delete: <a name="122d"> delete: </a> delete: <strong> insert: <p>

  insert: </p>

insert: <p>

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

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

Procedure

The RIPE NCC will:

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

    • The reason for termination of the SSA

    • The immediate termination of the SSA

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

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

delete: </li> delete: <li> delete: <p> delete: <a name="122e"> delete: </a> delete: <strong> insert: <p>

  insert: </p>

insert: <p>

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

In case of non-payment, in accordance with the RIPE NCC Billing Procedure, the SSA is will be terminated after 120 days. For more information, please see the RIPE NCC Billing Procedure .

delete: </li> delete: <li> delete: <p> delete: <a name="122f"> delete: </a> delete: <strong> insert: <p>

  insert: </p>

insert: <p>

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

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). RIPE NCC Articles of Association).

Procedure

The RIPE NCC will:

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

    • The reason for termination of the SSA

    • The immediate termination of the SSA

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

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

delete: </li> delete: <li> delete: <p> delete: <a name="122g"> delete: </a> delete: <strong> insert: <p>

  insert: </p>

insert: <p>

insert: <strong> insert: <a name="a122g"> insert: </a> g. Untruthful information

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: <ol type="a">
    • Falsified/incorrect information

    delete: <p> If the insert: </ol>
insert: <p>

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

insert: <ol type="a">
    • Fraudulent requests

    delete: <p> If the insert: </ol>
insert: <p>

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

Procedure

The RIPE NCC will:

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

    • The reason for termination of the SSA

    • The immediate termination of the SSA

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

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

delete: </li> delete: <li> delete: <p> delete: <a name="122h"> delete: </a> delete: <strong> insert: <p>

  insert: </p>

insert: <p>

insert: <strong> insert: <a name="a122h"> insert: </a> h. Non-compliance with RIPE NCC audits

Non-compliance with RIPE NCC audits includes repeated unresponsiveness to or failure to cooperate with the RIPE NCC auditors' requests regarding registrations of Internet number resources for the Member's own network. For more information about the audit procedure, please see the RIPE NCC audit activity Audit Activity .

Procedure

The RIPE NCC will:

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

    • The reason for termination of the SSA

    • The immediate termination of the SSA

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

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

delete: </li> delete: <li> delete: <p> delete: <a name="122i"> delete: </a> delete: <strong> insert: <p>

  insert: </p>

insert: <p>

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

If the 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.

Procedure

The RIPE NCC will:

insert: <ol type="a">
    • Send an email to the registered contact(s) indicating:

      • The reason for termination of the SSA

      • The immediate termination of the SSA

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

    insert: </ol>

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: </li> delete: </ol> delete: <p> delete: <a name="2"> delete: </a> insert: <p>

 

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

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

delete: <p> delete: <a name="21"> delete: </a> delete: </p>

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

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

insert: <a name="a211"> insert: </a> 2.1.1. General services delete: </strong> delete: </h3> Services insert: </strong> insert: </h4>

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 Resource Certification Service (RPKI) service

  • Participation in RIPE NCC Training Courses training courses

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

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

The RIPE NCC will deregister the relevant Internet number resource records. The procedure for deregistration is described in section B.2. The RIPE NCC will also revoke any certificates generated by the RIPE NCC Certification Service.

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

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

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. delete: </p> delete: <p> delete: <a name="22"> delete: </a> delete: </p> delete: <h3> B.2.2 below. insert: </p>

insert: <h4>

insert: <a name="a22"> insert: </a> 2.2. End of RIPE NCC member status delete: </strong> delete: </h3> Member Status insert: </strong> insert: </h4>

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

delete: <a name="B"> delete: </a>  

insert: <a name="b"> insert: </a> B. Deregistration of Internet Number Resources

delete: <p> delete: <a name="B1"> delete: </a> delete: </p> delete: <h2> insert: <h3>

insert: <a name="b1"> insert: </a> insert: <strong> 1. Reasons for deregistration of Internet number resources delete: </h2> delete: <p> delete: <a name="B11"> delete: </a> delete: </p> delete: <h3> 1.1 Deregistration of Internet Number Resources - Allocations and Independent Internet number resources assigned Number Resources Assigned for the Member's own network Own Network or assigned through a “sponsoring Assigned Through a “Sponsoring LIR” insert: </strong>

delete: <ol class="listTypeLowerAlpha"> delete: <li> delete: <p> delete: <a name="B11a"> delete: </a> delete: <strong> insert: <p>

insert: <a name="b1a"> insert: </a> insert: <strong> a. Termination of the SSA

For more information, see section A. For Independent independent Internet number resources through a “sponsoring LIR”, see delete: <a href="http://www.ripe.net/ripe/docs/lir-dau"> 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: </li> delete: <li> delete: <p> delete: <a name="B11b"> delete: </a> delete: <strong> insert: <p>

  insert: </p>

insert: <p>

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

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

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

  insert: </p>

insert: <p>

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

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

Proper registration must be as follows:

insert: <ol>
    • delete: <p> 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 delete: </p> delete: </li> delete: <li> delete: <p> insert: </li>
    • insert: <li>
    • The date in the first “changed:” attribute must not be earlier than the date of approval from the RIPE NCC delete: </p> delete: </li> delete: <li> delete: <p> insert: </li>
    • insert: <li>
    • 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: </p>
    delete: </li> delete: <li> delete: <p> delete: <a name="B11d"> delete: </a> delete: <strong> insert: </ol>
insert: <div class="column">
  insert: </div>
insert: <div class="column">
insert: <strong> insert: <a name="b1d"> insert: </a> d. Falsified/incorrect information delete: </p> insert: </div>

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 independent resource, the RIPE NCC will deregister the relevant records.

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

  insert: </p>

insert: <p>

insert: <strong> insert: <a name="b1e"> insert: </a> e. Fraudulent request

If a Member has submitted a fraudulent request for an allocation or an Independent 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> delete: <a name="B11f"> delete: </a> delete: <strong> insert: <p>

  insert: </p>

insert: <p>

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

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

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

  insert: </p>

insert: <p>

insert: <strong> insert: <a name="g"> insert: </a> insert: <a name="b1g"> insert: </a> g. Court order

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

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

  insert: </p>

insert: <p>

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

See delete: <a href="http://www.ripe.net/ripe/docs/lir-dau"> 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: </li> delete: </ol> insert: <p>

  insert: </p>

insert: <h2>

insert: <a name="b2"> insert: </a> insert: <strong> 2. Procedures for Deregistration of Different Types of Internet Number Resources insert: </strong> insert: </h2>

1.2 insert: <a name="b21"> insert: </a> insert: <strong> 2.1 Allocations and Independent Internet Number Resources for Member's Own Network insert: </strong> insert: </h3>

insert: <p>

The RIPE NCC will send an official notification by email to all registered contacts stating that the allocation/independent Internet number resources directly assigned 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: <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>
  • The Member must stop announcing the allocation/independent Internet number resources insert: </li>
  • insert: <li>
  • The RIPE NCC will change the “mnt-by” attribute on the Member's insert: <strong> inetnum insert: </strong> object to a RIPE NCC maintainer insert: </li>
  • insert: <li>
  • A warning statement will be added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources insert: </li>
  • insert: <li>
  • The RIPE NCC will revoke any certificates generated by the RIPE NCC for Direct Assignment Users Resource Certification (RPKI) service 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>
  • Change the “mnt-by insert: <strong> :” insert: </strong> attribute on the Member's insert: <strong> inetnum insert: </strong> object to a RIPE NCC maintainer; and/or 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 provider 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 Resource Certification (RPKI) Service insert: </p>

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

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

insert: <p>

Please note: insert: </p>

insert: <p>

If the Member responds, but with no intention to comply, or objects at some point within the four-week period, the RIPE NCC will allow the time remaining in this four-week period for the Member to submit evidence that there is no reason for the deregistration of the Internet number resources or to request arbitration (see the 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 lock the relevant records in the RIPE Database and add a warning statement to them, until the communication of the arbiter's ruling. insert: </p>

insert: <p>

  insert: </p>

insert: <h3>

insert: <a name="b22"> insert: </a> insert: <strong> 2.2 Independent Internet Number Resources Assigned Through a “Sponsoring LIR” insert: </strong>

delete: <ol class="listTypeLowerAlpha"> delete: <ol class="listTypeLowerAlpha"> delete: <li> delete: <p> delete: <a name="B12a"> delete: </a> delete: <strong> Termination of the RIPE NCC 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 Assignment Agreement delete: </strong> delete: </p> delete: <p> The RIPE NCC about the imminent deregistration. insert: </p>

insert: <p>

During this period: insert: </p>

insert: <ul>
    insert: <li>
  • The End User Assignment must stop announcing the independent Internet number resources insert: </li>
  • insert: <li>
  • insert: <p>

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

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

    A warning statement will be 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>
  • Change the “mnt-by:” attribute on the relevant object to RIPE NCC maintainer; and/or 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 provider 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 the deregistration of the Internet number resources to reflect reality. As a result, if the Internet number resources are no longer announced after one of these actions, the RIPE NCC might not perform any other actions. insert: </p>

insert: <p>

Please note: insert: </p>

insert: <p>

If the Member responds, but with no intention to comply, or objects at some point within the four-week period, the RIPE NCC will allow the time remaining in this four-week period for the Member to submit evidence that there is no reason for deregistration of the Internet number resources or to request arbitration (see the 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 lock the relevant records in the RIPE Database and add a warning statement to them until the communication of the arbiter's ruling. insert: </p>

insert: <p>

  insert: </p>

insert: <h2>

insert: <a name="c"> insert: </a> insert: <strong> C. Legacy Internet Resources insert: </strong> insert: </h2>

insert: <h3>

insert: <a name="c1"> insert: </a> insert: <strong> 1. Termination of the Legacy Services insert: </strong> insert: </h3>

insert: <p>

This section describes the reasons for the termination of: insert: </p>

insert: <ul> insert: <h3>

insert: <a name="c11"> insert: </a> insert: <strong> 1.1 Legacy Services by the RIPE NCC to a Member Pursuant to the Terms and Conditions Regarding Legacy Internet Resources for Members insert: </strong> insert: </h3>

insert: <p>

The Legacy Services can be terminated by the Member (see section 1.1.1) or by the RIPE NCC. The Termination by the RIPE NCC can either be with a notice period of three months (see section 1.1.2.1) or for specific reasons with a shorter notice period and immediate effect (see section 1.1.2.2). insert: </p>

insert: <h4>

insert: <a name="c111"> insert: </a> insert: <strong> 1.1.1. Termination by the Member insert: </strong> insert: </h4>

insert: <p>

According to Article 5.2 of the Terms and Conditions Regarding Legacy Internet Resources for Members, the Member shall be entitled to terminate the Legacy Services at any time with a written notice period of three months. insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

The notice must be: insert: </p>

insert: <ul>
    insert: <li>
  • Dated and signed by an authorised representative of the Member insert: </li>
  • insert: <li>
  • insert: <p>

    Sent to the RIPE NCC by email at insert: <a class="email-link" title="" href="mailto:legacy@ripe.net" target="_self"> or by postal mail to: 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 regarding Legacy Services is terminated. insert: </p>

insert: <p>

The termination of the Legacy Services will take place three months after the receipt of the notice by the RIPE NCC. insert: </p>

insert: <h4>

insert: <a name="c112"> insert: </a> insert: <strong> 1.1.2. Termination by the RIPE NCC insert: </strong> insert: </h4>

insert: <p>

insert: <a name="c1121"> insert: </a> insert: <strong> 1.1.2.1. Non-compliance with Contractual Responsibilities insert: </strong> insert: </p>

insert: <p>

According to Article 5.3 of the insert: <a data-val="5d4fff292ce54c9791a4537dbfd48894" href="resolveuid/5d4fff292ce54c9791a4537dbfd48894" data-linktype="internal"> RIPE NCC Services for Legacy Internet Resources of RIPE NCC Members Terms and Conditions, insert: </a> the RIPE NCC can terminate the Legacy Services. Grounds for such termination may be the following: insert: </p>

insert: <div class="column">
insert: <p>

a. The Member does not provide the RIPE NCC with complete, updated and accurate information necessary for the provision of the Legacy Services insert: </p>

insert: <p>

b. The Member does not maintain accurate data in the RIPE Database regarding the Legacy Internet Resources insert: </p>

insert: <p>

c. The Member does not assist the RIPE NCC with data accuracy checks in accordance with the procedure described in RIPE NCC procedural documents, including the documents insert: <a href="http://www.ripe.net/publications/due-diligence"> Due Diligence for the Quality of the RIPE NCC Registration Data insert: </a> and insert: <a data-val="db489aea245ca2a1b81478bf121c58ab" href="resolveuid/db489aea245ca2a1b81478bf121c58ab" data-linktype="internal"> RIPE NCC Audit Activity insert: </a> insert: </p>

insert: </div>
insert: <div class="column">
  insert: </div>
insert: <p>

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

insert: <p>

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

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

      The termination of the Legacy Services in three months if the violation continues insert: </p>

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

    Terminate the progress of any open requests related to Legacy Services insert: </p>

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

    Add the remark "under review" in the RIPE Database resource object insert: </p>

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

    Add a warning statement to the relevant records of the RIPE Database mentioning that the Legacy Internet Resources are not in compliance with data accuracy obligations insert: </p>

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

    Revoke any certificates generated by the RIPE NCC Resource Certification (RPKI) service relating to Legacy Internet Resources insert: </p>

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

  insert: </p>

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

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

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

    The termination of the Legacy Services in two months if the violation continues insert: </p>

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

  insert: </p>

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

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

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

    The termination of the Legacy Services in one month if the violation continues insert: </p>

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

  insert: </p>

insert: <p>

After 90 days from the date of the first email, if the Member continues to not comply, the RIPE NCC Managing Director will send an official notification of termination of the Legacy Services to all registered postal and email addresses of the Member. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <a name="c1122"> insert: </a> insert: <strong> 1.1.2.2. Termination with Immediate Effect insert: </strong> insert: </p>

insert: <p>

According to Article 5.4 of the Legacy Agreement, the RIPE NCC can terminate the Legacy Services with immediate effect for the following reasons: insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <a name="c1122a"> insert: </a> insert: <strong> a. The Member's SSA is terminated for any reason insert: </strong> insert: </p>

insert: <p>

Upon termination of the Member's SSA (see section A of this document), the Legacy Services are also terminated without any further notification being necessary. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <a name="c1122b"> insert: </a> insert: <strong> b. The Member transfers the Legacy Internet Resources to a third party insert: </strong> insert: </p>

insert: <p>

If the Member transfers the Legacy Internet Resources to a third party, the Legacy Services provided by the RIPE NCC regarding these Legacy Internet Resources are not transferred to the third party. The third party has to sign a contractual agreement with either the RIPE NCC or a sponsoring LIR. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <a name="c1122c"> insert: </a> insert: <strong> c. The Member has no rights to use the Legacy Internet Resources insert: </strong> insert: </p>

insert: <p>

If a third party provides sufficient evidence proving the Legacy Internet Resources must not be registered with the Member, the RIPE NCC will immediately terminate the Legacy Services. insert: </p>

insert: <p>

If the sufficient evidence refers to some of the Legacy Internet Resources, the RIPE NCC may decide not to terminate all Legacy Services but only those related to the Legacy Internet Resource in doubt. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <a name="c1122d"> insert: </a> insert: <strong> d. Reasons beyond control of the RIPE NCC insert: </strong> insert: </p>

insert: <p>

The RIPE NCC may terminate the Legacy Services if the continuation of the Legacy Services is impossible for reasons above and beyond control by the RIPE NCC or if the RIPE NCC cannot reasonably be required to continue the Legacy Services for reasons that cannot be attributed to the RIPE NCC and for which the RIPE NCC cannot be held accountable by virtue of law, a juridical act or generally accepted principles. 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 Legacy Services insert: </p>

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

      The immediate termination of the Legacy Services insert: </p>

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

    Terminate the progress of any open requests related to Legacy Services insert: </p>

    insert: </li>
  • insert: </ul>
insert: <div>
  insert: </div>
insert: <h3>

insert: <a name="c12"> insert: </a> insert: <strong> 1.2 Legacy Agreement Between the RIPE NCC and a Legacy Internet Resource Holder insert: </strong> insert: </h3>

insert: <p>

The Legacy Agreement can be terminated by the Legacy Internet Resource Holder (see section 1.2.1) or by the RIPE NCC. Termination by the RIPE NCC can either occur with a three-month notice period(see section 1.2.2.1), or, for specific reasons, with immediate effect (see section 1.2.2.2). insert: </p>

insert: <h4>

insert: <a name="c121"> insert: </a> insert: <strong> 1.2.1. Termination by the Legacy Internet Resource Holder insert: </strong> insert: </h4>

insert: <p>

According to Article 7.2 of the insert: <a data-val="998bd8c50578438bbf452944f6b1a4d7" href="resolveuid/998bd8c50578438bbf452944f6b1a4d7" data-linktype="internal"> Legacy Agreement insert: </a> , the Legacy Internet Resource Holder shall be entitled to terminate according the Legacy Agreement at any time with a written notice of three months. insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

It must be: insert: </p>

insert: <ul>
    insert: <li>
  • Dated and signed by an authorised representative of the Legacy Internet Resource Holder. insert: </li>
  • insert: <li>
  • Sent to the RIPE NCC by email to insert: <a class="email-link" title="" href="mailto:legacy@ripe.net" target="_self"> or by postal mail to: Singel 258, 1016 AB Amsterdam, the Netherlands insert: </li>
  • insert: </ul>
insert: <p>

  insert: </p>

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 regarding Legacy Services under the Legacy Agreement is terminated. insert: </p>

insert: <p>

The termination of the Legacy Agreement 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>

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

insert: <p>

  insert: </p>

insert: <h4>

insert: <a name="c122"> insert: </a> insert: <strong> 1.2.2. Termination by the RIPE NCC insert: </strong> insert: </h4>

insert: <p>

insert: <a name="c1221"> insert: </a> insert: <strong> 1.2.2.1. Non-compliance with Contractual Responsibilities insert: </strong> insert: </p>

insert: <p>

According to Article 7 of that agreement. Sections A.1 and A.2.2 above, referring to the SSA and the Members, 7.3 of the Legacy Agreement, the RIPE NCC can apply accordingly for the RIPE NCC End User Assignment Agreement and the Direct Assignment Users. delete: </p> delete: </li> delete: <li> delete: <p> delete: <a name="B12b"> delete: </a> delete: <strong> Unresponsive Direct Assignment User delete: </strong> delete: </p> delete: <p> Direct Assignment Users are considered to terminate the Legacy Agreement. Grounds for such termination may be unresponsive if they do not react to a specific email/request made by the RIPE NCC relating to an incorrect/ambiguous registration of Internet number resources, regardless of whether they are at the same time responsive to a different email/request from the RIPE NCC or they continue paying the RIPE NCC fees (see also the RIPE Policy delete: <a href="http://www.ripe.net/ripe/docs/contract-req"> Contractual Requirements for Provider Independent the following: insert: </p>

insert: <p>

a. The Legacy Internet Resource Holders in the RIPE NCC Service Region delete: </a> ). delete: </p> delete: </li> delete: <li> delete: <p> delete: <a name="B12c"> delete: </a> delete: <strong> Invalidity of original criteria delete: </strong> delete: </p> delete: <p> If the Direct Assignment User Holder does not inform the RIPE NCC of provide the RIPE NCC with complete, updated and accurate information necessary for the provision of the service under the Legacy Agreement insert: </p>

insert: <p>

b. The Legacy Internet Resource Holder does not maintain accurate data in the RIPE Database regarding the Legacy Internet Resources insert: </p>

insert: <p>

c. The Legacy Internet Resource Holder does not assist the RIPE NCC with data accuracy checks in accordance with the procedure described in RIPE NCC procedural documents, including the documents insert: <a href="http://www.ripe.net/publications/due-diligence"> Due Diligence for the Quality of the RIPE NCC Registration Data insert: </a> and insert: <a href="http://www.ripe.net/ripe/docs/audit" data-val="http://www.ripe.net/ripe/docs/audit" data-linktype="external"> RIPE NCC Audit Activity insert: </a> insert: </p>

insert: <p>

d. The Legacy Internet Resource Holder does not comply with an arbiter's ruling (see insert: <a data-val="b81490fe2c00243a37cb5c5ffaab8f6e" href="resolveuid/b81490fe2c00243a37cb5c5ffaab8f6e" data-linktype="internal"> RIPE NCC Conflict Arbitration Procedure insert: </a> ) insert: </p>

insert: <p>

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

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

    Send an email to the registered contact(s) of the Legacy Internet Resource Holder indicating: insert: </p>

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

      The violation insert: </p>

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

      The Legacy Internet Resource Holder's obligation to stop or rectify the violation insert: </p>

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

      The termination of the Legacy Agreement in three months if the violation continues insert: </p>

      insert: </li>
    • insert: </ul>
    insert: </li>
  • insert: <li>
  • Terminate the progress of any open requests related to the Legacy Agreement insert: </li>
  • insert: <li>
  • insert: <p>

    Add the remark "under review" in the RIPE Database resource object insert: </p>

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

    Add a warning statement to the relevant records of the RIPE Database mentioning that the Legacy Internet Resources are not in compliance with data accuracy obligations insert: </p>

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

    Revoke any certificates generated by the RIPE NCC Resource Certification (RPKI) service relating to Legacy Internet Resources insert: </p>

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

If the Legacy Internet Resource Holder does not comply within 30 days of the date of the email, the RIPE NCC will send a reminder email to the registered contact(s) indicating: insert: </p>

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

    The Legacy Internet Resource Holder's obligation to stop or rectify the violation insert: </p>

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

    The termination of the Legacy Agreement in two 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 Legacy Internet Resource Holder still does not comply, the RIPE NCC will send a second reminder email and a reminder by postal mail to the registered email and email addresses indicating: insert: </p>

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

    The Legacy Internet Resource Holder's obligation to stop or rectify the violation insert: </p>

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

    The termination of the Legacy Agreement in one 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 Legacy Internet Resource Holder continues to not comply, the RIPE NCC Managing Director will send an official notification of termination of the Legacy Agreement to all registered postal and email addresses of the Legacy Internet Resource Holder. 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: </p>

insert: <p>

insert: <a name="c1222"> insert: </a> insert: <strong> 1.2.2.2. Termination with Immediate Effect insert: </strong> insert: </p>

insert: <p>

According to Article 7.4 of the Legacy Agreement, the RIPE NCC can terminate the Agreement with immediate effect for the following reasons: insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <a name="c1222a"> insert: </a> insert: <strong> a. The Legacy Internet Resource Holder files for bankruptcy, is liquidated, suspends their 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 Legacy Internet Resource Holder by the relevant authority or by public announcement of the fact, the RIPE NCC will terminate the Legacy Agreement. If the relevant national authority decides that the Legacy Internet Resource Holder's operations can continue, and provided that the Legacy Internet Resource Holder fulfils the obligations imposed by the Legacy Agreement, the RIPE NCC will not terminate the Legacy Agreement. 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 Legacy Agreement insert: </p>

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

      The immediate termination of the Legacy Agreement insert: </p>

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

    Terminate the progress of any open requests related to the Legacy Agreement insert: </p>

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

  insert: </p>

insert: <p>

The RIPE NCC Managing Director will send an official notification of termination of the Legacy Agreement to all registered contacts of the Legacy Internet Resource Holder or to the legal successor, both by electronic and registered postal mail. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <a name="c1222b"> insert: </a> insert: <strong> b. The Legacy Internet Resource Holder damages the name, trademarks or intellectual property rights of the RIPE NCC insert: </strong> insert: </p>

insert: <p>

Examples: insert: </p>

insert: <p>

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

insert: <p>

The Legacy Internet Resource Holder unreasonably makes allegations against the RIPE NCC in order to damage the RIPE NCC's reputation and operations, resulting in irreversible damage to the RIPE NCC 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>
    • The violation insert: </li>
    • insert: <li>
    • The Legacy Internet Resource Holder's obligation to stop or rectify the violation insert: </li>
    • insert: <li>
    • The termination of the SSA if the violation continues insert: </li>
    • insert: </ul>
    insert: </li>
  • insert: <li>
  • insert: <p>

    Terminate the progress of any open requests related to the Legacy Agreement insert: </p>

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

  insert: </p>

insert: <p>

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

insert: <p>

After 60 days from the date of the first email, if the Legacy Internet Resource Holder still does not comply, the RIPE NCC will send a second reminder email to the registered contact(s) indicating the same as above. insert: </p>

insert: <p>

After 90 days from the date of the first email, if the Legacy Internet Resource Holder continues to not comply, the RIPE NCC will send a third reminder email and a reminder by postal mail to the registered email and postal addresses indicating the same as above. insert: </p>

insert: <p>

After 120 days from the date of the first email, if the Legacy Internet Resource Holder still does not comply, the RIPE NCC Managing Director will send an official notification of termination of the Legacy Agreement to all registered postal and email addresses of the Legacy Internet Resource Holder. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <a name="c1222c"> insert: </a> insert: <strong> c. The Legacy Internet Resource Holder fails to submit to the RIPE NCC a valid extract from the Commercial Trade Register or equivalent register insert: </strong> insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

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

insert: <p>

If there is any change in the original technical criteria or the original Legacy Internet Resource Holder's business purposes for using the resources when the change takes place, the RIPE NCC after signing the Legacy Agreement (for example, the Legacy Internet Resource Holder has merged with another company, has changed name, etc.) and, because of this change, the Legacy Internet Resource Holder's registration with the relevant register has been changed, then the Legacy Internet Resource Holder is authorised to deregister the relevant Internet number resources. delete: </p> delete: </li> delete: <li> delete: <p> delete: <a name="B12d"> delete: </a> delete: <strong> Incorrect obliged to submit the updated registration of the assignment in the RIPE Database delete: </strong> papers to the RIPE NCC.

If the Direct Assignment User Legacy Internet Resource Holder does not properly register submit the aforementioned documents within one month of them being requested by the RIPE NCC, the RIPE NCC will terminate the Legacy Agreement (see Article 7.5.d of the Legacy Agreement). 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 Legacy Internet Resource Holder's obligation to submit the relevant documents insert: </p>

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

      The termination of the Legacy Agreement 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 related to the Legacy Agreement insert: </p>

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

  insert: </p>

insert: <p>

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

insert: <p>

After 30 days from the date of the first email, if the Legacy Internet Resource Holder continues to not comply, the RIPE NCC Managing Director will send an official notification of termination of the Legacy Agreement to all registered postal and email addresses of the Legacy Internet Resource Holder. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <a name="c1222d"> insert: </a> insert: <strong> d. The Legacy Internet Resource Holder fails to observe any rule of applicable law insert: </strong> insert: </p>

insert: <p>

The Legacy Agreement is exclusively governed by the laws of the Netherlands because the RIPE NCC is an association under Dutch law. The RIPE NCC is allowed to terminate the Legacy Agreement of a Legacy Internet Resource Holder with immediate effect, provided it receives a Dutch court order to do so. 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 Legacy Agreement insert: </p>

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

      The immediate termination of the Legacy Agreement insert: </p>

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

    Terminate the progress of any open requests related to the Legacy Agreement insert: </p>

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

The RIPE NCC Managing Director will send an official notification of termination of the Legacy Agreement. to all registered postal and email addresses of the Legacy Internet Resource Holder. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <a name="c1222e"> insert: </a> insert: <strong> e. Non-payment insert: </strong> insert: </p>

insert: <p>

In case of non-payment, in the RIPE Database the assignment approved by the RIPE NCC, the RIPE NCC accordance with the RIPE NCC Billing Procedure, the Legacy Agreement will be 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: <p>

  insert: </p>

insert: <p>

insert: <a name="c1222f"> insert: </a> insert: <strong> f. Untruthful information insert: </strong> insert: </p>

insert: <p>

The RIPE NCC concludes the Legacy Agreement and provides services to Legacy Internet Resource Holder in good faith. The Legacy Internet Resource Holder is authorised to deregister the relevant Internet number resources. delete: </p> delete: <p> Proper registration must be as follows: delete: </p> delete: <ul> delete: <li> delete: <p> The delete: <strong> inetnum delete: </strong> and the delete: <strong> inet6num delete: </strong> object(s) for approved assignments must use the netname(s) approved by the RIPE NCC and not be larger than the size approved by the RIPE NCC delete: </p> delete: </li> delete: <li> delete: <p> The date in the first “changed:” attribute must not be earlier than the date of approval from the RIPE NCC delete: </p> delete: </li> delete: <li> delete: <p> The data must be valid and must allow the RIPE NCC to contact the natural person referenced directly in the delete: <strong> inetnum delete: </strong> or delete: <strong> inet6num delete: </strong> object(s) or via the maintainers of the delete: <strong> inetnum delete: </strong> or delete: <strong> inet6num delete: </strong> object(s) within a reasonable time without having to get information from another source delete: </p> delete: </li> delete: </ul> delete: </li> delete: <li> delete: <p> delete: <a name="B12e"> delete: </a> delete: <strong> Falsified/ incorrect information delete: </strong> delete: </p> delete: <p> If a Direct Assignment User has provided breach of good faith, if the Legacy Internet Resource Holder repeatedly provides falsified data or information, or purposefully and/or repeatedly provided provides incorrect data or information (for example, falsified registration documents or IDs, incorrect/inaccurate contact details, etc.) regarding 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 allocation or an Independent resource, the RIPE NCC will deregister the relevant records. delete: </p> delete: </li> delete: <li> delete: <p> delete: <a name="B12f"> delete: </a> delete: <strong> Fraudulent request delete: </strong> delete: </p> delete: <p> If a Direct Assignment User has submitted a fraudulent request for assignment of an Independent resource (for example, providing incorrect purpose/need or falsified information about the network, etc.), the RIPE NCC will deregister the relevant records. delete: </p> delete: </li> delete: <li> delete: <a name="B12g"> delete: </a> delete: <strong> Non-compliance with a RIPE NCC audit delete: </strong> delete: </li> delete: </ol> delete: </ol> delete: <p> If a Direct Assignment User does not comply with a RIPE NCC audit regarding an assignment of an Independent resource, the RIPE NCC will deregister the relevant records. Non-compliance includes, but is not limited to, unresponsiveness to or failure to cooperate with the RIPE NCC auditors' requests. For more information about the audit procedure, please see the delete: <a href="http://www.ripe.net/ripe/docs/audit"> RIPE NCC Audit Activity delete: </a> . delete: </p> delete: <ol class="listTypeLowerAlpha"> delete: <li> delete: <p> delete: <a name="B12h"> delete: </a> delete: <strong> Court order delete: </strong> delete: </p> delete: <p> The RIPE NCC is an association under Dutch law. In the event a Dutch court orders deregistration of specific Internet number resources, the RIPE NCC must and will comply. delete: </p> delete: </li> delete: </ol> delete: <h2> delete: <a name="---procedures-for-deregistration-of-different-types-of-internet-number-resources"> delete: </a> 2. Procedures for deregistration of different types of Internet number resources delete: </h2> delete: <h3> delete: <a name="----allocations-and-independent-internet-number-resources-for-member-s-own-network"> delete: </a> 2.1 Allocations and independent Internet number resources for Member's own network delete: </h3> delete: <p> The RIPE NCC email to the registered contact(s) indicating: insert: </p>

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

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

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

      The immediate termination of the Legacy Agreement insert: </p>

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

    Terminate the progress of any open requests related to the Legacy Agreement insert: </p>

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

The RIPE NCC Managing Director will send an official notification by email of termination of the Legacy Agreement to all registered contacts stating postal and email addresses of the Legacy Internet Resource Holder. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <a name="c1222g"> insert: </a> insert: <strong> g. 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 Legacy Internet Resource Holder's own network. 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: <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 Legacy Agreement insert: </p>

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

      The immediate termination of the Legacy Agreement insert: </p>

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

    Terminate the progress of any open requests related to the Legacy Agreement. insert: </p>

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

The RIPE NCC Managing Director will send an official notification of termination of the Legacy Agreement to all registered postal and email addresses of the Legacy Internet Resource Holder. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <a name="c1222h"> insert: </a> insert: <strong> h. Reasons beyond control of the RIPE NCC insert: </strong> insert: </p>

insert: <p>

If the continuation of the Legacy Agreement is impossible for reasons above and beyond control by the RIPE NCC or if the RIPE NCC cannot reasonably be required to continue the Legacy Agreement for reasons that the allocation/independent 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. 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 Legacy Agreement insert: </p>

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

      The immediate termination of the Legacy Agreement 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 Legacy Agreement to all registered postal and email addresses of the Legacy Internet Resource Holder. 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: </p>

insert: <p>

insert: <a name="c1222i"> insert: </a> insert: <strong> i. The Legacy Internet Resource Holder transfers the Legacy Internet Resources to a third party insert: </strong> insert: </p>

insert: <p>

If the Legacy Internet Resource Holder transfers the Legacy Internet Resources to a third party, the Legacy Services provided by the RIPE NCC regarding these Legacy Internet Resources are not transferred to the third party. The third party has to sign a contractual agreement with either the RIPE NCC or a sponsoring LIR. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <a name="c1222j"> insert: </a> insert: <strong> j. The Legacy Internet Resource Holder has no rights to use the Legacy Internet Resources insert: </strong> insert: </p>

insert: <p>

If a third party provides sufficient evidence proving the Legacy Internet Resources must not be registered with the Legacy Internet Resource Holder, the RIPE NCC will immediately terminate the Legacy Agreement. insert: </p>

insert: <p>

If the sufficient evidence refers to some of the Legacy Internet Resources, the RIPE NCC may decide not to terminate the Legacy Agreement but to update it by removing the Legacy Internet Resources in doubt. insert: </p>

insert: <p>

  insert: </p>

insert: <h2>

insert: <a name="c2"> insert: </a> insert: <strong> 2. Consequences insert: </strong> insert: </h2>

insert: <p>

This section describes the consequences of the termination of: insert: </p>

insert: <ul> insert: <p>

  insert: </p>

insert: <p>

Upon termination of the Legacy Services/Agreement for reasons of non-compliance with contractual responsibilities: insert: </p>

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

    The RIPE NCC will add the remark “No-contract” in the RIPE Database resource object; and insert: </p>

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

    A warning statement will be added to the relevant records in the RIPE Database mentioning that the Legacy Internet Resources are not covered by a contractual relationship; and insert: </p>

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

    The RIPE NCC will withdraw the reverse delegation; and insert: </p>

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

    The RIPE NCC will not be obliged to keep providing the holder with services other than those provided, with regards to each Legacy Internet Resources immediately before the agreement to the insert: <a data-val="5d4fff292ce54c9791a4537dbfd48894" href="resolveuid/5d4fff292ce54c9791a4537dbfd48894" data-linktype="internal"> RIPE NCC Services for Legacy Internet Resources of RIPE NCC Members Terms and Condition insert: </a> s or the signing of the Legacy Agreement (this does not include the reverse delegation) insert: </p>

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

  insert: </p>

insert: <p>

Upon termination of the Legacy Service/Agreement for any other reason: insert: </p>

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

    The RIPE NCC will add the remark “No-contract” in the RIPE Database resource object; and insert: </p>

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

    A warning statement will be added to the relevant records in the RIPE Database mentioning that the Legacy Internet Resources are not covered by a contractual relationship; and insert: </p>

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

    The RIPE NCC will not be obliged to keep providing the holder with services other than those provided, with regards to each Legacy Internet Resources immediately before the agreement to the insert: <a data-val="5d4fff292ce54c9791a4537dbfd48894" href="resolveuid/5d4fff292ce54c9791a4537dbfd48894" data-linktype="internal"> RIPE NCC Services for Legacy Internet Resources of RIPE NCC Members Terms and Conditions insert: </a> or the signing of the Legacy Agreement insert: </p>

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

Please note that if the termination of the Legacy Agreement takes place because of contractual relationship changes between the Legacy Internet Resource Holder and the sponsoring LIR, the RIPE NCC procedural document insert: <a data-val="37f6439b9c5e4e479b652d0830127df7" href="resolveuid/37f6439b9c5e4e479b652d0830127df7" data-linktype="internal"> Legacy Internet Resources – Contractual Relationship Changes Between Sponsoring LIR and Legacy Internet Resource Holder insert: </a> is applicable. insert: </p>

insert: <p>

  insert: </p>

insert: <h2>

insert: <a name="c3"> insert: </a> insert: <strong> 3. Change of Status of Legacy Internet Resources insert: </strong> insert: </h2>

insert: <p>

If a Legacy Internet Resource Holder (Member or not) wants to have particular Legacy Internet Resources registered as if they had been distributed by the RIPE NCC, the Legacy Internet Resource Holder must send an email to insert: <a href="mailto:legacy@ripe.net"> legacy@ripe.net insert: </a> . In the email, the Legacy Internet Resource Holder must: insert: </p>

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

    Indicate the Legacy Internet Resources; and insert: </p>

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

    Acknowledge that the RIPE NCC will apply for these resources the RIPE Policies concerning Internet number resources distributed by the RIPE NCC insert: </p>

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

The RIPE NCC will send an acknowledgement of the receipt of the notice. Upon the sending of such notice, the resources will be deregistered, explaining the reasons for this deregistration and the procedure of the deregistration. The Member considered as distributed by the RIPE NCC. insert: </p>

insert: <h2>

insert: <a name="c4"> insert: </a> insert: <strong> 4. Deregistration of Legacy Internet Resources insert: </strong> insert: </h2>

insert: <p>

If a Legacy Internet Resource Holder (Member or not) wants to deregister particular Legacy Internet Resources, the Legacy Internet Resource Holder must send an email to insert: <a href="mailto:legacy@ripe.net"> legacy@ripe.net insert: </a> . In the email, the Legacy Internet Resource Holder must: insert: </p>

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

    Indicate the Legacy Internet Resources; and insert: </p>

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

    Acknowledge that they resign from any rights with regards to these resources insert: </p>

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

The RIPE NCC will not be able make any further assignments from the allocations. delete: </p> delete: <p> Should the Member respond within four weeks, the RIPE NCC will provide a timeframe of three months for the Members to take care of any actions necessary for the deregistration of the Internet number resources. In the case of allocations, Members are responsible for requesting that their customers renumber immediately and for providing them with all available options. In particular, Members must refer their customers to the list of other Members. This list is available at: delete: </p> delete: <p> delete: <a href="http://www.ripe.net/membership/indices"> http://www.ripe.net/membership/indices delete: </a> delete: </p> delete: <p> During the three-month period: delete: </p> delete: <ul> delete: <li> delete: <p> The Member send an acknowledgement of the receipt of the notice. Upon the sending of such notice, the Legacy Internet Resource Holder must stop announcing the allocation/independent Internet number resources delete: </p> delete: </li> delete: <li> delete: <p> The RIPE NCC will change the delete: <strong> mnt-by delete: </strong> object on the Member's records to the status “deregistered maintainer” delete: </p> delete: </li> delete: <li> delete: <p> A warning statement is added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources delete: </p> delete: </li> delete: <li> delete: <p> The RIPE NCC will revoke any certificates generated by the RIPE NCC Certification Service delete: </p> delete: </li> delete: </ul> delete: <p> After the three-month period, the allocation/assignment will be deregistered from the RIPE Database. delete: </p> delete: <p> Should the Member not react within four weeks, the Legacy Internet Resources. The RIPE NCC will:

    delete: <li> delete: <p> Change the delete: <strong> mnt-by delete: </strong> object on the Member's records to the status “deregistered maintainer”; and/or delete: </p> delete: </li> delete: <li> delete: <p> Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the Internet number resources; and/or delete: </p> delete: </li>
  • 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 and

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

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

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

insert: <pre>
 Note: this page was edited on 5 August 2016 with a minor correction to the table of contents: C. Legacy Internet Resources, sections 1.2.2.2 b., 1.2.2.2 c., 1.2.2.2 d., 1.2.2.2 i. and 1.2.2.2 j. were updated to match the corresponding headings in the document. There were  no longer announced after one of these actions, the RIPE NCC might not perform any other actions.  delete: </p> delete: <p> Please note:  delete: </p> delete: <p> If the Member responds but with no intention to comply or objects at some point within the four-week period, the RIPE NCC will allow the time remaining in this four-week period for the Member to submit evidence that there is no reason for the deregistration of the Internet number resources or to request arbitration (see  delete: <a href="http://www.ripe.net/ripe/docs/arbitration"> RIPE NCC Conflict Arbitration Procedure  delete: </a> ). However, if the four-week period expires without the submission of such evidence by the Member or without the submission of a request for arbitration, the RIPE NCC will proceed as if the Member had never reacted (see relevant procedure above). The Member may still request arbitration according to the timeframes of the RIPE NCC Conflict Arbitration Procedure. If the Member requests arbitration, the RIPE NCC will change the  delete: <strong> mnt-by  delete: </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.  delete: </p> delete: <h3> delete: <a name="22"> delete: </a> delete: <a name="----independent-internet-number-resources-assigned-through-a--sponsoring-lir-"> delete: </a> 2.2 Independent Internet number resources assigned through a “sponsoring LIR”  delete: </h3> delete: <p> The RIPE NCC will send an official notification to all registered contacts stating that the Independent Internet number resources will be deregistered, explaining the reasons for this deregistration and the procedure for the deregistration. The Member must immediately inform the End User about the imminent deregistration.  delete: </p> delete: <p> During this period:  delete: </p> delete: <ul> delete: <li> 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: <strong> mnt-by  delete: </strong> object on the relevant records to the status “deregistered maintainer”  delete: </p> delete: </li> delete: <li> delete: <p> A warning statement is added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources  delete: </p> delete: </li> delete: </ul> delete: <p> After the three-month period, the independent Internet number resources will be deregistered from the RIPE Database.  delete: </p> delete: <p> Should the Member not react within four weeks, the RIPE NCC will:  delete: </p> delete: <ul> delete: <li> delete: <p> Change the  delete: <strong> mnt-by  delete: </strong> object on the relevant records to the status “deregistered maintainer”; and/or  delete: </p> delete: </li> delete: <li> delete: <p> Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the Internet number resources; and/or  delete: </p> delete: </li> delete: <li> delete: <p> Withdraw the reverse delegation; and/or  delete: </p> delete: </li> delete: <li> delete: <p> Contact the upstream to investigate possible hijacking of Internet number resources; and/or  delete: </p> delete: </li> delete: <li> delete: <p> Delete all relevant objects in the RIPE Database, including allocation/assignment and  delete: <strong> route  delete: </strong> objects  delete: </p> delete: </li> delete: </ul> delete: <p> The sole purpose of these actions by the RIPE NCC is for deregistration of the Internet number resources to reflect reality. As a result, if the Internet number resources are no longer announced after one of these actions, the RIPE NCC might not perform any other actions.  delete: </p> delete: <p> Please note:  delete: </p> delete: <p> If the Member responds but with no intention to comply or objects at some point within the four-week period, the RIPE NCC will allow the time remaining in this four-week period for the Member to submit evidence that there is no reason for deregistration of the Internet number resources or to request arbitration (see  delete: <a href="http://www.ripe.net/ripe/docs/arbitration"> RIPE NCC Conflict Arbitration Procedure  delete: </a> ). However, if the four-week period expires without the submission of such evidence by the Member or without the submission of a request for arbitration, the RIPE NCC will proceed as if the Member had never reacted (see relevant procedure above). The Member may still request arbitration according to the timeframes of the RIPE NCC Conflict Arbitration Procedure. If the Member requests arbitration, the RIPE NCC will change the  delete: <strong> mnt-by  delete: </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.  delete: </p> delete: <h3> delete: <a name="-b------independent-internet-number-resources-directly-assigned-by-the-ripe-ncc-to-direct-assignment-users--b-"> delete: </a> delete: <strong> 2.3. Independent Internet number resources directly assigned by the RIPE NCC to Direct Assignment Users  delete: </strong> delete: </h3> delete: <p> The RIPE NCC will send an official notification by email to all registered contacts stating that the Independent Internet number resources will be deregistered, explaining the reasons for this deregistration and the procedure for the deregistration.  delete: </p> delete: <p> Should the Direct Assignment User respond within four weeks, the RIPE NCC will provide a timeframe of three months for the Direct Assignment User to take care of any actions necessary for the deregistration of the Internet number resources.  delete: </p> delete: <p> During the three-month period:  delete: </p> delete: <ul> delete: <li> delete: <p> The Direct Assignment User must stop announcing the Independent Internet number resources  delete: </p> delete: </li> delete: <li> delete: <p> The RIPE NCC will change the  delete: <strong> mnt-by  delete: </strong> object on the Direct Assignment User's records to the status “deregistered maintainer”  delete: </p> delete: </li> delete: <li> delete: <p> A warning statement is added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources  delete: </p> delete: </li> delete: </ul> delete: <p> After the three-month period, the Independent Internet number resources will be deregistered from the RIPE Database.  delete: </p> delete: <p> Should the Direct Assignment User not react within four weeks, the RIPE NCC will:  delete: </p> delete: <ul> delete: <li> delete: <p> Change the  delete: <strong> mnt-by  delete: </strong> object on the Member's records to the status “deregistered maintainer”; and/or  delete: </p> delete: </li> delete: <li> delete: <p> Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the Internet number resources; and/or  delete: </p> delete: </li> delete: <li> delete: <p> Withdraw the reverse delegation; and/or  delete: </p> delete: </li> delete: <li> delete: <p> Contact the upstream to investigate possible hijacking of Internet number resources; and/or  delete: </p> delete: </li> delete: <li> delete: <p> Delete all relevant objects in the RIPE Database, including assignment and  delete: <strong> route  delete: </strong> objects  delete: </p> delete: </li> delete: </ul> delete: <p> The sole purpose of these actions by the RIPE NCC is for deregistration of the Internet number resources to reflect reality. As a result, if the Internet number resources are no longer announced after one of these actions, the RIPE NCC might not perform any other actions.  delete: </p> delete: <p> Please note:  delete: </p> delete: <p> If the Direct Assignment User responds but with no intention to comply or objects at some point within the four-week period, the RIPE NCC will allow the time remaining in this four-week period for the Direct Assignment User to submit evidence that there is no reason for deregistration of the Internet number resources or to request arbitration (see  delete: <a href="http://www.ripe.net/ripe/docs/arbitration"> RIPE NCC Conflict Arbitration Procedure  delete: </a> ). However, if the four-week period expires without the submission of such evidence by the Direct Assignment User or without the submission of a request for arbitration, the RIPE NCC will proceed as if the Direct Assignment User had never reacted (see relevant procedure above).  delete: </p> delete: <p> The Direct Assignment User may still request arbitration according to the timeframes of the RIPE NCC Conflict Arbitration procedure. If the Member requests arbitration, the RIPE NCC will change the  delete: <strong> mnt-by  delete: </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.  delete: </p> delete: <p>    delete: </p> delete: <p> delete: <span class="discreet"> changes made to the content itself.  insert: </pre> 
insert: <p class="callout">

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

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