How can we help you?

How to create route object with resources that you do not manage

You will have to use the dual-authentication method to create route(6) objects where the “mnt-lower” in the inetnum/inet6num object and the “mnt-routes” in the aut-num object do not match but both objects exist in the AFRINIC whois database.

The above will usually be the case when the holder of the IP address and the holder of the ASN routing the IP address are not the same entity, thus, having different maintainer objects.

To create such route objects, you will have to submit it with the password of the maintainer referenced in your inetnum/inet6num or aut-num which has been specified in the route object. If the authorisation for the “mnt-by” maintainer in the route object passes, the object will be queued for up to one week. Within the one week the other entity will have to submit the exact same route object and add the missing password of their maintainer which is referenced in the inetnum/inet6num or aut-num which has been specified in the route object.

The IRR DB will check to see whether the route object now passes all the required authorisations. If so, the object is created. If this does not happen within one week, the object is dropped from the queue.

Example:

The organisation “Example Provider” is creating a route object with their IPv4 prefix, 196.192.48.0/20, and the AS number, AS327800, of another entity “Example Transit Provider”. In this example “Example Provider” will be initiating the creation process, however, the opposite scenario is also possible where “Example Origin” is the initiator.

The inetnum and aut-num have different “mnt-lower” and “mnt-routes”;

Step 1) “Example Provider” gets the route object template and fills in all the mandatory fields.

The object would look like;

route:   196.192.48.0/20
descr:   Example route object
origin:  AS327800
mnt-by:  EXAMPLE-1-MNT
changed: This email address is being protected from spambots. You need JavaScript enabled to view it.
source:  AFRINIC

Step 2) “Example Provider” provides the maintainer password of "EXAMPLE-1-MNT" in clear-text before submitting the object.

Upon successful authorisation for "EXAMPLE-1-MNT" the message, “Object successfully created!” will be displayed. However, the second authorisation will still be pending as in the detailed explanation;

Step 3: “Example Transit Provider” will have to submit the exact same object as in the output above within one week.

The object should be:

route:   196.192.48.0/20
descr:   Example route object
origin:  AS327800
mnt-by:  EXAMPLE-1-MNT
changed: This email address is being protected from spambots. You need JavaScript enabled to view it. 20180711
source:  AFRINIC

Step 4: “Example Transit Provider” must provide the missing authorisation.

Therefore, provide the password for the maintainer EXAMPLE-2-MNT.

Upon successful authorisation for "EXAMPLE-2-MNT" there will no longer be any pending authorisation and the route object will be created;