Migration issues: route creation

Dear Colleagues,

You may know that the new version of the RIPE database (v3.0) also
supports Routing Policy Security System (RFC2725). One of the
implications is that this may prevent registrations of "foreign" routes
in the RIPE IRR (that is routes from non RIPE address space and/or non
RIPE ASN).

According to RFC2725, creation of a route object should be authorized by
the "owner" of the respective address space or aggregate route and by
the "owner" of the ASN that is specified as route origin. In case of
absence of the corresponding objects, creation of the route object will
fail.

The creation of the corresponding "foreign" objects will not be as easy
in the new version as it is in the current one. The ASN space will be
protected by as-block object, and IP address space by corresponding top
level inetnum object. This makes registration of "foreign" routes almost
impossible, which affects current practice when an IPS requests that
clients' routes should be registered in the RIPE IRR.

Possible solutions to this problem are:

1. Send such registration requests to the Database Administration
(ripe-dbm) who will perform registration by overriding security (and
performing necessary checks before). This puts additional load on
ripe-dbm and creates duplicate objects in the RIPE database and
"foreign" IRR.

2. Do not allow such registrations. In this case some ISPs will need to
change their peering policy and accept routing information from a
"foreign" IRR.

Your comments and suggestions are highly appreciated.

Regards,


Andrei Robachevsky
DB Group Manager
RIPE NCC