RADb and other IRRs

• The RADb (Routing Assets Database) is one of many databases within the Internet Routing Registry (IRR).

• The IRR consists of multiple registries maintained by various national and international networking organizations.

• While many IRR registries cater to specific customer bases, RADb handles registrations for networking organizations not covered by other routing registries.

• No. Each IRR database is a separate entity, and users typically register with only one.

• Merit (operator of RADb) keeps copies of many registries, but data from other databases does not become part of RADb.

• There is no single answer since most IRR information is used locally by providers for their customers.

• You should contact your provider to determine which databases they use to generate their routing policy configurations.

Example:

• Level3 allows customers to reference a specific database as a source for as-set information.

• This is done using a "remarks:" attribute containing the tag "Level3 members:".

• The entry format is:

  remarks: Level3 members: <DatabaseName>::<ReferencedObject>

• RADb supports data from other IRR databases through mirroring.

• RADb support and administrators can only modify data that originates from RADb.

• To modify or delete an object from a mirrored database, contact the original IRR using their provided contact information.

RADb Object Example:

Mirrored Object Example (from RIPE IRR):

• This object is sourced from the RIPE IRR and cannot be modified by RADb support.

• To update or delete this object, you need to contact RIPE.

Information about the databases linked below is at IRR.net.

• AFRINIC

• ALTDB

• APNIC

• ARIN

• BBOI

• BELL

• CANARIE

• IDNIC

• JPIRR

• LACNIC

• LEVEL3

• NESTEGG

• NTTCOM

• PANIX

• RADB

• REACH

• RIPE

• RIPE-NONAUTH

• TC