- db-wg - mailman.ripe.net

Call for agenda items, DB-WG Meeting during RIPE57, Dubai, UAE
by Wilfried Woeber, UniVie/ACOnet 25 Sep '08

25 Sep '08

Dear DB-WG folks, planning activities for the next RIPE Meeting - RIPE57 in Dubai - have already started, thus this call for agenda items. Please submit (to the WG list!) your item requests and|or suggest topics for discussion to be included in the draft agenda! (I plan to distribute the 1st version of the draft agenda in about one week from now.) Please note that the DataBase-WG meeting is, again, scheduled for *Thursday* (in the morning) - due to the meeting starting on Sunday. The overall RIPE 57 meeting outline is already available at http://www.ripe.net/ripe/meetings/ripe-57/meeting-plan.html The list of plenary presentations and the session archive may eventually become available at [- this page probably does not exist yet -] http://www.ripe.net/ripe/meetings/ripe-57/presentations/ or at a different URL. Have a successful meeting in Dubai, Wilfried.

1 0

Adequate contact information in the RIPE database must be enforced (was: NCC#2008090071 Unreachable Italian Host)
by Thor Kottelin 03 Sep '08

03 Sep '08

Anonymized extracts from a correspondence between a phish takedown operator and the RIPE NCC: PIRT: "There's a phish on 192.0.2.227. The server is rooted. The address a(a)a.example.net in the IP whois comes back 'host not found'. The ASN address we have, b(a)b.example.net, comes back 'connect timeout'. c(a)c.example.net comes back 'Address rejected'. The webform on the allocee's website (such as it is) doesn't actually do anything.--RIPE can you contact the IP owner and get them to update your database please." RIPE NCC: "Please try contact the Network owners/maintainers. Phone number registered for the maintainer is correct and working." PIRT: "I'm a volunteer and don't have the resources to make international phone calls. Plus I don't speak Italian (I don't write Italian either but there are websites for translation, which is why email is preferable). Doesn't RIPE have the resources to do this? And isn't it in your interest to keep the database accurate? Otherwise what's the point? I have already emailed the d(a)d.example.net address. I have had no reply and the phish is still active." RIPE NCC: "There may be options we could pursue to check the validity of the contact data in the objects in the RIPE Database. Where we have a direct relationship with the owners of these objects we could request that they update this information. But we do not have a mandate from the RIPE community to allocate any resources to this activity." (End of correspondence extracts.) The issue of false or otherwise inadequate RIPE database entries has been discussed before in various RIPE working groups. It is bizarre that the problems nevertheless continue, year in and year out. Publishing sufficient and up-to-date contact information in the RIPE database should be an absolute prerequisite for holding any kind of RIR-allocated resource. Whenever a deficiency is discovered and reported, the RIPE NCC should efficiently and urgently contact the allocee, requiring a full and immediate correction. If one is not made, the resources should be deregistered. I realize that IP connectivity is not directly contingent on registration, but I also believe that allocees would still want to avoid having their resources bogonized. Should this pressure nevertheless prove insufficient, further sanctions, such as elevated fees, should be available. It is intolerable that important and urgent security-related communications repeatedly fail due to a lack of adequate contact information. -- Thor Kottelin CISM, CISSP fax +358 102 961 064 thor(a)anta.net, PGP 0x327B7345 http://www.anta.net/

4 3

RIPE Database legal documents
by Denis Walker 28 Jul '08

28 Jul '08

Apologies for duplicates] Dear Colleagues, The RIPE Data Protection Task Force (DP TF), working with the RIPE NCC and the company lawyers, has finalised a set of legal documents for the RIPE Database. These documents are: - RIPE Database Terms and Conditions - RIPE Database Acceptable Use Policy - Procedure for the Removal of Personal Contact Details from the RIPE Database They can be seen on the RIPE DP TF web page at this address: http://www.ripe.net/ripe/tf/dp/index.html The documents have been subjected to a final review by the DP TF but they are not yet legally effective. They are now available for review and comments by the wider community. Please let us know if you have any considerations or issues. Please bear in mind that with any documents such as these, the wording can always be changed. However, we would prefer not to make any subjective changes at this stage but only amend anything that is inaccurate. The documents will become legally effective from 1 September 2008 and they will then be available on a new Legal Documents page on the RIPE NCC website. Regards, Denis Walker (on behalf of the RIPE DP TF)

2 1

Subject: White Pages Implementation
by Denis Walker 24 Jul '08

24 Jul '08

[Apologies for duplicates] Dear Colleagues, The RIPE NCC Database Group has now implemented the White Pages functionality discussed in the Database Working Group session at RIPE 56. For those not familiar with the discussions surrounding White Pages, please refer to the document outlining all the details of the implementation in the RIPE Database Document Library: http://www.ripe.net/db/docs.html This document also explains how to have yourself listed in the White Pages. We plan to re-start a clean-up project to remove unreferenced PERSON objects early in September. This will start to delete objects from the database late in September. Anyone who wishes to be listed in the White Pages to avoid deletion should submit an application as soon as possible. Regards Denis Walker Business Analyst RIPE NCC Database Group

1 0

Re: [db-wg] Notification message change
by Thor Kottelin 19 Jun '08

19 Jun '08

> Date: Wed, 18 Jun 2008 17:04:16 +0200 > From: Denis Walker <denis(a)ripe.net> > To: Database WG <db-wg(a)ripe.net>, > ncc-services-wg <ncc-services-wg(a)ripe.net> > With most updates to the RIPE Database, notification messages are sent > out. Many of these notifications are hitting users' ticketing > systems or arriving in mailboxes with auto-responders. The "Reply-to:" > address in these notifications was <ripe-dbm(a)ripe.net>. Our help desk > ticketing system was receiving hundreds of e-mails a month from these > auto-responders. This was causing a serious operational > problem for our > Customer Services Department. > > To solve this problem, we have changed the e-mail header in the > notification messages we send out. They now have the "From:" and > "Reply-to:" addresses set to <unread(a)ripe.net>. As the name suggests, > any replies to this address are not read by anyone and they are just > dropped from our mail system. Hello Denis, The local-part "unread" gives such a suggestion--at most--in English, and not because of any standard or other convention. The "Reply-To:" line, on the other hand, unequivocally (RFC 2822) states that replies are expected at the address it shows. As you probably know, localized mail clients often use it to display something along the lines of "your replies are invited to". While you are to thank for the heads-up, I would have expected RIPE NCC, of all organizations, to come up with a more stylish and exemplary solution to the problem. Also, assuming that "hundreds" stands for e.g. nine hundred, that would mean 900 / 30 = approximately 30 surplus messages per day. Does such a volume really cause serious operational issues on a departmental level? Some of us (tinu) receive hundreds of spurious messages every *day* into (or intended for) *personal* mailboxes, and are easily able to handle that noise, perhaps with a little help from filtering software. With regards, -- Thor Kottelin CISM, CISSP fax +358 102 961 064 thor(a)anta.net, PGP 0x327B7345 http://www.anta.net/

2 1

Notification message change
by Denis Walker 18 Jun '08

18 Jun '08

[Apologies for duplicates] Dear Colleagues, With most updates to the RIPE Database, notification messages are sent out. Many of these notifications are hitting users' ticketing systems or arriving in mailboxes with auto-responders. The "Reply-to:" address in these notifications was <ripe-dbm(a)ripe.net>. Our help desk ticketing system was receiving hundreds of e-mails a month from these auto-responders. This was causing a serious operational problem for our Customer Services Department. To solve this problem, we have changed the e-mail header in the notification messages we send out. They now have the "From:" and "Reply-to:" addresses set to <unread(a)ripe.net>. As the name suggests, any replies to this address are not read by anyone and they are just dropped from our mail system. We have also made a small change to the introductory text to make it clear that these e-mails are auto-generated. We also clearly show users the e-mail reply address to use if they have an issue with the notification. This change was implemented today. It should not affect any users unless they parse the mail headers or the introductory text in the notification. Examples of the old and new notification messages are shown below. Regards, Denis Walker Business Analyst RIPE NCC Database Group Old notification message ____________________________________________________ To: user(a)somewhere.com From: RIPE Database Notifications <bitbucket(a)ripe.net> Subject: Notification of RIPE Database changes Reply-To: ripe-dbm(a)ripe.net Precedence: bulk Auto-Submitted: auto-generated Dear Colleague, This is to notify you that some object(s) in RIPE database which you either maintain or are listed as to-be-notified have been added, deleted or changed. The update causing these changes had the following mail headers: > From: user(a)somewhereelse.com > Subject: > Date: Tue, 17 Jun 2008 00:00:18 +0200 (CEST) > Reply-To: user(a)somewhereelse.com > MsgId: <2008061622> For assistance or clarification please contact: RIPE Database Administration <ripe-dbm(a)ripe.net> New notification message ____________________________________________________ To: user(a)somewhere.com From: RIPE Database Notifications <unread(a)ripe.net> Subject: Notification of RIPE Database changes Reply-To: unread(a)ripe.net Precedence: bulk Auto-Submitted: auto-generated Dear Colleague, This is to notify you that some object(s) in RIPE database which you either maintain or are listed as to-be-notified have been added, deleted or changed. This message is auto-generated. Please DO NOT reply to this message. If you do not understand why we sent you this message, or for assistance or clarification please contact: RIPE Database Administration <ripe-dbm(a)ripe.net> The update causing these changes had the following mail headers: > From: user(a)somewhereelse.com > Subject: > Date: Tue, 17 Jun 2008 00:00:18 +0200 (CEST) > Reply-To: user(a)somewhereelse.com > MsgId: <2008061622>

1 0

ANNOUNCEMENT: RIPE NCC Training Courses
by Training 26 May '08

26 May '08

[Apologies for duplicate e-mails] Dear Colleagues, The RIPE NCC invites you to register for one of our upcoming training courses: - The LIR Training Course This course teaches LIRs how to request Internet number resources and interact with the RIPE NCC. A course outline is available at: http://www.ripe.net/training/lir/outline.html - The Routing Registry Training Course This course teaches LIRs how to use the RIPE Database for routing. A course outline is available at: http://www.ripe.net/training/rr/outline.html - The DNS for LIRs Training Course This course teaches LIRs about the RIPE NCC's DNS-related services. A course outline is available at: http://www.ripe.net/training/dns/outline.html To see the location of upcoming courses and to register, please use the LIR Portal or complete the registration form on our website at: http://www.ripe.net/cgi-bin/trainingform.pl.cgi If you have any questions please do not hesitate to contact us at <training(a)ripe.net>. Kind regards, Rumy Kanis Training Services Manager RIPE NCC

1 0

RIPE56 DB-WG Draft Agenda V2
by Wilfried Woeber, UniVie/ACOnet 05 May '08

05 May '08

Dear DB-WG folks, Chairpersons, "Meeting"! This is the 2ndt draft of an agenda for the DB-WG at RIPE56 in Berlin, May 2008. For time slot allocations please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-56/meeting-plan.html Attention please: this time the DB-WG meeting is scheduled for *Thursday* at 4 PM in the afternoon! Please note that, for our convenience, the time slot map has become 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 55 . review of action list B. Data Base Update (Jos I. B., RIPE NCC) [~40 min] . Actions from previous meetins . DB Terms & Conditions . modification proposals (maintainer required, ...) . retiring rev-srv: attribute C. Follow-Up on [~20 min] . Task-Force on Data Protection Issues [t.b.c.] . Contact Data Quality/Requirements Discussion [t.b.c.] . Resource Certification Project [t.b.c.] D. High Avalability SW Update for IRR (Yasuhiro Shirasaki, NTT) . using ripe-whois and our experimental syncronization trial Y. Input from other WGs and TFs Z. AOB ________________________________________________________________________

1 0

RIPE56 DB-WG Draft Agenda V1
by Wilfried Woeber, UniVie/ACOnet 29 Apr '08

29 Apr '08

Dear DB-WG folks, Chairpersons, "Meeting"! This is the (very rough) 1st draft of an agenda for the DB-WG at RIPE56 in Berlin, May 2008. For time slot allocations please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-56/meeting-plan.html Attention please: this time the DB-WG meeting is scheduled for *Thursday* at 4 PM in the afternoon! 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 55 . review of action list B. Data Base Update (N.N., RIPE NCC) [~20 min] C. Follow-Up on [~30 min] . Task-Force on Data Protection Issues [t.b.c.] . DB-Terms and Conditions [t.b.c.] . Contact Data Quality/Requirements Discussion [t.b.c.] . Resource Certification Project [t.b.c.] D. DB-Software Developmen Activities [~20 min] . modification proposals (maintainer required, ...) . retiring rev-srv: attribute Y. Input from other WGs and TFs Z. AOB ________________________________________________________________________

1 0

A request for more information about "person" objects
by Searcher Wang 25 Apr '08

25 Apr '08

Dear DatabaseMaster: Thank you for reading my letter. I am a Ph.D student in Computer Science. Recently, I am working on how to validate the origins of BGP routes with the information exploited from RIRs. As well-known, the database of RIPE is famous for its accuracy. Thanks for the public access services of ripe database, I have built a prototype. However, some information of "person" objects that can be got from ftp://www.ripe.net has been taken out. I think you are trying to prevent spam. I do not intend to get the personal information of the person objects such as email, address and so on, but the relations among them are important for me. What I really want is the person objects' admin-c, tech-c, mnt-by attributes. I have done many experiments, in which there is a high false positive rate with my prototype. It seems that it is difficult to bypass this barrier. So I beg for your help to get more information about person objects. Could you please tell me how to get the entire information? Thanks for your reading again. Best Wishes! Sincerely Xiaoqiang <db-wg(a)ripe.net>

1 0

Outage report for mail updates to the RIPE Database
by Katie Petrusha 18 Apr '08

18 Apr '08

[ Apologies for duplicate mails ] Dear colleagues, From approximately 14:15 (UTC) on Thursday, 17 April 2008 to 09:00 (UTC) on Friday, 18 April 2008, some e-mail update messages to the RIPE Database service, <auto-dbm(a)ripe.net>, were not processed due to a problem with our system. All the messages received by <auto-dbm(a)ripe.net> were stored on our mail server and the problem has now been resolved. All the saved update messages are currently being processed. If you sent an e-mail update to the RIPE Database service during this period, you will receive an acknowledgement message shortly. There is no need to re-send any update messages. We apologise for any inconvenience that this may have caused. Regards, Katie Petrusha Senior Software Engineer RIPE NCC

1 0

Call for agenda items, DB-WG Meeting during RIPE56, Berlin, DE
by Wilfried Woeber, UniVie/ACOnet 16 Apr '08

16 Apr '08

Dear DB-WG folks, planning activities for the next RIPE Meeting - RIPE56 in Berlin - 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 in about one week from now.) Please note that the DataBase-WG meeting is, this time, scheduled for *Thursday* afternoon. The overall RIPE 56 meeting outline is already available at http://www.ripe.net/ripe/meetings/ripe-56/meeting-plan.html The list of plenary presentations and the session archive may eventually become available at [- this page does not exist yet -] http://www.ripe.net/ripe/meetings/ripe-56/presentations/ or a different URL. See you soon in Berlin, Wilfried.

1 0

Announcement: Maintenance on 12-13 April 2008
by James Aldridge 09 Apr '08

09 Apr '08

[Apologies for duplicates] Dear Colleagues, The RIPE NCC will migrate a number of servers to new racks at NIKHEF between 08:00 and 18:00 (UTC) on the following dates: - Saturday, 12 April 2008 - Sunday, 13 April 2008 Aspects of the following services will be affected at various times during the migration periods: - BGP peering sessions will be down - nikrtr.ripe.net - AS3333 (217.79.172.5; 195.69.144.69; 2001:7f8:1::a500:3333:1) - K-Root (AS25152) at AMS-IX, NL-IX and XPE - AS112 (AS112) at AMS-IX - RIS (AS12654) at AMS-IX, NL-IX and GN-IX - DNS services: - The AMS-IX/XPE/NL-IX K-Root instance and the AS112 server at AMS-IX will be unavailable - WWW/FTP/Hostcount/E-Learning - LIR-Portal - WHOIS: - Syncupdates of the RIPE Database will be down - Mail updates will be queued and executed after the maintenance - RIPE DB-related CGIs on WWW will be down - Test Traffic Measurements (tt01) We apologise for any inconvenience that this may cause. If you have any questions about this, please send an e-mail to <ops(a)ripe.net> Regards, James Aldridge Senior Systems Engineer, RIPE NCC

1 0

RIPE Database (IPV6) outage on 2 April 2008
by RIPE Database Administration 31 Mar '08

31 Mar '08

[Apologies for duplicate messages] Dear Colleagues, On Wednesday, 2 April 2008, querying the RIPE Database via IPv6 will not be possible from 10:00-13:00 (UTC) due to maintenance. During this period, the RIPE Database will be accessible via IPv4 as usual. We apologise for any inconvenience this may cause. If you have any questions or concerns about this, please send an e-mail to <ripe-dbm(a)ripe.net> Regards, Katie Petrusha RIPE Database Administration RIPE NCC

1 0

Near Real Time Mirror access now available
by RIPE Database Manager 21 Feb '08

21 Feb '08

[Apologies for duplicate e-mails] Dear Colleagues, We are happy to announce that it is now possible to request Near Real Time Mirroring (NRTM) access to the RIPE Database. NRTM is a mechanism that allows any authorised client to receive a stream of data modifications from the RIPE Database in near real time. For technical details, please consult: http://ripe.net/db/support/mirroring-RIPE-database.pdf To gain NRTM access, you will have to sign an agreement for bulk access. This agreement is available at: http://ripe.net/db/support/agreement-for-db.pdf To request NRTM access, please contact <ripe-dbm(a)ripe.net>. If you have any questions or concerns, please send an e-mail to <ripe-dbm(a)ripe.net>. Kind regards, Agoston Horvath Database Group, RIPE NCC

1 0

ANNOUNCEMENT: RIPE NCC Training Courses.
by RIPE NCC Training Services 21 Feb '08

21 Feb '08

[Apologies for duplicate e-mails] Dear Colleagues, The RIPE NCC invites you to register for one of our upcoming training courses: - The LIR Training Course This course teaches LIRs how to request Internet number resources and interact with the RIPE NCC. A course outline is available at: http://www.ripe.net/training/lir/outline.html - The Routing Registry Training Course This course teaches LIRs how to use the RIPE Database for routing. A course outline is available at: http://www.ripe.net/training/rr/outline.html - The DNS for LIRs Training Course This course teaches LIRs about the RIPE NCC's DNS-related services. A course outline is available at: http://www.ripe.net/training/dns/outline.html To see the location of upcoming courses and to register, please use the LIR Portal or complete the registration form on our website at: http://www.ripe.net/cgi-bin/trainingform.pl.cgi If you have any questions please do not hesitate to contact us at <training(a)ripe.net>. Kind regards, Rumy Kanis Training Services Manager RIPE NCC

1 0

Re: NCC#2007121786 Customer number 106400
by RIPE NCC Billing Department 19 Feb '08

19 Feb '08

Dear Elena, We have updated the billing address and will resend the invoice there. However, you need to update the postal address of the registry via the LIR Portal (https://lirportal.ripe.net). -- Regards, Rabia Gawish RIPE NCC On Fri, 14 Dec 2007 11:09:51 +0300, Khortseva Elena wrote: > Dear All, > I would like to inform you about change registered address. > Registered address is > > Suite A > The Chambers > 5A The Square > Petersfield > Hampshire > GU32 3HJ U.K. > > Can you please re invoice the following invoice? > > #I0805322 dated 4/12/2007 > > I make apologize for late informing. > > > Best regards, > > Khortseva Elena > Manager,ReTN Ltd. > phone: +7 (495) 740-48-40 > fax: +7 (495) 740-48-41 > e-mail: khortseva(a)retn.net

2 2

Important change to RIPE NCC services
by RIPE Database Manager 03 Jan '08

03 Jan '08

[Apologies for duplicate e-mails] Dear Colleagues, On Wednesday, 27 February 2008, between 17:00 and 19:00 (UTC), RIPE NCC staff will replace the web server www.ripe.net. This change means there are some possible issues that you need to be aware of. The IP address of www.ripe.net will change on Wednesday, 27 February. If you have any software that connects to this website, you should ensure that the IP address is not hard coded. The change will also result in a new URL for the syncupdates service. Most of the client software that uses syncupdates should be able to handle HTTP redirects, return code 301. If your software does this, then it will continue to work, though it is still advisable that you configure your software to use the new URL. If your software cannot handle HTTP redirects, you will need to update the URL in your software before Wednesday, February 27, to continue using this service. We would also advise that you fully implement HTTP handling in your software to avoid any future problems. The current syncupdates URLs are: http://www.ripe.net/syncupdates http://www.ripe.net/syncupdates-test These will change to: http://syncupdates.db.ripe.net http://syncupdates-test.db.ripe.net There will be a period between Wednesday, 13 February, and Wednesday, 27 February, when both the new and old syncupdates URLs will be available. We apologise for any inconvenience this may cause. If you have any questions or concerns about this, please send an e-mail to <ripe-dbm(a)ripe.net>. Regards, Agoston Horvath Software Engineer, RIPE NCC

1 0

ripe whois server on freebsd
by Matkhamtkha Brekher 03 Jan '08

03 Jan '08

my compilation of ripe whois server 3.3.0 has failed on freebsd 7.0-beta4 gmake[3]: Entering directory `/usr/home/ono/Desktop/whoisserver-latest/src/defs' mkdir -p /usr/home/ono/Desktop/whoisserver-latest/src/modules/rpsl && \ cd /usr/home/ono/Desktop/whoisserver-latest/src/modules/rpsl && \ RIPINCDIR="/usr/home/ono/Desktop/whoisserver-latest/src/include/" RIPLIBDIR="/usr/home/ono/Desktop/whoisserver-latest/src/" CC="gcc -DHAVE_CONFIG_H -I/usr/local/bind/include -L/usr/local/bind/lib -I/usr/include/openssl -I/usr/local/include/openssl" CFLAGS="-I/usr/home/ono/Desktop/whoisserver-latest/src/defs -I/usr/home/ono/Desktop/whoisserver-latest/src/defs -I/usr/local/bind/include -L/usr/local/bind/lib -I/usr/include/openssl -I/usr/local/include/openssl -D_REENTRANT -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/home/ono/Desktop/whoisserver-latest/src/include/" gmake -f /usr/home/ono/Desktop/whoisserver-latest/src/defs/Makefile.syntax && \ touch syntax gmake[4]: Entering directory `/usr/home/ono/Desktop/whoisserver-latest/src/modules/rpsl' gmake[4]: Nothing to be done for `all'. gmake[4]: Leaving directory `/usr/home/ono/Desktop/whoisserver-latest/src/modules/rpsl' gmake[3]: Leaving directory `/usr/home/ono/Desktop/whoisserver-latest/src/defs' gmake[3]: Entering directory `/usr/home/ono/Desktop/whoisserver-latest/src' if gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_REENTRANT -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/mysql -fno-strict-aliasing -pipe -march=athlon-mp -I/usr/local/include -I/usr/local/include/libxml2 -I/usr/local/bind/include -L/usr/local/bind/lib -I/usr/include/openssl -I/usr/local/include/openssl -I/usr/local/include/c-client/ -I/usr/home/ono/Desktop/whoisserver-latest/src/modules/rpsl -I/usr/home/ono/Desktop/whoisserver-latest/src/include -I/usr/home/ono/Desktop/whoisserver-latest/src/include -I/usr/local/bind/include -L/usr/local/bind/lib -I/usr/include/openssl -I/usr/local/include/openssl -MT crypt-md5.o -MD -MP -MF ".deps/crypt-md5.Tpo" -c -o crypt-md5.o `test -f 'modules/au/crypt-md5.c' || echo './'`modules/au/crypt-md5.c; \ then mv -f ".deps/crypt-md5.Tpo" ".deps/crypt-md5.Po"; else rm -f ".deps/crypt-md5.Tpo"; exit 1; fi modules/au/crypt-md5.c: In function 'crypt_md5': modules/au/crypt-md5.c:28: error: 'MD5_CTX' undeclared (first use in this function) modules/au/crypt-md5.c:28: error: (Each undeclared identifier is reported only once modules/au/crypt-md5.c:28: error: for each function it appears in.) modules/au/crypt-md5.c:28: error: expected ';' before 'ctx' modules/au/crypt-md5.c:56: error: 'ctx' undeclared (first use in this function) modules/au/crypt-md5.c:68: error: 'ctx1' undeclared (first use in this function) gmake[3]: *** [crypt-md5.o] Error 1 gmake[3]: Leaving directory `/usr/home/ono/Desktop/whoisserver-latest/src' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/home/ono/Desktop/whoisserver-latest/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/home/ono/Desktop/whoisserver-latest' gmake: *** [all] Error 2 any suggestions? P.S. [~/Desktop/whoisserver-latest]$ gcc -v Using built-in specs. Target: i386-undermydesk-freebsd Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 4.2.1 20070719 [FreeBSD]

1 0

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