Frequently Asked Questions

1. What is the Megapath-RR?

The second field, descr, is a brief description of the maintainter object.

The third field, admin-c, allows the user to specify an admin contact. I have opted to use my NIC handle. A simple text name will suffice, however.

The upd-to field is where you specify what email address is notified when FAILED modifications are attempted on objects registered under the maintainter.

The mnt-nfy field is where you specify what email address is notified upon SUCCESSFUL modifications of objects registered under the maintainer.

The auth line controlls the authentication method used to verify that a user has permission to modify objects under this maintainer. The "MAIL-FROM" is a keyword that indicates that mail must be recieved from the user with an email address of kevin@epoch.net in order to be approved. All other mail users will be denied. Other options include CRYPT-PW and PGP-FROM. For a detailed explanation visit http://www.radb.net/docs/auth.html. Currently PGP-FROM is not supported in the Megapath-RR but there are plans to add PGP support if there is demand.

The mnt-by field sets the Maintainer object which controls the object being registered. As redundant as it may seem in this case, it is required. When registering other objects, it becomes more meaningful.

The changed field reflects when the objects was created or last modified and the user who made the changes. It is customary to use an email address followed by the date in YYYYMMDD format.

The source field specifies what database the object belongs to. Since the route server software supports multiple registries, you will need to specify "EPOCH" on this line.

The second field, as-name, allows you to name the AS object.

The descr field is where you put the descripton of the AS. It is good policy to enter valid 24 hour contact info in this field. Data can span multiple lines.

The admin-c and tech-c fields are where you can put other NIC handle information. Names or email addresses are also valid.

The nofity, mnt-by, changed, and source have the same meaning as in the maintainer object.

The import and export lines are the real meat of the AS object. The import field is where you define what routes you would like Megapath to send to you. For example:

• If you would not like to receive any routes from Megapath, you would simply omit this field.
• If you would like to receive full routes from Megapath you would use the keywords "accept any". This is reflected in the example above. The "AND NOT {0.0.0.0/0} denies the default route.
• If you would like to receive only partial routes, you would use the keywords "accept AS-EPOCH". This will tell the Route Registry to send all routes in the Megapath domain.

The export field is where you define what routes you would like to announce to Megapath. For most of you, you will simply say

export:        to AS4565
               announce AS5649

If you are a large BGP customer and announce more than one AS to Megapath, you will want to use an AS-SET object. This applies only to a select few customers.

The descr field provides a brief description of the route. For example you could put the CIDR block name given by ARIN if applicable.

The origin field attaches the Route Object to an AS Object thereby defining the route policy for the network.

The mnt-by field is where you put the maintainer object.

The changed and source fields are the same for all objects.

route:         192.168.0.0/24
descr:         Sample Route in the AS5649 Domain
origin:        AS5649
mnt-by:        MAINT-AS5649
changed:       kevin@epoch.net 20000519
source:        EPOCH    
delete:        kevin@epoch.net 20001012 network no longer routed via AS5649

14. How long does it take for Megapath to update their filters after I submit an object?