[db-wg] Concerning the authentication for route object creation

Dear RIPE, dear Colleagues.

I'd like to discuss a topic which most likely has already been discussed
several times - only I have not seen that so far. If so, please excuse the
100th time being asked about it and just point me to results of these
discussions.

Anyway, here we go:

According to 

  http://www.ripe.net/info/faq/db/route-creation-IP-space-check.html

if it is found that there is no exact matching route object already in
existence in the RIPE DB, the less specific route is examined.

If one is found deciding for authentication are then contained mnt-routes,
mnt-lower or mnt-by fields.

What annoys me here is, that holes are completely disregarded, meaning so
even if because of defined holes the route object is not authoritative for a
network, nonetheless it's authentication data is used.

As we have several larger aggregated routes and additional some routes for IP
allocations that have a status of "ALLOCATED UNSPECIFIED"  we have to update
our route objects to include maintainers for other companies so that they
become able to maintain PI allocations.

If the authentication process would regard holes all we would have to do would
be defining a hole once, and not have to change the mnt-routes for a network
for every provider change. 

This might ease the daily business of us all slightly.

Cheers

Hendrik

-- 
Hendrik T. Voelker               HTV5-RIPE               EMEA Registrar Team
Verizon Deutschland GmbH      Sebrathweg 20     D-44149 Dortmund     GERMANY
http://www.verizonbusiness.com/de/ tel +49-231-972-1565 fax +49-231-972-2587
PubKey   1024D/92479A5D   EC1B 76F2 D69D 11C6 2611  5CD1 5269 9351 9247 9A5D


Verizon Deutschland GmbH - Sebrathweg 20, 44149 Dortmund, Germany - Amtsgericht Dortmund, HRB 14952 - Geschäftsführer: Donald Badoux - Vorsitzender des Aufsichtsrats: Mark Kearns