Creating Route object


Route objects and other routing information can only be created in an Internet Routing Registry (IRR) – such as RADB and RIPE. AfriNIC does not operate a routing registry at this time. However, AfriNIC members can freely create route objects and other routing information in the RIPE Routing Registry. The information in this page attempts to provide the guidelines necessary to create a route in the RIPE database

Procedure to create the route object in RIPE Database

The route object depends on other objects listed below, that must be created first (if they do not exist yet) in the RIPE database. This guide assumes that the reader is already an AfriNIC member and is therefore familiar with the basic methods of interacting with the whois database. The RIPE and AfriNIC databases share pretty much the same object nomenclature and attribute syntax.

  • A person object needs to be created if it does not exist. This object contains information about the technical or administrative contact(s) that will be responsible for the route and other objects in the database.

  • A mntner object – which specifies authentication information is required to authorise creation, deletion or modification of the objects protected by that mntner. 

  • An aut-num object – defines the number of the AS that originates the prefix into the inter-AS routing system.

The RIPE database has a web-based interface from which the objects above (and all other objects) can be added or even modified or deleted. The interface is here.

Other Considerations:

  1. Authorisation: Route objects and AS numbers need to authenticate against a generic mntner, RIPE-NCC-RPSL-MNT whose password is “RPSL” without the quotes. In a route or aut-num object, this will be represented as:

    mnt-by: RIPE-NCC-RPSL-MNT
    password: RPSL
  2. Data Protection: The “mntner” stated above has a publicly known password. To ensure full data protection, it's necessary to add another mntner. To protect the person, route or aut-num object with the new mntner, the following attributes need to be added (in addition to those listed above):

    mnt-by: YOUR-MNTNER
    password: your-mntner-password
  3. For more information, please see the illustration about the authorisation hierarchy of the Routing Registry data in the RIPE database here

Finally the route object can be created since all the requirements should be in place by now. It can be done through the “webupdates” link or by using the e-mail method.

Using the email method, the process is as follows:

  • Obtain the (route) object template from here

  • Copy the template into the body of a new-email, complete as appropriate and mail to

  • Wait for the acknowledgement e-mail message.

A route object template appears as follows. The values of all the mandatory attributes must be defined, and those of the optional attributes can be added later-on.

route:          [mandatory]  [single]     [primary/look-up key]
descr:          [mandatory]  [multiple]   [ ]
origin:         [mandatory]  [single]     [primary/inverse key]
holes:          [optional]   [multiple]   [ ]
org:            [optional]   [multiple]   [inverse key]
member-of:      [optional]   [multiple]   [ ]
inject:         [optional]   [multiple]   [ ]
aggr-mtd:       [optional]   [single]     [ ]
aggr-bndry:     [optional]   [single]     [ ]
export-comps:   [optional]   [single]     [ ]
components:     [optional]   [single]     [ ]
remarks:        [optional]   [multiple]   [ ]
notify:         [optional]   [multiple]   [inverse key]
mnt-lower:      [optional]   [multiple]   [inverse key]
mnt-routes:     [optional]   [multiple]   [inverse key]
mnt-by:         [mandatory]  [multiple]   [inverse key]
changed:        [mandatory]  [multiple]   [ ]
source:         [mandatory]  [single]     [ ]

Special cases

There are certain cases in which the member or even AfriNIC will not be able to create the routes.

Case 1: AS numbers not existing in the RIPE db and belonging to a third party

In this case, it will be better to ask the organisation who has been assigned the ASN to create the aut-num object and route object for you in the RIPE RR.

Case 2: AS numbers existing in the RIPE db and belonging to a third party

In this case, it will be better to ask the organisation who has been assigned the ASN to create the route object for you in the RIPE database as their aut-num object will be having a mnt-lower or mnt-routes which must authorise creation of routing information.