Deletion of person objects. Final reminder
Dear all, (apologies for duplicates) Today is the 21st of September. As such, the RIPE NCC will proceed to delete the set of person/role objects detailed in my previous announcements from the RIPE Database. Please see the URL http://www.ripe.net/ripencc/pub-services/db/orphaned.html for information on the details of the objects to be deleted. The following is an outline of the process we will be using: 1. Stop updating the database on Friday, 21, at 18:00 CEST. 2. Remove all person objects according to the criteria: - maintained _only_ by DE domain resellers and not referenced - not maintained and not referenced This will take ~15 hours 3. Next day, on Saturday restart the server with the new database. 4. Resume the updates. As you can see, this process will result in period of a few hours during which UPDATE/ADDITION/DELETION messages sent to the RIPE Database will not be processed immediately, but rather stored for later processing. Queries will be serviced by our hot spare machine. Users will not notice any downtime on that part of the service. The length of the outage is directly related to the number of objects to be deleted (more than 2 million) and the need to use special processes to finalise the process in a reasonable time. Further to this deletion, and in order to avoid replication of the current situation after this deletion process, incoming messages containing person and role objects originating from domain name related activities will NOT be processed. The RIPE NCC will contact any source of such messages in order to clear any possible misunderstandings. Hoping to have informed you well, Joao Luis Silva Damas Chief Technical Officer RIPE NCC
Hi Joao,
Further to this deletion, and in order to avoid replication of the current situation after this deletion process, incoming messages containing person and role objects originating from domain name related activities will NOT be processed.
The RIPE NCC will contact any source of such messages in order to clear any possible misunderstandings.
Just for clarification. If a customer had a RIPE Handle which was needed for the domain adminc, we won't get a new handle which we'll use for a netassigment ? Considered that the old one would have been deleted by tomorrow latest. regards, Andreas Wittkemper
If your "handle" is being used for IP registration our any IRR related function, it will be referenced from an already existing object in the RIPE Database and will therefore NOT be deleted. If your handle was only in use for domain (other that in-addr.arpa) registration purposes, then your contact information should be registered with the corresponding TLD administrator as it will be deleted from the RIPE Database. No new handles are being created in this process as only handles used for functions foreign to the RIPE Database will be deleted in the process later today. Hopes this clarifies the situation for you, if not, please contact me. Regards, Joao Damas RIPE NCC At 16:01 +0200 21/9/01, Andreas Wittkemper wrote:
Hi Joao,
Further to this deletion, and in order to avoid replication of the current situation after this deletion process, incoming messages containing person and role objects originating from domain name related activities will NOT be processed.
The RIPE NCC will contact any source of such messages in order to clear any possible misunderstandings.
Just for clarification. If a customer had a RIPE Handle which was needed for the domain adminc, we won't get a new handle which we'll use for a netassigment ? Considered that the old one would have been deleted by tomorrow latest.
regards,
Andreas Wittkemper
--
The process of deletion itself is clear. I'm just wondering about the consequences of your statement.
Further to this deletion, and in order to avoid replication of the current situation after this deletion process, incoming messages containing person and role objects originating from domain name related activities will NOT be processed.
The RIPE NCC will contact any source of such messages in order to clear any possible misunderstandings.
Are you going to check if the data of a new requested handle were used before as a domainonly referenced handle ? Would you block that and we couldn't request a new handle with this specific data for an inetnum object ? regards, Andreas Wittkemper
If your "handle" is being used for IP registration our any IRR related function, it will be referenced from an already existing object in the RIPE Database and will therefore NOT be deleted.
If your handle was only in use for domain (other that in-addr.arpa) registration purposes, then your contact information should be registered with the corresponding TLD administrator as it will be deleted from the RIPE Database.
No new handles are being created in this process as only handles used for functions foreign to the RIPE Database will be deleted in the process later today.
Hopes this clarifies the situation for you, if not, please contact me.
Regards, Joao Damas RIPE NCC
At 16:01 +0200 21/9/01, Andreas Wittkemper wrote:
Hi Joao,
Further to this deletion, and in order to avoid replication of the current situation after this deletion process, incoming messages containing person and role objects originating from domain name related activities will NOT be processed.
The RIPE NCC will contact any source of such messages in order to clear any possible misunderstandings.
Just for clarification. If a customer had a RIPE Handle which was needed for the domain adminc, we won't get a new handle which we'll use for a netassigment ? Considered that the old one would have been deleted by tomorrow latest.
regards,
Andreas Wittkemper
At 16:42 +0200 21/9/01, Andreas Wittkemper wrote:
The process of deletion itself is clear. I'm just wondering about the consequences of your statement.
Further to this deletion, and in order to avoid replication of the current situation after this deletion process, incoming messages containing person and role objects originating from domain name related activities will NOT be processed.
The RIPE NCC will contact any source of such messages in order to clear any possible misunderstandings.
Are you going to check if the data of a new requested handle were used before as a domainonly referenced handle ? Would you block that and we couldn't request a new handle with this specific data for an inetnum object ?
No we will NOT block the creation of such handles. It doesn't matter whether the handle existed or not before as long as now it is used for IP related issues. What we will do is track the creation of significant amounts of unreferenced contact data. Ideally we would like to implement a regular clean up so that the situation does not build up to what we have now again. regards, Joao Damas RIPE NCC
regards,
Andreas Wittkemper
--
Dear all, This is just to notify you that the removal of the set of person objects has finished successfully. Almost 3 million person objects have been deleted from the RIPE Database. It took a bit longer than we expected, but everything went without problems. Sorry for inconvenience this caused. Best regards, Andrei Robachevsky DB Group Manager RIPE NCC Joao Luis Silva Damas wrote:
Dear all,
(apologies for duplicates)
Today is the 21st of September.
As such, the RIPE NCC will proceed to delete the set of person/role objects detailed in my previous announcements from the RIPE Database. Please see the URL http://www.ripe.net/ripencc/pub-services/db/orphaned.html for information on the details of the objects to be deleted.
The following is an outline of the process we will be using:
1. Stop updating the database on Friday, 21, at 18:00 CEST. 2. Remove all person objects according to the criteria: - maintained _only_ by DE domain resellers and not referenced - not maintained and not referenced This will take ~15 hours 3. Next day, on Saturday restart the server with the new database. 4. Resume the updates.
As you can see, this process will result in period of a few hours during which UPDATE/ADDITION/DELETION messages sent to the RIPE Database will not be processed immediately, but rather stored for later processing.
Queries will be serviced by our hot spare machine. Users will not notice any downtime on that part of the service.
The length of the outage is directly related to the number of objects to be deleted (more than 2 million) and the need to use special processes to finalise the process in a reasonable time.
Further to this deletion, and in order to avoid replication of the current situation after this deletion process, incoming messages containing person and role objects originating from domain name related activities will NOT be processed.
The RIPE NCC will contact any source of such messages in order to clear any possible misunderstandings.
Hoping to have informed you well,
Joao Luis Silva Damas Chief Technical Officer RIPE NCC
participants (3)
-
Andrei Robachevsky -
aw＠de.uu.net -
Joao Luis Silva Damas