Changing inetnum objects

On Fri, 8 Sep 2000, Herbert Baerten wrote:

>> can one company foo.com request its LIR to change the company's inetnum
>> (netname, description, tech-c) so it appears to belong to another company
>> bar.com?

RIPE NCC keeps their own internal records on allocated/assigned address
space. So, although you may modify anything you like in the RIPE
Database, you'll get into conflicts with their internal records and
that will probably trigger an auditing action from hostmasters.

Not sure about "descr:" and "tech-c:" attributes, but "netname:" change
will make inconsistency with internal NCC data for sure. Remember that
notice when you get an assignment from NCC (if you want to combine more
inetnums into one object, inform NCC ...).

Finally, everything depends on your assignment window: if the inetnum
covers address space smaller or equal to your assignment window - it's
always better to delete the old object and create a new one for the
same address range, for another customer and it's higly possible your
action won't be audited, since that's a regular action. However, if the
assignemnt exceeds your assignment window, it's better that you follow
strict procedures: prepare the ripe-141 form for the new customer, get
the approval, delete the old object, create a new object.

Regards,
Beri

---------    Berislav Todorovic, Network Engineer    ---------
-------   KPNQwest N.V. - IP NOC (formerly EUnet NOC)  -------
----  Wilhelmina van Pruisenweg 78, 2595 AN Den Haag, NL  ----
---    Phone: +31-70-379-3990; Mobile: +31-651-333-641     ---
--         Email: beri at kpnqwest.net <=> beri at EU.net         --
---      _   _  ____      _  .--.        ____  ____ __/_   ---
-----    /__/  /___/ /\  /  /   / |   / /___/ /___   /  ------
------ _/  \_ /    _/  \/  (__.\  |/\/ /___  ____/  (__. -----