yes, I 've made the same experiences! 2 route objects, 2 different AS, same precision (/22). In the the RIPE DB are some of these examples... Marcus Ruchti -----Ursprüngliche Nachricht----- Von: Gert Doering [mailto:gert@space.net] Gesendet am: Montag, 14. Oktober 2002 10:38 An: Shane Kerr Cc: Ruchti, Marcus; db-wg@ripe.net Betreff: Re: Hierarchical authorisation failed, request forwarded to maintaine r ??? Hi, On Mon, Oct 14, 2002 at 10:23:14AM +0200, Shane Kerr wrote:
Most objects are uniquely identified by the first attribute, or "route:" in this case. However, you must include the "origin:" attribute for a route object. So this is:
route: 143.58.120.0/22 origin: AS3320
The object you are trying to create will be:
route: 143.58.120.0/22 origin: AS8220
Shane, your explanation is confusing me. There are other examples with "same route, different origin AS" in the RIPE-DB (check 194.97.0.0/16), which is sometimes necessary while migrating a network to a new origin AS. So the database should permit entry of this *new* object, instead of checking for modification permission on the *existing* object. Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 48282 (47686) SpaceNet AG Mail: netmaster@Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299