Re: Can anyone shed some light on this?

["Larisa A. Yurkina" <]

On Wed, 5 Dec 2001, Stephen Burley wrote:

Hi,

it looks like a problem we had some time ago.
the answer from Database admin was:
RPSL requires that both the maintainer of the IP space (i.e. the inetnum
object) and the AS number (i.e. the aut-num object) of a route authorize
the route creation.  This means that the authentication of both
maintainers must be included in the e-mail update.

The problem is, inetnum object is maintained with RIPE-NCC-HM-MNT
but not with your as-mntner.

To solve the problem you should ask RIPE NCC hostmaster
to add 
mnt-routes: AS702-MNT to the allocation object.



> Further to this i also get the forwarded message that an atempt was made to
> change this object - go figure.
> 
> ----- Original Message -----
> From: "Stephen Burley" stephenb@localhost
>
> Cc: db-wg@localhost
> Sent: Wednesday, December 05, 2001 10:30 AM
> 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@localhost 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@localhost 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
> >
> >
> >
> 


With respect,
Larisa Yurkina
---
RIPN Registry center
-----