February 2002 - db-wg - mailman.ripe.net

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

17 May '18

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

2 2

Flap Viewer
by Fabrizio Lombardozzi 02 Apr '02

02 Apr '02

Hi ris-users, my name is Fabrizio Lombardozzi, I've developed a system to monitor inter-AS routing instabilities (route flaps) at the Computer Networks Research Group, of the Roma III University, Italy. The system retrieves BGP data from RIS, and produces interactive graphs and animations using a graph drawing engine and intuitive morphing animations, with a reasonably friendly web graphic user interface (it's an applet). I will be grateful if you could give me some comments and hopefully suggestions. At the url http://www.dia.uniroma3.it/~compunet/ you will find detailed instructions to start the applet and also a gallery with screenshots and animations. Thanks in Advance Fabrizio

2 2

RIPE Whois Server version 3.1.0
by RIPE Database Administration 26 Feb '02

26 Feb '02

Dear Colleagues, [Apologies for multiple messages]. The RIPE NCC is pleased to announce the release of Version 3.1.0 of the RIPE Whois server. This software is compliant with both RPSL (RFC-2622) and RPS-Security (RFC-2725). This release adds several user-visible improvements: - New status type for inetnum objects: LIR-PARTITIONED. - New object type, irt, and associated new attributes: "irt:", "mnt-irt:", "irt-nfy:", "signature:", and "encryption:". The RPSL parsing has been totally rewritten. The new mechanism makes adding new classes and attributes much easier. Additionally, many, many bugs have been fixed. Detailed release notes can be found at the following URL: ftp://ftp.ripe.net/ripe/dbase/software/RELEASE-NOTES-3.1.0 You can download this release by anonymous FTP from the following URL: ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-3.1.0.tar.gz If you do not intend to use the cross-reference files or prefer to build them yourself via "make docs", you can download the source without these files by anonymous FTP from the following URL: ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-3.1.0-nocxref.tar.gz A diff for the 3.1.0 "nocxref" version is also available, if you already have 3.0.2 and would prefer to patch that version instead, at the following URL: ftp://ftp.ripe.net/ripe/dbase/software/patch-ripe-dbase-3.0.2-nocxref-3.1.0… If you have any more questions, please don't hesitate to contact <ripe-dbm(a)ripe.net>. -- Shane Kerr RIPE NCC

2 1

New Document available: RIPE-238
by RIPE NCC Document Announcement Service 13 Feb '02

13 Feb '02

[Apologies for duplicate mails] New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store. Ref: ripe-238 Title: RIPE Database Reference Manual Author: Joao Luis Silva Damas, Andrei Robachevsky Date: 6 February 2002 Format: PS=277479 TXT=124400 Obsoletes: ripe-223 Obsoleted by: Updates: Updated by: Short content description ------------------------- This document is an updated version of the "RIPE Database reference manual" (ripe-223). It describes the functionality of version 3.0 of the RIPE Database that uses the Routing Policy Specification Language to represent all Database objects. It also implements the Routing Policy System Security (RPSS) to provide authorisation mechanisms to enable a higher level of security for Internet Routing Registries (IRR). Accessing the RIPE document store --------------------------------- The RIPE document store is available via anonymous FTP to ftp.ripe.net, in the directory ripe/docs. The URLs for the new documents on the FTP-server are: ftp://ftp.ripe.net/ripe/docs/ripe-238.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-238.txt plain text version You can also access the RIPE documents in HTML format via WWW. The RIPE Database reference manual is available from the WWW at the following URL: http://www.ripe.net/ripe/docs/databaseref-manual.html

1 0

Re: Missing mnt-routes in ALLOCATED PA objects
by RIPE Database Administration 12 Feb '02

12 Feb '02

Dear Karsten, Please see Sabrina Waschke's message regarding the issue: http://www.ripe.net/ripe/mail-archives/db-wg/20010701-20020101/msg00099.html If you have any more questions, please don't hesitate to contact <ripe-dbm(a)ripe.net>. Regards, Engin Gunduz ____________________________ RIPE Database Administration. Karsten Koepp wrote: >Hi all, > >already twice customers of us were not able to update route >records, because RIPE had not included mnt-routes (and mnt-lower) >lines into the inetnum object when allocating a block. >The blocks where we experienced the problem were allocated >in 1996: inetnum: 193.203.96.0 - 193.203.127.255 >and 1999: inetnum: 212.95.64.0 - 212.95.95.255 > >This is not an easy to understand problem for small ISPs dealing >with route objects only now and then. To solve this problem it is >necessary that LIRs send the inetnum object to be updated to >hostmaster(a)ripe.net and RIPE update the object with RIPE-NCC-HM-MNT. >Only then the ISP can update their route records. > >Question: >- Is there a reason for not existing mnt-lower and mnt-routes lines? >- If not, can RIPE update all affected inetnums in an automatic manner? > >This would really help a lot, because manual updates create a lot of >consultancy need from upstream providers (us in this case) and, I guess, >a considerable workload on the RIPE hostmaster team. > >Regards Karsten > >------------------------------------------------------------- >Karsten Koepp >IP Network Planning

1 0

Missing mnt-routes in ALLOCATED PA objects
by Koepp, Karsten 11 Feb '02

11 Feb '02

Hi all, already twice customers of us were not able to update route records, because RIPE had not included mnt-routes (and mnt-lower) lines into the inetnum object when allocating a block. The blocks where we experienced the problem were allocated in 1996: inetnum: 193.203.96.0 - 193.203.127.255 and 1999: inetnum: 212.95.64.0 - 212.95.95.255 This is not an easy to understand problem for small ISPs dealing with route objects only now and then. To solve this problem it is necessary that LIRs send the inetnum object to be updated to hostmaster(a)ripe.net and RIPE update the object with RIPE-NCC-HM-MNT. Only then the ISP can update their route records. Question: - Is there a reason for not existing mnt-lower and mnt-routes lines? - If not, can RIPE update all affected inetnums in an automatic manner? This would really help a lot, because manual updates create a lot of consultancy need from upstream providers (us in this case) and, I guess, a considerable workload on the RIPE hostmaster team. Regards Karsten ------------------------------------------------------------- Karsten Koepp IP Network Planning Lambdanet Communications GmbH (AS13237) Guenther-Wagner-Allee 13 D-30177 Hannover (Germany) Phone +49 (0)511 / 84 88 - 12 55 Fax +49 (0)511 / 84 88 - 12 59 Mobile +49 (0)178 / 3 62 - 12 55 mailto:Karsten.Koepp@lambdanet.net News & Facts on our Website: www.lambdanet.net -------------------------------------------------------------

2 1

RIPE DB down for updates?
by Daniel Roesen 10 Feb '02

10 Feb '02

Hi, http://www.ripe.net/ripencc/pub-services/db/mrtg/whois.html it looks like the update processing is halted since yesterday evening... Best regards, Daniel

2 1

New RIPE Database features
by Andrei Robachevsky 07 Feb '02

07 Feb '02

Dear colleagues, [ Apologies for multiple messages ] The new features of the RIPE Database requested by the community are now available in "beta version" on our TEST whois server (http://www.ripe.net/ripencc/pub-services/db/testdb.html). The new features are: - the "irt" object (please see my previous announcement at http://www/ripe/mail-archives/db-wg/current/msg00012.html) - the new "status:" value of the inetnum object "LIR-PARTITIONED PA/PI" (please see the original proposal at http://www/ripe/mail-archives/db-wg/20010701-20020101/msg00090.html). You may try these features by - sending your updates to test-dbm(a)ripe.net; - querying the test-whois.ripe.net, port 43. The new version of the software is under heavy testing now and will be put into production shortly after the RIPE meeting. Your comments are appreciated. You may contact the development team directly at dbrip(a)ripe.net. Best regards, Andrei Robachevsky DB Group Manager RIPE NCC

2 4