- db-wg - mailman.ripe.net

Modifying references to contact info in the RIPE DB
by Joao Luis Silva Damas 24 Jun '99

24 Jun '99

Dear all, the Database consistency project has been going forward in its goals since RIPE 33 (eg. addition of nic handles to all objects without one.) Statistics and reports about the "status" of the database can be seen at http://www.ripe.net/db/state/. We will keep adding information to these pages as the project progresses. We are now at the point where we would like to tackle the issue of references by name in the admin-c, tech-c and zone-c. As a next step, we would like to have references by nic handles (which are unique) instead of references by name (which can be non -unique). At this point, we would like to automatically go through all the references by name which can uniquely be assigned to a person or role object and substitute them by references to their nic handles. This will prevent these references from becoming non-unqiue in the future. Later we will go through the process of fixing the non-unique references left in the database. This process requires user intervention since we can't decide who "owns" a particular set of resources. For this later stage, we will be preparing reports that we will send to all maintainers for whom we detect objects with inconsistencies and try to get them fixed. Information about this part will be sent to the lists in a few weeks. We would like to do this after as much as possible has been done by automatic means to correct inconsistencies so that human effort is reduced to a minimum. If there are any concerns regarding this move, please make them known before next Friday (June 25th). Looking forward to your comments, Joao Damas Database Group RIPE NCC

4 6

Changing old format dates in the RIPE DB
by Joao Luis Silva Damas 24 Jun '99

24 Jun '99

Dear all, we are going to start with the procedure to modify all the dates in the changed fields of database objects that were using only two figures for the year. After the modifications, the year part of the date will contain 4 digits. Changed fields which currently do not have a date will not be changed (*) This is taking place according to the action points agreed on the Vienna RIPE meeting. The process will be carried over the next few days due to the time it takes to re-index some of the bigger files. Regards, Joao Damas DB Group RIPE NCC (*) These objects will not be updatable by the user unless a date is included at update time or the only changed field without a date is the last one, in which case the database automatically fills in the date at which the update takes place.

1 0

Update processing delayed
by RIPE Database Administration 22 Jun '99

22 Jun '99

Dear Colleagues, the database is very loaded now, due to some huge updates sent tonight. The queue of waiting updates is very long and you should be prepered for waiting times of several hours before your update gets processed. Please do not resend your updates. Thank you for your patience. If you have any questions, please contact <ripe-dbm(a)ripe.net>. Regards, Roman Karpiuk ____________________________ The RIPE NCC Database Group.

1 0

Adding nic handles to objects without one
by Joao Luis Silva Damas 16 Jun '99

16 Jun '99

Dear all, as discussed and agreed to during discussions in the mailing lists and at the RIPE Meeting in Vienna, the RIPE NCC will be adding newly generated NIC handles to person objects that do not currently have one. Over the last days we have been testing the procedures to do this in a non-disruptive way. Unfortunately, due to the nature of the current database, the process needs about 5 hours to run. Due to this and to avoid interactions with nightly jobs that create several copies of the files, including the ftp site and the full text search indexes, we will stop updates tomorrow Tuesday at 19:00 (Amsterdam time). This will cause all updates to the DB sent after 19:00 to be queued for later processing that night. There is no need to send updates more than once. Queries will not be affected. That is, the whois server will keep answering queries normally. During the process, objects without nic handles will get unique new ones and also a "changed" attribute will be added with tomorrow's data and ripe-dbm(a)ripe.net as the author of the change. This is for future reference. If you have any questions, please do not hesitate to contact us. Best regards, Joao Damas DB Group RIPE NCC

2 1

RE: status on RIPE-DB rewrite
by Wilfried Woeber, UniVie/ACOnet 07 Jun '99

07 Jun '99

Rick, >can anyone give a status on the ripe-db rewrite in 'C' http://www.ripe.net/meetings/ripe/ripe-33/pres/db-reimpl/index.html might provide you with some answers. I'm sure RIPE NCC staff can give more details, if required. 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 --------------------------------------------------------------------------

2 1

Tagging of IP adresses / Application-Database
by Nacamar AS Guardian 07 Jun '99

07 Jun '99

Hi, at RIPE-Meeting 33, the issue on the agenda of the lir-wg of "Tagging of IP adresses and ANTI SPAM" was rejected. Partly, because this has been implemented by Paul Vixi, http://maps.vix.com/dul Further, it was felt that these tags should not be an addition to the IP-Objects, because it has a much broader range of possible applications. So, the issue was handed over to the db-wg to think about a new application-registry. Such an application-object could look like: >>> location: [mandatory] [single] [primary/look-up key] app-type: [mandatory] [single] [primary key] app-subtype: [mandatory] [single] [primary key] descr: [mandatory] [multiple] [ ] admin-c: [mandatory] [multiple] [inverse key] tech-c: [mandatory] [multiple] [inverse key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [optional] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] <<< Location would be a range of IP-Addresses or maybe a hostname, app-type a value/keyword like "nameserver", "dialin", "mail" etc., app-subtype a more detailed code for the application, like root-nameserver, tld-nameserver, cc-nameserver, etc. Details to be discussed... Then descr, contacts etc, just the usual stuff. Technically, this shouldn't be too hard, but the main questions remain on the administrative side: - who would use this database, and for what purpose (Anti-SPAM, better route-flap-dampening ...) - who should insert/maintain the contents - how to determine if the contents are 'legal', e.g. come from the 'owner' of the mentioned ip-ranges/hosts - what to do if someone protests against some contents, or claims damages because of some contents Just to spark a bit of discussion... Best Regards, HaJo Gurt ------------------------------------------------------------------- Nacamar Network Administration NACAMAR Data Communications guardian(a)nacamar.net Robert-Bosch-Str. 32 D-63303 Dreieich +49 6103 993 0 Voice Germany +49 6103 993 222 FAX gurt(a)nacamar.de ------------------------------------------------------------------- Titanic 12 - Hiroshima 45 - Tschernobyl 86 - Windows 95 - Silvester 99

3 4

Re: Tagging of IP adresses / Application-Database
by Wilfried Woeber, UniVie/ACOnet 04 Jun '99

04 Jun '99

=> >> back to basics: The only thing I wanted was an attribute => >> which said "SMTP connections from these IP numbers shouldn't happen" Yup, that was where it came from :-) And we are grateful to you for seeing this "spark" to get the whole discussion going! => > => >'overloading' of the current IP-Database with additional, => >basically unrelated informations was not wanted. => => Rather than bloat the idea to that size, I thing I'd rather drop => the proposal then. = =Ok, that would be the easiest way to get this issue done, sort of... Well, from the "users'" point of view, the innards of the implementation shouldn't be that important ?? >On the other hand, the administrative overhead >for the IP-Database with tags as extensions >is likely to be at least the same >as for a new, separate database. During the various discussions we hit a few interesting aspects (non-exhaustive list): - people do have a broad set of ideas what they woukd like to see documented. From dial-up use of IP addresses to "golden" networks for registry servers or root NS, to web-cache sites/peerings, to IPv6 tunnels... - the problem of over-loading existing objects, both schema-wise as well as maintainance-wise. E.g., for a larger ISP there's a good chance that the LIR staff wouldn't want to/be able to maintain application level entries... - the problem of authority for the data. We do have "over-loading" already, within the RIPE-DB. . I.e. the DB is (formally) authoritative for IP numbers, . it's a "reasonable" place to offer a routing registry service, but with much less (formal) authority attached by the NCC . it's offered/used as a repository for DNS data, discussion has started if "authority" for that subset should be moved to CENTR . an application type registry probably needs some sort of environment. Learning from DNS, I suppose the NCC is very reluctant to spend implementation effort unless we can come up with a model for use, authority and - eventually - funding. But, this list is emphasising the potential stumbling blocks... I'd be much more interested in proposals on the use and setup, how to maintain the data, how to derive and attach credibility, and the like. The floor is your's! Input, please! 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 --------------------------------------------------------------------------

1 0

status on RIPE-DB rewrite
by Rick H. Wesson 04 Jun '99

04 Jun '99

can anyone give a status on the ripe-db rewrite in 'C' thanks, -Rick

1 0

New RIPE DB sw version
by Joao Luis Silva Damas 04 Jun '99

04 Jun '99

Dear all, the RIPE NCC is happy to announce version 2.3 of the RIPE Database software. This new version introduces complete support for the IPv6 address objects. Only the RIPE NCC can introduce objects with value ALLOCATED in the status field of IPv4 address objects. This reflects the current registration policy. Some other minor features and a number of bug fixes have been introduced. For more details, please see the release notes included below and on the software package. This new version is available immediately from ftp.ripe.net and will be used on whois.ripe.net starting next Monday (7th June). Regards, Joao Damas DB Group RIPE NCC

1 0

Proposal to change default source search behavior in the whois server
by Jake Khuon 27 May '99

27 May '99

Currently, the RIPE whois server returns a result from a single-source (RIPE) search by default. One needs to pass a -a flag in order to obtain multiple-source returns. Because of this behaviour in conjunction with the necessity to allow a "defaulted" query to return inetnums, the architecture of the database is limited to a single source. For those organisations who may wish to run their own registry and participate in mirroring, this poses a considerable issue. I propose that the behaviour be modified so that the default would be to return a single-match first-hit from multiple-source search. That is, a query will return only one result but it will search through the source search order and return the first match it finds rather than simply stopping at the RIPEdb. -- /*====================[ Jake Khuon <khuon(a)GCtr.Net> ]======================+ | Network Statistics Engineer, NSM/Net-Eng /~ |2 () |\| ~|~ | @ |2 | | VOX: +1(408)328-4828 Fax: +1(408)328-4806 _/~ G L & B A L C E N T E R | +============[ 1154 East Arques Avenue, Sunnyvale, CA 94086 ]============*/

1 0