Reminder: Removal of selected sets of contact information from the RIPE Database
Dear all, (apologies for duplicates) This message is a reminder of the ongoing process of removal of unreferenced contact information from the RIPE Database. We have updated the web page http://www.ripe.net/ripencc/pub-services/db/orphaned.html with a more up to date list of maintainer objects relevant to this process. I would like to use the opportunity to clarify an apparently confusing aspect of previous notes: If your person/role object already has a mnt-by attribute that references a maintainer object not contained in the list provided in the above mentioned web page, there is no need to add a reference to RIPE-NCC-PN-NONE-MNT. This maintainer has been created by the RIPE NCC with the sole purpose of facilitating a mechanism for people without maintainer objects to tag their person/role objects to avoid deletion. If you already have a proper maintainer object, DO NOT include RIPE-NCC-PN-NONE-MNT as this would lower your protection level. Best regards, Joao Damas RIPE NCC
On Tue, Sep 11, 2001 at 05:50:10PM +0200, Joao Luis Silva Damas wrote:
Dear all,
(apologies for duplicates)
This message is a reminder of the ongoing process of removal of unreferenced contact information from the RIPE Database.
We have updated the web page http://www.ripe.net/ripencc/pub-services/db/orphaned.html with a more up to date list of maintainer objects relevant to this process.
The page says: | 3.Due to the nature and the size of the data set involved, the RIPE NCC can | not publish a list of all the objects affected. and suggests to poll the status of the entries with a usual whois client. Due to the nature and size of the data set involved this requires a million queries to the RIPE database to avoid ambiguities with the very very likeley event of rapidly reassigned handles. I suggest to create a list of involved entries and pass it to the maintainer in question. -- i.A. Michael van Elst / phone: +49 721 9652 330 Xlink - Network Information Centre \/ fax: +49 721 9652 349 Emmy-Noether-Strasse 9 /\ link http://nic.xlink.net/ D-76131 Karlsruhe, Germany /_______ email: hostmaster@xlink.net [ KPNQwest Germany GmbH, Sitz Karlsruhe ] [ Amtsgericht Karlsruhe HRB 8161, Geschaeftsfuehrer: Peter Dressler ]
Dear Michael van Elst, (ripe-list is removed from the cc:) Michael van Elst wrote:
On Tue, Sep 11, 2001 at 05:50:10PM +0200, Joao Luis Silva Damas wrote:
Dear all,
(apologies for duplicates)
This message is a reminder of the ongoing process of removal of unreferenced contact information from the RIPE Database.
We have updated the web page http://www.ripe.net/ripencc/pub-services/db/orphaned.html with a more up to date list of maintainer objects relevant to this process.
The page says:
| 3.Due to the nature and the size of the data set involved, the RIPE NCC can | not publish a list of all the objects affected.
and suggests to poll the status of the entries with a usual whois client.
Due to the nature and size of the data set involved this requires a million queries to the RIPE database to avoid ambiguities with the very very likeley event of rapidly reassigned handles.
Could you please explain the problem? The proposed protection mechanism with the RIP-NCC-PN-NONE-MNT is targeted only at individuals who have unreferenced and unmaintained person objects and want to protect their objects in the database. It is not supposed to be used by a maintainer from the published list.
I suggest to create a list of involved entries and pass it to the maintainer in question.
-- i.A. Michael van Elst / phone: +49 721 9652 330 Xlink - Network Information Centre \/ fax: +49 721 9652 349 Emmy-Noether-Strasse 9 /\ link http://nic.xlink.net/ D-76131 Karlsruhe, Germany /_______ email: hostmaster@xlink.net [ KPNQwest Germany GmbH, Sitz Karlsruhe ] [ Amtsgericht Karlsruhe HRB 8161, Geschaeftsfuehrer: Peter Dressler ]
Regards, Andrei Robachevsky DB Group Manager RIPE NCC
On Thu, Sep 13, 2001 at 04:11:31PM +0200, Andrei Robachevsky wrote:
Dear Michael van Elst,
Could you please explain the problem? The proposed protection mechanism with the RIP-NCC-PN-NONE-MNT is targeted only at individuals who have unreferenced and unmaintained person objects and want to protect their objects in the database.
It is not supposed to be used by a maintainer from the published list.
Sorry if there was a misunderstanding. It's not about protecting entries. I am responsible for a huge part of the to-be-deleted entries (XLINK-MNT) and I would really _welcome_ a list of the then deleted entries belonging to XLINK-MNT to synchronize this change with our own databases. It would be less of a problem if RIPE wouldn't re-assign handles. But as it is, our only way is to validate each and every database entry to find out what had been deleted. Greetings, -- i.A. Michael van Elst / phone: +49 721 9652 330 Xlink - Network Information Centre \/ fax: +49 721 9652 349 Emmy-Noether-Strasse 9 /\ link http://nic.xlink.net/ D-76131 Karlsruhe, Germany /_______ email: hostmaster@xlink.net [ KPNQwest Germany GmbH, Sitz Karlsruhe ] [ Amtsgericht Karlsruhe HRB 8161, Geschaeftsfuehrer: Peter Dressler ]
Michael van Elst wrote:
On Thu, Sep 13, 2001 at 04:11:31PM +0200, Andrei Robachevsky wrote:
Dear Michael van Elst,
Could you please explain the problem? The proposed protection mechanism with the RIP-NCC-PN-NONE-MNT is targeted only at individuals who have unreferenced and unmaintained person objects and want to protect their objects in the database.
It is not supposed to be used by a maintainer from the published list.
Sorry if there was a misunderstanding. It's not about protecting entries.
I am responsible for a huge part of the to-be-deleted entries (XLINK-MNT) and I would really _welcome_ a list of the then deleted entries belonging to XLINK-MNT to synchronize this change with our own databases.
It would be less of a problem if RIPE wouldn't re-assign handles. But as it is, our only way is to validate each and every database entry to find out what had been deleted.
We will try to help maintainers responsible for huge amount of contact information stored in the RIPE Database. If you feel you need such help, please contact ripe-dbm@ripe.net (with a copy to myself, andrei@ripe.net) to discuss your situation. Thanks, Andrei Robachevsky DB Group Manager RIPE NCC
Greetings, -- i.A. Michael van Elst / phone: +49 721 9652 330 Xlink - Network Information Centre \/ fax: +49 721 9652 349 Emmy-Noether-Strasse 9 /\ link http://nic.xlink.net/ D-76131 Karlsruhe, Germany /_______ email: hostmaster@xlink.net [ KPNQwest Germany GmbH, Sitz Karlsruhe ] [ Amtsgericht Karlsruhe HRB 8161, Geschaeftsfuehrer: Peter Dressler ]
participants (3)
-
Andrei Robachevsky -
Joao Luis Silva Damas -
Michael van Elst