[lir-wg] Problems with route object update

Hi Marcus,


We have had the same situation a few times. The problem seems to be that
"Provider Independent" IP addresses are not at all provider independent
since the LIR is usually the maintainer of the inetnum object, so the
customer will not be able to take the PI net to another LIR unless the
previous LIR agrees to release the object.

A solution could be to make the customer maintainer of the inetnum, that way
the customer could simply add the new LIR's maintainer to MNT-ROUTES.



Med venlig hilsen/Best regards

Christian Rasmussen
Hosting manager, jay.net a/s

Smedeland 32, 2600 Glostrup, Denmark

Email: noc at jay.net
Personal email: chr at corp.jay.net
Tlf./Phone: +45 3336 6300, Fax: +45 3336 6301

Produkter / Products:
http://hosting.jay.net

> -----Original Message-----
> From: lir-wg-admin at ripe.net [mailto:lir-wg-admin at ripe.net]On Behalf Of
> Marcus.Ruchti at colt.de
> Sent: 21. maj 2003 15:17
> To: lir-wg at ripe.net
> Subject: [lir-wg] Problems with route object update
>
>
> Hi all,
>
> I've recognized that we have massive problems
> in the last weeks with RIPE database updates by
> other ISP's.
>
> e.g. a new customer wants that we will announce a PI network
> used by him but it is maintained by another LIR.
>
> I've asked for creating a route object with our maintainer several times
> without success.
>
> I think all this happens with intention to constrain
> the business activity of the competitor !
>
> Is there a possibility to insert the RIPE-NONE Maintainer
> in the whole PI blocks (e.g. /16).
>
> In this step I won't mention the names of those ISP's...
>
> regards,
>
> Marcus Ruchti
> COLT Telecom GmbH
>