- db-wg - mailman.ripe.net

Sad news
by Joao Luis Silva Damas 27 Aug '99

27 Aug '99

Dear all, It is with great heart pain that I bring you some very sad news. Last Tuesday, our friend and colleague Roman Karpiuk suffered a terrible traffic accident while on holidays in his home country that has caused his death and that of his wife, Danka. The whole of the RIPE NCC is shocked after this event. I think I speak for the whole RIPE community if I say that we'll miss Roman and remember him as the joyful, creative and always ready to help colleague that he was. We shall always remember both of them with fond memories. Yours, Joao Luis Silva Damas RIPE NCC DB Group

1 0

Delay in processing updates
by RIPE Database Administration 25 Aug '99

25 Aug '99

Dear Colleagues, Due to an unprecedented series of major operational problems over the last few days, there are now many updates waiting to be processed by the RIPE Database. The waiting time for some updates has reached 24 hours. We have worked to fix this problem and the situation is improving. We expect the performance of the RIPE Database to be back to normal late tonight. In the meantime, we would ask you to be patient. If you have not yet received an acknowledgement to your updates, there is no need to send them again. All updates received by auto-dbm(a)ripe.net have been queued. We realise that is causing some inconvenience to you, but we would appreciate your co-operation. If you have any questions, please contact <ripe-dbm(a)ripe.net>. Regards, Marek Bukowy ____________________________ RIPE Database Administration.

1 0

Top 100 Maintainers List - 19990820
by RIPE Database Manager 24 Aug '99

24 Aug '99

4 5

Top 100 Maintainers List
by RIPE Database Manager 04 Aug '99

04 Aug '99

2 1

Re: Interesting object in the RIPE database
by Steven Bakker 11 Jul '99

11 Jul '99

>>>>> On Wed, 7 Jul 1999, "RLE" == Robert_Martin-Leg=E8ne wrote: RLE> Doesn't mean that it makes sense in the IP Registry world. Let's be RLE> practical. And besides, classful addressing is a Thing of the Past (ahem). The BSD way of doing it is clever, but complicated and it has no place in the DB, IMO. I always understood that the DB software would pad missing octets at the end of an IP address, no ambiguity there. What I'm surprised about is that the DB apparently allows someone to register address space that's most likely not even theirs... Of course, once it gets allocated and entered into the DB, a conflict will be detected and flagged (right!?), but until then, the error will go undetected. Is this a feature? Cheers, Steven

4 3

Interesting object in the RIPE database
by Niels Bakker 07 Jul '99

07 Jul '99

Hi, I noticed the following object in the RIPE database this afternoon: inetnum: 195.59.213.0 - 213.127.0.255 netname: WILLIAMBROOKES-TF13-GW descr: William Brookes School country: GB admin-c: PC2598-RIPE tech-c: IH22-ORG rev-srv: ns0.insnet.net rev-srv: ns1.insnet.net status: ASSIGNED PA mnt-by: AS5378-MNT changed: cliveg(a)insnet.net 19990706 source: RIPE (I stumbled over it while querying the RIPE database for an object within the APNIC database while accidentally omitting the -a option.) Clive Galway (the creator of this object) told me after I contacted him that he had entered the following information into the template: 195.59.213.0 - 213.127 instead of 195.59.213.0 - 195.59.213.127 He added, "funny that it dont complain though" - I agree wholeheartedly with him here. :) A check for the number of dots in the inetnum: line should be quite easy, and similar to this: # fix for people who don't include the first two or three octets s/^(\d+\.\d+)\.(\d+\.\d+) - (\d+\.\d+)$/$1.$2 - $1.$3/ s/^(\d+\.\d+\.\d+\).(\d+) - (\d+)$/$1.$2 - $1.$3/ if ($_ =~ /^\d+\.\d+\.\d+\.\d+ - \d+\.\d+\.\d+\.\d+$/) { &complain; } I believe there is a sub to check whether something is a valid IP address but can't find it offhand in my (by now pretty dated) copy of the RIPE database software... With regards, -- Niels Bakker, * * EuroNet Internet BV Network Operations * * Herengracht 208-214 * 1016 BS Amsterdam NJB9 * +31 (0)20 535 5555

3 2

Converting named references to NIC handle references
by Engin Gunduz 29 Jun '99

29 Jun '99

Dear collegues, As discussed and agreed to in the mailing lists, we will be converting unambiguous named references in the admin-c and tech-c fields of as-macro, autnum, community, dom-prefix, inet-rtr, mntner and role objects to NIC handle references, on 1 July, 1999, at 17:00, GMT. The process will take around half an hour, and during the process the updates will be queued. Whois queries will not be affected. The maintainers of the affected objects will get notifications about the changes. The conversion on domain and inetnum objects will be done at a later date, due to substantial time they require for this process. If you have any questions, please do not hesitate to contact us. Regards, Engin Gunduz RIPE NCC DB Group

1 0

T1
by OrderOffice - ICP Lueck und Lanzrath GbR 25 Jun '99

25 Jun '99

T1

1 0

address field limitation???
by Pedro Goncalves 25 Jun '99

25 Jun '99

Hi I would like to know what is the char limit (if any) for the address field. Some of my submitions apparently where returned because of the usage of more than 64 chars. Best regards Com os melhores cumprimentos. Pedro Gonçalves Telepac, SA Tel: 351-1-7907354 Fax: 351-1-7907001

2 1

Re: Modifying references to contact info in the RIPE DB
by Wilfried Woeber, UniVie/ACOnet 24 Jun '99

24 Jun '99

Hi Joao! >If the reference is by name then when I query the DB I will get the list of >persons with that name, right? Right. >Whether the object belongs to the person or not is not going to save this >person from being contacted. From the point of view of the database and the >user querying it, the object belongs to that person. Right >The link is via a name. > >Now we substitute the reference by name with a reference by nic handle >pointing to the same person. >What is the difference? > >ALMOST NONE except that: True, for the case where there is a strict one-to-one mapping, e.g the recursion using the name returns *one* object. What do you suggets to do with the case where the recursion, based on the names, returns a *set* of objects? I can see 2 approaches (at least): - do not perform the handle substitution for that referring object and put it on the list of those requiring human intervention - expand the xxxx-c: list (which? the tech-c:?) to refer to *all* objects, but by ref'ing their handles While human beings are quite clever in selecting the "proper" instance of a person: object (by looking at country, address, email,...) a script might be quite clueless with that respect :-) 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 --------------------------------------------------------------------------

3 2