- db-wg - mailman.ripe.net

java.xml
by Michael Theurl 15 May '07

15 May '07

Hello DB-WG, I have a problem with the build of the whois server. I checked the latest from the cvs server out. The ./configure setup worked without an problem. Hopefully you can help me out: make all-recursive make[1]: Entering directory `/home/theurlm/whois/whoisserver' Making all in src make[2]: Entering directory `/home/theurlm/whois/whoisserver/src' Making all in defs make[3]: Entering directory `/home/theurlm/whois/whoisserver/src/defs' ---------- 1. ERROR in AttributeSyntax.java (at line 22) import javax.xml.parsers.*; ^^^^^^^^^^^^^^^^^ The import javax.xml cannot be resolved ---------- 2. WARNING in AttributeSyntax.java (at line 24) import org.xml.sax.*; ^^^^^^^^^^^ The import org.xml.sax is never used ---------- 2 problems (1 error, 1 warning) make[3]: *** [AttributeSyntax.class] Error 255 make[3]: Leaving directory `/home/theurlm/whois/whoisserver/src/defs' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/theurlm/whois/whoisserver/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/theurlm/whois/whoisserver' make: *** [all] Error 2 best regards Michael

2 1

RIPE54 DB-WG Draft Agenda V3
by Wilfried Woeber, UniVie/ACOnet 10 May '07

10 May '07

Dear DB-WG folks, Chairpersons, Meeting-Role! This is the 3rd draft of an agenda for the DB-WG at RIPE54 in Tallinn, May 2007. Changes from V2: (in order to take into account on-site stuff) - removed rDNS topic (may come up again in autumn) - added detail to item C. - item Y, "scaled-down" item CA-TF report 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 (Jos B., RIPE NCC) [~30 min] . operational update . status of CRYPT-PW retirement . status of DB documentation . abuse handling C. Task-Force on Data Protection Issues (Jochen d. R. RIPE NCC) [~30 min] . Follow-up proposals/discussion: require link to maintainer for all objects (person, role!) re-open discussion on country: attribute 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 TF: impact on DB, if any (Nigel T.) for full CA-TF report please see http://www.ripe.net/ripe/meetings/ripe-54/presentations/Certification_Task_… . DNS: retire rev-srv: attribute in inetnum: (Peter K, DENIC) Z. AOB . do we need to perform a review of our WGs mandate? (WW144) ________________________________________________________________________

1 0

Compile the Whois server
by Michael Theurl 08 May '07

08 May '07

Hello DB-WG, I tried to compile the Whois server software but I got the following error: ./build.sh --prefix=/opt/whoisserver ./build.sh: line 36: ./configure: No such file or director It seem that the "configure" file is missing ! I downloaded the last version from the whoisserver software from the ripe ftp server. hopefully you can help me. best regards Michael -- [] this Email is made of 100% Recyclable electrons [] visit : www.smog.at ; www.theurl.at ; www.lugv.at [] private: members.smog.at/michael [] mailto : michael.theurl(a)smog.at [] key : www.smog.at/key

2 1

New E-Learning Module: Using PGP and X509 to Protect MNTNER Objects
by Rumy Kanis 03 May '07

03 May '07

Dear Colleagues, We are pleased to announce the launch of the latest module on the RIPE NCC E-Learning Centre: - Using PGP Keys and X509 Certificates in MNTNER objects This module explains the steps required to use a PGP Key and/or X509 Certificate to protect objects in the RIPE Database. The module provides step-by-step guidelines for: - Creating a KEY-CERT object - Adding the KEY-CERT object to an existing MNTNER object as a method of authentication - Updating an object protected by that MNTNER using the PGP key or X509 certificate The RIPE NCC E-Learning Centre is a free of charge service available to everyone, and can be found at https://e-learning.ripe.net. If you have any questions, please feel free to contact us at: e-learning(a)ripe.net Happy Learning, Rumy Kanis Training Services Manager

1 0

Fwd: [db-wg] RIPE54 DB-WG Draft Agenda V2
by Wilfried Woeber, UniVie/ACOnet 27 Apr '07

27 Apr '07

Dear DB-WG folks, Chairpersons, Meeting-Role! This is the 2nd draft of an agenda for the DB-WG at RIPE54 in Tallinn, May 2007. Changes from V1: - moved one line down to AOB, where it belongs, - added 1 item for "Input from..." 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.] . DNS: retire rev-srv: attribute in inetnum: (Peter K, DENIC) Z. AOB . do we need to perform a review of our WGs mandate? (WW144)

1 0

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