RPSL

The RIPE Database server speaks the Routing Policy Specification Language (RPSL) (see RFC 2622) which improves the publishing of routing information.

The migration from the old RIPE Database (RIPE-181) to the RPSL version of the RIPE Database has been completed in 2001.

What is RPSL?

RPSL was designed for Internet Service Providers (ISPs) to publish their routing policies. Since the introduction of RPSL, many ISPs publish their policies in public Internet Routing Registries, such as the RIPE Routing Registry. Routing policies in RPSL are used by ISPs to automatically configure the filters on their routers. Because of this, it is very important to keep published routing policies up-to-date.

So how about RPSLng?

RPSLng makes it possible to document routing policies for the IPv6 and multicast addresses in the the RPSL language.

Routing Registry Training Courses

RIPE NCC members (LIRs) can attend a one-day hands-on Routing Registry course to learn more about RPSL and the Routing Registry. Course information and registration is available in our Training section.

Archived Documentation:

Several documents are available about the migration to the RPSL RIPE Database:

 

Software:

  • RtConfig for the RAToolSet, which allows router configurations to be generated from routing registry entries in the RIPE Database.
  • Whois Client WhoisRIP is a slightly modified version of the RIPE whois client, which allows the usage of the newest flags supported by the RIPE whois server software.
  • Whois Server The latest software version for the RIPE Database server.

Related Pages:

The RIPE Database Working Group discusses issues related to the RIPE Database.

The RIPE Database page provides a starting point for information about the RIPE Database.

The RIPE Database re-implementation project page is useful for those interested in server software.

Mailing Lists:

There are two mailing lists related to the RIPE Database RPSL migration.