From ripe-dbm at ripe.net Thu Feb 3 09:41:13 2000 From: ripe-dbm at ripe.net (RIPE Database Administration) Date: Thu, 03 Feb 2000 09:41:13 +0100 Subject: Top 100 Maintainers List 20000203 Message-ID: <200002030841.JAA00467@birch.ripe.net> Dear list members, This is biweekly report on inconsistent objects in the RIPE whois database. The first 100 maintainers are listed as a table below sorted according to number of their inconsistent objects in the database. The rest of the maintainers which have inconsistent objects can be found at http://www.ripe.net/ripencc/pub-services/db/state/mntnerreport1.html You can find further information about the Consistency Project at http://www.ripe.net/ripencc/pub-services/db/state/ Regards, RIPE NCC Database Group =============================================================== Maintainer no of name inconsistent objects 1 DENIC-P 76215 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DENIC-P.html 2 XLINK-MNT 56276 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/XLINK-MNT.html 3 FREEDOMS 18267 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/FREEDOMS.html 4 DK-DOMREG 11592 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DK-DOMREG.html 5 ECCE-NOC 3953 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ECCE-NOC.html 6 ROKA-P 3933 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ROKA-P.html 7 DTAG-NIC 3855 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DTAG-NIC.html 8 SCHLUND-P 2549 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/SCHLUND-P.html 9 ABCAG-MNT 2080 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ABCAG-MNT.html 10 DREIMARK49-MNT 2059 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DREIMARK49-MNT.html 11 FR-NIC-MNT 1772 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/FR-NIC-MNT.html 12 BO-DOMREG 1757 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/BO-DOMREG.html 13 WWW-MNT 1654 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/WWW-MNT.html 14 NACAMAR-NOC 1650 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/NACAMAR-NOC.html 15 DENIC-N 1034 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DENIC-N.html 16 ECORE-NET 876 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ECORE-NET.html 17 AS1849-MNT 874 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS1849-MNT.html 18 HIGHSPEED-DOM 846 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/HIGHSPEED-DOM.html 19 INTERNET-NOC 714 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/INTERNET-NOC.html 20 CSL-MNT 619 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/CSL-MNT.html 21 DKNET-MNT 606 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DKNET-MNT.html 22 DFN-NTFY 584 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DFN-NTFY.html 23 DNSNET-MNT 581 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DNSNET-MNT.html 24 SEKTORNET-MNT 580 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/SEKTORNET-MNT.html 25 NACAMAR-RES 522 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/NACAMAR-RES.html 26 WESPE-MNT 522 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/WESPE-MNT.html 27 DE-VOSS 520 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DE-VOSS.html 28 OLEANE-NOC 499 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/OLEANE-NOC.html 29 IL-P 483 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/IL-P.html 30 TDK-MNT 470 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/TDK-MNT.html 31 GLOBAL-MNT 446 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/GLOBAL-MNT.html 32 SDT-NOC 446 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/SDT-NOC.html 33 RAK-NET 441 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/RAK-NET.html 34 WEBSPACE-SERVICE-DE 438 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/WEBSPACE-SERVICE-DE.html 35 KNIPP-NOC-MNT 415 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/KNIPP-NOC-MNT.html 36 IDNET-MNT 387 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/IDNET-MNT.html 37 MARIDAN-P 379 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/MARIDAN-P.html 38 NACAMAR-POP 374 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/NACAMAR-POP.html 39 GIGABELL-MNT 365 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/GIGABELL-MNT.html 40 NETTUNO 363 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/NETTUNO.html 41 DIGITALWEB-MNT 361 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DIGITALWEB-MNT.html 42 RAIN-TRANSPAC 360 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/RAIN-TRANSPAC.html 43 INX-MNT 341 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/INX-MNT.html 44 NETCOLOGNE-MNT 340 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/NETCOLOGNE-MNT.html 45 FREENAME-NOC 328 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/FREENAME-NOC.html 46 SL-CUS-MNT 325 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/SL-CUS-MNT.html 47 AS6678-MNT 323 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS6678-MNT.html 48 AS3233-MNT 319 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS3233-MNT.html 49 TRMD-MNT 309 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/TRMD-MNT.html 50 AS5617-MNT 298 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS5617-MNT.html 51 AS5378-MNT 279 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS5378-MNT.html 52 MBT-MNT 274 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/MBT-MNT.html 53 AS5427-MNT 271 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS5427-MNT.html 54 PRHO-GUARDIAN 256 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/PRHO-GUARDIAN.html 55 ONE2ONE-MNT 252 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ONE2ONE-MNT.html 56 NDH-P 250 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/NDH-P.html 57 KDT-MNT 246 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/KDT-MNT.html 58 EUROCONNECT 233 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/EUROCONNECT.html 59 IBGNET 231 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/IBGNET.html 60 AS1717-MNT 226 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS1717-MNT.html 61 IMAGINET-NOC-MNT 224 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/IMAGINET-NOC-MNT.html 62 AS1899-MNT 213 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS1899-MNT.html 63 ROM-MIKNET 208 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ROM-MIKNET.html 64 AS2120-MNT 206 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS2120-MNT.html 65 PSINET-UK-SYSADMIN 202 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/PSINET-UK-SYSADMIN.html 66 EU-IBM-NIC-MNT2 201 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/EU-IBM-NIC-MNT2.html 67 AS2529-MNT 196 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS2529-MNT.html 68 IWAY-NOC 193 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/IWAY-NOC.html 69 AS2871-MNT 189 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS2871-MNT.html 70 FR-EASYNET 180 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/FR-EASYNET.html 71 IT-NIC 175 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/IT-NIC.html 72 AS1241-MNT 165 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS1241-MNT.html 73 ICMS-NOC-MAINTAINER 163 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ICMS-NOC-MAINTAINER.html 74 OMNILINK-MNT 159 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/OMNILINK-MNT.html 75 SKYNETBE-MNT 159 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/SKYNETBE-MNT.html 76 ITNET-MNT 158 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ITNET-MNT.html 77 ISTLD-MNT 157 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ISTLD-MNT.html 78 AS6721-MNT 153 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS6721-MNT.html 79 EVOSYS-MNT 144 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/EVOSYS-MNT.html 80 PROFI-MNT 141 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/PROFI-MNT.html 81 NNCC 135 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/NNCC.html 82 SEICOM-MNT 129 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/SEICOM-MNT.html 83 SPACENET-P 127 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/SPACENET-P.html 84 COMMPLEX-MNT 123 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/COMMPLEX-MNT.html 85 ISMA-MNT 123 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ISMA-MNT.html 86 XMS-MNT 123 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/XMS-MNT.html 87 INETWIRE-MNT 121 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/INETWIRE-MNT.html 88 AS3292-MNT 119 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS3292-MNT.html 89 DK-NIC 117 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DK-NIC.html 90 IVM-MNT 110 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/IVM-MNT.html 91 AS5551-MNT 105 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS5551-MNT.html 92 ODN-MNT 105 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ODN-MNT.html 93 SCHUETZ-MNT 105 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/SCHUETZ-MNT.html 94 WEB4YOU-MNT 102 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/WEB4YOU-MNT.html 95 OMC1-RIPE-MNT 99 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/OMC1-RIPE-MNT.html 96 ROSNIIROS-MNT 99 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ROSNIIROS-MNT.html 97 VISCOMP-MNT 98 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/VISCOMP-MNT.html 98 AS8875-MNT 96 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS8875-MNT.html 99 CU-MNT 90 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/CU-MNT.html 100 MDA-Z 90 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/MDA-Z.html From ripe-dbm at ripe.net Thu Feb 3 14:09:10 2000 From: ripe-dbm at ripe.net (RIPE Database Administration) Date: Thu, 03 Feb 2000 14:09:10 +0100 Subject: Whoisd buffer overrun Message-ID: <200002031309.OAA24349@birch.ripe.net> 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 . 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 From marck at ti.ru Thu Feb 3 14:21:38 2000 From: marck at ti.ru (Dmitry Morozovsky) Date: Thu, 3 Feb 2000 16:21:38 +0300 (MSK) Subject: Whoisd buffer overrun In-Reply-To: <200002031309.OAA24349@birch.ripe.net> Message-ID: On Thu, 3 Feb 2000, RIPE Database Administration wrote: > 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 > > 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 [skip] > 2. execute in the directory where your whoisd lives: > $ patch < /tmp/whoisdpatch I suppose everyone should pay attention that patch mentioned is _reverse_ (i.e. old and new file had been swapped) Sincerely, D.Marck --------------------------------------------------------------------- *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at ti.ru *** --------------------------------------------------------------------- From tino at kiosk-online.de Thu Feb 3 20:19:13 2000 From: tino at kiosk-online.de (Valentin Hilbig) Date: Thu, 3 Feb 2000 20:19:13 +0100 (MET) Subject: Whoisd buffer overrun In-Reply-To: <200002031309.OAA24349@birch.ripe.net> from RIPE Database Administration at "Feb 3, 2000 02:09:10 pm" Message-ID: <200002031919.UAA13775@cappuccino.kiosk-online.de> Perhaps you should note that the patch has to be applied REVERSE. You can state this in the patch call like this: $ patch -R < /tmp/whoisdpatch You can see this if you examine the diff. No big problem, because without -R patch should detect this case and should ask if the patch should be applied reverse, though. But I haven't checked myself because I do not have a copy of whoisd running. Anyway, I thank you for your quick warning. -Tino RIPE Database Administration schrieb: > > > 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 . > > > 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 > > -- Valentin `Tino' Hilbig mailto:tino at kiosk-online.de NOC Online-Kiosk GmbH http://www.noc.baycix.de/ Tel. +49-180-5654357 privat: http://geht.net/ Fax. +49-871-9253629 privat: nospam at geht.net From woeber at cc.univie.ac.at Tue Feb 15 17:59:07 2000 From: woeber at cc.univie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Tue, 15 Feb 2000 17:59:07 MET Subject: 1. Draft, proposed agenda DB-WG meeting RIPE-35, Thu.,Feb.24 2000 Message-ID: <009E5B66.D1011F08.33@cc.univie.ac.at> 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 at 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... __________________________________________________________________________ From engin at ripe.net Thu Feb 17 17:44:54 2000 From: engin at ripe.net (Engin Gunduz) Date: Thu, 17 Feb 2000 17:44:54 +0100 (CET) Subject: inetnum conversion Message-ID: 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 . Also, please send your comments about the conversion to the list, Regards, Engin Gunduz RIPE NCC Database Group ----------------------- From lutz at clippernet.de Thu Feb 17 17:58:47 2000 From: lutz at clippernet.de (Wolf-Guido Lutz) Date: Thu, 17 Feb 2000 17:58:47 +0100 Subject: RIPE Database usage Message-ID: <01BF7970.A49CC9E0.lutz@clippernet.de> 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 From margit at belanna.augsburg.net Thu Feb 17 21:54:47 2000 From: margit at belanna.augsburg.net (Margit Steidl) Date: Thu, 17 Feb 2000 21:54:47 +0100 (MET) Subject: RIPE Database usage In-Reply-To: <01BF7970.A49CC9E0.lutz@clippernet.de> Message-ID: Hello Wolf-Guido! On Thu, 17 Feb 2000, Wolf-Guido Lutz wrote: > From: Wolf-Guido Lutz > To: "'db-wg at ripe.net'" > Date: Thu, 17 Feb 2000 17:58:47 +0100 > Subject: RIPE Database usage > > 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? > According to the whois -h whois.ripe.net Wolf-Guido Lutz there is a Maintainer CU-MNT. This Maintainer belongs to CU-Connection Universe Netzgesellschaft mbH and is protected by password. You have to contact the owner of this above mentioned maintainer owner to get your WL202-RIPE or your WL321-RIPE changed or deleted. Just ask whois -h whois.ripe.net CK-RIPE whois -h whois.ripe.net CD-RIPE Then you can see the necessary contact information. They can change it for you. How to get one's own maintainer - I have to forward this question to the others. Or there might be some pretty well hidden information within the ripe homepage http://www.ripe.net (somewhere below). > TIA > Wolf-Guido Lutz > Best regards from Margit Steidl System administrator of augsburg.net From ripe-dbm at ripe.net Thu Feb 17 22:08:23 2000 From: ripe-dbm at ripe.net (RIPE Database Administration) Date: Thu, 17 Feb 2000 22:08:23 +0100 Subject: Top 100 Maintainers List 20000217 Message-ID: <200002172108.WAA09388@birch.ripe.net> Dear list members, This is biweekly report on inconsistent objects in the RIPE whois database. The first 100 maintainers are listed as a table below sorted according to number of their inconsistent objects in the database. The rest of the maintainers which have inconsistent objects can be found at http://www.ripe.net/ripencc/pub-services/db/state/mntnerreport1.html You can find further information about the Consistency Project at http://www.ripe.net/ripencc/pub-services/db/state/ Regards, RIPE NCC Database Group =============================================================== Maintainer no of name inconsistent objects 1 DENIC-P 87596 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DENIC-P.html 2 XLINK-MNT 58609 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/XLINK-MNT.html 3 FREEDOMS 24059 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/FREEDOMS.html 4 DK-DOMREG 13112 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DK-DOMREG.html 5 ECCE-NOC 5227 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ECCE-NOC.html 6 ROKA-P 4309 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ROKA-P.html 7 DTAG-NIC 4205 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DTAG-NIC.html 8 SCHLUND-P 2594 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/SCHLUND-P.html 9 ABCAG-MNT 2518 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ABCAG-MNT.html 10 DREIMARK49-MNT 2271 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DREIMARK49-MNT.html 11 BO-DOMREG 1841 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/BO-DOMREG.html 12 WWW-MNT 1735 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/WWW-MNT.html 13 NACAMAR-NOC 1685 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/NACAMAR-NOC.html 14 FR-NIC-MNT 1647 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/FR-NIC-MNT.html 15 DENIC-N 1033 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DENIC-N.html 16 AS1849-MNT 943 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS1849-MNT.html 17 ECORE-NET 943 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ECORE-NET.html 18 INTERNET-NOC 929 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/INTERNET-NOC.html 19 HIGHSPEED-DOM 926 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/HIGHSPEED-DOM.html 20 DNSNET-MNT 737 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DNSNET-MNT.html 21 CSL-MNT 636 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/CSL-MNT.html 22 DKNET-MNT 636 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DKNET-MNT.html 23 WESPE-MNT 601 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/WESPE-MNT.html 24 DFN-NTFY 595 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DFN-NTFY.html 25 OLEANE-NOC 583 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/OLEANE-NOC.html 26 SEKTORNET-MNT 583 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/SEKTORNET-MNT.html 27 NACAMAR-RES 544 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/NACAMAR-RES.html 28 DE-VOSS 529 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DE-VOSS.html 29 IL-P 520 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/IL-P.html 30 TDK-MNT 498 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/TDK-MNT.html 31 RAK-NET 488 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/RAK-NET.html 32 WEBSPACE-SERVICE-DE 482 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/WEBSPACE-SERVICE-DE.html 33 SDT-NOC 467 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/SDT-NOC.html 34 GLOBAL-MNT 458 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/GLOBAL-MNT.html 35 KNIPP-NOC-MNT 452 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/KNIPP-NOC-MNT.html 36 GIGABELL-MNT 442 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/GIGABELL-MNT.html 37 MARIDAN-P 418 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/MARIDAN-P.html 38 IDNET-MNT 393 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/IDNET-MNT.html 39 NETTUNO 390 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/NETTUNO.html 40 NACAMAR-POP 378 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/NACAMAR-POP.html 41 NETCOLOGNE-MNT 368 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/NETCOLOGNE-MNT.html 42 DIGITALWEB-MNT 359 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DIGITALWEB-MNT.html 43 INX-MNT 350 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/INX-MNT.html 44 RAIN-TRANSPAC 350 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/RAIN-TRANSPAC.html 45 SL-CUS-MNT 347 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/SL-CUS-MNT.html 46 TRMD-MNT 340 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/TRMD-MNT.html 47 AS3233-MNT 335 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS3233-MNT.html 48 FREENAME-NOC 333 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/FREENAME-NOC.html 49 AS6678-MNT 323 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS6678-MNT.html 50 AS5617-MNT 319 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS5617-MNT.html 51 AS5378-MNT 306 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS5378-MNT.html 52 MBT-MNT 301 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/MBT-MNT.html 53 KDT-MNT 294 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/KDT-MNT.html 54 AS5427-MNT 289 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS5427-MNT.html 55 PRHO-GUARDIAN 283 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/PRHO-GUARDIAN.html 56 NDH-P 281 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/NDH-P.html 57 ONE2ONE-MNT 275 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ONE2ONE-MNT.html 58 PSINET-UK-SYSADMIN 251 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/PSINET-UK-SYSADMIN.html 59 EUROCONNECT 234 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/EUROCONNECT.html 60 IBGNET 233 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/IBGNET.html 61 IMAGINET-NOC-MNT 225 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/IMAGINET-NOC-MNT.html 62 AS1717-MNT 223 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS1717-MNT.html 63 AS1899-MNT 220 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS1899-MNT.html 64 ROM-MIKNET 218 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ROM-MIKNET.html 65 AS2871-MNT 212 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS2871-MNT.html 66 EU-IBM-NIC-MNT2 210 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/EU-IBM-NIC-MNT2.html 67 AS2120-MNT 207 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS2120-MNT.html 68 AS2529-MNT 205 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS2529-MNT.html 69 ICMS-NOC-MAINTAINER 196 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ICMS-NOC-MAINTAINER.html 70 IWAY-NOC 193 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/IWAY-NOC.html 71 ITNET-MNT 178 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ITNET-MNT.html 72 IT-NIC 173 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/IT-NIC.html 73 OMNILINK-MNT 169 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/OMNILINK-MNT.html 74 AS1241-MNT 168 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS1241-MNT.html 75 SPACENET-P 166 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/SPACENET-P.html 76 AS6721-MNT 165 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS6721-MNT.html 77 ISTLD-MNT 165 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ISTLD-MNT.html 78 SKYNETBE-MNT 157 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/SKYNETBE-MNT.html 79 EVOSYS-MNT 152 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/EVOSYS-MNT.html 80 COMMPLEX-MNT 150 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/COMMPLEX-MNT.html 81 PROFI-MNT 142 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/PROFI-MNT.html 82 XMS-MNT 138 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/XMS-MNT.html 83 NNCC 136 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/NNCC.html 84 INETWIRE-MNT 133 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/INETWIRE-MNT.html 85 SEICOM-MNT 129 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/SEICOM-MNT.html 86 ISMA-MNT 125 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ISMA-MNT.html 87 AS3292-MNT 120 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS3292-MNT.html 88 DK-NIC 120 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/DK-NIC.html 89 WEB4YOU-MNT 119 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/WEB4YOU-MNT.html 90 SCHUETZ-MNT 114 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/SCHUETZ-MNT.html 91 OMC1-RIPE-MNT 111 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/OMC1-RIPE-MNT.html 92 VISCOMP-MNT 111 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/VISCOMP-MNT.html 93 ODN-MNT 109 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ODN-MNT.html 94 AS5551-MNT 106 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/AS5551-MNT.html 95 IVM-MNT 105 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/IVM-MNT.html 96 FO-DOMREG 103 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/FO-DOMREG.html 97 CHEAPDOM-RIPE-MNT 102 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/CHEAPDOM-RIPE-MNT.html 98 NM-NOC 99 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/NM-NOC.html 99 ROSNIIROS-MNT 99 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/ROSNIIROS-MNT.html 100 FR-EASYNET 95 http://www.ripe.net/ripencc/pub-services/db/state/maintainers/FR-EASYNET.html From ripe-dbm at ripe.net Fri Feb 18 13:00:27 2000 From: ripe-dbm at ripe.net (RIPE Database Administration) Date: Fri, 18 Feb 2000 13:00:27 +0100 Subject: RIPE Database usage In-Reply-To: Your message of Thu, 17 Feb 2000 21:54:47 +0100. References: Message-ID: <200002181200.NAA02750@birch.ripe.net> Dear All, The procedure for obtaining a maintainer in RIPE database has been described in section 2.3.4 of RIPE-157 document, which is *the* database documentation. If you have any suggestions for how to make the database webpage http://www.ripe.net/ripencc/pub-services/db more user-friendly, we will be delighted to hear them. Regards, Daniele Arena ____________________________ RIPE Database Administration. Margit Steidl writes: * * Hello Wolf-Guido! * * On Thu, 17 Feb 2000, Wolf-Guido Lutz wrote: * * > From: Wolf-Guido Lutz * > To: "'db-wg at ripe.net'" * > Date: Thu, 17 Feb 2000 17:58:47 +0100 * > Subject: RIPE Database usage * > * > 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? * > * According to the * whois -h whois.ripe.net Wolf-Guido Lutz * there is a Maintainer CU-MNT. * * This Maintainer belongs to * CU-Connection Universe Netzgesellschaft mbH * and is protected by password. * * You have to contact the owner of this above mentioned maintainer owner to get * your WL202-RIPE or your WL321-RIPE changed or deleted. * Just ask * whois -h whois.ripe.net CK-RIPE * whois -h whois.ripe.net CD-RIPE * * Then you can see the necessary contact information. * They can change it for you. * * How to get one's own maintainer - I have to forward this question to the other * s. * Or there might be some pretty well hidden information within the ripe homepage * http://www.ripe.net (somewhere below). * * > TIA * > Wolf-Guido Lutz * > * * Best regards from Margit Steidl * System administrator of augsburg.net * * From ripe-dbm at ripe.net Mon Feb 21 17:27:19 2000 From: ripe-dbm at ripe.net (RIPE Database Administration) Date: Mon, 21 Feb 2000 17:27:19 +0100 Subject: Next step in the RIPE database reimplementation project Message-ID: <200002211627.RAA03433@birch.ripe.net> 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 if the limit turns out to be too small for your tests. Please send your comments and bug reports to mailing list. To subscribe to this list send a message to 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. From ripe-dbm at ripe.net Mon Feb 21 19:05:18 2000 From: ripe-dbm at ripe.net (RIPE Database Administration) Date: Mon, 21 Feb 2000 19:05:18 +0100 Subject: Updates to the RIPE whois database stopped Message-ID: <200002211805.TAA21983@birch.ripe.net> 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 . Regards, Marek Bukowy ____________________________ RIPE Database Administration. From ripe-dbm at ripe.net Tue Feb 22 17:39:04 2000 From: ripe-dbm at ripe.net (RIPE Database Administration) Date: Tue, 22 Feb 2000 17:39:04 +0100 Subject: RIPE DB service restored Message-ID: <200002221639.RAA17355@birch.ripe.net> 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 . If you have any questions, please don't hesitate to contact . Regards, Daniele Arena ____________________________ RIPE Database Administration. From nils at work.de Tue Feb 22 23:53:12 2000 From: nils at work.de (Nils Jeppe) Date: Tue, 22 Feb 2000 23:53:12 +0100 Subject: RIPE DB service restored In-Reply-To: <200002221639.RAA17355@birch.ripe.net> Message-ID: 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. 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 . > > If you have any questions, please don't hesitate > to contact . > > Regards, > > Daniele Arena > ____________________________ > RIPE Database Administration. > > - ----------------------------------------------------------------- - n at work Internet Informationssysteme GmbH Tel +49 40 23880900 Spaldingstrasse 160d Fax +49 40 23880929 20097 Hamburg, Germany http://www.work.de/ From zsako at banknet.net Wed Feb 23 14:10:35 2000 From: zsako at banknet.net (Janos Zsako) Date: Wed, 23 Feb 2000 14:10:35 +0100 (MET) Subject: RIPE DB service restored Message-ID: <200002231310.OAA29838@banknet.banknet.net> > From owner-lir-wg at ripe.net Wed Feb 23 13:47:01 2000 > From: Nils Jeppe 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 . > > > > If you have any questions, please don't hesitate > > to contact . > > > > Regards, > > > > Daniele Arena > > ____________________________ > > RIPE Database Administration. > > > > ----- Begin Included Message ----- From ripe-dbm at ripe.net Mon Feb 21 19:05:18 2000 From: ripe-dbm at ripe.net (RIPE Database Administration) Date: Mon, 21 Feb 2000 19:05:18 +0100 Subject: Updates to the RIPE whois database stopped Message-ID: <200002211805.TAA21983@birch.ripe.net> 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 . Regards, Marek Bukowy ____________________________ RIPE Database Administration. ----- End Included Message ----- From nils at work.de Wed Feb 23 15:11:33 2000 From: nils at work.de (Nils Jeppe) Date: Wed, 23 Feb 2000 15:11:33 +0100 Subject: RIPE DB service restored In-Reply-To: <200002231310.OAA29838@banknet.banknet.net> Message-ID: Hello Janos, I do not subscribe to the db-wg so I never received the message you forwarded. I also didn't say I don't appreciate the work the RIPE NCC does. I have been to one Ripe Meeting, it was great and the RIPE-People are cool. I also stated quite clearly in my email that I understand perfectly if a server goes down, even unexpected. It happens. But PLEASE find the time to send an email out to people. It is NOT too much to ask for. RIPE managed to send the "we're back" message to the lir's, so why not the "we're going down" message? Surely you can't expect everybody to subscribe to the RIPE DB WG List. I don't have time to filter through a million emails a day just in case there's a problem and someone only announces it to one of the many RIPE Mailing Lists. I sent email to ncc at ripe.net and promptly got the reply that yes, there were DB problems, but they were only supposed to tell people who ask specifically about it. Hence my "Dictatorship" comment. RIPE and RIPE NCC are not closed like a government, who lives in secrecy and hides all problems from everybody, as a gov't would hide a nuclear accident or something. I apologize if I sounded a little harsh, that wasn't quite my intention, but my original point still stands. RIPE NCC manages to create an incredibly bureacracy in other fields, and fails to create a simple "trouble ticket". This is not good. Best wishes, Nils On Wed, 23 Feb 2000, Janos Zsako wrote: > > From owner-lir-wg at ripe.net Wed Feb 23 13:47:01 2000 > > From: Nils Jeppe > > 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 . > > > > > > If you have any questions, please don't hesitate > > > to contact . > > > > > > Regards, > > > > > > Daniele Arena > > > ____________________________ > > > RIPE Database Administration. > > > > > > > > > ----- Begin Included Message ----- > > >From owner-db-wg at ripe.net Mon Feb 21 18:35:59 2000 > Delivered-To: lists-db-wg-out at lists.ripe.net > Received: (qmail 26581 invoked by uid 66); 21 Feb 2000 18:05:21 -0000 > Message-Id: <200002211805.TAA21983 at birch.ripe.net> > To: db-wg at ripe.net > Subject: Updates to the RIPE whois database stopped > From: RIPE Database Administration > X-Organization: RIPE Network Coordination Centre > X-Phone: +31 20 535 4444 > X-Fax: +31 20 535 4445 > Date: Mon, 21 Feb 2000 19:05:18 +0100 > Sender: owner-db-wg at ripe.net > Precedence: bulk > Content-Length: 652 > X-Lines: 25 > Status: RO > > > 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 . > > Regards, > > Marek Bukowy > ____________________________ > RIPE Database Administration. > > > > > > > ----- End Included Message ----- > > - ----------------------------------------------------------------- - n at work Internet Informationssysteme GmbH Tel +49 40 23880900 Spaldingstrasse 160d Fax +49 40 23880929 20097 Hamburg, Germany http://www.work.de/ From joao at ripe.net Wed Feb 23 16:25:04 2000 From: joao at ripe.net (Joao Luis Silva Damas) Date: Wed, 23 Feb 2000 16:25:04 +0100 (CET) Subject: RIPE DB service restored In-Reply-To: Message-ID: Dear Nils, sorry to hear we have caused you some much problems. As the situation was we needed to perform an emergency shutdown of the update process to prevent corruption of the database after we detected some problems after a system crash. We did try to reach the community by sending out a mail to db-wg. We later realized that, contrary to the norm, we did not cc the lir-wg. We did send out a message (included below) to the lir-wg a few hours later trying to correct the situation. We realize this not what should have been done, but we are humans. During the outage, our home page (http://www.ripe.net) also had a note notifying the event. We do our best to try to keep a good service running and inform everyone affected when it is not possible to do so. What we mean by the reply you got from ncc at ripe.net is that mailbox replies only to requests and does not spam everyone. We use several wg lists to try to reach the interested parties. I hope you will accept our apologies and we promise to work harder to avoid circumstances like this in the future. ********** Begin included message Dear Colleagues, Due to a regretable oversight, the following message was not sent to this list last night. Due to a crash of our whois server, we had to stop the updates and re-index the data. There is no need to resend your updates. The updates are queued and they will be processed later. We are also going to upgrade the main server so that it can cope better with the ever growing load. The whois query service has been switched to our backup server, therefore the response time is slower than usual. The latest news is that the re-indexing process has finished and we are currently working on the main server itself. We anticipate that the full service will be restored sometime later today. We shall keep you informed. If you have anymore questions, please contact . Regards, A. M. R. Magee ______________ RIPE NCC ********** End included message Yours sincerely, Joao Damas Head of external services RIPE NCC From schiefne at mail.berlin.contrib.net Wed Feb 23 17:31:08 2000 From: schiefne at mail.berlin.contrib.net (Carsten Schiefner) Date: Wed, 23 Feb 2000 17:31:08 +0100 (MET) Subject: RIPE DB service restored In-Reply-To: <200002231310.OAA29838@banknet.banknet.net> from "Janos Zsako" at Feb 23, 2000 02:10:35 PM Message-ID: <200002231631.RAA25027@mail.berlin.contrib.net> > 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 Fully agreed here. And BTW: RTFM (where 'M' stands for 'Mail[s]' here...) Greetings, -C. -- Carsten Schiefner mailto:carsten.schiefner at 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 ====================================================================== From engin at ripe.net Fri Feb 25 15:46:37 2000 From: engin at ripe.net (Engin Gunduz) Date: Fri, 25 Feb 2000 15:46:37 +0100 (CET) Subject: inetnum conversion In-Reply-To: Message-ID: Dear colleagues, Since we didn't get any comments/objections about this issue, we will be performing inetnum conversions in the early hours of 26 February, Saturday. Best regards, Engin Gunduz RIPE NCC Database Group ----------------------- On Thu, 17 Feb 2000, Engin Gunduz wrote: > > 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 . > > Also, please send your comments about the conversion to the list, > > > Regards, > Engin Gunduz > > RIPE NCC Database Group > ----------------------- > > > From engin at ripe.net Mon Feb 28 10:08:00 2000 From: engin at ripe.net (Engin Gunduz) Date: Mon, 28 Feb 2000 10:08:00 +0100 (CET) Subject: inetnum conversion In-Reply-To: Message-ID: Dear colleagues, As announced, we have converted all legacy inetnum objects in RIPE whois database into classless format, without any problem. The conversion took place on 26 February, saturday. We have sent notifications to the maintainers of the converted objects. Please do not hesitate to contact for any problems or comments, Regards, Engin Gunduz RIPE NCC Database Group ----------------------- On Fri, 25 Feb 2000, Engin Gunduz wrote: > > Dear colleagues, > > Since we didn't get any comments/objections about this > issue, we will be performing inetnum conversions in the > early hours of 26 February, Saturday. > > Best regards, > > Engin Gunduz > > RIPE NCC Database Group > ----------------------- > > > > On Thu, 17 Feb 2000, Engin Gunduz wrote: > > > > > 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 . > > > > Also, please send your comments about the conversion to the list, > > > > > > Regards, > > Engin Gunduz > > > > RIPE NCC Database Group > > ----------------------- > > > > > > > > From nigel.titley at level3.com Mon Feb 28 17:04:16 2000 From: nigel.titley at level3.com (Nigel Titley) Date: Mon, 28 Feb 2000 16:04:16 -0000 (UTC) Subject: Charter? Does anybody have a copy Message-ID: 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) From jhma at EU.net Mon Feb 28 17:30:39 2000 From: jhma at EU.net (James Aldridge) Date: Mon, 28 Feb 2000 17:30:39 +0100 Subject: Charter? Does anybody have a copy In-Reply-To: Your message of "Mon, 28 Feb 2000 16:04:16 GMT." Message-ID: <200002281630.RAA15640@aegir.EU.net> Nigel Titley wrote: > 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. You mean something more than what's on the WG web page http://www.ripe.net/ripe/wg/db/index.html which says: "Charter The Database working group deals with all issues related to the RIPE NCC Database. Changes of existing objects, creation of new objects and features, and distribution of databases and security issues are discussed here." ??? James From nigel.titley at level3.com Tue Feb 29 17:21:34 2000 From: nigel.titley at level3.com (Nigel Titley) Date: Tue, 29 Feb 2000 16:21:34 -0000 (UTC) Subject: Charter? Does anybody have a copy In-Reply-To: <200002281630.RAA15640@aegir.EU.net> Message-ID: Strange, I'm sure this wasn't there a couple of days ago when I looked last, and Wilfried specifically asked me to hunt down the charter as a first step. OK, having made a complete fool of myself. Is the working group happy with this Charter? It looks nice and concise to me but if the WG isn't happy then suggestions are invited. Nigel On 28-Feb-2000 James Aldridge wrote: > Nigel Titley wrote: >> 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. > > You mean something more than what's on the WG web page > http://www.ripe.net/ripe/wg/db/index.html which says: > > "Charter > > The Database working group deals with all issues related to the RIPE > NCC Database. Changes of existing objects, creation of new objects and > features, and distribution of databases and security issues are > discussed here." > > ??? > > James -- 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) From ripe-dbm at ripe.net Tue Feb 29 19:49:16 2000 From: ripe-dbm at ripe.net (RIPE Database Manager) Date: Tue, 29 Feb 2000 19:49:16 +0100 (CET) Subject: Attn. NRTM clients: Missing serial files Message-ID: <200002291849.TAA22043@office.ripe.net> 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 Regards, Andrei Robachevsky ____________________________ RIPE Database Administration. From andre at NL.UU.NET Tue Feb 29 18:49:31 2000 From: andre at NL.UU.NET (Andre Koopal) Date: Tue, 29 Feb 2000 18:49:31 +0100 Subject: Charter? Does anybody have a copy In-Reply-To: ; from Nigel Titley on Tue, Feb 29, 2000 at 04:21:34PM -0000 References: <200002281630.RAA15640@aegir.EU.net> Message-ID: <20000229184931.C28741@NL.UU.NET> On Tue, Feb 29, 2000 at 04:21:34PM -0000, Nigel Titley wrote: > Strange, I'm sure this wasn't there a couple of days ago when I looked last, > and Wilfried specifically asked me to hunt down the charter as a first step. > > OK, having made a complete fool of myself. > > Is the working group happy with this Charter? It looks nice and concise to me > but if the WG isn't happy then suggestions are invited. Do we want to discuss the code development of the database software? That is not really covered under the current charter. Or is that a NCC-matter only? Regards, Andre Koopal UUNET > > Nigel > > On 28-Feb-2000 James Aldridge wrote: > > Nigel Titley wrote: > >> 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. > > > > You mean something more than what's on the WG web page > > http://www.ripe.net/ripe/wg/db/index.html which says: > > > > "Charter > > > > The Database working group deals with all issues related to the RIPE > > NCC Database. Changes of existing objects, creation of new objects and > > features, and distribution of databases and security issues are > > discussed here." > > > > ??? > > > > James > > -- > 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)