- db-wg - mailman.ripe.net

RIPE54 DB-WG Draft Agenda V1
by Wilfried Woeber, UniVie/ACOnet 27 Apr '07

27 Apr '07

Dear DB-WG folks, Chairpersons, Meeting-Role! This is the 1st draft of an agenda for the DB-WG at RIPE54 in Tallinn, May 2007. For time slot allocations please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-54/meeting-plan.html Please note that, for our convenience, the time slot map becomes clickable for those sessions which have already submitted a (draft) agenda. Best regards, Wilfried. ________________________________________________________________________ A. Administrative Matters - scribe (N. Titley) - list of participants - agenda - approval of minutes - review of action list - "remote participation" coordination (if needed) B. Data Base Update (N.N., RIPE NCC) [~30 min] . operational update . status of CRYPT-PW retirement . status of DB documentation . abuse handling . revDNS scrpit behaviour (t.b.c.) C. Task-Force on Data Protection Issues (Jochen d. R. RIPE NCC) [~30 min] D. Treatment of orphaned objects (N.N., RIPE NCC) [~10 min] . proposal to remove orphaned person objects Y. Input from other WGs and TFs . Resource Certification Task Force (impact on DB, if any) [t.b.c.] . do we need to perform a review of our WGs mandate? (WW144) Z. AOB

1 0

RIPE Database update problem
by Denis Walker 26 Apr '07

26 Apr '07

[Apologies for duplicate e-mails] Dear Colleagues, >From 21:30 (UTC) on 24 April 2007 until 10:20 (UTC) on 26 April 2007, e-mail updates sent by users to the RIPE Database update service were not processed by the RIPE Database. This problem has now been resolved. ALL the updates submitted have now been processed. No updates were lost. We apologise for this problem with the RIPE Database update service. This was caused by some network adjustments affecting our firewall and mail servers. It had no effect on updates submitted using syncupdates or webupdates, or changes made using the LIR Portal interface. Any changes made by the RIPE NCC Registration Services Department on behalf of RIPE NCC members were also unaffected. We would like to thank all our users for their patience while we fixed this problem. Regards Denis Walker Database Group RIPE NCC

1 0

auto-dbm?
by Max Tulyev 26 Apr '07

26 Apr '07

Hi! I sent a number of letters to auto-dbm(a)ripe.net yesterday and today, all of them was accepted by RIPE mail server, but it seems all of them went to /dev/null without any actions and replies. My friends confirm this too. When DB updates will be fixed? -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

4 4

[Fwd: [db-wg] auto-dbm?]
by Wilfried Woeber, UniVie/ACOnet 26 Apr '07

26 Apr '07

I guess this rather needs to go to ripe-dbm and (maybe) ops than to DB-WG list.... Wilfried. -------- Original Message -------- Subject: [db-wg] auto-dbm? Date: Thu, 26 Apr 2007 12:08:50 +0300 From: Max Tulyev <president(a)ukraine.su> To: Database WG <db-wg(a)ripe.net> Hi! I sent a number of letters to auto-dbm(a)ripe.net yesterday and today, all of them was accepted by RIPE mail server, but it seems all of them went to /dev/null without any actions and replies. My friends confirm this too. When DB updates will be fixed? -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

1 0

Cleanup of unreferenced person objects
by Denis Walker 23 Apr '07

23 Apr '07

Hi There has been some useful feedback already on this proposal. Perhaps I need to clarify some points and suggest some changes to the proposal. We have always wanted to keep the database as clean as possible. So whilst half a million extra person objects has no effect on the operation, we prefer them not to be there if they are serving no useful purpose. We have also been looking more closely at Data Protection issues recently. We have a number of points to discus with the Data Protection Task Force. But the bottom line is, we have to define the purpose(s) of the RIPE Database. We are only allowed to keep personal data in the database if it fits the defined purpose. Although we are only at the stage of drafting these definitions, it is difficult to see how unreferenced person objects could fit any definition that we finally agree on. As for e-mails, I have discussed the numbers with our IT operations guys. They are confident we can handle the worst case scenario with our mail servers. So I suggest we process the deletions with the normal notification procedure where e-mails are sent to any "notify:" addresses in the person objects and to the maintainers if maintained. We will use a modified notification text for this purpose. It will refer to a web page that explains why these person objects are being deleted. Regarding the issue of temporary unreferenced person objects. For example when someone is moving to a new company and de-references their person object from the old companies data and intends to reference it with the new companies data. The proposal allows for a (minimum) one month waiting period before deletion. It could be up to two months, depending on when it is de-referenced. If there is a feeling that this needs to be a longer period it can be extended. I hope this addresses the issues so far raised. Regards Denis Walker Database Group RIPE NCC

1 0

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

22 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

8 12

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

Call for agenda items, DB-WG Meeting during RIPE54, Tallinn, EE
by Wilfried Woeber, UniVie/ACOnet 05 Apr '07

05 Apr '07

Dear DB-WG folks, the RIPE NCC will soon ask us to submit the draft agendas for the WGs. As I'll be out of office till April 18th, I'd like to distribute this Call for Agenda Items even before the Easter Holidays :-) Please submit (to the WG list or to me personally) your item requests or suggest topics for discussion to be included in the draft agenda! I plan to distribute the 1st version of the draft agenda around the 20th of April. The DataBase-WG meeting is scheduled for Friday morning, May 11, 2007. The overall RIPE meeting outline is already available at http://www.ripe.net/ripe/meetings/ripe-54/meeting-plan.html The list of plenary presentations scheduled may eventually be available at [- as of early April this page does not exist yet -] http://www.ripe.net/ripe/meetings/ripe-54/presentations/ See you in Estonia, Wilfried.

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

Concerning the authentication for route object creation
by Hendrik T Voelker 04 Apr '07

04 Apr '07

Dear RIPE, dear Colleagues. I'd like to discuss a topic which most likely has already been discussed several times - only I have not seen that so far. If so, please excuse the 100th time being asked about it and just point me to results of these discussions. Anyway, here we go: According to http://www.ripe.net/info/faq/db/route-creation-IP-space-check.html if it is found that there is no exact matching route object already in existence in the RIPE DB, the less specific route is examined. If one is found deciding for authentication are then contained mnt-routes, mnt-lower or mnt-by fields. What annoys me here is, that holes are completely disregarded, meaning so even if because of defined holes the route object is not authoritative for a network, nonetheless it's authentication data is used. As we have several larger aggregated routes and additional some routes for IP allocations that have a status of "ALLOCATED UNSPECIFIED" we have to update our route objects to include maintainers for other companies so that they become able to maintain PI allocations. If the authentication process would regard holes all we would have to do would be defining a hole once, and not have to change the mnt-routes for a network for every provider change. This might ease the daily business of us all slightly. Cheers Hendrik -- Hendrik T. Voelker HTV5-RIPE EMEA Registrar Team Verizon Deutschland GmbH Sebrathweg 20 D-44149 Dortmund GERMANY http://www.verizonbusiness.com/de/ tel +49-231-972-1565 fax +49-231-972-2587 PubKey 1024D/92479A5D EC1B 76F2 D69D 11C6 2611 5CD1 5269 9351 9247 9A5D Verizon Deutschland GmbH - Sebrathweg 20, 44149 Dortmund, Germany - Amtsgericht Dortmund, HRB 14952 - Gesch�ftsf�hrer: Donald Badoux - Vorsitzender des Aufsichtsrats: Mark Kearns

1 0