How to set up the necessary to manage your own objects in the database of Ripe.


Ripe is the organization that is responsible for the management of public internet resources for Europe and Middle East area. These resources include IP (v4 and v6) and AS numbers.

To ensure the management and documentation of the use of these resources, but also many other information, the Ripe maintains a database to which it is wrongly refers to the name of the protocol used to interrogate .

The “whois” and the base

Whois is a very simple protocol (I’ll let you read the very short RFC 3912. Whois is used to query the basis of Ripe, but not for the update. In fact, the basic structure is much more complex it uses a language called branched PCNs, which distributes information in “objects” typed (probably made tables).

The updating of these objects is mainly in two ways: the online interface Ripe on the website, and email. The objective here is to get set up email exchanges signed with PGP, but also the way we will use other tools.


To ensure a sufficient level of security, maintained in the database objects are protected by rights mechanisms. In some cases an algorithm that uses permission checks on many items previously reported is used to confirm a change on another object.

These authorization mechanisms are not detailed here, we only addresses part authentication.

Authentication can be done either by password (via the Web and email) or by signing PGP changed objects (mail only). Say what key and what passwords to authenticate an applicant, it is the function of the “Maker” objects (maintainer in English) and in the database: mntner.

Comments Are Closed!!!