Route objects and other routing information can only be created in a Routing Registry (RR) - for example, RADB, RIPE, etc . AfriNIC does not operate a routing registry at this time. AfriNIC members can freely create route objects and other routing information in the RIPE database. The information in this page bases on creating a route in the RIPE database RR.
Introduction
Each interAS route (also referred to as an interdomain route) originated by an AS is specified using a route object. The "route:" attribute is the address prefix of the route and the "origin:" attribute is the AS number of the AS that originates the route into the interAS routing system.
Procedure to create the route object in RIPE Database
• A person object needs to be created if you do not have a nic-handle yet. A person object contains information about the technical or administrative contact(s) responsible for an object.
• Create a mntner object. A mntner object specifies authentication information required to authorise creation, deletion or modification of the objects protected by that mntner.
• Create the aut-num object in case it does not exist in RIPE DB
The aut-num object contains the AS number of the AS that originates the prefix into the interAS routing system. If it is an AS number assigned by AfriNIC, you will have to add the following maintainer in addition to your own created in (3) above:
mnt-by: RIPE-NCC-RPSL-MNT
password: RPSL
You may add your mantainer as a mnt-by, mnt-lower or both: Assuming you created a mantainer called "ROUTE-MNT", here is what will be in your aut-num object:
mnt-by: RIPE-NCC-RPSL-MNT
mnt-by: ROUTE-MNT ## optional
mnt-lower: ROUTE-MNT
password: RPSL
password: plain text password for ROUTE-MNT
Finally create the route object. Please use the mantainer created in (3) above. To get a template and description of the attributes for your better understanding of the different objects, open the following link and type −v object-name in the search for area. http://www.ripe.net/fcgi-bin/whois
for e.g if you want the route template, type −v route and you shall get a reply as follows:
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] [ ]
You can create the objects by completing the template and sending to auto-dbm@ripe.net
Alternatively, you can also create the different objects using the online web-based facility at:
http://www.ripe.net/fcgi-bin/webupdates.pl
There are certain cases in which you or 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 organization 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 organization who has been assigned the ASN to create the route object for you in RIPE as their aut-num object will be having a mnt-lower or mnt-routes which must authorize creation of routing information.
AfriNIC is willing to help you in creating the objects in case you face difficulties in doing so in the RIPE Database.
|
