- ncc-services-wg - mailman.ripe.net

Clean up of unreferenced person/role objects
by Denis Walker 23 Apr '07

23 Apr '07

Introduction ------------ According to our database consistency statistics program (dbconstat [1]) we currently have 460,573 unreferenced person/role objects [2]. Some of these may be maintained, but are still unreferenced. Any personal data not referenced by Internet resources do not fit within the purpose of the RIPE Database. They should not be stored in the RIPE Database beyond a reasonable 'work in progress' period. The RIPE NCC has had a mandate to delete these unreferenced person/role objects since RIPE 40: http://www.ripe.net/ripe/wg/db/minutes/ripe-40.html (2001) At RIPE 41, the Database Working Group agreed that "maintained objects will now be removed" and "gave a mandate to the RIPE NCC to continue with the cleanup process." http://www.ripe.net/ripe/wg/db/minutes/ripe-41.html (2002) The cleanup process of 2003 (http://www.ripe.net/db/news/unref-cleanup-200304.html) involved using a script to run periodic cleanups. This script was put in place. However, it failed about 18 months ago. Because of other priorities, we have not had the time to examine this issue again until now. The graph showing the increase in these unreferenced person objects [3] indicates that the cleanup script appeared not to be performing correctly. At the start of 2006, there were about 300,000 unreferenced person/role objects. Since then there has been a steady increase with a large increase of almost 50,000 in February 2007. The graph also shows a slightly higher rate of increases in these objects since February 2007. Because of the high number now of unreferenced person objects, we want to raise the issue with the community again and propose the below procedure to clean them up. Because redundant personal data is a serious data protection issue, we want to take a new approach to this in the future. Once the initial cleanup is in progress, we will create a new proposal for a new, regular cleanup procedure. This will be sent to the Data Protection Task Force [4] and then to the rest of the community. One time bulk cleanup procedure ------------------------------- Month 1 * Select 80,000 unreferenced person/role objects. Month 2 * Check selected person/role objects. * Those still unreferenced: o Delete using normal update process. o 2000 objects per update message. o Run updates overnight (Saturday/Sunday). o One update every 15 minutes. o This should avoid any unnecessary load on the servers. * Select next 80,000 unreferenced person/role objects. Month 3 * Repeat process until complete. Notes ----- This procedure will take about 6 months to clear the current backlog, not including the extra time that may be necessary due to the increases over that period. Because of the high numbers involved, we prefer NOT to send out individual e-mail notifications, either before or after deletion. This is to prevent a high load on our mail servers, especially in the event of a high number of bounced e-mails. This means that there will be no individual announcements to listed e-mail addresses before the deletion and none of the usual update notifications. This also means that even if the objects are maintained, the maintainer will not be notified directly about the deletion of their unreferenced person/role object. We will, however, announce the cleanup to the Working Group mailing lists and as a news item on our web site home page. The worst problem that can occur is that someone will enter a reference to their person/role object just as we delete it. However, as we are only deleting unreferenced person/role objects, the time needed to re-create them is minimal. We suspect that a very large proportion of the unreferenced person/role objects that we will be deleting are abandoned objects that are no longer used. References ---------- [1] dbconstat http://www.ripe.net/projects/dbconstat/index.html [2] current unreferenced person/role objects http://www.ripe.net/projects/dbconstat/html/cons-current.html [3] graph of unreferenced person object increase http://www.ripe.net/projects/dbconstat/cons-unrefpero.html [4] Data Protection Task Force http://www.ripe.net/ripe/tf/dp/index.html

9 15

Updated RIPE Database Manuals
by Denis Walker 17 Apr '07

17 Apr '07

[apologies for duplicates] Dear Colleagues, We are pleased to announce the publication of three updated RIPE Database Documents. ripe-401 RIPE Database Query Reference Manual ripe-402 RIPE Database User Manual: Getting Started DRAFT RIPE Database Update Reference Manual Previously, the Query and Update Reference Manuals were part of ripe-252, The RIPE Database Reference Manual. The content has been thoroughly revised and updated, and we have also improved the wording to make it clearer. The Update Reference Manual also contains a lot of new content, reflecting many of the changes made to the database software over recent years. Because it is so long since this manual has been revised, the list of changes is considerable. It has not been possible to reflect all these changes in the first revision. This is why it is only released as a draft document at this stage. A second revision will take place after the RIPE 54 Meeting. Together, the Query Reference Manual and Update Reference Manual (currently in draft format) will completely obsolete ripe-252. You can find ripe-401 and ripe-402 at: http://www.ripe.net/ripe/docs/database.html The draft of the RIPE Database Update Reference Manual is available at: http://www.ripe.net/ripe/draft-documents/draft_db_manual.pdf Regards Denis Walker Database Group RIPE NCC

1 0

RIPE NCC Maintenance Wednesday 18/04/2007 http://e-learning.ripe.net 1700 UTC
by Mark Guz 16 Apr '07

16 Apr '07

Dear Colleagues, On Wednesday 18/04/07 between 17:00 and 19:00 UTC we will be renumbering the website http://e-learning.ripe.net. This will result in a small outage during the posted maintenance window while the new IP address filters through DNS. We apologise for any inconvenience this might cause. As usual, if you have any questions please forward them to ops(a)ripe.net Regards Mark Guz Senior Engineer OPS/IT Department RIPE NCC http://www.ripe.net

1 0

RIPE 54 Agenda Items for NCC Services WG
by Sanghani, Bijal 12 Apr '07

12 Apr '07

Hi all, We are currently compiling the draft agenda for the RIPE NCC Services Working Group for RIPE 54 in Tallinn. If anyone would like to suggest a presentation or raise a topic for discussion please let either Kurtis or me know and we'll arrange a spot on the agenda. Regards, Bijal ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

1 0

RIPE NCC Network Maintenance Tuesday April 17 at 17:00 UTC
by Mark Guz 12 Apr '07

12 Apr '07

[apologies for duplicates] Dear Colleagues, On Tuesday 17/04/2007, between 17:00 and 19:00 (UTC), the RIPE NCC will carry out planned maintenance work on our core network infrastructure. RIPE NCC services will be temporarily unavailable during this period. We apologise for any inconvenience that this may cause. This work is due to the deployment of a new section of dark fibre between 2 of our PoPs, which was aborted on April 12. If you have any questions about this, please send an e-mail to: ops(a)ripe.net Regards Mark Guz Senior Engineer Operations Department RIPE NCC http://www.ripe.net

1 0

RIPE NCC Network Maintenance 1700 UTC (1900 CEST) Thurday 5 April 2007 Postponed
by Mark Guz 05 Apr '07

05 Apr '07

Dear Colleagues, Due to the fact that the RIPE NCC will be closed tomorrow and Monday we have decided to postpone this maintenance until next Wednesday (11/04/07 ). Apologies for the inconvenience this may cause. If you have any questions please send them to ops(a)ripe.net Kind Regards Mark Guz Senior Engineer OPS/IT RIPE NCC Amsterdam

1 0

Test Traffic Task Force
by Mark Dranse 05 Apr '07

05 Apr '07

[Apologies for duplicate e-mails] Dear Colleagues, At RIPE 52, a task force was formed to discuss the future developments of the RIPE NCC Test Traffic Measurements (TTM) platform. In response to feedback received on the task force list, we have a new draft proposal for network improvements that we plan to distribute for discussion next week. We encourage anyone with an interest in this subject to participate in the task force by subscribing to the mailing list. You can subscribe to the list at: http://www.ripe.net/mailman/listinfo/tt-tf More information about TTM is available at: http://www.ripe.net/ttm The presentation that led to the creation of the task force is available at: http://www.ripe.net/ripe/meetings/ripe-52/presentations/ripe52-tt-future.pdf Kind regards, Mark Dranse Information Services Manager RIPE NCC

1 0

RIPE NCC Network Maintenance 1700 UTC (1900 CEST) Thurday 5 April 2007
by Mark Guz 03 Apr '07

03 Apr '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [apologies for duplicates] Dear Colleagues, On Thursday 05/04/2007, between 17:00 and 19:00 (UTC), the RIPE NCC will carry out planned maintenance work on our core network infrastructure. RIPE NCC services will be temporarily unavailable during this period. We apologise for any inconvenience that this may cause. This work is due to the deployment of a new section of dark fibre between two of our PoPs If you have any questions about this, please send an e-mail to: ops(a)ripe.net Regards Mark Guz Senior Engineer Operations Department RIPE NCC http://www.ripe.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGEhqgl42z2L2N9gERAofHAKClFauaor8xhKENLD4dp5PSfN9MFQCfZhCh D1RBdhQbWlox3dtzLzLPvLE= =g9jU -----END PGP SIGNATURE-----

1 0

Maintenance on ns-sec.ripe.net
by Brett Carr 02 Apr '07

02 Apr '07

[Apologies for duplicates] Dear Colleagues, On 4 April, 2007, authoritative Reverse DNS Services on ns- sec.ripe.net will be unavailable between 19:00 and 20:00 UTC. During this time we need to carry out maintenance work. We apologise for any inconvenience this causes. If you have any questions or concerns about this, please e-mail: dns- help(a)ripe.net -- Brett Carr Manager -- DNS Services Group RIPE Network Coordination Centre Amsterdam

1 0

2006-06 implementation: IPv4 Maximum Allocation Period
by Alex le Heux 21 Mar '07

21 Mar '07

[Apologies for duplicate e-mails.] Dear Colleagues, We are pleased to announce that the policy proposed in proposal 2006-06: 'IPv4 Maximum Allocation Period' will come into effect on 18 April, 2007. This proposal can be found at: http://www.ripe.net/ripe/policies/proposals/2006-06.html We will also publish the new 'IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region' document on this day. This document will be available at: http://www.ripe.net/ripe/docs/ipv4-policies.html Best regards, Alex Le Heux RIPE NCC IP Resource Analyst

1 0