- db-wg - mailman.ripe.net

RIPE Database main server up and running again
by RIPE Database Administration 28 Mar '00

28 Mar '00

Dear All, Thank you for your patience. The RIPE Database main server is now up and running again. The queue of updates is being processed, but please take into account that it will take several hours to clear the queue. Technical details: The failure of one of the memory modules of the server caused a parity error, thus forcing the kernel to panic. The memory module had to be replaced and tested. We are very sorry for the inconvenience caused. If you have any questions or comments, please don't hesitate to contact <ripe-dbm(a)ripe.net>. Regards, Daniele Arena ____________________________ RIPE Database Administration.

1 0

Whois service running on a backup server
by RIPE Database Administration 28 Mar '00

28 Mar '00

Dear Colleagues, Unfortunately this morning the main RIPE Whois server experienced a hardware crash. We switched the service to a backup server; thus you may find that the response time for whois queries is longer than usual. The updates are currently not being processed, but they are queued; they will be processed as soon as the main server is up and running again. There is no need to resend your updates. We are currently working to repair the hardware damage on the main server, and we hope to return to the normal situation as soon as possible. Please accept our apologies for this inconvenience. If you have any questions, please don't hesitate to contact <ripe-dbm(a)ripe.net>. Regards, Daniele Arena ____________________________ RIPE Database Administration. P.S.: Apologies if you receive this mail more than once.

1 0

New DB release 2.3.1
by RIPE Database Administration 21 Mar '00

21 Mar '00

Dear colleagues, We have made available the new release of RIPE Perl database software at our fto site. You can find it at ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-2.3.2.tar.gz Please find attached notes of the new release. Please note that CLIENTADDRESS type of referral can be used in our production server readily. Best regards, RIPE NCC DB Group ----------------- RELEASE NOTES for RIPE Database 2.3.2 This is mainly a bugfix release, without major new features added. There are also a few maintenance and performance-related changes, and an important security fix. SUPPORTED SYSTEMS This release has been tested with perl 5.00502 on BSDI3.1 and perl 5.00404 on Solaris 2.6 systems. Please let us know if you have problems running it on other systems. NEW FEATURES - New type of referral: CLIENTADDRESS o A fourth kind of referral is defined, CLIENTADDRESS (The other three were RIPE, INTERNIC and SIMPLE). o The IP address of the client is sent to the referred whois server, if the referral type is CLIENTADDRESS. o The IP address is sent using the -V flag. The version and the IP address will be separated by a comma (eg, -Vripe2.3.1,193.140.45.45). o No other flag will be forwarded to the referred whois server. o When the server gets such a request, it checks the IP number of the server which does the referral against a list of authorized whois servers. If it is not in the list, it will be rejected. The list is named AUTHORIZEDFORREFERRAL in the configuration. o Then, the IP address of the client is extracted from the -V flag string and it will be regarded as if it is the IP address of a directly querying whois client (ie, it is checked against the list of DENYWHOISACCESS list). MAINTENANCE RELATED CHANGES - Introduced some debugging functionality: WHOISDSTAT - creation of files describing the activity of whoisd query processes. Those are normally deleted if the whoisd exits the normal way. WHOISDSTAT is a base filename for those files. - Introduced some limitation on bad clients: QUERYLOOPLIMIT defines a limit for '-k' connections. If more than so many queries for the same search term are detected, QUERYLOOPTXT is printed and the connection is closed. Mainly meant to protect against ptraceroute parsing broken as-macros. SECURITY FIXES - On February 2, 2000, we got a report for a possible buffer overflow in whoisd. An extremely long and specific query, such as the following: % whois `perl -e '{print "0." x 20000}'`(a)joshua.ripe.net (query example from a Linux host; it does not work, of course, if the client has built-in query size limits) caused the forked server process to crash with a segmentation fault. We immediately introduced a patch on whoisd.pl, truncating the queries to 255 characters immediately after they were being read. BUG FIXES - cross-misc: now the sender of cross-notifications is set to HUMAILBOX. - whoisd.pl: o the text for DENIED connection was mistakenly printed on STDOUT. o The timeout handler would wait infinitely to print a msg about closing the connection. Now an alarm has been set up to stop it, the message can be printed to WHOISDSTAT file if active. PERFORMANCE FIXES - addkey: The overflow file handling has been modified, so that it would use a smaller amount of memory.

1 1

Top 100 Maintainers List 20000314
by RIPE Database Administration 14 Mar '00

14 Mar '00

1 0

Charter? Does anybody have a copy
by Nigel Titley 07 Mar '00

07 Mar '00

Gentlefolk, At the last RIPE conference I made the mistake of putting up my hand and offering Wilfried help in putting the paperwork of the DB WG in order. One of the first things I'd like to sort out is the group charter. Does anybody have a copy? It probably needs some work doing on it by now, but if we've got an old one, at least it will be a start. Thanks Nigel -- Tel: +44 171 864 4450 Fax: +44 171 864 4488 Well I'm disenchanted too. We're all disenchanted (James Thurber) (http://www.seanet.com/~thurber/disenchanted.gif)

3 4

RE: DB consistancy checking tools
by Matthew Robinson 07 Mar '00

07 Mar '00

I won't be at RIPE-35 as my first child is due at the same time but I'll definitely knock something together as a draft. If other people are interested then things should go ahead at RIPE-35 otherwise I do have permission from my wife to attend RIPE-36 ;-) Kind regards Matthew -----Original Message----- From: Wilfried Woeber, UniVie/ACOnet [mailto:woeber@cc.univie.ac.at] Sent: 20 January 2000 14:55 To: matthew(a)planet.net.uk Cc: lir-wg(a)ripe.net; db-wg(a)ripe.net; woeber(a)cc.univie.ac.at Subject: RE: DB consistancy checking tools Matthew, I think this is an interesting proposal: >I have been wondering recently whether a separate group should be set up for >the sole purpose of creating tools/advise/methods/hints 'n' tips for LIR's >to keep on top of their entries and make management easier. A sort of RIPE >users working group not concerned with designing objects for the database >but how to put existing objects in it, remove them, manage them, etc. > >My 2c > >Matthew To start things moving, could you come up with a coarse draft of ideas and short-term goals to take up? On the more formal side, one of the possible solutions to accomodate that activity might be to create a TaskForce to work on well-defined items during RIPE35 (do you intend to particpate?). This TF might be supported by both LIR and DB, or sponsored by whichever group is seen to be appropriate... Wilfried.

6 6

Re: DB consistancy checking tools
by mediaWays Hostmaster 06 Mar '00

06 Mar '00

Hi, we do whois -h whois.ripe.net -r -m <our Allocation/16> | grep inetnum | sed "s/inetnum: //" | sed "s/ - /./" > <some file> for our Allocations once a month and analyse this with awk script #!/usr/bin/sh nawk -F. 'BEGIN{summe=0} NF==8 { for(i=1; i<=NF; i++) byte[i]=$i; if(byte[3]!=byte[7]) { size=(byte[7]-byte[3])*256; if(byte[4]>byte[8]) size-=byte[8]-byte[4]; else size+=byte[8]+byte[4]; size++; } else { size=byte[8]-byte[4]+1; } summe+=size; printf("%s: %d IPs\n", $0, size); } END{printf("Summe %ld\n", summe);}' < <some file> so we could calculate the #IPs, check overlappings, check our own IP-DB against it ... and so on. We hope that this querys do not bother the RIPE-DB ;-) Kind Regards, _____________________________ Stephan Mankopf +49 5241 80 88729 stephan.mankopf(a)mediaways.net

1 0

Attn. NRTM clients: Missing serial files(2)
by RIPE Database Manager 01 Mar '00

01 Mar '00

Dear Colleagues, The message that was sent to you concerning the missing serial files contains an unfortunate misprint: the number of missing serial files is 605, not 30605 as was reported. The missing range is 8929802-8930406. Again, sorry for trouble and inconvenience. If you have any further questions, please do not hesitate to contact <ripe-dbm(a)ripe.net> Regards, Andrei Robachevsky ____________________________ RIPE Database Administration.

1 0

Attn. NRTM clients: Missing serial files
by RIPE Database Manager 29 Feb '00

29 Feb '00

Dear Colleagues, Due to a filesystem problem, 30605 serial files were not written. The missing range is 8929802-8930406. Unfortunately to continue near real-time mirroring of the RIPE database, you will need to resync with the RIPE database. The new snapshot of the database will be available tonight (at 1 a.m. CET, 1 March). This problem does not affect the queries and the RIPE databse consistency. Sorry for trouble and inconvenience. If you have any further questions, please do not hesitate to contact <ripe-dbm(a)ripe.net> Regards, Andrei Robachevsky ____________________________ RIPE Database Administration.

1 0

inetnum conversion
by Engin Gunduz 28 Feb '00

28 Feb '00

Dear colleagues, RIPE NCC will be converting the legacy inetnum objects which are in old classful notation into classless range notation. We provide the list of inetnum objects to be converted during this process at: http://www.ripe.net/ripencc/pub-services/db/in_conversion/ There are 16404 such inetnums in the RIPE whois database, so we have divided them in four parts, but the list is available also as a big single file. The list contains the classful notation, new classless notation and the netname of the inetnums. The conversion is planned to take place on 26-27 February. You can check the list for your inetnum objects. If you detect a problem, please contact <ripe-dbm(a)ripe.net>. Also, please send your comments about the conversion to the list, Regards, Engin Gunduz RIPE NCC Database Group -----------------------

1 2

Re: RIPE DB service restored
by Janos Zsako 23 Feb '00

23 Feb '00

> From owner-lir-wg(a)ripe.net Wed Feb 23 13:47:01 2000 > From: Nils Jeppe <nils(a)work.de> Dear Nils, > Yes, one question; why haven't you announced taking down the DB? I find > this unacceptable, some of us have to work with it you know? We have > customers which need new Person objects, new Domains, etc. etc. Now, I > understand perfectly if there are emergency maintainances or whatever, but > don't just switch it off for an entire day without at least letting us > know! How much effort would it have been if you had written a seven line > email explaining that you have to take the DB down, and why? > > It's not like you're some kind of Internet Dictatorship or IP God which > can do as it pleases; the RIPE NCC takes care of this stuff on the behalf > of the LIRs and is financed by the LIRs, so this heavy-handed approach is > really not something I appreciate. I guess the RIPE community in general does not appreciate YOUR approach (at least I do not). :(( Please find below the mail the RIPE NCC sent out BEFORE they turned updates off. I guess you have not been at the RIPE meetings and did not follow the work the RIPE NCC has been doing in the last many years. Otherwise I do not think you would make a remark like the above. Best regards, Janos > > > Best wishes, > Nils Jeppe > > > On Tue, 22 Feb 2000, RIPE Database Administration wrote: > > > > > Dear Colleagues, > > > > We wish to announce that the whois and update service > > of the RIPE Database has returned to normal. Currently, the > > queue of updates is being processed. We expect this queue to > > be cleared later this evening. > > > > Thank you for being patient. You will find that the service > > level of the RIPE Database has been improved. If you > > have questions, please contact <ripe-dbm(a)ripe.net>. > > > > If you have any questions, please don't hesitate > > to contact <ripe-dbm(a)ripe.net>. > > > > Regards, > > > > Daniele Arena > > ____________________________ > > RIPE Database Administration. > > > > ----- Begin Included Message -----

4 3

RIPE DB service restored
by RIPE Database Administration 22 Feb '00

22 Feb '00

Dear Colleagues, We wish to announce that the whois and update service of the RIPE Database has returned to normal. Currently, the queue of updates is being processed. We expect this queue to be cleared later this evening. Thank you for being patient. You will find that the service level of the RIPE Database has been improved. If you have questions, please contact <ripe-dbm(a)ripe.net>. If you have any questions, please don't hesitate to contact <ripe-dbm(a)ripe.net>. Regards, Daniele Arena ____________________________ RIPE Database Administration.

2 1

Updates to the RIPE whois database stopped
by RIPE Database Administration 21 Feb '00

21 Feb '00

Dear All, Due to a crash of our whois server which we experienced last Saturday we are stopping the updates tonight and we are going to reindex the data. There is no need to resend your updates. The updates will be queued and they will be resumed tomorrow. We are also going to upgrade the main server so that it can cope better with the ever growing load. The whois query service will be switched to our backup server, therefore the response time will be slower than usual. If you have any questions, please don't hesitate to contact <ripe-dbm(a)ripe.net>. Regards, Marek Bukowy ____________________________ RIPE Database Administration.

1 0

Next step in the RIPE database reimplementation project
by RIPE Database Administration 21 Feb '00

21 Feb '00

Dear all, This is to notify you of the further steps in the development of the new RIPE Database. Today we have put online the next version of the reimplemented whois server. It is running on the machine reimp.ripe.net on port 43. This server is running as a near real-time mirror client, mirroring the current RIPE database. Please have a look and let us know if you find anything wrong. The results of the queries are supposed to match the results of the queries from our production server. Please note that the access control mechanism may prevent you from obtaining excessive contact information. Please contact <ripe-dbm(a)ripe.net> if the limit turns out to be too small for your tests. Please send your comments and bug reports to <db-beta(a)ripe.net> mailing list. To subscribe to this list send a message to <majordomo(a)ripe.net> with the line: subscribe db-beta in the body of your letter. This is a moderated mailing list so some delays in subscription are possible. The source code is also being released. It can be found at our ftp site: ftp://ftp.ripe.net/ripe/dbase/reimp/RIP-0.2.0beta2.tar.gz The instructions for installing the software and loading the database can be found in the file INSTALL in the main directory. Best regards, Daniele Arena ____________________________ RIPE Database Administration.

1 0

RIPE Database usage
by Wolf-Guido Lutz 18 Feb '00

18 Feb '00

Hello List, forgive me if this is a question that doesn't belong here, but maybe someone can point me in the right direction. I have started maintaining my own nameserver a few months ago and the company that does the second level domain connections for me doesn't seem to be able to help me with this: how can I change the information in the maintainer object of my own RIPE record? In fact, I would like to create my own maintainer object. Is there any documentation maybe on who/how to change that information in the RIPE database? TIA Wolf-Guido Lutz

3 2

Top 100 Maintainers List 20000217
by RIPE Database Administration 17 Feb '00

17 Feb '00

1 0

1. Draft, proposed agenda DB-WG meeting RIPE-35, Thu.,Feb.24 2000
by Wilfried Woeber, UniVie/ACOnet 15 Feb '00

15 Feb '00

Dear DB-WG! Attached please find the 1st draft: Proposed Agenda for the DB-WG Meeting during RIPE35, Amsterdam. As always, comments and proposals for additional topics are welcome. There might be last-minute changes, so stay tuned (this time we've been less successful in finding an optimal solution for the scheduling maze)! Regards, and see you in Amsterdam, Wilfried. ______________________________________________________________________ Proposed Agenda for the Database Working Group Meeting RIPE-35, February 2000, Amsterdam, NL 1. Draft Note: for any updates between now and just before the WG meeting, watch the DB WG Mailing List, please! Slot #1, Thursday, Feb. 24th, 09:00 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A. Administrative stuff (Wilfried Woeber, chair) B. RIPE DB, operational update (NCC: AMRM, 20min.) C. A short review on the maintainer mechanism - are there any security concerns? D. (tentatively) Is there an interest to register CERT/IRT-related info? - brainstorming/proposals Slot #2, Thursday, Feb. 24th, 11:00 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ E. Status of the reimplementation project (NCC: JLSD, 20min.) F. Transition to ripe db v3.0 and transition TF (JLSD & WW, 15min G. Do we need/want a DB WG review/re-structuring? - future topics of interest (workplan/charter?) - I/O with other WGs - logistics Y. Input from other WGs - t.b.d. Z. AOB ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ WW, 15-FEB-2000 17:23:23 -------------------------------------------------------------------------- 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Common sense requires a common language... __________________________________________________________________________

1 0

Whoisd buffer overrun
by RIPE Database Administration 03 Feb '00

03 Feb '00

Dear colleagues, It was brought to our attention last night that the perl whoisd server the RIPE NCC is currently running is vulnerable to a buffer overflow attack. We have taken action immediately and fixed this problem on our production servers. We have also checked for traces of people taking advantage of the vulnerability and concluded that this was not the case. The whois service was not affected. Should you be running a copy of our software, please apply the patch attached below to bin/whoisd. It truncates the query to 255 characters. If you have any questions or comments, please contact <ripe-dbm(a)ripe.net>. We would like to thank Geert Jan de Groot and Steve Bellovin for bringing this to our attention. Kind Regards, Mirjam Kuehne Head External Services RIPE NCC -------------------- 1. save the following text as /tmp/whoisdpatch ----------cut here------------------------------ *** whoisd.trunc Wed Feb 2 22:28:34 2000 --- whoisd Wed Feb 2 22:29:46 2000 *************** *** 1679,1694 **** $query=join(" ", @ARGV); } else { - my($trunclen); - alarm $KEEPOPEN if (!$commandline); $query=<$input>; - - # truncate to 255 chars - $trunclen = length($query); - $trunclen = 255 if $trunclen > 255; - substr( $query, $trunclen ) = ""; - } # &dpr("query: -$query- errorcode: -$!-\n"); --- 1679,1686 ---- ----------cut here-------------------------------- 2. execute in the directory where your whoisd lives: $ patch < /tmp/whoisdpatch

3 2

Top 100 Maintainers List 20000203
by RIPE Database Administration 03 Feb '00

03 Feb '00

1 0

Fault vs. feature in the 'mnt-by' mechanism
by Carsten Schiefner 28 Jan '00

28 Jan '00

Folks, I would like to draw your attention to a fact that might be intended as a feature but what I consider more or less as a fault: I can't find any good reason that it is possible to protect objects which are previously unprotected or protected with an own mnt object also with other strong ("password") mnt objects without knowing the password of this maintainer. So it is possible for almost everyone to enter a bunch of bogus objects in the RIPE database without protection and then - as a 2nd step - to update all these objects, now including our company's mnt objects - thus we will become "responsible" for these bogus objects in a way, but we won't get aware of it. This may not be so significant for person objects, but is definitely much more serious regarding AS or route objects - so a redesign of this protection mechanism should be discussed at least. Please see http://www.ripe.net/cgi-bin/whois?sg4456-ripe as an example. Best regards, Carsten Schiefner -- Carsten Schiefner mailto:carsten.schiefner@tcpip-gmbh.de TCP/IP GmbH, Berlin (Germany) http://www.tcpip-gmbh.de Phone: +49.30.443366-0 Fax: +49.30.443366-15 Mobile: +49.172.5425797 TCP/IP GmbH runs the Contrib.Net backbone http://www.contrib.net ======================================================================

2 1

New tool announcement from Merit/IRRd: IRRj
by Jonathan Poland 22 Jan '00

22 Jan '00

Merit's IRRd team is pleased to announce the 1.0 Beta version of IRRj, a Java interface to the Internet Routing Registry. IRRj replaces the traditional e-mail submission process for database objects, and offers the following features: - Speed: IRRj opens a TCP socket connection to IRRd and provides fast, immediate feedback on the success or failure of your object submission. - Authentication: supports CRYPT-PW, PGP-FROM, and NONE authentication schemes transparently. - IRRd query support: offers full querying capabilities to retrieve objects for editing and resubmission. - Custom editing features: automatically appends delete fields to all objects, imports object templates. - Split window interface: IRRj includes a submission window and an IRRd feedback window. IRRj can be invoked from the Web or as a standalone application. System requirements are Sun's JDK (free from java.sun.com), Netscape 4.5+ or Java Plugin 1.2.2 (Internet Explorer or Netscape on Win32). IRRj runs on any Java capable machine, including Windows, Solaris, and most flavors of Unix. IRRj object submission will work with the RADB and any other IRR database that supports the IRRd synchronous object submission protocol. See http://www.irrd.net for more information about the freely available IRRd software. IRRj is freeware and can be downloaded and/or invoked from the web at: http://www.merit.edu/ipma/javairr/irr.html Please contact the IRRd team (irrd-support(a)merit.edu) with comments, feedback, suggestions, or questions. Jon Poland IRRd Team

1 0

RE: DB consistancy checking tools
by Wilfried Woeber, UniVie/ACOnet 20 Jan '00

20 Jan '00

Matthew, I think this is an interesting proposal: >I have been wondering recently whether a separate group should be set up for >the sole purpose of creating tools/advise/methods/hints 'n' tips for LIR's >to keep on top of their entries and make management easier. A sort of RIPE >users working group not concerned with designing objects for the database >but how to put existing objects in it, remove them, manage them, etc. > >My 2c > >Matthew To start things moving, could you come up with a coarse draft of ideas and short-term goals to take up? On the more formal side, one of the possible solutions to accomodate that activity might be to create a TaskForce to work on well-defined items during RIPE35 (do you intend to particpate?). This TF might be supported by both LIR and DB, or sponsored by whichever group is seen to be appropriate... 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 Handle: WW144 A-1010 Vienna, Austria, Europe : PGP public key ID 0xF0ACB369 __________________________________________________________________________

1 0

None
by RIPE Database Administration 20 Jan '00

20 Jan '00

Dear All, Following a request from the Chair, here is the status of the works on the new implementation of the RIPE database. Currently we are testing the query part of the database. It has been made publicly available at http://www.ripe.net/ripencc/pub-services/db/reimp/ on December 31, 1999 and a message has been sent to the db-beta mailing list. The database contains about 2.5 million objects corresponding to all the objects as of June 17th. You should also be able to query it directly at reimp.ripe.net, port 43. Please have a look and let us know if you spot something terribly wrong. We would like to detect as many differences as possible with respect to the old database. We know that some types of queries returned wrong information in the old incarnation, notably the more/less specific route/inetnum queries. This changed now with the introduction of radix trees. There may be some bugs though, so everybody is encouraged to try the server and compare the output. The source code has also been released. It can be found at our ftp site: ftp://ftp.ripe.net/ripe/dbase/reimp/RIP-0.1.0beta1.tar.gz All comments are welcome. We are now actively working on making the server a near-real-time mirror client of our main (old) server, so that the data in both is nearly identical at all times. We are confident this will be available in the next days, maybe weeks. The part which needs most work is the update part. We are also working on that quite hard now. Our goal is to present the community with a working beta version including updates, around the time of the coming RIPE meeting at the end of February 1900^H^H^H^H2000. If you have any more questions, please don't hesitate to contact <ripe-dbm(a)ripe.net>. Regards, Marek Bukowy ____________________________ RIPE Database Administration.

1 0

RE: DB consistancy checking tools
by Wilfried Woeber, UniVie/ACOnet 20 Jan '00

20 Jan '00

With reference to: >From: stephenb(a)uk.uu.net >Date: Tue, 11 Jan 2000 11:49:34 +0000 (GMT) >Subject: DB consistancy checking tools >To: lir-wg(a)ripe.net > >Hi > After making a number of NEWBLOCK requests and recieving the > information back of the errors in the DB for the previous block, > i would like to make the suggestion to the RIPE NCC the we are > allowed accuess to this most useful tool. This way we could do > the consitancy checks and get our house in order before making > the NEWBLOCK request, lessening the load on RIPE and speeding > up the allocation of more CIDR. > >If there is enough interest can we add this as a point of discussion at >the LIR working group, or should it be in the DB group. > >BTW i do like the new web site. > >Regards, >-- >---------------------------------- >E-Mail: stephenb(a)uk.uu.net >Phone: +44 (0)1223 581051 I've got one tech Q and one org Q: Tech: Would you want to propose a "public release" of the tool (e.g. to be able to deploy it in a local environment), or would it be useful / sufficient to be able to trigger the tool (for a given address range) and to have access to the result? I'm aware of the fact that there might be access and/or security related issues requiring a solution, but we might be able to solve that as soon as we know what to look for.... Org.: Where is this to go? LIR or DB? Preferences? ( In general I prefer a path where the goals and application requirements emerge from an "application WG" and the implementation is then passed on to the DB-WG. ) Wilfried.

1 0

RE: DB consistancy checking tools
by Matthew Robinson 20 Jan '00

20 Jan '00

I have been wondering recently whether a separate group should be set up for the sole purpose of creating tools/advise/methods/hints 'n' tips for LIR's to keep on top of their entries and make management easier. A sort of RIPE users working group not concerned with designing objects for the database but how to put existing objects in it, remove them, manage them, etc. My 2c Matthew -----Original Message----- From: Wilfried Woeber, UniVie/ACOnet [mailto:woeber@cc.univie.ac.at] Sent: 20 January 2000 13:07 To: stephenb(a)uk.uu.net Cc: lir-wg(a)ripe.net; woeber(a)cc.univie.ac.at; db-wg(a)ripe.net Subject: RE: DB consistancy checking tools

1 0