route: 212.249.0.0/16
descr: UUNET CH
origin: AS702
mnt-by: AS702-MNT
password: *********
changed: jsc(a)ch.uu.net 20011204
source: RIPE
I send the above object to the DB and get the following error:
New FAILED: [route] 212.249.0.0/16
route: 212.249.0.0/16
descr: UUNET CH
origin: AS702
mnt-by: AS702-MNT
changed: stephenb(a)uk.uu.net 20011204
source: RIPE
***Error: Hierarchical authorisation failed, request forwarded to
maintainer.
Objects in RIPE-181 format are no longer accepted.
Please see http://www.ripe.net/rpsl for more information.
RIPE Database Maintenance Department
Which is strange as the mainainer is us AS702-mnt. Any help on this matter
whould be appreciated as this is not the only one.
Regards
Stephen Burley
UUNET EMEA Hostmaster
SB855-RIPE
http://www.ripe.net/ripe/docs/databaseref-manual.html
3.6.5 Protection of route object space
The route object creation must satisfy several authentication criteria.
It must match the authentication specified in the aut-num and the
authentication specified in either a route object or, if no applicable
route object is found, then an inetnum. Finally the creation must be
authorised by the maintainer of the route object itself referenced by
the "mnt-by:" attribute of the object.
When checking for prefix authorisation, an exact route object prefix
match is checked for first. If there is no exact match, then a longest
prefix match that is less specific than the prefix is searched for. If
the route prefix search fails, then a search is performed for an inetnum
object that exactly matches the prefix or for the most specific inetnum
object that is less specific than the route object submission. The
aut-num object used for authentication checks is referenced by the
"origin:" attribute of the route object.
A route object must pass authorisation from both the referenced aut-num
object and the route or inetnum object. Authorisation shall be tested
using the maintainer(s) referenced in the "mnt-routes:" attribute(s)
first. If that check fails, the "mnt-lower:" attributes are checked.
If that check fails, the "mnt-by:" attributes are used for the
authorisation check.
----------
aut-num: AS702
as-name: AS702
descr: UUNET - Commercial IP service provider in Europe
....
mnt-routes: UUNETDK-MNT
mnt-routes: AS1270-MNT
mnt-routes: AS1849-MNT
mnt-routes: AS1890-MNT
mnt-routes: IWAY-NOC
mnt-by: UUNET-MNT
---------
I bet you didn't pass this authorization check.
does this shed a light? :)
BR,
CCNP Boyan Krosnov
Network Administrator
Lirex Net
phone: +359-2-91815
> -----Original Message-----
> From: Stephen Burley [mailto:stephenb@uk.uu.net]
> Sent: Wednesday, December 05, 2001 12:30 PM
> To: lir-wg(a)ripe.net
> Cc: db-wg(a)ripe.net
> Subject: Can anyone shed some light on this?
>
>
> route: 212.249.0.0/16
> descr: UUNET CH
> origin: AS702
> mnt-by: AS702-MNT
> password: *********
> changed: jsc(a)ch.uu.net 20011204
> source: RIPE
>
> I send the above object to the DB and get the following error:
>
> New FAILED: [route] 212.249.0.0/16
> route: 212.249.0.0/16
> descr: UUNET CH
> origin: AS702
> mnt-by: AS702-MNT
> changed: stephenb(a)uk.uu.net 20011204
> source: RIPE
> ***Error: Hierarchical authorisation failed, request forwarded to
> maintainer.
>
> Objects in RIPE-181 format are no longer accepted.
> Please see http://www.ripe.net/rpsl for more information.
>
> RIPE Database Maintenance Department
>
> Which is strange as the mainainer is us AS702-mnt. Any help
> on this matter
> whould be appreciated as this is not the only one.
>
> Regards
> Stephen Burley
> UUNET EMEA Hostmaster
> SB855-RIPE
>
>
>
>
<Apologies for duplicate mails>
New/Revised RIPE Document Announcement
--------------------------------------
A revised/new document is available from the RIPE document store.
Ref: ripe-201
Title: Routing Registry Consistency Check
Author: Joachim Schmitz, Engin Gunduz, Shane Kerr, Andrei
Robachevsky, Joao Luis Silva Damas
Date: 4 December 2001
Format: PS=33719 TXT=15425
Obsoletes:
Obsoleted by:
Updates:
Updated by:
Short content description -------------------------
"Routing Registry Consistency Check" describes a project to crosscheck
European Internet routing against data registered in the RIPE Routing
Registry. This project was proposed as a new activity by the RIPE
Routing Working Group. The document gives an overview of the project,
discusses the implementation, and mentions some points that have to be
addressed in future design documents. This document is intended to
solicit input from interested parties.
Accessing the RIPE document store
---------------------------------
The RIPE document store is available via anonymous FTP to
ftp.ripe.net, in the directory ripe/docs.
The URLs for the new documents on the FTP-server are:
ftp://ftp.ripe.net/ripe/docs/ripe-201.ps PostScript version
ftp://ftp.ripe.net/ripe/docs/ripe-201.txt plain text version
You can also access the RIPE documents in HTML format via WWW.
RIPE-201 is available at the following URL:
http://www.ripe.net/docs/rr-consistencycheck.html
Dear Colleagues,
Herewith we like to remind you of the registration for the RIPE 41 meeting which has been opened. The meeting will be held from 14th January - 18th January 2002 at hotel Krasnapolsky in Amsterdam, The Netherlands.
More information about this meeting and accommodations can be found on
this page:
http://www.ripe.net/ripe/meetings/current/ripe-41/
Online registration will open on Monday 19th November 2001 and close
on Friday 4th January 2002. On-site registration will open on Monday
14th January 2002.
Please note the following:
To avoid waiting queues at the registration desk on-site we encourage
pre-payment by credit card. The registration fee for this meeting is
EUR 350.00 (this includes refreshments and lunches) and the dinner fee
is EUR 65.00. However, if payment is received before 4 January 2002,
the pre-payment cut-off date, you will receive a pre-registration discount
of EUR 50.00. Therefore, the fee for attendees paying before the cut-off
date is EUR 300.00 for the meeting and 65.00 EUR for the RIPE dinner event.
Confirmation of Registration:
For your convenience you can register using our secure website at:
https://www.ripe.net/cgi-bin/mtgreg (encrypted form)
http://www.ripe.net/cgi-bin/mtgreg (non-encrypted form)
If you still prefer not to send your credit card number using an
encrypted transfer method, we have prepared a fax form. This form is
attached to the acknowledgment of your registration.
You will receive a second acknowledgment by e-mail as soon your
payment has been processed. In addition, you will find the receipt for your
payment in your conference envelope.
Participants requiring a visa to enter The Netherlands are advised to begin
the required procedures as soon as possible. The RIPE Meeting
organizers are pleased to provide letters of invitation to those
attendees requiring them.
Should you have any further questions, please do not hesitate to
contact us at <meeting(a)ripe.net>.
Kind regards,
Asha Raghoebarsing
RIPE Meeting Co-ordinator
<meeting(a)ripe.net>
