Dear Arif, The authentication mechanism for routes in RPSL specification is quite different than that of v2 software which we used prior to April 23, 2001. In the new authentication scheme, also the authorisation from aut-num object mentioned in 'origin' attribute of the route must be satisfied. If the authorisation from that aut-num object fails or the aut-num object does not exist, than the creation of the route object is rejected. Please see a graphical representation of this at http://www.ripe.net/ripencc/faq/database/qa4.html#5 Also please see RFC2725, page 36 for this (ftp://ftp.ripe.net/rfc/rfc2725.txt). RIPE Database Reference Manual is available at http://www.ripe.net/ripe/docs/databaseref-manual.html Please contact us at ripe-dbm@ripe.net with more details and we will help you to find the solution. Regards, Katie Petrusha _____________________________ RIPE Database Administration. Original message follows: ------------------------
X-Recipient: <dbint@ripe.net> Delivered-To: lists-lir-wg-out@lists.ripe.net X-Sender: arif.oktay@mail.telekom.gov.tr X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 10 Jun 2002 11:48:54 +0300 To: lir-wg@ripe.net From: Arif OKTAY <arif.oktay@telekom.gov.tr> Subject: updating route object Precedence: bulk X-Loop-Detect: RIPE NCC
Hi,
I receive following error from db when I try to update a route object. I provide proper authorization schema. Can anybody help me about this problem ?
Regards, arif
Hierarchical authorisation failed, request forwarded to maintainer.
------------------------ Arif OKTAY Tel:+90 312 5551922 Fax:+90 312 5551959 ------------------------ ... TYLER And, now it's gone. JACK All gone. --------------------------------------- Fight Club ---
-- Shane Kerr RIPE NCC