- db-wg - mailman.ripe.net

Unreferenced person/role objects
by Denis Walker 03 Jan '08

03 Jan '08

[Apologies for duplicates] Dear Colleagues, The RIPE Data Protection Task Force asked the RIPE NCC to look at why so many unreferenced person/role objects are being created. We found that one organisation was responsible for about 80% of all objects that became unreferenced over the course of 2007. At the time of investigation, this same organisation was responsible for about 30% of all existing unreferenced objects in the RIPE Database. We contacted them and they responded very quickly. They gave the RIPE NCC permission to delete all these unreferenced objects, and they have now adjusted their procedures. Over the New Year period, when we expected the load on the RIPE Database to be quite low, we deleted 161062 person/role objects. You can see the drop in the graph here: http://www.ripe.net/projects/dbconstat/cons-unrefpero.html This problem was caused by deleting inetnum objects, but not deleting the referenced person/role objects. We would like to ask you to please check your own assignment procedures. As customers come and go and you delete or re-assign address space, please delete any person/role objects that are no longer referenced. In the long term, the RIPE NCC will implement an automatic clean-up process, but this may take some time to develop. Regards Denis Walker Business Analyst, RIPE NCC

1 0

Replicated global whois DB
by Hank Nussbacher 19 Nov '07

19 Nov '07

Not sure if this is the right place to ask but is there available software available to download the complete whois DBs of ARIN/RIPE/APNIC/LACNIC/AFRINIC and have it available offline for whois lookups? Thanks, Hank

2 4

Announcement Routing Registry Training Courses
by RIPE NCC Training Services 12 Nov '07

12 Nov '07

[Apologies for duplicate e-mails] Dear Colleagues The RIPE NCC Training Services Department invites you to register for one of our upcoming Routing Registry Training Courses: Date: Monday 28 January 2008 Time: 09:00 - 17:00 Location: London, United Kingdom AND Date: Tuesday 5 February 2008 Time: 09:00 - 17:00 Location: Muscat, Oman AND Date: Friday 29 February 2008 Time: 09:00 - 17:00 Location: Milan, Italy AND Date: Friday 28 March 2008 Time: 09:00 - 17:00 Location: Amsterdam, Netherlands The main objective of the "Routing Registry Training Course" is to familiarise the LIRs with the features of the Routing Registry, while introducing the relevant tools and services of the RIPE NCC. The course also offers practical exercises. OVERVIEW OF TOPICS COVERED IN THE COURSE: - Routing Registry as a part of the RIPE Whois Database and the Internet Routing Registry (IRR) - Specifying routing policies using (RPSL) Routing Policy Specification Language and the RtConfig tool - IRRToolSet - Routing Information Service (RIS) - Routing Registry Consistency Check Project Please note that this is an advanced course. It will: - NOT teach the basics of routing - NOT teach the basics of RIPE Database operations - NOT describe how to receive Internet resources from the RIPE NCC - NOT describe how to operate a Local Internet Registry (LIR) The target audience of the course are technical staff of LIRs: e.g. network operators, engineers etc. This course is not intended for administrative or management staff (e.g. Hostmasters) . It is assumed that all attendees will be familiar with Border Gateway Protocol routing and with the RIPE Database (i.e. creating/modifying objects). This course is based on interactive exercises in a local network set-up. Please bring your laptops equipped with the following: - A working Ethernet card, - Three meters of Ethernet cable, - A secure connection client, - A web browser. Please be prepared to share your laptop (or at least allow another attendee to "look over your shoulder") if necessary. The course is free of charge. We provide lunch and printed training materials. We do not cover any of your travel expenses or accommodation. We give all of our training courses in English. You can find more information about the course at: http://www.ripe.net/training/rr/ How to register: --------------------- You can register up to two people from your LIR for each course. (If there are places left nearer the time of the course, you can register more people). To register for this course, you can either use the LIR Portal at: https://lirportal.ripe.net/lirportal/training/course-list.html Or the online registration form on our website: http://www.ripe.net/cgi-bin/trainingform.pl.cgi If you have any questions, send an e-mail to <training(a)ripe.net>. Kind regards, Rumy Kanis Training Services Manager RIPE NCC

1 0

Draft Minutes v1.0 RIPE 55
by Nigel Titley 26 Oct '07

26 Oct '07

Gentlefolk, Please find the first draft of the DB-WG minutes. Comments, as always, are welcome. Nigel Minutes Database WG RIPE 55 Amsterdam Draft 1 A. Administrative Matters * Welcome * Select a scribe (Nigel T) * Finalise agenda (Agenda accepted) * Approve minutes from RIPE 54 (Approved) [AP54.1 RIPE NCC] To go ahead with final implementation of whois IRT query behaviour (-c), within 4 weeks. Deployed on 1st August after testing. Complete. [AP54.2 RIPE NCC + Chairs] To check through and decide how to split the Database manuals into RIPE and non-RIPE documents. Placeholder document RIPE-419 now points to technical manual. Complete [AP54.3 RIPE NCC] To go ahead and investigate ensuring that all objects are maintained, including timeline and notifications. Submit proposal to the Working Group. Discussion continues on when to implement (hopefully soon). [AP54.4 RIPE NCC] To investigate the provision of a "white pages" facility for industry related persons. Ongoing [AP54.5 DP-TF] To analyse better the function of the country attribute in inetnum and inet6num. Possibly related to the restructuring of the addressing information. However still unclear. Suggested that it should be related to the ultimate point of management of the resource. Ongoing. [AP54.6 RIPE NCC] To summarise the discussion on orphaned objects and write up for the mailing list Ongoing. No objection to proceding with Phase 2 and 3 and removing the objects. [AP54.7 RIPE NCC] To prepare a plan for removal of the rev-srv attribute from the inetnum, inet6num objects. Ongoing B1. Database Update - Jos Boumans, RIPE NCC * Operational update (See presentation) * Status of CRYPT-PW retirement * Removal of orphaned objects B2. DB-Software Developmen Activities * restructuring of documentation set Now complete * modification proposals (maintainer to become mandatory) See presentation [AP55.1 RIPE NCC] Add the feature to the LIRPortal "allocation editor" to include the "irt-mnt" attribute. C. Follow-up on: * Task Force on Data Protection Issues Nothing further to report * Resource Certification Project Ongoing. Nothing concrete likely before next April. D. Improvements to the DB Software - Yasuhiro Shirasaki, NTT See presentation. (High availability IRR systems) This is important in relation to a research project on anti prefix hijacking. Used RIPE whois-server as base system due to its speed and scalability. Uses NDBCluster to provide high availability database. However current performance still not adequate. Memory and CPU upgrades should help (4 -> 8GB RAM). Will be implementing offsite redundancy soon. Coverage is basically for Japanese prefixes at the moment but will be extended. In use by several JP ISPs at the moment to filter hijacked prefixes. E. A Case for NRTM for IRR Updates - Raymond J., Elisa, FI * 1075 peering session, 509 unique AS:ses See presentation. Extensively peered, so aut-num object maintenance is an major overhead. Tool XIRR gives contact information, traffic and advertisement information NRTM needed in order to keep the local copy up to date. F. A Review of the "changed:" Attribute - Peter K., DEnic, DE * syntax, semantics, quality of info in changed: ? Problem with changed: attribute. If it is present (even historical copies) then no new changed: line is needed. This casts some doubt on the utility of the changed: line. It cannot be relied upon as a reliable change history of the object or even as the latest change of the object. It is suggested that the changed: attribute should be changed: maybe by enforcing a timestamp for non-null changes. Maybe just maintain the creation and last modification dates? What about ensuring accuracy (a timestamp to say "this record was accurate on this date"). What about data protection issues on personal data? It is possible to produce virtually any variant of this from the database. A full audit trail of object modifications is maintained within the database but is generally only produced in response to a court order. Note that hostmasters actually use these attributes despite their dubious value. [AP55.2 Peter K] To find out what the changed: line is used for and come up with a possible way forward. Will need coordination with the DP-TF. Y. Input from Other Working Groups and Task Forces * Contact Data Quality/Requirements Discussion [Anti-Spam-WG] Continue with this in the DP-TF * "Dot-Notation" for ASN32 [Routing-WG] Some people are not happy with the Dot-Notation for ASN32. Conflict with router RE parsing. No consensus in the Routing-DB so not a lot we can do. Very few ASN32s have yet been issued. However it not an insignificant change. IRRToolset has been patched to allow the dot. The Dot-Notation is still only a draft RFC so may not end up turning into a full RFC anyway. At least one major router vendor has already adopted the Dot-Notation. Z. A.O.B. * External object removal requests (Malcom H.) The issue here is where a legal request might arrive to remove an item from the DB. If this is likely to happen, how should the RIPE NCC respond? At present there is no law that might mandate this, but one might come along. The RIPE DB covers far more than the EU, and this could create a conflict of interest (or even a diplomatic incident). Important that all be aware that this sort of thing is being proposed by certain elements within the EU and we should perhaps think about this. There is clearly a job for the RIPE NCC communications group to make it clear to appropriate bodies what the function of the database actually is [AP55.3 RIPE NCC]. Current RIPE NCC policy on information requests is to first point to the public data, and then if more is required, then require a court order from a Dutch judge. We clearly need to discuss this, but it probably needs discussing in a wider scope but it is very important to have arguments prepared beforehand.

1 0

RIPE55 DB-WG Draft Agenda V2
by Wilfried Woeber, UniVie/ACOnet 24 Oct '07

24 Oct '07

Dear DB-WG folks, Chairpersons, "Meeting"! This is an updated draft (V2) of the proposed agenda for the DB-WG during RIPE55 in Amsterdam, October 2007. For time slot allocations please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-55/meeting-plan.html Please note that, for our convenience, the time slot map became clickable for those sessions which have already submitted a (draft) agenda! Best regards, Wilfried. ________________________________________________________________________ A. Administrative Matters . Welcome . select scribe . finalise agenda . approval of minutes from RIPE 54 . review of action list B1. Data Base Update (Jos B., RIPE NCC) [~30 min] . operational update . status of CRYPT-PW retirement . removal of orphaned objects (AP54.7) B2. DB-Software Developmen Activities . restructuring of documentation set . modification proposals (maintainer required, ...) C. Follow-Up on . Task-Force on Data Protection Issues [t.b.c.] . Resource Certification Project [t.b.c.] D. Improvements to the DB Software (Yasuhiro Shirasaki-san, NTT JP[~10 min] E. A case for NRTM for IRR updates (Raymond J., Elisa, FI) [~10 min] . 1075 peers, 509 unique AS:ses F. A review of the changed: attribute (Peter K., DEnic, DE) [~10 min] . syntax, semantics, quality of info in changed: ? Y. Input from other WGs and TFs . Contact Data Quality/Requirements Discussion [AS-WG] [t.b.c.] . "Dot-Notation" for ASN32 [Routing-WG] [t.b.c.] Z. AOB ________________________________________________________________________

1 0

New RIPE Database document
by Denis Walker 11 Oct '07

11 Oct '07

[Apologies for duplicates] Dear Colleagues, During the Database Working Group (DB WG) session at RIPE 54, it was decided to review the status of those RIPE Documents relating to the RIPE Database. Following discussion on the DB WG Mailing List, a proposal to address this issue was produced, which can be viewed at: http://ripe.net/ripe/maillists/archives/db-wg/2007/msg00162.html No concerns were raised and this proposal has now been implemented. This implementation has resulted in a new RIPE Document, ripe-419 "RIPE Database Reference Manual". This provides a brief introduction to the RIPE Database and references the new RIPE Database Document Library, which can be viewed at: http://www.ripe.net/db/docs.html This library references all the available documents concerning the RIPE Database and associated services. These documents will, in future, be kept up-to-date with all changes to database software and procedures. If you have any questions or concerns, please send an e-mail to <ripe-dbm(a)ripe.net>. Regards Denis Walker RIPE NCC

1 0

RIPE 54 Minutes (2nd Draft)
by Nigel Titley 14 Sep '07

14 Sep '07

Following comments made offlist, I attach an updated copy of the minutes. The relevant changes are in the discussion of the country attribute. Nigel This email and any attachments may be confidential and/or legally privileged. If you have received this e-mail and you are not a named addressee, please inform the sender of this email by sending a return email to the address above and then delete the e-mail and your response from your system. If you are not a named addressee you must not use, disclose, distribute, copy, print or rely on this e-mail. Any views or opinions presented are solely those of the author. Any statements made, or intentions expressed in this communication may not necessarily reflect the view of Easynet. No content herein will bind Easynet or any associated company unless confirmed by the execution of a formal contract by Easynet. Any figures or amounts given in this email are quotations only and are subject to change. Although Easynet routinely screens for viruses, addressees should scan this e-mail and any attachments for viruses. Easynet makes no representation or warranty as to the absence of viruses in this e-mail or any attachments. Please note that to ensure regulatory compliance and for the protection of our customers and business, we may monitor and read e-mails sent to and from our server(s). Easynet Limited a company incorporated and existing under the laws of England and Wales, with company number 2954343 and having its registered office at 44-46 Whitfield Street London, W1T 2RJ.

1 0

RIPE55 DB-WG Draft Agenda V1
by Wilfried Woeber, UniVie/ACOnet 14 Sep '07

14 Sep '07

Dear DB-WG folks, Chairpersons, "Meeting"! This is the (very rough) 1st draft of an agenda for the DB-WG at RIPE55 in Amsterdam, October 2007. For time slot allocations please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-55/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 . Welcome . select scribe . finalise agenda . approval of minutes from RIPE 54 . review of action list B. Data Base Update (N.N., RIPE NCC) [~30 min] . operational update . status of CRYPT-PW retirement . removal of orphaned objects (AP54.7) C. follow-Up on . Task-Force on Data Protection Issues [t.b.c.] . Contact Data Quality/Requirements Discussion [t.b.c.] . Resource Certification Project [t.b.c.] D. DB-Software Developmen Activities [~30 min] . restructuring of documentation set . modification proposals (maintainer required, ...) Y. Input from other WGs and TFs Z. AOB ________________________________________________________________________

1 0

Call for agenda items, DB-WG Meeting during RIPE55, Amsterdam, NL
by Wilfried Woeber, UniVie/ACOnet 30 Aug '07

30 Aug '07

Dear DB-WG folks, Planning activities for the next RIPE Meeting - RIPE55 in Amsterdam - have already started, thus this call for agenda items. 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 during the first week of September. The DataBase-WG meeting is, as "usual" scheduled for Friday morning, October 26, 2007. The overall RIPE meeting outline is already available at http://www.ripe.net/ripe/meetings/ripe-55/meeting-plan.html The list of plenary presentations and the session archive may eventually become available at [- as of late August this page does not exist yet -] http://www.ripe.net/ripe/meetings/ripe-55/presentations/ See you in Amsterdam, Wilfried.

1 0

Proposal to re-structure the RIPE DB Software Documentation
by Wilfried Woeber, UniVie/ACOnet 30 Aug '07

30 Aug '07

Following up on discussions in eMail and personally with folks at the NCC who are responsible for maintaining and developing the DB Software, Jos and I would like to come forward with the following proposal, in order to - ease the burden and formal overhead of keeping the DB-SW Documentation up-to-date and in synch with the software development, to - remove the formal RIPE Document status from ripe-401, ripe-252, "ripe-draft" and ripe-402, and to - create a *new* "formal" RIPE Document which acts as an anchor for the (new or updated) set of documentation and as a cross reference to the relevant operational manuals. This new RIPE Document may also include procedure- related topics that might be of special interst regarding implementation of the software at the NCC. The big advantage of this approach is to help with keeping the software and the documentation in synch and up-to-date, even for non-fundamental changes, instead of having formal and stable "baseline documents" and - over time - a set of change notices. Or, worse, outdated documentation :-) I hope this approach does not raise any fundamental concerns with the community and I will put that topic onto the DB-WG's draft agenda for RIPE55, for feedback and an update on where we are. If you do see major problems or have objections, please let us know as soon as possible on the mailing list! Thanks, Wilfried.

2 2