Tutorials: How to Register Objects in the RADB

This is a brief explanation of how to register in the RADB. It is intended as a sort of 'quick start' document, detailing only the minimum steps necessary to register. If you are not familiar with RPSL (Routing Policy Specification Language, used to express policy in the RADB), you may wish to refer to the REFERENCE section for background documents. This document provides templates for registering three types of objects in the RADB, as well as basic troubleshooting tips:

   *In order to register in the RADB, you'll first need to obtain
    an Autonomous System (AS) number. ARIN handles such assignments
    in North America.  There are also regional registries for Latin
    America (LACNIC), Europe (RIPE), the Asia-Pacific region (APNIC)
    and Africa (Afrinic).

To register your maintainer object, please use the RADB registration form. An RADB administrator will then verify your AS contact information and, subject to approval, notify you of your successful registration. Once the RADB adminstrator has notified you that your maintainer object has been added, you can pay your invoice online. After the Maintainer object is created, modifications can be made at the RADB Web Update page.

After registering Maintainer, the next step is to register Route objects. To register routes, please proceed to the route object web form. Please refer to the example below as a guide.

Route Example

Attributes	Comments
route: 128.223.0.0/16	Route in CIDR format
descr: UONet University of Oregon Computing Center Eugene, OR 97403-1212 USA	Description or location of the network
origin: AS3582	AS originating the route
mnt-by: MAINT-AS3582	Which mntner objects can update this entry
changed: meyer@ns.uoregon.edu 19960222	Email address and date
source: RADB	Name of database containing the object

(This example is taken from RFC 2650, "Using RPSL in Practice.")

Step Three - Register AS and Policy Information

After registering a Maintainer object and routes, the next step is to register an aut-num object, thereby specifying an AS's routing policy. A sample aut-num object is shown below for a simple stub AS multihomed to two providers (AS64444 and AS64488). (For a more detailed description of aut-num objects, see RFC 2650 or see the REFERENCE section below). To register AS policy, please proceed to the aut-num web form.

Note that the mnt-by field should contain the string you submitted in the mntner field of the Maintainer object.

Aut-num Example

Attributes	Values	Comments
aut-num:	AS64323	AS Number
as-name:	MAINESTATE	Short descriptive one word name for the AS
descr:	Maine State University	Longer description of object
import:	from AS64444 accept ANY
import:	from AS64488 accept ANY
export:	to AS64444 announce AS64323
export:	to AS64488 announce AS64323
admin-c:	Fred Meyer	Administrative Contact
tech-c:	Ann Taylor	Technical Contact
mnt-by:	MAINT-AS64323	mntner responsible
changed:	fmeyer@mainestate.edu 20060328	Email address and date
source:	RADB	Name of database containing the object

AS-SET Objects

AS-SET objects are optional and may be registered with the as-set object web form. They are typically used by ISP's to list the AS's for which they provide transit. Please refer to the example below as a guide. See section 5.2 in RFC 2622 for more information.

AS-SET Example

as-set:        AS-BIGISP-TRANSIT

descr:         Provides Transit to these ASes

members:       AS64423, AS64899, AS65000

mnt-by:        MAINT-AS64488

changed:       alan@bigisp.com 20060316   

source:        RADB

For More Information

If you have questions about using the RADB, please send email to the database team at db-admin@radb.net.

References