This document describes the Publish in Parent Service that the RIPE NCC offers to RIPE NCC members and End Users. This Service is based on Internet Engineering Task Force (IETF) standards, in particular RFC 8181, “A Publication Protocol for the Resource Public Key Infrastructure (RPKI)”.
The use of the Service and of the Publish in Parent Repository is available subject to prior agreement to these Terms and Conditions.
In the Terms and Conditions, the following terms shall be understood to have the meanings assigned to them below:
RIPE NCC - Réseaux IP Européens Network Coordination Centre, a membership association under Dutch law, operating from its registered ofﬁce in Amsterdam, the Netherlands
Users – Anyone who downloads the Repository and/or accesses or uses the data contained therein.
RIPE NCC Certiﬁcation Service – The RIPE NCC service through which the Certiﬁcates are issued or revoked and RPKI-signed objects are created, modiﬁed, or deleted.
Internet number resources – Globally unique IP addresses (IPv4 and IPv6) and Autonomous System Numbers (ASNs) registered with any Internet Number Registry, such as the RIPE NCC, that allocates Internet number resources and holds and publishes details of Internet number resource information.
RPKI-signed objects – Digitally signed data objects created using the Certiﬁcate, such as Route Origin Authorisation (ROA) objects.
Certiﬁcate – Digitally signed data object generated by the RIPE NCC Certiﬁcation Service.
Certiﬁcate Holder – RIPE NCC Member or End User who uses the RIPE NCC Certiﬁcation Service.
Member – A natural person or a legal entity that has entered into the RIPE NCC Standard Service Agreement with the RIPE NCC.
End User - A natural person or a legal entity that is assigned Independent Internet Number Resources from the RIPE NCC through an agreement with a Member
CA – Certiﬁcation Authority. CA is an entity that issues, publishes and revokes the Certiﬁcates.
Delegated CA – Type of CA setup technically hosted by the RIPE NCC Member or End User, who chooses the Delegated CA setup instead of the Hosted CA. The Certiﬁcate Holder, as a Delegated CA, manages their CA on their own infrastructure instead of that of the RIPE NCC, including the hosting of the public and private key pair.
Publish in Parent Service, or Service – the RIPE NCC service based on RFC 8181 through which the Delegated CA can choose to publish their Certiﬁcates, CRLs and RPKI-signed objects in the RIPE NCC Publish in Parent Repository instead of their own infrastructure.
Publish in Parent Repository, or Repository – A publicly accessible location where the RIPE NCC publishes all Certiﬁcates, CRLs and RPKI-signed objects of the Certiﬁcate Holders who chose the Publish in Parent Service as part of the Delegated CA setup and makes it available for download by Users under these Terms and Conditions.
LIR Portal – The secure web interface through which Members access various RIPE NCC services.
2.1. Users shall be able to download, access or use the Repository and the data contained therein, to the extent permitted by these Terms and Conditions and provided these Terms and Conditions are followed. By downloading the Repository and accessing and using the data contained therein, the User agrees to be bound by these Terms and Conditions.
2.2. Certiﬁcate Holder shall be able to choose the Publish in Parent Service in the LIR Portal and use all the features of the Service to the extent permitted by these Terms and Conditions and provided these Terms and Conditions are followed. By choosing the Publish in Parent Service as part of the Delegated CA setup option in the LIR portal and clicking the appropriate box/link in the LIR Portal, the Certiﬁcate Holder agrees to be bound by these Terms and Conditions.
2.3. The RIPE NCC reserves the right to amend these Terms and Conditions. The RIPE NCC shall notify the Member or the End User of such amendments. After such amendments, a Member or an End User may continue to use the RIPE NCC Publish in Parent Service, provided they read, understand and agree to the amended Terms and Conditions.
3.1. Users shall only be permitted to download the Repository and to access and use the data contained therein in order to validate Certiﬁcates, CRLs and RPKI-signed objects, or for scientiﬁc research purposes.
3.2. Download of the Repository, access to or use of the data contained therein for any other purpose not listed above, including but not limited to identiﬁcation purposes, advertising, direct marketing or any other commercial purpose, is strictly forbidden.
3.3 The use of the Certiﬁcate does not support claims of alleged "ownership" of Internet number resources. Internet number resources registered by the RIPE NCC are subject to and exclusively governed by the policies adopted by the RIPE community.
3.4 Users should always check revocation information when using a Certiﬁcate or RPKI-signed object and should always ensure that they are using the latest version of the data in the Repository, which is updated every 24 hours. The Repository will be available for download on a best effort basis and the RIPE NCC may suspend its operation or liability to the User for technical, legal, anti-abuse or any other reasons within the scope of managing the operations of the Repository.
4.1. Only Certiﬁcate Holders who chose the Delegated CA setup can use the Publish in Parent Service, upon prior agreement to these Terms and Conditions as per article 2.2 above.
4.2. The Certiﬁcate Holder shall only upload Certiﬁcates, CRLs and other RPKI-signed objects to the Repository.
4.3. The Certiﬁcate Holder shall not upload any content or materials that are unlawful or promotes unlawful or fraudulent activities; is or contains inappropriate, obscene or illegal content; is discriminatory or abusive toward any individual or group, including the RIPE NCC; contains or installs any malware, viruses, corrupted ﬁles or any other malicious data that are aimed at or can potentially disrupt the operations of the RIPE NCC or damage its software or any other data ; contains personal or conﬁdential data, infringes on any proprietary right of any party, including patent, trademark, copyright, or other rights.
4.4. The RIPE NCC shall reserve the right to remove from the Repository any objects, data, ﬁles, or other materials that do not conform to the requirements for the RPKI-signed objects as per article 4.2. without any prior notice.
4.5. The Publish in Parent Repository shall be available on a best effort basis. The RIPE NCC shall not be responsible for any technical or other issues that prevent the Certiﬁcate Holder from accessing or uploading ﬁles to the Repository.
4.6. The RIPE NCC shall not be responsible for any accidental loss of Certiﬁcate Holder’s data from the Repository. In the event of such loss, the RIPE NCC shall attempt to undertake reasonable measures to restore the lost data or contact the affected Certiﬁcate Holder and ask them to republish the lost RPKI-signed objects.
5.1. The Certiﬁcate Holder shall be solely responsible for maintaining the accuracy and validity of the RPKI-signed objects uploaded to the Publish in Parent Repository at all times.
5.2. The RIPE NCC shall reserve the right to remove any RPKI-signed objects from the Repository should the Certiﬁcate Holder fail to comply with the requirements set in article 5.1.
6.1. Download of the Repository, access and use of the data contained therein is at the User's own risk.
6.2. The use of the Publish in Parent Service and all of its associated aspects is at the Certiﬁcate’s Holder own risk. The Certiﬁcate Holder shall be liable for all aspects of the use of the Service.
6.3. The RIPE NCC shall not be liable for not being able to restore the lost data or to contact the Certiﬁcate Holder as per article 4.5.
6.4. The RIPE NCC is in no way liable for any direct or indirect damages, including, but not limited to, damages to the User's or Certiﬁcate Holder’s business, loss of proﬁt, damages to third parties, personal injury or damages to property, except in cases involving willful misconduct or gross negligence on the part of the RIPE NCC.
6.5. Users are responsible for making decisions based on the latest version of the data in the Repository. The RIPE NCC shallnot be liable for any decisions made based on an outdated version of the data in the Repository.
6.6. The RIPE NCC shall, in any event, not be liable for non-performance or damages due to force majeure, including but not limited to industrial action, strikes, occupations and sit-ins, blockades, embargoes, governmental measures, denial of service attacks, war, revolutions or comparable situations, power failures, defects in electronic lines of communication, ﬁre, explosions, damage caused by water, ﬂoods and earthquakes.
6.7. The RIPE NCC is not liable in the case that local legislation prohibits the use of any technical aspects of the Repository and the data contained therein.
6.8. Any right on the part of the User towards the RIPE NCC in connection with the download of the Repository, the access and use of the data contained therein shall ﬁnally and unconditionally lapse one year from the date on which the User became aware of (or could in all fairness have been aware of) the existence of such rights and entitlements. This one-year term can only be barred or interrupted by actual legal action instituted by the User against the RIPE NCC.
7.1. The RIPE NCC's intellectual property (agreements, documents, software, databases, website, etc.) may only be used, reproduced and made available to third parties upon prior written authorisation from the RIPE NCC.
7.2. The RIPE NCC Publish in Parent Service is only available via the LIR Portal and access to the LIR Portal is therefore a prerequisite for access to this Service.
7.3. If any provision contained in the Terms and Conditions is held to be invalid by a court of law, this shall not in any way affect the validity of the remaining provisions.
7.4. The titles appearing next to the articles of these Terms and Conditions are for convenience only and shall not be taken into account for the interpretation of the articles.
8.1. These Terms and Conditions shall be exclusively governed by the laws of the Netherlands.
8.2. The competent court in Amsterdam shall have exclusive jurisdiction with regard to disputes arising from these Terms and Conditions.