You are here: Home > Publications > RIPE Document Store > Due Diligence for the Quality of the RIPE NCC Registration Data

Changes to Due Diligence for the Quality of the RIPE NCC Registration Data

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-748: ripe-657: Due Diligence for the Quality of the RIPE NCC Registration Data

Introduction

The RIPE NCC has a mandate from the RIPE community to keep an up-to-date and correct Internet number resource registry. In order to comply with this mandate, the RIPE NCC performs due diligence on organisations the RIPE NCC registers Internet number resources resource for.

Due diligence refers to the controls the RIPE NCC performs:

  • Before  the the registration of Internet number resources (see Section section 1)
  • After  the the registration of Internet number resources (see Section section 2)

This document outlines the minimum information and documentation the RIPE NCC requires to make sure that the registration data is valid and up-to-date while complying with the applicable legislation as an association under Dutch law. up-to-date.

Table of Contents delete: </h3> delete: <p> delete: <a href="#1--before-the-registration-of-internet-number-resources" data-linktype="anchor" data-val="2"> 1. Before the Registration of Internet Number Resources delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> delete: <a href="#11" data-linktype="anchor" data-val="1"> 1.1. Establishment of an agreement delete: </a> delete: </p> delete: <p style="padding-left: 60px;"> delete: <a href="#111" data-linktype="anchor" data-val="2"> 1.1.1. If the signing party is a natural person delete: </a> delete: </p> delete: <p style="padding-left: 60px;"> delete: <a href="#112" data-linktype="anchor" data-val="3"> 1.1.2. If the signing party is a legal person delete: </a> delete: </p> delete: <p style="padding-left: 90px;"> delete: <a href="#1121" data-linktype="anchor" data-val="4"> 1.1.2.1. Proof of establishment/registration delete: </a> delete: </p> delete: <p style="padding-left: 90px;"> delete: <a href="#1122" data-linktype="anchor" data-val="5"> 1.1.2.2. Approval by authorised representative delete: </a> delete: </p> delete: <p style="padding-left: 60px;"> delete: <a href="#113" data-linktype="anchor" data-val="6"> 1.1.3. Entities without legal personality delete: </a> delete: </p> delete: <p style="padding-left: 60px;"> delete: <a href="#114" data-linktype="anchor" data-val="7"> 1.1.4. The signing party is a former member delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> delete: <a href="#12" data-linktype="anchor" data-val="8"> 1.2. Compliance with RIPE Policies delete: </a> delete: </p> delete: <p> delete: <a href="#2--after-the-registration-or-distribution-of-internet-number-resources" data-linktype="anchor" data-val="3"> 2. After the Registration of Distribution of Internet Number Resources delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> delete: <a href="#21" data-linktype="anchor" data-val="10"> 2.1. Submission of a change delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> delete: <a href="#22" data-linktype="anchor" data-val="11"> 2.2. Agreement for the transfer of Internet Number Resources delete: </a> delete: </p> delete: <p> delete: <a href="#3--sanctions-and-areas-under-dispute" data-linktype="anchor" data-val="4"> 3. Sanctions and areas under dispute delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> delete: <a href="#31" data-linktype="anchor" data-val="13"> 3.1. Sanctions delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> delete: <a href="#32" data-linktype="anchor" data-val="14"> 3.2. Areas under dispute delete: </a> delete: </p> delete: <p> delete: <a href="#4--fraudulent-documentation" data-linktype="anchor" data-val="5"> 4. Fraudulent documentation delete: </a> delete: </p> delete: <p> delete: <a href="#5--confidentiality-and-privacy-issues" data-linktype="anchor" data-val="6"> 5. Confidentiality and Privacy issues delete: </a> delete: </p> delete: <p>   delete: </p> delete: <h3> delete: <a name="1--before-the-registration-of-internet-number-resources"> delete: </a> 1. Before the Registration of Internet Number Resources registration of Internet number resources

The RIPE NCC registers Internet number resources to legal or natural persons that:

  • Are contractually bound with either the RIPE NCC or a sponsoring LIR (see Section 1.1 below) below section 1.1) and
  • Meet the criteria defined by  by the RIPE Policies  (see Section 1.2 below) (see below section 1.2)

delete: <a id="11"> delete: </a> 1.1. Establishment of an agreement

Legal or natural persons requesting the registration of Internet number resources and related services must have signed an agreement with either the RIPE NCC or a sponsoring LIR.

The RIPE NCC performs due diligence on these contractual agreements to verify that the contractual parties exist (and are valid) and that they are properly represented in the signing of the agreement.

For consistency purposes, all legal or natural persons that sign an agreement with the RIPE NCC are considered as intending to request Internet number resources.

Agreements signed with a sponsoring LIR must be submitted to the RIPE NCC. If there are doubts over the correctness of this information, the RIPE NCC reserves the right to contact the person that appears to have signed the agreement with the sponsoring LIR and to confirm the correctness of this information.

Each agreement signed with either the RIPE NCC or with a sponsoring LIR must be accompanied by  by supporting   documentation  proving proving the existence (and validity) of the legal or natural person (see below).

delete: <h5> delete: <a id="111"> delete: </a> 1.1.1. insert: <p>

insert: <strong> If insert: </strong> insert: <strong> the insert: </strong> insert: <strong> signing insert: </strong> insert: <strong> party insert: </strong> insert: <strong> is insert: </strong> insert: <strong> a insert: </strong> insert: <strong> natural insert: </strong> insert: <strong> person insert: </strong> insert: </p>

insert: <p>

If the signing party is a natural person delete: </h5> delete: <p> If the signing party is a natural person, the RIPE NCC has we have to be sure of their identity (before an agreement is concluded with them). Proof of identification could be:

  • Valid identification documents (e.g., identification card, passport)
  • Valid driving license with photo, birth certificate issued by the relevant municipality, notary declaration proving the existence of the person, etc., etc. in the case of countries with non-official identification documents (e.g., the UK)
delete: <h5> delete: <a id="112"> delete: </a> 1.1.2. insert: <p>

insert: <strong> If the insert: </strong> insert: <strong> the insert: </strong> insert: <strong> signing insert: </strong> insert: <strong> party is a insert: </strong> insert: <strong> is insert: </strong> insert: <strong> a insert: </strong> insert: <strong> legal insert: </strong> insert: <strong> person delete: </h5> insert: </strong> insert: </p>

If somebody is signing on behalf of a legal person, the RIPE NCC must verify that:

  • The legal person is appropriately established by the national authorities or registered with them (see below under a. Proof of establishment/registration) and
  • An authorised representative of the legal person approves this application (see below under b. Approval by authorised representative)
delete: <h6> delete: <a id="1121"> delete: </a> 1.1.2.1 insert: <h4>

a. Proof of establishment/registration delete: </h6> insert: </h4>

Normally, proof of establishment of a legal person can be registration with the national authorities (e.g., a recent extract from the Commercial Trade Register or equivalent document proving registration with the national authorities). When this is not available, other another proof of establishment may be required (e.g., the law according to which the legal person was established).

The RIPE NCC reserves the right to check the validity of this documentation by requesting further documentation or additional information from third parties.

delete: <h6> delete: <a id="1122"> delete: </a> 1.1.2.2. insert: <h4>

b. Approval by authorised representative delete: </h6> insert: </h4>

A contract with either the RIPE NCC or a sponsoring LIR must be signed by an authorised representative of the legal person. insert: </p>

insert: <p>

In order to obtain a degree of certainty that the person that signs a contract is indeed authorised to represent the legal person, they must indicate:

  • Their name
  • Their position in the structure of the legal person

The RIPE NCC may request official documentation proving that the person signing on behalf of the legal person is authorised to do so. delete: </p> delete: <p> If there are doubts over the correctness of this information, the RIPE NCC reserves the right to check the validity of this documentation by requesting further documentation (including will request proof of identity) or additional information from third parties. delete: </p> delete: <h5> delete: <a id="113"> delete: </a> 1.1.3. Entities without legal personality delete: </h5> identity of the signing person. insert: </p>

insert: <p>

insert: <strong> 1.1.1. Sanctions and areas under dispute insert: </strong> insert: </p>

The RIPE NCC strives to achieve legal certainty over the persons that have registered Internet number resources and their potential legal successors. Therefore, the RIPE NCC does believes that the means of communication should not accept contracts with entities that lack distinct legal personality from their partners or owners. be affected by political discussions or disputes. This includes partnerships that do the provision of correctly registered Internet numbering resources. The RIPE NCC is committed to taking all lawful steps available to ensure that the RIPE NCC can provide undisrupted services to all members across our service region. The RIPE NCC will not have distinct legal personality take positions with regard to specific political disputes. insert: </p>

insert: <p>

insert: <strong> Sanctions insert: </strong> insert: </p>

insert: <p>

The RIPE NCC as an association under Dutch Law has to comply with sanctions imposed by the Netherlands and the EU. insert: </p>

insert: <p>

The RIPE NCC follows developments regarding sanctions and reviews whether they restrict us from their partners, businesses that do not have distinct legal personality providing services to network operators in certain regions or from their owners etc.  delete: <br /> delete: <br /> However, any of the partners or owners (natural or legal person) of such entities can enter into a contract with the RIPE NCC or a sponsoring LIR. having a contractual relationship with them. Additionally, the RIPE NCC communicates with the Dutch authorities in order to clarify the details of imposed sanctions and our obligations. insert: </p>

insert: <p>

If they wish to highlight their link to the name of the particular entity, they may include the entity’s registered (trade)name next to their name with the notion “trading as”. delete: </p> delete: <h5> delete: <a id="114"> delete: </a> 1.1.4. The the signing party is former member delete: </h5> delete: <p> If the signing party is a former member, of which the Standard Service Agreement was terminated in accordance with Article 9.4.h ( delete: <em> “if the Member provides the RIPE NCC with falsified or misleading data or provides the RIPE NCC repeatedly with incorrect data” delete: </em> ), the RIPE NCC will subject to such sanctions, the RIPE NCC may refuse to sign an agreement with, with or to provide services to, to this party.

insert: <strong> Areas under dispute insert: </strong> insert: </p>

insert: <p>

The restriction shall cease to apply five years from the date the SSA was terminated. In the event that the former member is reported to RIPE NCC will strive to facilitate the provision of services to network operators in areas under dispute and does not wish to deny services for political reasons. Our foremost concern as a neutral membership organisation is to ensure accurate registration of Internet number resources. The RIPE NCC can neither recognise nor deny one state's authority over a region. insert: </p>

insert: <p>

The RIPE NCC relies on proof of establishment provided by the signing party. This proof of establishment must be issued by a national authority and prove that the signing party exists. insert: </p>

insert: <p>

If the signing party is located in an area claimed by two or more widely recognised states, the RIPE NCC may accept proof of establishment issued by whichever national authority the signing party chooses. insert: </p>

insert: <p>

If the legal person is located in an area that is self-proclaimed as an independent state, the RIPE NCC may accept proof of establishment issued by the relevant authorities by the RIPE NCC, and the relevant authorities acquit the former member or dismiss the charges against them before the end of this five year period, the restriction shall cease to apply on the day the RIPE NCC is informed of this. delete: </p> delete: <p> The same applies for applications on behalf of natural persons who acted as contact persons or representatives of the former member. accompanied by further documentation (e.g., proof of identity of the authorised representative, articles of incorporation etc).

delete: <a id="12"> delete: </a> 1.2. Compliance with RIPE Policies

The RIPE NCC performs due diligence on requests for Internet number resources and the validity of the distribution criteria before registration in order to ensure compliance with the appropriate RIPE Policies ( IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region , IPv6 Address Allocation and Assignment Policy , Autonomous System (AS) Number Assignment Policy ).

During these checks, the RIPE NCC may ask for information about the network the Internet number resources are meant to be assigned to, as well as for documents supporting this information.

Details of this due diligence depend on the specific Internet number resources that are requested. These details can be found in the  the Request Forms and Supporting Notes and for IPv4 addresses in the insert: <a href="http://www.ripe.net/ipv4-evaluation-procedures"> IPv4 Registration Procedures insert: </a> .

delete: <a name="2--after-the-registration-or-distribution-of-internet-number-resources"> delete: </a> 2. After the Registration or Distribution of Internet Number Resources registration or distribution of Internet number resources

After the agreement has been signed and the Internet number resources have been registered, the RIPE NCC must ensure that relevant registration data are kept up-to-date and correct. To this end, the RIPE NCC performs audits (please see  see RIPE NCC Audit Activity activity ) and has procedures to ensure that (legal or natural) persons that have registered Internet number resources are aware of the changes that must be communicated to the RIPE NCC (e.g., see RIPE NCC procedural documents about  delete: <a href="http://ripe.net/publications/docs/mergers"> about insert: <a href="https://www.ripe.net/publications/mergers"> transfers of Internet number resource records and change of a Member’s Member's official name delete: <a class="external-link" title="" href="http://ripe.net/docs/lir-end-user-contractual-changes" target="_self"> , insert: <a href="https://www.ripe.net/publications/lir-end-users-contractual-changes"> Independent resources – contractual changes between sponsoring LIR and End User  and  and Closure of LIR and Deregistration of Internet Number Resources ).

delete: <h4> delete: <a id="21"> delete: </a> 2.1. insert: <p>

insert: <strong> Submission of a insert: </strong> insert: <strong> of insert: </strong> insert: <strong> a insert: </strong> insert: <strong> change delete: </h4> insert: </strong> insert: </p>

Changes in the registration data must be requested by:

  • A registered contact person (someone that has been delegated the authority to contact the RIPE NCC via the LIR Portal on behalf of the person that has been registered Internet number resources); resources through the LIR portal); or
  • An authorised person (someone that has the general authority to act on behalf of the person that has been registered Internet number resources)

If there is any doubt about the identity or the authority of the person requesting these changes, the RIPE NCC reserves the right to request additional documentation (e.g., proof of identity, court decisions, etc.) and to request support or information from third parties.

The RIPE NCC will ask the requester to submit all relevant documentation that supports this change. Such documentation may include:

  • Registration papers from local authorities of the country the organisation is registered in
  • Court decisions establishing, recognising or ordering the change
  • Agreements mentioning the change
  • Confirmation signed by an authorised person

For more information, please see the RIPE NCC procedural document " delete: <a href="http://ripe.net/publications/docs/mergers"> Transfers of Internet Number Resources and Change of a Member’s Official Legal Name about insert: <a href="https://www.ripe.net/publications/mergers"> transfers of Internet number resource records and change of a Member's official name ". .

The RIPE NCC reserves the right to check the validity of this documentation by requesting support or information from third parties.

delete: <h4> delete: <a id="22"> delete: </a> 2.2. Agreement for the transfer of Internet number resources delete: </h4> delete: <p> In case of a transfer of registered Internet number resources, and in accordance with the relevant RIPE NCC procedural documents (“ delete: <a href="http://ripe.net/publications/docs/mergers"> Transfer of Internet Number Resources and Change of a Member’s Official Legal Name delete: </a> ” and “ delete: <a href="http://ripe.net/docs/lir-end-user-contractual-changes"> Independent Internet Number Resources – Contractual Relationship Changes Between Sponsoring LIR and End User delete: </a> ”), both parties must agree to the terms of the transfer. To this end, the RIPE NCC provides the  delete: <a href="http://ripe.net/transfer-agreement"> Transfer Agreement delete: </a>  template that both parties must sign. delete: </p> delete: <p> The Transfer Agreement must be signed by authorised persons from both parties. For the transferring party, it is required that the Transfer Agreement is signed by an authorised representative having the general capacity to sign and act on behalf of this party. delete: </p> delete: <p> The RIPE NCC reserves the right to request official documentation proving that the person signing on behalf of either party is authorised to do so. In particular, the RIPE NCC may request either party to submit any relevant documentation listing the names of the persons authorised to sign and act on behalf of their organisation and/or to undertake any other necessary action in order to verify the validity of the provided documentation. delete: </p>

delete: <a name="3--sanctions-and-areas-under-dispute"> delete: </a> 3. Sanctions and areas under dispute delete: </h3> delete: <p> The RIPE NCC believes that the means of communication should not be affected by political discussions or disputes. This includes the provision of correctly registered Internet number resources. The RIPE NCC is committed to taking all lawful steps available to ensure that the RIPE NCC can provide undisrupted services to all members across its service region. The RIPE NCC will not take positions with regard to specific political disputes. delete: </p> delete: <h4> delete: <a id="31"> delete: </a> 3.1. Sanctions delete: </h4> delete: <p> The RIPE NCC, as an association under Dutch Law, has to comply with sanctions imposed by the Netherlands and the EU. delete: </p> delete: <p> The RIPE NCC follows developments regarding sanctions and reviews whether they restrict the provision of services to network operators in certain regions or from having a contractual relationship with them. Additionally, the RIPE NCC communicates with the Dutch authorities in order to clarify the details of imposed sanctions and its obligations. delete: </p> delete: <p> If the signing party is subject to such sanctions, the RIPE NCC may refuse to sign an agreement with, or to provide services to, this party. delete: </p> delete: <p> In particular: delete: <br /> Before the signing of the Standard Service Agreement, the RIPE NCC will check all signing parties and, in case of legal persons, authorised representatives against the applicable sanctions list. delete: </p> delete: <p> After the signing of the Standard Services Agreement, the RIPE NCC will perform: delete: </p> delete: <ul> delete: <li> Triggered checks – any administration change requested by a member will trigger a new check of the member and its authorised representatives against the sanctions list. delete: </li> delete: <li> Periodic scheduled checks - all members and authorised representatives will be checked against the sanctions list at least once per year. The RIPE NCC will conduct additional checks by using independent third parties at least once per year. delete: </li> delete: </ul> delete: <p> If the RIPE NCC identifies a member as a potential sanctioned party, an audit will be initiated according to the RIPE NCC procedural document “ delete: <a href="https://www.ripe.net/../../../ripe-694"> Audit Activity delete: </a> ”. If a member is confirmed to be sanctioned, the RIPE NCC may suspend the provision of RIPE NCC services to them. The member may contest RIPE NCC’s audit outcome by submitting evidence proving that they are not in the sanctioned list. delete: </p> delete: <h4> delete: <a id="32"> delete: </a> 3.2. Areas under dispute delete: </h4> delete: <p> The RIPE NCC will strive to facilitate the provision of services to network operators in areas under dispute and does not wish to deny services for political reasons. The RIPE NCC’s foremost concern as a neutral membership organisation is to ensure accurate registration of Internet number resources. The RIPE NCC can neither recognise nor deny one state’s authority over a region. delete: </p> delete: <p> The RIPE NCC relies on proof of establishment provided by the signing party. This proof of establishment must be issued by a national authority and prove that the signing party exists.  delete: </p> delete: <p> If the signing party is located in an area claimed by two or more widely recognised states, the RIPE NCC may accept proof of establishment issued by whichever national authority the signing party chooses. delete: </p> delete: <p> If the legal person is located in an area that is self-proclaimed as an independent state, the RIPE NCC may accept proof of establishment issued by the relevant authorities accompanied by further documentation (e.g., proof of identity of the authorised representative, articles of incorporation etc.). delete: </p> delete: <h3> delete: <a name="4--fraudulent-documentation"> delete: </a> 4. Fraudulent Documentation delete: </h3> delete: <p> If it becomes apparent that the RIPE NCC has been presented with fraudulent documentation, either before or after the registration of Internet number resources, this will be reported to the relevant authorities. delete: </p> delete: <h3> delete: <a name="5--confidentiality-and-privacy-issues"> delete: </a> 5. Confidentiality and Privacy Issues privacy issues

The RIPE NCC maintains a duty of confidentiality towards the legal or natural persons that request Internet number resources. Information passed to the RIPE NCC is securely stored and will not be distributed further than is necessary. necessary, within the RIPE NCC and beyond.

Details of the process of handling personal data by the RIPE NCC can be found in the  the RIPE NCC Privacy Statement .

Due Diligence for the Quality of the RIPE NCC Registration Data
RIPE Documents Search