Skip to main content

You're viewing an archived page. It is no longer being updated.

RIPE Database to support RPSLng

• ripe database news announcement

[21 December 2004]

From Wednesday 29 December 2004, the RIPE Database will support RPSLng. RPSLng extends the Routing Policy Specification Language (RPSL) allowing description of IPv6 and multicast routing policies. It includes a new object type, ROUTE6, and new attributes, such as "mp-import:" and "mp-export:".

This change will not affect the current contents of the database. It is optional for any objects you maintain.

RPSLng was submitted to the IETF to become an RFC. You can read the most recent draft at:

http://www.radb.net/rfc4012.html

The main differences for query users are as follows:

  • Currently a query for an IPv4 address or network may return INETNUM, ROUTE, and INET-RTR objects. A query for an IPv6 address or network can only return an INET6NUM object. After we put RPSLng into production, IPv6 queries will also return ROUTE6 and INET-RTR objects, if they are in the database.
  • Currently an inverse query (using the "-i" flag) for AUT-NUM objects may return ROUTE objects. After we put RPSLng into production, a query will return both ROUTE and ROUTE6 objects.

If you want to limit your query, you can use the "-T" flag.
For example, if you only want ROUTE objects returned to an inverse query, you can type:

whois -h whois.ripe.net -T route -i origin AS3333

Please change your scripts if necessary.

Because we will not move the contents of the RPSLng prototype Whois server to the RIPE Database, you will have to create any objects that define your routing policy in the production RIPE Database.