April 1999 - db-wg - mailman.ripe.net

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

16 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

1. Draft, proposed agenda DB-WG meeting RIPE-33 @ Vienna
by Wilfried Woeber, UniVie/ACOnet 23 Apr '99

23 Apr '99

Dear WG participants, dear WG-Chairs, attached please find a very preliminary agenda draft for the DB-WG meeting in Vienna in May. Any comments and proposals for modification are very much appreciated. Looking forward to see you in Vienna, 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 -------------------------------------------------------------------------- Proposed Agenda for the Database Working Group Meeting RIPE-33, May 1999, Vienna, AT 1. Draft A. Administrative stuff (Wilfried Woeber, chair) - appointment of scribe - agenda bashing - review of action items B. RIPE DB, operational update (RIPE NCC) - statistics, performance, changes, most recent mod.s - RPSL migration update, usage - current status of PGP deployment D. DB SW Re-implementation (RIPE NCC) - progress, milestones/roadmap, deployment, documentation - operational aspects, mirrors, clients - proposal to *not* migrate obsoleted objects and attributes . dom-prefix . others? E. I-D draft-ietf-rps-auth-??, -rps-dist-?? (??) - RIPE region requirements/comments - any progress X. IETF report(s) Y. Input from other WGs - t.b.d. Z. AOB ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ WW, 23-APR-1999 15:03:27

1 0

Adding nic handles to contact objects without one (72 chars/line)
by Joao Luis Silva Damas 19 Apr '99

19 Apr '99

Thou shall not send vi docs directly on a mail! At people's request here goes the mail again with sorter lines. Regards, Joao ------- Include message ------ Dear all, During the month of February the RIPE NCC, at the RIPE Database working group's request after the RIPE 32 meeting in Amsterdam, put out a proposal to add automatically generated nic handles to existing person objects that do not currently have one. Some other unrelated issues have caused me to not follow this up appropriately. I am sorry for that. In order to resume (and hopefully swiftly conclude) this issue, I will use the rest of this message to summarize the state of discussions. I would like to ask for a 10 day discussion period after which I will summarize the conclusion to the list and have the Database group take whatever action is agreed to. Summary: The initial proposal called just for the addition of an automatically generated nic handle to person and role objects which currently do not have one. This would be done using the same automatic procedure used by the Database software when a user request an AUTO nic handle. That is, the database takes up to 4 initials from the name, looks for the highest exisiting number of a nic handle in the sequence of nic handles with the same initials, generates a new number and adds the suffix "-RIPE". Input received discussed if we should use the opportunity and try to modify some database objects that reference person and role objects by name instead of nic handle as is required now in the RIPE Database. These are two separate issues. The first one could be approved without the second one. The first one alone brings old objects up to date to current specifications, simplifies the prorammers life and enables further steps to increase the DB's consistency. In my personal opinion it is a Good Thing. The main advantage of the second part is that: - References by nic handle are less ambiguous than references by name since the DB ensures that there are no duplicate nic handles whereas there is no reason why two persons can't have the same name. (Note: currently there are around 30 duplicate nic handles in the RIPE DB due to legacy objects from the past and bugs in past releases of the software. This problem is being addressed in the context of the RIPE DB consistency project. There will be an extensive report on the progress of this project in the coming RIPE meeting in Vienna). Doing this doesn't solve all the problems, naturally, and may have some problems as itemized below: - If the reference by name is to a name for which more than one object exists then there is an ambiguity that can't be handled automatically. The solution to this requires intervention by the referencing object's owner. This will be handled by the DB consistency project. - If there is no object with the referenced name then the referencing object is at least partially orphaned. This issue will also be addressed by the DB consistency project and may eventually need further policy decisions in the future, to be discussed by the community. - There is a chance that a person/role object with a refenced name exists and is unique but is not the one that created the referencing object. Eg. if I created an inetnum object in 1991 but then deleted my person object and then my twin ghost registered in the DB and created some new objects: should the original inetnum object (still in the database) be linked to my twin ghost (who probably doesn't know anything about it)? If this issue is seen as a heavy one then no name references can be modified to references by NIC handle automatically, unless an exhaustive search of the DB update logs is performed (and even then, there is no guaranteed result). I think this summarizes the state of affairs. Please give your input as soon as possible so that a conclusion can be reached. If possible, address the original and the extension proposal separately. Thanks, Joao Damas RIPE DB Group Manager RIPE NCC

3 2

Re: Objects to deprecate (OSI dom-prefix)
by Wilfried Woeber, UniVie/ACOnet 16 Apr '99

16 Apr '99

Wearing my plain DB user hat, >the RIPE NCC hereby requests from the RIPE community to consider NOT >to support the Domain-prefix object in the new RIPE DB code currently >under development. >This would mean not writing the code to support the object and dump the data >in the transition to the new code (still a few months away). I fully support this proposal. 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

Objects to deprecate (OSI dom-prefix)
by Joao Luis Silva Damas 16 Apr '99

16 Apr '99

Dear all, the RIPE NCC hereby requests from the RIPE community to consider NOT to support the Domain-prefix object in the new RIPE DB code currently under development. This would mean not writing the code to support the object and dump the data in the transition to the new code (still a few months away). This object is intented to store OSI CLNS prefixes and has seen little use. Currently there are 6 objects of this type. The most current update took place in May 1994. The prefixes stored right now are: 39.528f.1100 39.756f.1111 39.756f 39.250f 39.250f.0000.02 39.276f.3100 in case the owners want to inspect them and check their use :-) Best regards, Joao Damas RIPE NCC

2 1

2 digit years in the RIPE DB (Y2K)
by Joao Luis Silva Damas 16 Apr '99

16 Apr '99

Dear all, at the last RIPE meeting the Database Working group asked the RIPE NCC to propose to the community a rewrite of all dates currently stored in the RIPE Database that are using two figures for the year as dates with four figures for the year. The RIPE DB software has already been modified to avoid problems with Y2K. Changing the date format would make things cleaner and not dependant on conventions for interpretation of dates. This simplifies software development both at the RIPE NCC and by users writing their own programs. This is a rather small change although it involves modification of user data and therefore we would like to open a comment period of 10 days to see if there any user concerns about the proposed change. Best regards, Joao Damas RIPE DB Group Manager RIPE NCC

1 0

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

16 Apr '99

Dear all, During the month of February the RIPE NCC, at the RIPE Database working group's request after the RIPE 32 meeting in Amsterdam, put out a proposal to add automatically generated nic handles to existing person objects that do not currently have one. Some other unrelated issues have caused me to not follow this up appropriately. I am sorry for that. In order to resume (and hopefully swiftly conclude) this issue, I will use the rest of this message to summarize the state of discussions. I would like to ask for a 10 day discussion period after which I will summarize the conclusion to the list and have the Database group take whatever action is agreed to. Summary: The initial proposal called just for the addition of an automatically generated nic handle to person and role objects which currently do not have one. This would be done using the same automatic procedure used by the Database software when a user request an AUTO nic handle. That is, the database takes up to 4 initials from the name, looks for the highest exisiting number of a nic handle in the sequence of nic handles with the same initials, generates a new number and adds the suffix "-RIPE". Input received discussed if we should use the opportunity and try to modify some database objects that reference person and role objects by name instead of nic handle as is required now in the RIPE Database. These are two separate issues. The first one could be approved without the second one. The first one alone brings old objects up to date to current specifications, simplifies the prorammers life and enables further steps to increase the DB's consistency. In my personal opinion it is a Good Thing. The main advantage of the second part is that: - References by nic handle are less ambiguous than references by name since the DB ensures that there are no duplicate nic handles whereas there is no reason why two persons can't have the same name. (Note: currently there are around 30 duplicate nic handles in the RIPE DB due to legacy objects from the past and bugs in past releases of the software. This problem is being addressed in the context of the RIPE DB consistency project. There will be an extensive report on the progress of this project in the coming RIPE meeting in Vienna). Doing this doesn't solve all the problems, naturally, and may have some problems as itemized below: - If the reference by name is to a name for which more than one object exists then there is an ambiguity that can't be handled automatically. The solution to this requires intervention by the referencing object's owner. This will be handled by the DB consistency project. - If there is no object with the referenced name then the referencing object is at least partially orphaned. This issue will also be addressed by the DB consistency project and may eventually need further policy decisions in the future, to be discussed by the community. - There is a chance that a person/role object with a refenced name exists and is unique but is not the one that created the referencing object. Eg. if I created an inetnum object in 1991 but then deleted my person object and then my twin ghost registered in the DB and created some new objects: should the original inetnum object (still in the database) be linked to my twin ghost (who probably doesn't know anything about it)? If this issue is seen as a heavy one then no name references can be modified to references by NIC handle automatically, unless an exhaustive search of the DB update logs is performed (and even then, there is no guaranteed result). I think summarizes the state of affairs. Please give your input as soon as possible so that a conclusion can be reached. If possible, address the original and the extension proposal separately. Thanks, Joao Damas RIPE DB Group Manager RIPE NCC

1 0

ANNOUNCEMENT: RELEASE OF IRRd-1.3-Beta
by Gerald Andrew Winters 09 Apr '99

09 Apr '99

Merit Network, Inc. is pleased to announce the first production-quality release of the Internet Routing Registry Daemon (IRRd). Source code, manuals and binaries are now *freely* available from: http://www.irrd.net IRRd is an optimized, multi-threaded IRR database server with support for a complete set of RIPE-181 registry services, including: whois queries, an interactive Cisco-like configuration/management interface, remote registry mirroring, email/tool object submissions, and password/PGP. IRRd also includes private database support, security access lists, and an expanded query language. We encourage providers actively using the RADB (and other IRR registries) in production for the generation of router access lists/config files to run a local, mirroring copy of the IRRd server. IRRd has served as the production RADB routing registry daemon since early February. Note: Complete RPSL support will be available with IRRd-2.0 (beta release scheduled for late May). If you are interested in serving as an alpha tester for IRRd-2.0 please send email to irrd-support(a)irrd.net. -- The IRRd Development Team

1 0