Events of Tuesday, 27 October 1998
RIPE Database Administration
Tue Nov 3 16:58:29 CET 1998
Dear Rimas Janusauskas, We wish to correct this statement. When AUTO-# is used to create a nic-handle, it uses the lowest available number that is consistent with the initials of the name in the "person" line of the object. "Holes" can and do exist, but no-one should depend on this. Rimas Janusauskas <rimas at taide.lt> writes: * On Thu, 29 Oct 1998, RIPE Database Administration wrote: * * > When a person object is deleted, its nic-handle is available for * > re-use immediately. Therefore, you may find that a nic-handle now * > points to a different person or role object. We recommend that you * > check the consistency of your data i.e. see if the nic-handles in the * > admin-c, tech-c, and zone-c lines of your objects refer to the correct * > person or role objects. * * It's true, that nic-handle is available for re-use, but it * could be (re)created only using directly. * If AUTO-# is used to creat new nic handle, bigest * value+1 is choosen although "holes" exists. * * > Please note * > that it is the users responsibility to restore their own data. * > We would like to stress that the RIPE NCC operates the RIPE Database, * > however the responsibility for managing user data lies with the users. * * Is it possible implement such feature, that "e-mail" attribute(s) * should be used as "notify" as well. In that case nic handle holder * will be always informed about (un)expected changes. * That is an interesting suggestion. Perhaps you should send it to the mailing list of the Database Working Group, <db-wg at ripe.net>. * best regards, * * Rimas Janusauskas, * Taide Net Hostmaster * * If you have any more questions, please don't hesitate to contact <ripe-dbm at ripe.net>. Regards, Roman Karpiuk ____________________________ RIPE Database Administration.
[ lir-wg Archive ]