August 1998 - db-wg - mailman.ripe.net

<auto-dbm@ripe.net> is slow this afternoon.
by RIPE Database Administration 16 May '18

16 May '18

Dear Colleagues, Because of a very high level of use this afternoon, the response time of <auto-dbm(a)ripe.net> is longer than normal. I have made contact with those who are responsible and I expect the situation to improve as the machine works through the queue. Please be patient. Obviously we at the RIPE NCC Database Group are continuously working to make the performance of the database as good as possible. However, we cannot make improvements in zero time. We thank you for your co-operation up to now and we ask for your continued co-operation so that everyone receives the best possible service. If you have anymore questions, please contact <ripe-dbm(a)ripe.net>. Regards, Ambrose Magee ____________________________ RIPE Database Administration.

2 2

1. draft, proposed agenda for DB-WG Mtg @ Edinburgh
by Wilfried Woeber, UniVie/ACOnet 27 Aug '98

27 Aug '98

Attached plese find the 1st draft of the proposed agenda for the DB-WG meeting during RIPE#31 in Edinburgh. As always, comments and suggestions more than welcome! In particular, please get in touch with me asap in case you want to get a slot for a presentation! Looking forward to see many of you in Edinburgh! Wilfried. -------------------------------------------------------------------------- Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Vienna University : Fax: +43 1 4277 - 9 140 Universitaetsstrasse 7 : RIPE-DB (&NIC) Handle: WW144 A-1010 Vienna, Austria, Europe : PGP public key ID 0xF0ACB369 -------------------------------------------------------------------------- Proposed Agenda for the Database Working Group Meeting RIPE-31, September 1998, Edinburgh 1. Draft, August 27, 1998 A. Administrative stuff (Wilfried Woeber, chair, 5min) - appointment of scribe - agenda bashing B. RIPE DB, operational update (RIPE NCC) - statitics, performance, changes - most recent mod.s: cross-notification handling of changed: referral - RPSL status, usage - mirror systems at other registries' sites C. RIPE DB, software development status (RIPE NCC) - done, being worked on, in the queue D. DB SW Re-implementation (RIPE NCC) - status, milestones/roadmap, resources required/available E. I-D draft-zsako-ripe-dbsec-pgp-authent-00 (Janos ? [Joao]) F. PGP deployment in the RIPE DB (RIPE NCC) - licenses, support G. ripe-157++ - who, how & when H. I-D draft-ietf-rps-auth-01, -rps-dist-?? (Cengiz ?) - RIPE region requirements/comments X. Chicago IETF report(s) ? Y. Input from other WGs - t.b.d. Z. AOB WW, 28-AUG-1998 00:19:01

1 0

New beta version of the RIPE DB
by Joao Luis Silva Damas 21 Aug '98

21 Aug '98

Dear all, we are happy to announce a new beta version of the RIPE DB. The major change in this release is the introduction of support for an additional authentication method, which in this case uses PGP. The previous authentication methods were NONE, MAIL-FROM and CRYPTPW. The new method is called PGPKEY and is described in draft-zsako-ripe-dbsec-pgp-authent-00.txt internet-draft (available at the usual places, eg. ftp.ripe.net). This draft reflects the work done by the RIPE Database Security Task Force up to this moment. The code is not available for download at this moment. There is a setup so users can experiment with it. * Queries can be done using a whois client pointed to the beta database at beta-whois.ripe.net port 43. * Updates can be sent to auto-beta(a)ripe.net The current setup contains only maintainer objects (a copy of the real ones as of yesterday) which are necessary to experiment. The draft is not yet fully implemented in this beta release (some checks are not done) but it allows operational experience. The code is beta quality and may have bugs. If you find any, please report them to ripe-dbm(a)ripe.net. The messages will however not be answered as fast as normal ripe-dbm. We will issue a new beta release soon and a final release is planned before RIPE31. Details about licensing PGP (free) for use with the RIPE Database will also be made public soon. If you have any questions, don't hesitate to ask. Happy testing, Joao Damas RIPE NCC

1 0

IRRd source code release
by Gerald Andrew Winters 17 Aug '98

17 Aug '98

For those who are interested we are announcing our first IRRd source code release which can be found at the following location: http://www.merit.edu/radb/irrd We will be updating the source code periodically with bug fixes, feature enhancements, etc... Each new IRRd release will be tagged with the version number to distinguish it from prior releases. The current code release is version 1.0. We wish to thank those people who have already begun to test IRRd and we continue to solicit users who feel they might be interested in the IRRd software package. -- IRRd Development Team <irrd-support(a)merit.edu>

1 0

"Changed:" field
by Andrey Petukhov 17 Aug '98

17 Aug '98

Dear Colleagues, I'd like to propose new behavior of the "Changed:" field of the database objects. It would be more convenient if database (or its front-end robot, processing requests from mail messages) sets value of the "changed:" field itself using "From:" field of the mail header/envelope. Database could contain "changed:" information in three modes depending of user needs: 1. Only one record, reflecting last change. 2. Two records, reflecting event of the creation of the object and "last changed" event. 3. Full history of the changes. The first record means "created", and next records reflect every change, sorted by date. The mode of the "Changed:" field can be described in the "mntner" object and is applied to all objects controlled by this mntner. The default behavior of this field applied to objects without mntner. In all cases the field(s) "changed:" have form "Changed: <e-address> <date>", as it is now, but <e-address> is retrieved from mail header/envelope with appropriate authorization checks (it is being done now), <date> is current date of the modification. There is no need to store changes itselves, that is subsequent versions of the object are not stored. Best Regards, -- Andrey Petukhov (AP9-RIPE) Phone: +7 095 705 9229 Systems Engineer Fax: +7 095 929 9363 Global One Russia (RoSprint) Mailto:pooh@ipnms.rosprint.net

1 0

Performance of the RIPE Database
by RIPE Database Administration 17 Aug '98

17 Aug '98

Dear Colleagues, There is normally a delay of 10 minutes between an update being processed and it being visible using the whois service. We are aware that this delay has increased and we are taking action now to maintain the delay at normal levels. If you have any questions, please contact <ripe-dbm(a)ripe.net>. Regards, Ambrose Magee ____________________________ RIPE Database Administration.

1 0

Performance of the RIPE Database.
by RIPE Database Administration 10 Aug '98

10 Aug '98

Dear Colleagues, There is a time-delay between when an object is processed by <auto-dbm(a)ripe.net> and when it is visible through the whois service. This delay is normally 10 minutes. This delay became very long recently, but no updates were lost. If you received an acknowledgement mail, which said that your update was successful, then your update was indeed successful. No updates were lost. The problem is fixed now. If you continue to have problems, please contact <ripe-dbm(a)ripe.net> with details of the problem. If you have anymore questions, please contact <ripe-dbm(a)ripe.net>. Regards, Ambrose Magee ____________________________ RIPE Database Administration.

1 0

Announce: IRRd-1.0 Beta Release
by Gerald Winters 07 Aug '98

07 Aug '98

IRRd-1.0 Beta Release --------------------- Merit Network is pleased to announce the 1.0 Beta release of the Internet Routing Registry Daemon (IRRd): http://www.merit.edu/radb/ IRRd is designed as a stand-alone routing registry server. IRRd handles RIPE-181 and RPSL whois and RAToolSet queries, as well as database management tasks, including mirroring and object submission. Future versions will support object authentication and notification. The IRRd server features a Cisco Systems-like management and configuration interface. The IRRd architecture was designed to address performance problems with the original RAWhoisd and RADB databases. The current IRRd version supports router configurations up to 600% faster than previously. The IRRd server also supports indexing to disk and memory, handles both the RIPE-181 and RPSL databases, determines database syntax dynamically, and indexes the entire IRR in about a minute. Although this is a beta release, the software is currently in production use as the main RABD (whois.ra.net) server. The current beta release only includes binaries. A complete source code release is planned at the end of the beta trial (anticipated mid September 1998). IRRd is freely available and may be redistributed so long as the University of Michigan copyright is preserved. Development of the RPSL portions of IRRd were supported by the National Science Foundation (NCR-9321060). All other sections were supported by Merit Network, Inc. The ongoing IRRd efforts include significant efforts by a number of Beta testers, including Kevin Oberman (ESnet), Mark Prior (connect.com.au pty ltd), John Heasley (Verio), George Matey (Bay Networks), WeeSan Lee (USC/ISI), and Pierre Thibaudeau (Teleglobe). Many thanks for your suggestions and support! A mailing list, irrd-discuss(a)merit.edu, has been created for IRRd users to share experiences and advice. Subscribe by sending mail to irrd-discuss-request(a)merit.edu. -- IRRd Development Team <irrd-support(a)merit.edu> Gerald Winters Craig Labovitz Tom Spindler Jake Khuon Susan R. Harris

1 0

SUCCEEDED: Person: Wilfried Hauf (fwd)
by Hostmaster Schlund+Partner GmbH & Co. 07 Aug '98

07 Aug '98

Hello Hostmaster, as you can see, this Handle has been created at 8:32 today, which is 10:32 local time. Now, THREE hours after, ...: admin hostmast ~%date; wripe WH724-RIPE Fri Aug 7 13:23:43 CEST 1998 [sequoia.ripe.net] % Rights restricted by copyright. See http://www.ripe.net/db/dbcopyright.html % No entries found for the selected source(s). % % If you would like to search on arbitrary strings, % please see the Database page on the RIPE NCC % web-site at http://www.ripe.net/db/ % This will only work for RIPE data. This is not a single case, all our handles aren't available hours(!) after the succeeded mail has arrived. The 10 Minutes stated in the return messages would be okay, but we can't afford to have one day between handle registration and domain registration. I consider this a serious problem. Can you tell me if this is going to be fixed soon? Kind regards, Eric Schaetzlein Schlund + Partner GmbH & Co. Erbprinzenstr. 1 Tel. +49-721-91374-50 76133 Karlsruhe, Germany Fax +49-721-91374-20 http://www.schlund.de hostmaster(a)schlund.de ----- Forwarded message from RIPE Database Management <ripe-dbm(a)ripe.net> ----- Date: 7 Aug 1998 08:32:13 -0000 To: hostmaster(a)schlund.de From: RIPE Database Management <ripe-dbm(a)ripe.net> Subject: SUCCEEDED: Person: Wilfried Hauf Reply-To: ripe-dbm(a)ripe.net Your update was SUCCESSFUL, but it can take 10 minutes before your update is visible using a whois look-up. > From: hostmaster(a)schlund.de > Subject: Person: Wilfried Hauf > Date: Fri, 7 Aug 1998 10:19:22 +0200 > Msg-Id: <E0z4hkA-00040w-00(a)admin.schlund.de> The following objects were processed. New OK: [person] WH724-RIPE (Wilfried Hauf) ----- End forwarded message -----

1 0