RIPE Database docs
Sidebar Navigation

Introduction to the RIPE Database

RIPE Database Documentation Overview

Intended Audience

Conventions Used in the RIPE Database Documentation

What is the RIPE Database

Purpose and Content of the RIPE Database

History of the RIPE Database

Personal Data Database Management and Reponsabilities

RIPE Database Structure

Database Object

Primary and Secondary Objects

List of Primary Objects

List of Secondary Objects

The Attributes in Database Objects

Attribute Names

Attributes in an Object

Attribute Values

Attribute Properties

How to Organise Your Data

REST API Data model

RPSL Object Types

Descriptions of Primary Objects

Descriptions of Secondary Objects

Available Databases

RIPE Database

TEST Database

Release Candidate Database

Experimental Databases

Update Methods

RESTful API

Webupdates

Syncupdates

Email Updates

Updating Objects in the RIPE Database

Format of the Update Message

Accessing the Object Templates

Object Processing

Update Operations

Historical Data

Special Considerations for Object Creation

Garbage Collection

Dry run

Set Objects

Notifications

Acknowledgment Message

Notification Messages

Authorisation

Authorisation Model

Using the Authorisation Methods

Security of Data Using Authorisation

Protection of PERSON and ROLE Objects

Protection of AUT NUM Object Space

Protection of Address Space

Protection of Route Object Space

Protection of Reverse Delegation Objects

Protection of Objects with Hierarchical Names

Protecting Membership of a Set

Referencing an ORGANIZATION Object

Referencing an IRT Object

IRT Object

Force Delete Functionality

Request ENUM delegation

Request DNSSEC delegation

How to Query the RIPE Database

The Structure of a Query

Web Query Form

RESTful API Queries

Command Line Queries

Query Responses

Registration Data Access Protocol

Access to Personal Data

Types of Queries

Queries Using Primary and Lookup Keys

Queries for IP Networks

Queries for Autonomous Systems

More and Less Specific Lookups For Reverse Domains

Inverse Queries

Abuse Contacts

Grouping the RIPE Database Output

Filtering the Query Reponse

IRR Toolset Support

Persistent Connections and Keeping State

Getting All the Members of Set objects

Access Control for Queries

RIPE NCC Global Resource Service

Other Query Flags

Referenced Objects in Query Response

Historical Queries

Related Software and Tools

Geolocation in the RIPE Database

RIPE Database Mirror

Setup RIPE Database Mirror

Near Real Time Mirroring v3

Near Real Time Mirroring v4

Access to NRTM

Tables of Query Types Supported by the RIPE Database

How to Recover Access to a Maintainer Object

Installation and Development

Getting started on macOS

Getting started on Ubuntu Linux

Building whois

Configure MariaDB

Coding standard

Installation instructions

Database Support

Support Overview

Clean up of Unreferenced Data

Database Security

Configuring Reverse DNS

Database Business Rules

Highlighted Values in the RIPE Database

Create First Role Mntner

Removal of personal data

Release Notes

FAQ

Appendices

Appendix A Syntax of Object Attributes

Appendix B Copyright Statement

Appendix C RIPE Database Query Server Response Codes and Messages

Appendix-D--Route-Object-Creation-Flowchart

Appendix-E--Domain-Object-Creation-Flowchart

Appendix F Special Considerations for Object Types

Appendix G Object Types with Personal Data

Appendix H PGP Authentication Method

Appendix I Client Certificate Authentication

Appendix J Ripe Test Database

Appendix K API Keys

Glossary

Legal Information

RIPE Database Acceptable Use Policy

HTML Terms And Conditions

All Documentation Combined

On this page

Appendix F- Special Considerations for Object Types ​

This is a list of actions required of the Maintainer in a situation where one of the following object types references the person object to be removed and:

  • This is the only person or role object referenced in the object.
  • There are no options available for changing the reference.

Forward domain
This is a Top-Level Domain (TLD) problem. If the TLD is not responsive, the TLD should remove its data from the RIPE Database.

Reverse domain
These objects should be deleted and removed from the DNS system.

inet(6)num
The address space must be returned to the appropriate Internet Registry and then the object can be deleted.

The RIPE NCC will take no action until the Data Subject has cancelled any routing arrangements for the address space to be returned and any related route(6) objects have been deleted.

aut-num
These objects should be deleted.

The RIPE NCC will take no action until the Data Subject has cancelled any routing arrangements where this AS number is the origin and any related route(6) objects have been deleted.

role
If the role object only references this one person object, find all the references to the role object and consider them as if they were direct references to the person object.

mntner
Find all objects that reference this mntner object and carry out the following actions on each of these objects:

  • Where there are references to more than one mntner object in the same attribute type, remove the reference to this mntner object.
  • If it is referenced in an optional attribute, remove the attribute.
  • Where an object references only this mntner object in a single instance of a mandatory attribute, consider this object as if it had a single reference to the person object to be deleted. This object may also need to be deleted and then follow the chain of references to this object and handle all referencing objects according to this list.

When all references to the mntner object have been removed, delete the mntner object.

key-cert
References to person objects are optional, so remove any reference to this person object from the key-cert object.

irt
Remove references to this irt object from inet(6)num objects, then delete the irt object.

organisation
References to person objects are optional, so remove any reference to this person object from the organisation object.

Last updated:

Pager
Previous pageAppendix E Domain Object Creation Flowchart
Next pageAppendix G Object Types with Personal Data